[opensuse-kernel] 42.2: panic @ [0.2.64013] with kernel-default-4.4.46-11.1
DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 Leftover inexact backtrace: ... Kernel panic - not syncing: Attempted to kill init! exitcode=0x00 I removed and reinstalled 4.4.46 twice after initial installation. Same result each time. The panic message can be discovered only by leaving vga=791 off cmdline. With it, screen stays black and reset button is required to recover. Kernels 4.4.27 & 4.4.36 still work as expected. Fresh kernel on 42.1 on same PC also works as expected. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
On 02/16/2017, 11:34 AM, Felix Miata wrote:
DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 Leftover inexact backtrace: ... Kernel panic - not syncing: Attempted to kill init! exitcode=0x00
systemd crashed or cannot be run?
I removed and reinstalled 4.4.46 twice after initial installation. Same result each time.
The panic message can be discovered only by leaving vga=791 off cmdline. With it, screen stays black and reset button is required to recover. Kernels 4.4.27 & 4.4.36 still work as expected.
Could you boot without quiet and vga=791 options and with "debug" to see what actually happens? The most important are lines before the unwinder got stuck. thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Jiri Slaby composed on 2017-02-16 11:39 (UTC+0100):
Felix Miata wrote:
DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 Leftover inexact backtrace: ... Kernel panic - not syncing: Attempted to kill init! exitcode=0x00
systemd crashed or cannot be run?
Dunno what the difference is when the only things that work are the power button and the reset button. :-p NUM does nothing, and no route to host attempting remote connect.
I removed and reinstalled 4.4.46 twice after initial installation. Same result each time.
The panic message can be discovered only by leaving vga=791 off cmdline. With it, screen stays black and reset button is required to recover. Kernels 4.4.27 & 4.4.36 still work as expected.
Could you boot without quiet and vga=791 options and with "debug" to see what actually happens? The most important are lines before the unwinder got stuck.
I never have quiet. :-D
[top of screen]
[ 0.264000] [
On 02/16/2017, 11:59 AM, Felix Miata wrote:
[top of screen]
Doesn't shift-page-up work here? Anyway, it is worth a bug report. Care to create one? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Jiri Slaby composed on 2017-02-16 13:02 (UTC-0100):
Felix Miata wrote:
[top of screen]
Doesn't shift-page-up work here?
No keyboard response whatsoever.
Anyway, it is worth a bug report. Care to create one?
https://bugzilla.opensuse.org/show_bug.cgi?id=1025655 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (2)
-
Felix Miata -
Jiri Slaby