http://bugzilla.novell.com/show_bug.cgi?id=628631 http://bugzilla.novell.com/show_bug.cgi?id=628631#c0 Summary: kernel oops on openSUSE 11.2 after killing USB process Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: r.ems@gmx.net QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=380798) --> (http://bugzilla.novell.com/attachment.cgi?id=380798) screenshot of /dev/tty10 after the Oops User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 Hi all, this is on an openSUSE 11.2, 64 bit, Supermicro X8DTH mainboard, with 2 x Intel Xeon E5530 @ 2.40GHz CPUs and 12 GB memory. The server is in a cluster room and one of it's functions is to monitor the room's temperature. This is done by a sensor (from MessPC.de) attached to the USB port. This sensor is being read by two processes, one started by NAGIOS every two minutes, and a second one logging the temperature data to a file every 30s. About once a week the 2nd process logging to the file hangs and no more data can be read from the USB port. Killing this process makes the system Oops and, since nmi_watchdog is set to 1, it reboots. This happened already several times. We were using kernel-default from openSUSE 11.2, updated later a newer kernel from http://download.opensuse.org/repositories/Kernel:/openSUSE-11.2/openSUSE_11...., last one with the Oops from today was kernel-default-2.6.31.14-2.1.x86_64, and now we updated to today's one, kernel-default-2.6.31.14-2.1.x86_64. There is nothing logged in /var/log/messages. On a remote IP over KVM console showing /dev/tty10 I did a screenshot of the last messages there before rebooting, see attached file. Reproducible: Didn't try Steps to Reproduce: 1. Wait for temperature monitor to fail. 2. Kill usb port reading process. 3. System oops and reboot. I will try to reproduce it starting two infinite loops reading from the USB port in parallel, since I *guess* it could be a race condition from the two processes trying to read data from the same USB port. Actual Results: Oops and reboot. Expected Results: No Oops. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.