[Bug 340136] New: suspend to disk fails repeatedly, kernel freeze/panic
https://bugzilla.novell.com/show_bug.cgi?id=340136 Summary: suspend to disk fails repeatedly, kernel freeze/panic Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: qa@suse.de Found By: --- The machine was able to suspend to disk (and resume) using the same configuration. Yesterday however, when suspending, the suspend was aborted with no user-visible message. Looking in syslog I found: kernel: Stopping user space processes timed out after 20 seconds (39 tasks refusing to freeze): kernel: udevd syslog-ng[2322]: last message repeated 38 times kernel: Restarting tasks ... done. kernel: swsusp: Basic memory bitmaps freed acpid: client connected from 2650[0:0] acpid: 1 client rule loaded gnome-power-manager: (wiu09524) Rechner wird aufgeweckt When re-trying it, the same happened. At that time I thought the time limit might be too short, so I left the computer on over night. Then, this morning the machine suddenly froze (keyboard LEDs blinking) with no messages in syslog found. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |Ulrich.Windl@rz.uni-regensburg.de --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2007-11-09 11:27:37 MST --- Do you have the ability to set up a serial console for this machine? The blinking keyboard LEDs mean that a panic has occured. A serial console will let you capture the panic. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c2 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|Ulrich.Windl@rz.uni-regensburg.de | --- Comment #2 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2007-11-12 01:03:52 MST --- Serial Console: Difficult. But I've installed the most recent kernel update on Friday anyway, so we'll see... (I always thought that before the introduction of the blinking LED on panic I could use the keyboard to switch consoles, possibly seeing what syslog wrote to tty10...) Couldn't the panic routine save the kernel message buffer somewhere? HP-UX can do that for years, so the OS saves it (crash dump) on next boot. Even Windows/XP can do something like that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c3 --- Comment #3 from Jeff Mahoney <jeffm@novell.com> 2007-11-12 09:32:26 MST --- Yes, our kernels do support crash dumping, but there's a bit of configuration that needs to happen first. Older Unices had the advantage that they controlled the hardware and firmware as well, so that made crash dumping quite a bit easier to do that it is with commodity hardware. :) Check out kexec/kdump. There's even a yast module for configuring it (yast2-kdump). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c4 --- Comment #4 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2007-11-14 06:06:08 MST --- Maybe I should really do it: With a new kernel (2.6.22.12-0.1-default) the machine got a panic again. Not really a trace in syslog, but I noticed several of these messages: kernel: evdev: no more free evdev devices kernel: input: failed to attach handler evdev to device input81, error: -23 (I'm using an USB KVM switch to toggle between two computers; maybe 81 switches are too many... ;-) ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136 Jiri Kosina <jkosina@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c6 Jiri Kosina <jkosina@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |Ulrich.Windl@rz.uni-regensburg.de --- Comment #6 from Jiri Kosina <jkosina@novell.com> 2007-11-14 09:06:19 MST --- Could you please verify whether you are able to reproduce the bug with kernel of the day for HEAD? It can be obtained from ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c7 --- Comment #7 from Jiri Kosina <jkosina@novell.com> 2007-11-14 09:19:12 MST --- This should however definitely not be the reason for kernel panic, that is almost certainly a separate issue -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c8 --- Comment #8 from Jeff Mahoney <jeffm@novell.com> 2007-11-14 09:27:13 MST --- I wasn't sure if it could cause it or perhaps cause something to fail that would then cause a panic. Either way, it wouldn't hurt to take it out of the mix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c9 --- Comment #9 from Jiri Kosina <jkosina@novell.com> 2007-11-27 04:37:15 MST --- Ulrich, were you able to reproduce the bug with HEAD kotd? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c10 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Ulrich.Windl@rz.uni-regensburg.de | --- Comment #10 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2007-11-27 08:31:48 MST --- As the current kernel (kernel-default-2.6.22.12-0.1, installed Fr 09 Nov 2007 09:53:37 CET) did not show the problem (since using it), I did not try a more recent one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340136#c11 Jiri Kosina <jkosina@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #11 from Jiri Kosina <jkosina@novell.com> 2007-11-27 08:46:54 MST --- Closing the bug then. Please reopen if the bug strikes again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com