[Bug 732851] New: kernel panic
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c0
Summary: kernel panic
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@forge.provo.novell.com
ReportedBy: antoine.mechelynck@belgacom.net
QAContact: qa@suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111125
Firefox/11.0a1 SeaMonkey/2.8a1
I was typing a post in a forum when suddenly the kernel panicked. This is the
2nd panic I get since installing oS 12.1. This time I tried to copy what I saw
on the console before rebooting (see below, "Additional information"). Maybe
other stuff went by just before, too fast for me to write them down. If there
is any way to get more information after rebooting, just tell me where.
Reproducible: Sometimes
Steps to Reproduce:
0. Do nothing out of the ordinary.
Actual Results:
kernel panic
Expected Results:
don't panic
Additional information: what I copied (by hand) from /dev/tty1 after my
keyboard lights had gone blinking:
Kernel panic - not syncing: Fatal exception in interrupt:
Pid:3962, comm: plugin-containe Tainted: G D 3.1.0-1.2-desktop #1
Call trace:
[<ffffffff810043fa>] dump_trace+0xaa/0x260
[<ffffffff81582a4a>] dump_stack+0x69/0x6f
[<ffffffff815851d1>] panic+0xa4/0x1b8
[<ffffffff8159d62f>] oops_end+0xef/0xf0
[<ffffffff8159f662>] do_page_fault+0x402/0x530
[<ffffffff8159c8b5>] page_fault+0x25/0x30
[<ffffffff8100476a>] show_stack_log_eol+0x16a/0x1e0
[<ffffffff810048c3>] show_registers+0xe3/0x2d0
[<ffffffff8159d6eb>] __die+0xbb/0x100
[<ffffffff81005c10>] die+0x40/0x90
[<ffffffff81003202>] do_double_fault+0x25/0x30
panic occurred, switching back to text console
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0
Pid: 3598 comm: seamonkey-bin Tainted: G D 3.1.0-1.2-desktop #1
[<ffffffff810043fa>] dump_trace+0xaa/0x260
[<ffffffff81582a4a>] dump_stack+0x69/0x6f
[<ffffffff815851d1>] panic+0xa4/0x1b8
[<ffffffff810c3706>] watchdog_overflow_callback+0xb6/0xc0
[
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c1
Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c2
--- Comment #2 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c
Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c3
Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c4
--- Comment #4 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c5
--- Comment #5 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c6
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c7
--- Comment #7 from Tony Mechelynck
The one you've attached is a secondary oops (tainted D). Can you configure kdump (yast kdump) and boot with oops=panic? That will cause the system to crash dump when it fails rather than display the secondary oops it is now.
How do you want kdump to be configured? The "System → Kernel Kdump" section in yast2 has so many options (on five pages: start-up, dump filtering, dump target, email notification, expert settings) that I feel lost. Otherwise I'll reconfigure grub, adding oops=panic on the kernel command-line so I won't forget to boot with it. -- 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=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c8
Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c9
--- Comment #9 from Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c10
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c11
--- Comment #11 from Tony Mechelynck
Configure Yast2 Kdump by unchecking pretty much everything, like in the attached photo.
Done. It was the opposite, with everything ticked and "compressed" dump. On the previous page, "Kdump memory" is set to 128 MB: is that OK?
It's also worthwhile to update makedumpfile to the version from Factory (or Kernel:kdump).
After I send this comment, I'll start hunting for that. 'makedumpfile --dump-dmesg vmcore' will dump the full log. On restart from the panic, right? -- 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=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c12
--- Comment #12 from Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=732851
https://bugzilla.novell.com/show_bug.cgi?id=732851#c13
Tony Mechelynck
participants (1)
-
bugzilla_noreply@novell.com