Bug#903821:
On Fri, 2018-07-20 at 10:53 +0200, Wiebe Cazemier wrote: > Hi, > > Yesterday, it was already due to be installed on FTP. When is that? > Because of the delay, I caused our Xen server to get stuck into a > kernel panic reboot loop after upgrading and rebooting Jul 19 23:00 > UTC. It was actually during an upgrade from Debian 8 to 9 and I had > no older 4.9 kernel, so I'm now running one of the old 3.16 kernels. > > A fast release would be much appreciated. It's available in the "stretch-proposed-updates" suite. We will request adding it to the "stretch-updates" suite which is enabled by default. Note that you can work around this bug by adding "pti=off" to the kernel command line. This is safe to do in all Xen PV amd64 guests, because PTI is not needed and never used in this environment. Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot signature.asc Description: This is a digitally signed message part
Bug#903821:
Hi, Yesterday, it was already due to be installed on FTP. When is that? Because of the delay, I caused our Xen server to get stuck into a kernel panic reboot loop after upgrading and rebooting Jul 19 23:00 UTC. It was actually during an upgrade from Debian 8 to 9 and I had no older 4.9 kernel, so I'm now running one of the old 3.16 kernels. A fast release would be much appreciated.
Bug#903821: marked as done (xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64))
Your message dated Thu, 19 Jul 2018 19:17:39 + with message-id and subject line Bug#903767: fixed in linux 4.9.110-2 has caused the Debian Bug report #903767, regarding xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 903767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xen-hypervisor-4.8-amd64 Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 Severity: critical Justification: breaks the whole system Dear Maintainer, After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I notice a kernel panic on these 3 servers. If I boot xen hypervisor with advanced option in grub menu, and If i select linux-image-4.9.0-6-amd64 kernel, everything work. The 3 servers are from Dell : - 1 PowerEdge R720 - 2 PowerEdge R430 You can find the message displayed on IDRAC console when booting with 4.9.0-7-amd64 : Call Trace: 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 90 66 66 90 e9 c1 07 00 00 4c 89 e7 eb 11 e8 RIP [] ret_form_fork+0x2d/0x70 RSP ---[ end trace 28169cf87e381c4e ]--- Kernel panci - not syncing: Attempted to kill init! exicode=0x000b Kernel Offset: disabled After this, the servers reboot in loop. If you need any others informations, please let me know. Best regards. Benoît -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) xen-hypervisor-4.8-amd64 depends on no packages. Versions of packages xen-hypervisor-4.8-amd64 recommends: ii xen-utils-4.8 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 xen-hypervisor-4.8-amd64 suggests no packages. -- Configuration Files: /etc/default/grub.d/xen.cfg changed: XEN_OVERRIDE_GRUB_DEFAULT=1 echo "Including Xen overrides from /etc/default/grub.d/xen.cfg" GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=2G,max:2G dom0_max_vcpus=2 dom0_vcpus_pin" if [ "$XEN_OVERRIDE_GRUB_DEFAULT" = "" ]; then echo "WARNING: GRUB_DEFAULT changed to boot into Xen by default!" echo " Edit /etc/default/grub.d/xen.cfg to avoid this warning." XEN_OVERRIDE_GRUB_DEFAULT=1 fi if [ "$XEN_OVERRIDE_GRUB_DEFAULT" = "1" ]; then GRUB_DEFAULT="Debian GNU/Linux, with Xen hypervisor" fi -- no debconf information --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.9.110-2 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Jul 2018 18:57:56 +0100 Source: linux Binary: linux-source-4.9 linux-support-4.9.0-7 linux-doc-4.9 linux-manual-4.9 linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-7-common linux-headers-4.9.0-7-common-rt linux-libc-dev linux-headers-4.9.0-7-all linux-headers-4.9.0-7-all-alpha kernel-image-4.9.0-7-alpha-generic-di nic-modules-4.9.0-7-alpha-generic-di nic-wireless-modules-4.9.0-7-alpha-generic-di nic-shared-modules-4.9.0-7-alpha-generic-di serial-modules-4.9.0-7-alpha-generic-di usb-serial-modules-4.9.0-7-alpha-generic-di ppp-modules-4.9.0-7-alpha-generic-di pata-modules-4.9.0-7-alpha-generic-di cdrom-core-modules-4.9.0-7-alpha-generic-di scsi-core-modules-4.9.0-7-alpha-generic-di scsi-modules-4.9.0-7-alpha-generic-di loop-modules-4.9.0-7-alpha-generic-di btrfs-modules-4.9.0-7-alpha-generic-di ext4-modules-4.9.0-7-alpha-generic-di isofs-modules-4.9.0-7-alpha-generic-di
Bug#903821: 4.9.112 boots with Xen PV
I can confirm that a build of the 4.9 series against 4.9.112 boots under Xen PV with the following patches removed: --- linux-4.9.110/debian/patches/series 2018-07-15 18:05:38.614069505 + +++ linux-4.9.112/debian/patches/series 2018-07-16 03:22:09.551240940 + @@ -12,7 +12,6 @@ debian/tools-perf-install.patch # Fixes/improvements to firmware loading -features/all/drivers-media-dvb-usb-af9005-request_firmware.patch debian/iwlwifi-do-not-request-unreleased-firmware.patch bugfix/all/firmware_class-log-every-success-and-failure.patch bugfix/all/firmware-remove-redundant-log-messages-from-drivers.patch @@ -190,15 +189,8 @@ bugfix/all/jfs-Fix-inconsistency-between-memory-allocation-and-ea_buf_max_size.patch bugfix/all/ext4-add-corruption-check-in-ext4_xattr_set_entry.patch bugfix/all/ext4-always-verify-the-magic-number-in-xattr-blocks.patch -bugfix/all/ext4-always-check-block-group-bounds-in-ext4_init_bl.patch -bugfix/all/ext4-make-sure-bitmaps-and-the-inode-table-don-t-ove.patch -bugfix/all/ext4-only-look-at-the-bg_flags-field-if-it-is-valid.patch -bugfix/all/ext4-verify-the-depth-of-extent-tree-in-ext4_find_ex.patch -bugfix/all/ext4-clear-i_data-in-ext4_inode_info-when-removing-i.patch bugfix/all/ext4-never-move-the-system.data-xattr-out-of-the-ino.patch -bugfix/all/jbd2-don-t-mark-block-as-modified-if-the-handle-is-o.patch bugfix/all/ext4-avoid-running-out-of-journal-credits-when-appen.patch -bugfix/all/ext4-add-more-inode-number-paranoia-checks.patch bugfix/all/sr-pass-down-correctly-sized-scsi-sense-buffer.patch # Fix exported symbol versions I have not looked at these patches to see if they would apply with modifications.
Bug#903821: [Pkg-xen-devel] Bug#903821: linux-image-4.9.0-7-amd64: Can not boot 4.9.0_7_amd64 with Xen
I’ll pile on top of this: domUs crash with the kernel as well, with a GPF. Looks like any Xen + 4.9.0-7 = Crash, regardless of it being a domU or dom0. John > On 15 Jul 2018, at 21:55, Sebastien KOECHLIN wrote: > > Package: src:linux > Followup-For: Bug #903821 > > When booting with the new kernel, I got the following Dom0 crash: > > Loading Xen 4.8-amd64 ... > Loading Linux 4.9.0-7-amd64 ... > Loading initial ramdisk ... > (XEN) Xen version 4.8.4-pre (Debian 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) > (ijack...@chiark.greenend.org.uk) (gcc (Debian 6.3.0-18+deb9u1) 6.3.0 > 20170516) debug=n Fri Jun 22 15:50:19 UTC 2018 > (XEN) Bootloader: GRUB 2.02~beta3-5 > (XEN) Command line: placeholder dom0_mem=4096M,max:4096M com2=57600,8n1 > console=com2,vga > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds > (XEN) EDID info not retrieved because no DDC retrieval method detected > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) - 000a (usable) > (XEN) 0010 - 7faa (usable) > (XEN) 7faa - 7fab6000 (reserved) > (XEN) 7fab6000 - 7fad5c00 (ACPI data) > (XEN) 7fad5c00 - 8000 (reserved) > (XEN) e000 - f000 (reserved) > (XEN) fe00 - 0001 (reserved) > (XEN) 0001 - 00068000 (usable) > (XEN) ACPI: RSDP 000F23D0, 0024 (r2 DELL ) > (XEN) ACPI: XSDT 000F245C, 00AC (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: FACP 7FAD34F8, 00F4 (r3 DELL PE_SC3 1 DELL1) > (XEN) ACPI: DSDT 7FAB6000, 3E0D (r1 DELL PE_SC3 1 INTL 20050624) > (XEN) ACPI: FACS 7FAD5C00, 0040 > (XEN) ACPI: APIC 7FAD3078, 008A (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: SPCR 7FAD3104, 0050 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: HPET 7FAD3158, 0038 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: MCFG 7FAD3194, 003C (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: WD__ 7FAD31D4, 0134 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: SLIC 7FAD330C, 0024 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: ERST 7FABBB88, 0210 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: HEST 7FABBD98, 027C (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: BERT 7FABBA08, 0030 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: EINJ 7FABBA38, 0150 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: TCPA 7FAD3490, 0064 (r1 DELL PE_SC3 1 DELL1) > (XEN) ACPI: SSDT 7FAB9E0D, 0454 (r1 DELL PE_SC3 11 INTL 20050624) > (XEN) ACPI: SSDT 7FABA4B3, 0454 (r1 DELL PE_SC3 11 INTL 20050624) > (XEN) ACPI: SSDT 7FABAB59, 0454 (r1 DELL PE_SC3 11 INTL 20050624) > (XEN) ACPI: SSDT 7FABB1FF, 0454 (r1 DELL PE_SC3 11 INTL 20050624) > (XEN) ACPI: SSDT 7FABB8A5, 0162 (r1 DELL PE_SC3 10 INTL 20050624) > (XEN) System RAM: 24570MB (25159936kB) > (XEN) Domain heap initialised > (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec0, GSI 0-23 > (XEN) IOAPIC[1]: apic_id 5, version 32, address 0xfec1, GSI 256-279 > (XEN) IOAPIC[2]: apic_id 6, version 32, address 0xfec1, GSI 64-87 > (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs > (XEN) Failed to get Error Log Address Range. > (XEN) xstate: size: 0x240 and states: 0x3 > (XEN) Unrecognised CPU model 0x17 - assuming vulnerable to LazyFPU > (XEN) Speculative mitigation facilities: > (XEN) Hardware features: > (XEN) Compiled-in support: INDIRECT_THUNK > (XEN) Xen settings: BTI-Thunk RETP(XEN) Allocated console ring of 16 KiB. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) HVM: ASIDs disabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) not detected > (XEN) Brought up 4 CPUs > (XEN) Dom0 has maximum 856 PIRQs > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x1f66000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 00066a00->00066c00 (1035540 pages to be > allocated) > (XEN) Init. ramdisk: 00067ed14000->00067e7e > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: 8100->81f66000 > (XEN) Init. ramdisk: -> > (XEN) Phys-Mach map: 0080->00800080 > (XEN) St
Bug#903821: 4.9.110-1 Xen PV boot workaround
I've tested the workaround successfully. Added `pti=off` to my kernel's boot arguments, updated GRUB, and it started as intended. Benoît, Just to be sure, since you're loading your guests' kernels directly like that, you're passing pti=off via the `extra` config line in your domU config files, right? I.e. extra = 'elevator=noop pti=off' On Tue, 2018-07-17 at 00:39 +0200, Benoît Tonnerre wrote: > Hi, > > I tested this workaround : I confirm that it works on Xen host, but > not on Xen guest. > If you try to start a vm with latest kernel i.e. theses parameters in > cfg file : > > # > # Kernel + memory size > # > kernel = '/boot/vmlinuz-4.9.0-7-amd64' > extra = 'elevator=noop' > ramdisk = '/boot/initrd.img-4.9.0-7-amd64'
Bug#903821: 4.9.110-1 Xen PV boot workaround
Reportedly, adding pti=off to the kernel boot parameters will work around the issue for now. Turning off pti in the guest kernel is done in any case for PV. The issue between 4.9.107 and 4.9.111 affects the detection and turning off of pti, that's why forcing it off helps. In 4.9.112 it's fixed in commit 1adc34adc3447c34926994b87db5d929f5ab45b5 "x86/cpu: Re-apply forced caps every time CPU caps are re-read" Hans
Bug#903821: [Pkg-xen-devel] Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)
Hi, On 07/15/2018 12:16 PM, Benoît Tonnerre wrote: > [...] > > After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I > notice a kernel panic on these 3 servers. Thanks for the report. This is probably all related: This went into 4.9.102: https://www.spinics.net/lists/kernel/msg2808364.html This into 4.9.107: https://www.spinics.net/lists/stable/msg242657.html And this went into 4.9.112: https://www.spinics.net/lists/stable/msg246729.html Apparently kernels from 4.9.107 to 4.9.111 don't boot correctly. Hans
Bug#903821: 4.16 kernel
Hi, Thanks your report! I can start my system with 4.16 backport kernel.
Bug#903821: linux-image-4.9.0-7-amd64: Can not boot 4.9.0_7_amd64 with Xen
Package: src:linux Followup-For: Bug #903821 When booting with the new kernel, I got the following Dom0 crash: Loading Xen 4.8-amd64 ... Loading Linux 4.9.0-7-amd64 ... Loading initial ramdisk ... (XEN) Xen version 4.8.4-pre (Debian 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) (ijack...@chiark.greenend.org.uk) (gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516) debug=n Fri Jun 22 15:50:19 UTC 2018 (XEN) Bootloader: GRUB 2.02~beta3-5 (XEN) Command line: placeholder dom0_mem=4096M,max:4096M com2=57600,8n1 console=com2,vga (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 4 MBR signatures (XEN) Found 4 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 000a (usable) (XEN) 0010 - 7faa (usable) (XEN) 7faa - 7fab6000 (reserved) (XEN) 7fab6000 - 7fad5c00 (ACPI data) (XEN) 7fad5c00 - 8000 (reserved) (XEN) e000 - f000 (reserved) (XEN) fe00 - 0001 (reserved) (XEN) 0001 - 00068000 (usable) (XEN) ACPI: RSDP 000F23D0, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000F245C, 00AC (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: FACP 7FAD34F8, 00F4 (r3 DELL PE_SC3 1 DELL1) (XEN) ACPI: DSDT 7FAB6000, 3E0D (r1 DELL PE_SC3 1 INTL 20050624) (XEN) ACPI: FACS 7FAD5C00, 0040 (XEN) ACPI: APIC 7FAD3078, 008A (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: SPCR 7FAD3104, 0050 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: HPET 7FAD3158, 0038 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: MCFG 7FAD3194, 003C (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: WD__ 7FAD31D4, 0134 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: SLIC 7FAD330C, 0024 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: ERST 7FABBB88, 0210 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: HEST 7FABBD98, 027C (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: BERT 7FABBA08, 0030 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: EINJ 7FABBA38, 0150 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: TCPA 7FAD3490, 0064 (r1 DELL PE_SC3 1 DELL1) (XEN) ACPI: SSDT 7FAB9E0D, 0454 (r1 DELL PE_SC3 11 INTL 20050624) (XEN) ACPI: SSDT 7FABA4B3, 0454 (r1 DELL PE_SC3 11 INTL 20050624) (XEN) ACPI: SSDT 7FABAB59, 0454 (r1 DELL PE_SC3 11 INTL 20050624) (XEN) ACPI: SSDT 7FABB1FF, 0454 (r1 DELL PE_SC3 11 INTL 20050624) (XEN) ACPI: SSDT 7FABB8A5, 0162 (r1 DELL PE_SC3 10 INTL 20050624) (XEN) System RAM: 24570MB (25159936kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec0, GSI 0-23 (XEN) IOAPIC[1]: apic_id 5, version 32, address 0xfec1, GSI 256-279 (XEN) IOAPIC[2]: apic_id 6, version 32, address 0xfec1, GSI 64-87 (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs (XEN) Failed to get Error Log Address Range. (XEN) xstate: size: 0x240 and states: 0x3 (XEN) Unrecognised CPU model 0x17 - assuming vulnerable to LazyFPU (XEN) Speculative mitigation facilities: (XEN) Hardware features: (XEN) Compiled-in support: INDIRECT_THUNK (XEN) Xen settings: BTI-Thunk RETP(XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs disabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) not detected (XEN) Brought up 4 CPUs (XEN) Dom0 has maximum 856 PIRQs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x1f66000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00066a00->00066c00 (1035540 pages to be allocated) (XEN) Init. ramdisk: 00067ed14000->00067e7e (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8100->81f66000 (XEN) Init. ramdisk: -> (XEN) Phys-Mach map: 0080->00800080 (XEN) Start info:81f66000->81f664b4 (XEN) Page tables: 81f67000->81f7a000 (XEN) Boot stack:81f7a000->81f7b000 (XEN) TOTAL: 8000->8200 (XEN) ENTRY ADDRESS: 81d3d180 (XEN) Dom0 has maximum 4 VCPUs (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (ty
Bug#903821: Re : xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)
Hi, If you prefer, you can find a kernel panic screenshot from R720 Dell server's : https://s33.postimg.cc/b2t056y8f/S_lection_027.png Best regards Benoît
Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)
Package: xen-hypervisor-4.8-amd64 Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 Severity: critical Justification: breaks the whole system Dear Maintainer, After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I notice a kernel panic on these 3 servers. If I boot xen hypervisor with advanced option in grub menu, and If i select linux-image-4.9.0-6-amd64 kernel, everything work. The 3 servers are from Dell : - 1 PowerEdge R720 - 2 PowerEdge R430 You can find the message displayed on IDRAC console when booting with 4.9.0-7-amd64 : Call Trace: 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 90 66 66 90 e9 c1 07 00 00 4c 89 e7 eb 11 e8 RIP [] ret_form_fork+0x2d/0x70 RSP ---[ end trace 28169cf87e381c4e ]--- Kernel panci - not syncing: Attempted to kill init! exicode=0x000b Kernel Offset: disabled After this, the servers reboot in loop. If you need any others informations, please let me know. Best regards. Benoît -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) xen-hypervisor-4.8-amd64 depends on no packages. Versions of packages xen-hypervisor-4.8-amd64 recommends: ii xen-utils-4.8 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 xen-hypervisor-4.8-amd64 suggests no packages. -- Configuration Files: /etc/default/grub.d/xen.cfg changed: XEN_OVERRIDE_GRUB_DEFAULT=1 echo "Including Xen overrides from /etc/default/grub.d/xen.cfg" GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=2G,max:2G dom0_max_vcpus=2 dom0_vcpus_pin" if [ "$XEN_OVERRIDE_GRUB_DEFAULT" = "" ]; then echo "WARNING: GRUB_DEFAULT changed to boot into Xen by default!" echo " Edit /etc/default/grub.d/xen.cfg to avoid this warning." XEN_OVERRIDE_GRUB_DEFAULT=1 fi if [ "$XEN_OVERRIDE_GRUB_DEFAULT" = "1" ]; then GRUB_DEFAULT="Debian GNU/Linux, with Xen hypervisor" fi -- no debconf information
