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

2018-07-14 Thread 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

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

2018-07-14 Thread 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

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

2018-07-14 Thread 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%

Processed: reassign 898187 to src:linux, reassign 899356 to src:linux

2018-07-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 898187 src:linux Bug #898187 [linux-image-4.9.0-6-amd64] linux-image-4.9.0-6-amd64: irq affinity spreading for nvme not activated Warning: Unknown package 'linux-image-4.9.0-6-amd64' Bug reassigned from package

Processed: reassign 903776 to src:linux

2018-07-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 903776 src:linux 4.9.110-1 Bug #903776 [linux-image-4.9.0-7-amd64] Kernel 4.9.110-1 sit: non-ECT warnings Bug reassigned from package 'linux-image-4.9.0-7-amd64' to 'src:linux'. No longer marked as found in versions linux/4.9.110-1.

Bug#903778: linux-image-amd64-signed-template: copyright file missing (policy 12.5)

2018-07-14 Thread Andreas Beckmann
Package: linux-image-amd64-signed-template Version: 4.18~rc4-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5:

Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings

2018-07-14 Thread Thomas Leuxner
Package: linux-image-4.9.0-7-amd64 Version: 4.9.110-1 Hi, after upgrading today I started seeing these: Jul 14 12:46:18 edi kernel: [ 29.601249] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver Jul 14 12:46:24 edi kernel: [ 35.920488] sit: non-ECT from 238.163.0.0 with TOS=0x2 Jul 14

Bug#903767: Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8

2018-07-14 Thread Andy Smith
Also same symptoms in a PV guest under Xen 4.10. Works if booted on previous kernel. Also prevents installation of stable using the netboot image at e.g. Cheers, Andy

Bug#903767: Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8

2018-07-14 Thread Michael J. Redd
This also apparently affects at least PV guests. Upgrading a PV domU to kernel 4.9.110-1 and rebooting yields the following output via xl's console: Loading Linux 4.9.0-6-amd64 ... Loading Linux 4.9.0-7-amd64 ... Loading initial ramdisk ...   [ vmlinuz-4.9.0-7- amd6  2.69MiB  66%  1.67MiB/s ] [ 

Processed: reassign 903767 to src:linux

2018-07-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 903767 src:linux 4.9.110-1 Bug #903767 [linux-image-4.9.0-7-amd64] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8 Bug reassigned from package 'linux-image-4.9.0-7-amd64' to 'src:linux'. No longer marked as found in versions

Bug#903767: Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8

2018-07-14 Thread Michael J. Redd
Package: linux-image-4.9.0-7-amd64 Version: 4.9.110-1 Description: After installing the latest Stretch kernel, 4.9.110-1, on a server running Xen Hypervisor 4.8, bootstrapping the kernel fails. GRUB loads the hypervisor as normal, which then attempts to load the Dom0 kernel. Once