Bug 25309 - [aic7xxx] NMI watchdog detected LOCKUP on CPU0
[aic7xxx] NMI watchdog detected LOCKUP on CPU0
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i686 Linux
high Severity high
: ---
: ---
Assigned To: Doug Ledford
Brock Organ
Florence RC-2
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-30 11:41 EST by Mark Rusk
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-07 05:24:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screen shot of OOPS (308.66 KB, image/jpeg)
2001-01-30 17:15 EST, Mark Rusk
no flags Details

  None (edit)
Description Mark Rusk 2001-01-30 11:41:38 EST
After installing Beta 3 on a Dell 1400 (dual 933mhz) the systems OOPS when
rebooting into the SMP kernel after ACPI initialization with a "NMI
detected LOCKUP on CPU0".  When the OOPS output is re-directed to the
serial port for capture, the system boots SMP OK
Comment 1 Mark Rusk 2001-01-30 12:45:16 EST
Actual message is "NMI watchdog detected lockup on CPU0"
Comment 2 Arjan van de Ven 2001-01-30 14:25:16 EST
There has been a huge patch to ACPI accepted by Linus after the beta-kernel
was made. 
Comment 3 Glen Foster 2001-01-30 15:44:40 EST
This defect is considered MUST-FIX for Florence Release-Candidate #2
Comment 4 Mark Rusk 2001-01-30 17:15:44 EST
Created attachment 8520 [details]
screen shot of OOPS
Comment 5 Arjan van de Ven 2001-02-07 05:23:57 EST
I get this one as well, it's not ACPI that is the blame but
the aic7xxx driver! Once I remove that driver from the initrd,
all is well.
Comment 6 Doug Ledford 2001-02-07 06:02:12 EST
This is related to the 6.0.8BETA Adaptec aic7xxx driver in Beta 3.  It should be
fixed in the 6.1.0 Adaptec driver as well as by my 5.2.2 aic7xxx driver (which
didn't have the problem to begin with), both of which are in the latest kernel
CVS tree.

Note You need to log in before you can comment on or make changes to this bug.