Hello,

I just updated my Debian stretch system using apt-get dist-upgrade to stretch
9.5, which uses the new 4.9.0-7 kernel. On amd64, the kernel comes from the
linux-image-4.9.0-7-amd64_4.9.110-1_amd64.deb binary package. It was just
released about a week ago. The timestamp on the .deb file is July 6, 2018.

I am running stretch on a Haswell Intel 4590S processor and ASROCK B85M Pro4
motherboard as a Dom0 on the up-to-date Xen 4.8 hyervisor for stretch, or as
a DomU on the same machine and hypervisor for stretch. In both cases, with
the new 4.9.0-7 amd64 kernel, the system enters an endless cycle of kernel
panic -> reboot -> kernel panic -> reboot ...

I also have a Debian stretch 32-bit Xen DomU system and the new 4.9.0-7
i686-pae kernel boots the Debian 9.5 DomU normally on the same hardware.
Only the new amd64 kernel has the problem, not the new i686-pae kernel.

So to run the new Debian stretch 9.5 I need to set grub to boot the previously
working kernel, the up-to-date 4.9.0-6 version, for amd64. For i686-pae,
I can use the new 4.9.0-7 version of the kernel.

I captured a little bit of what was written to the xen console when the kernel
panics which is shown below.

Anyone else seen this?

Thanks,

Chuck

[    0.120071] dmi: Firmware registration failed.
[    1.176611] dmi-sysfs: dmi entry is absent.
[    1.189531] general protection fault: 0000 [#1] SMP
[    1.189538] Modules linked in:
[    1.189543] CPU: 1 PID: 1 Comm: init Not tainted 4.9.0-7-amd64 #1 Debian 4.9.110-1
[    1.189549] task: ffff8800bac08040 task.stack: ffffc90040628000
[    1.189553] RIP: e030:[<ffffffff81614d4d>] [<ffffffff81614d4d>] ret_from_fork+0x2d/0x70
[    1.189562] RSP: e02b:ffffc9004062bf50  EFLAGS: 00010006
[    1.189565] RAX: 00000002dd603000 RBX: ffffffff816076d0 RCX: ffffea0002ebafdf [    1.189570] RDX: 0000000000000002 RSI: 0000000000000002 RDI: ffffc9004062bf58 [    1.189574] RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8800b7a76000 [    1.189579] R10: 8080808080808080 R11: fefefefefefefeff R12: 0000000000000000 [    1.189583] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [    1.189592] FS:  0000000000000000(0000) GS:ffff8800bbf00000(0000) knlGS:0000000000000000
[    1.189597] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.189601] CR2: 00007fffb09bdb79 CR3: 00000000b5602000 CR4: 0000000000042660
[    1.189607] Stack:
[    1.189609]  0000000000000000 0000000000000000 0000000000000000 0000000000000000 [    1.189617]  0000000000000000 0000000000000000 0000000000000000 0000000000000000 [    1.189625]  0000000000000000 0000000000000000 0000000000000000 0000000000000000
[    1.189635] Call Trace:
[    1.189640] Code: c7 e8 b8 fe a8 ff 48 85 db 75 2f 48 89 e7 e8 5b ed 9e ff 50 90 0f 20 d8 65 48 0b 04 25 e0 02 01 00 78 08 65 88 04 25 e7 02 01 00 <0f> 22 d8 58 66 0f 1f 44 00 00 e9 c1 07 00 00 4c 89 e7 eb 11 e8
[    1.189708] RIP  [<ffffffff81614d4d>] ret_from_fork+0x2d/0x70
[    1.189714]  RSP <ffffc9004062bf50>
[    1.189719] ---[ end trace ddfc12432c0049a4 ]---
[    1.189798] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    1.189798]
[    1.189811] Kernel Offset: disabled

Reply via email to