Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 27393 - NMI Watchdog detected LOCKUP on CPU1 -- mouse dies
NMI Watchdog detected LOCKUP on CPU1 -- mouse dies
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Pete Zaitcev
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-02-13 10:28 EST by Chris Runge
Modified: 2005-10-31 17:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-19 10:40:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Runge 2001-02-13 10:28:58 EST

if I start X, then exit or switch to VC I see this:

NMI Watchdog detected LOCKUP on CPU1, registers:
CPU:    1
EIP:    0010:[<e0890c16>]
EFLAGS: 00000056
eax: 00000000   ebx: 00000020   ecx: 00000002   edx: 00000002
esi: 00000006   edi: 00000001   ebp: 00000003   esp: de229e7c
ds: 0018   es: 0018   ss: 0018
Process gpm (pid: 860, stackpage=de229000)

The mouse then dies, both under X and under a VC. service gpm restart does
not revive it; I must reboot. 

The system :

SuperMicro 370DE6 motherboard (based on ServerWorks III HE-SL chipset)
2x 1Ghz Pentium III
512 MB RAM
MS Intellimouse Explorer connected to USB port

cat'ing /proc/interrupts displays a non 0 value for NMI

Marking as high since a reboot is req'd to get the mouse to work again
Comment 1 Glen Foster 2001-02-13 15:22:30 EST
This defect is considered MUST-FIX for Florence Gold release
Comment 2 Michael K. Johnson 2001-02-13 19:49:40 EST
Please try the next kernel we release and see if it fixes the
problem.  If not, we need a decoded oops messages -- you need
to run the whole oops message through the ksymoops program so
that it is symbolically decoded.
Comment 3 Chris Runge 2001-02-15 11:30:04 EST
interesting.... I had a MS Force Feedback 2 joystick connected to one of the USB
ports in addition to the mouse. If I remove the joystick the problem appears to
go away.
Comment 4 Chris Runge 2001-02-15 11:33:53 EST
see 25849 for an example of how the joystick caused problems with Xconfigurator
Comment 5 Michael K. Johnson 2001-02-15 12:07:07 EST
Nalin, does this resemble what you saw?
Comment 6 Michael K. Johnson 2001-02-20 12:17:21 EST
We still need that ksymoops output...
Comment 7 Nalin Dahyabhai 2001-02-20 12:25:15 EST
Yes, this resembles what I saw.  I've upgraded to a newer kernel since then, so
the fixed ksymoops wouldn't give you any useful information.  Will try to
reproduce again today.
Comment 8 Michael K. Johnson 2001-02-28 22:44:35 EST
Seems to resemble latest behavior in bug #23670
Comment 9 Pete Zaitcev 2001-03-05 18:52:08 EST
So, where is a meaningful oops report?

I do not have a joystick and everything
works fine without one (I have RIO-600
and floppy on the same chain).
I _suspect_ that something may be up with
having several HID devices, or a joystick
specifically. But I need solid information
before I can try fixing anything.

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