Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Logan Gunthorpe]

Just wanted to add a me too.

After upgrading a Xen hypervisor to 4.9.0-7-amd64 I see the same
infinite reboot loop as reported above.

As this box is a production server I downgraded back to 4.9.0-6 to fix
the issue for now.

Thanks,

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Gianluigi Tiesi]

Source: linux
Version: 4.9.110-1
Followup-For: Bug #903800

I have same problems but on dum0, server reboots forever, by adding
no reboot the screen goes black just after the hypervisor loads (instead of
reboot)

This happens on i7-2600 and i7-4770

4.9.0-6 worked fine

I've also upgraded bios but same results



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Luis Miguel Parra]

Hi,

I am having the same issue.
After upgrade to 4.9.0-7-amd64 from 4.9.0-6-amd64 my xen vm they stop
working.

I run xenserver 6.2 and as a temporal fix I just convert the VM to HVM from
PV

xe vm-param-set uuid=YOURVMUID HVM-boot-policy="BIOS order" PV-bootloader=""


So looks like running in Hardware-assisted Virtualization (HVM) helps

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Vincent Lefevre]

On 2018-07-15 04:27:39 +0100, Ben Hutchings wrote:
> On Sun, 2018-07-15 at 02:27 +0200, Vincent Lefevre wrote:
> > Package: src:linux
> > Version: 4.9.110-1
> > Severity: critical
> > Justification: breaks the whole system
> > 
> > After upgrade to Debian 9.5, I get a kernel panic with 4.9.0-7-amd64:
> [...]
> 
> Are you running it on Xen?

Yes.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Robby]

Hi,

I may be running into the same issue here, running Xen.

I say "may", because after I updated to Debian 9.5 and linux
4.9.0-7-amd64, the server/Dom0 did not come back up after a reboot, and
I had to request a manual reboot from datacenter staff. The staff did
not provide any more error details from the console other than that the
OS failed to boot. I also did not find anything useful or relevant in
logs, so I cannot provide more information.

They rebooted it into a rescue-mode for me to login and fix it, from
there I made grub boot Xen with the previous linux 4.9.0-6-amd64 kernel
and the system came back up normally.

The Xen virtual machines/DomUs themselves, however, do seem to run just
fine with linux 4.9.0-7-amd64.

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Ben Hutchings]

On Sun, 2018-07-15 at 02:27 +0200, Vincent Lefevre wrote:
> Package: src:linux
> Version: 4.9.110-1
> Severity: critical
> Justification: breaks the whole system
> 
> After upgrade to Debian 9.5, I get a kernel panic with 4.9.0-7-amd64:
[...]

Are you running it on Xen?

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that
there are so many of them.



signature.asc
Description: This is a digitally signed message part

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Vincent Lefevre]

Package: src:linux
Version: 4.9.110-1
Severity: critical
Justification: breaks the whole system

After upgrade to Debian 9.5, I get a kernel panic with 4.9.0-7-amd64:

Loading Linux 4.9.0-7-amd64 ...
Loading initial ramdisk ...
[0.00] tsc: Unable to calibrate against PIT 17.14MiB  100%  7.83MiB/s ]
[0.108076] cpu 0 spinlock event irq 1
[0.109159] NMI watchdog: disabled (cpu0): hardware events not enabled
[0.183214] cpu 1 spinlock event irq 13
[0.184264] cpu 2 spinlock event irq 20
[0.184635] cpu 3 spinlock event irq 27
[0.184635] cpu 4 spinlock event irq 34
[0.184635] cpu 5 spinlock event irq 41
[0.188556] cpu 6 spinlock event irq 48
[0.188556] cpu 7 spinlock event irq 55
[0.188575] cpu 8 spinlock event irq 62
[0.188575] cpu 9 spinlock event irq 69
[0.192561] cpu 10 spinlock event irq 76
[0.192561] cpu 11 spinlock event irq 83
[0.192562] cpu 12 spinlock event irq 90
[0.196098] cpu 13 spinlock event irq 97
[0.196564] cpu 14 spinlock event irq 104
[0.196564] cpu 15 spinlock event irq 111
[0.201020] Grant table initialized
[0.708216] dmi: Firmware registration failed.
[0.708728] PCI: System does not support PCI
[0.709146] PCI: System does not support PCI
[2.161040] dmi-sysfs: dmi entry is absent.
[2.161725] mce: Unable to init device /dev/mcelog (rc: -5)
[2.183556] general protection fault:  [#1] SMP
[2.183799] Modules linked in:
[2.183955] CPU: 0 PID: 1 Comm: init Not tainted 4.9.0-7-amd64 #1 Debian 
4.9.110-1
[2.184010] task: 88001e6a3040 task.stack: c900400cc000
[2.184010] RIP: e030:[]  [] 
ret_from_fork+0x2d/0x70
[2.184010] RSP: e02b:c900400cff50  EFLAGS: 00010006
[2.184010] RAX: 000c5cc9b000 RBX: 816076d0 RCX: ea794b1f
[2.184010] RDX: 0002 RSI: 0002 RDI: c900400cff58
[2.184010] RBP:  R08:  R09: 880003073000
[2.184010] R10: 8080808080808080 R11: fefefefefefefeff R12: 
[2.184010] R13:  R14:  R15: 
[2.184010] FS:  () GS:88001ea0() 
knlGS:
[2.184010] CS:  e033 DS:  ES:  CR0: 80050033
[2.184010] CR2: 7ffd02276609 CR3: 0309a000 CR4: 00042660
[2.184010] Stack:
[2.184010]     

[2.184010]     

[2.184010]     

[2.184010] Call Trace:
[2.184010] 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 
[2.184010] RIP  [] ret_from_fork+0x2d/0x70
[2.184010]  RSP 
[2.184010] ---[ end trace 4b76af717f0b50cf ]---
[2.190717] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[2.190717] 
[2.191083] Kernel Offset: disabled

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information

** Network interface configuration:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 155.133.131.76
netmask 255.255.255.0
gateway 155.133.131.254

** PCI devices:
not available

** USB devices:
not available


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.9.0-7-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.9.0-7-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.9.0-7-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.02~beta3-5
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-7-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn