Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #82537 > unrolled thread
| Started by | m0x7e <xm0x7e@gmail.com> |
|---|---|
| First post | 2024-05-21 18:20 +0200 |
| Last post | 2025-02-20 15:50 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#1071584: linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup m0x7e <xm0x7e@gmail.com> - 2024-05-21 18:20 +0200
Bug#1071584: linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup alphacore@arcor.de - 2024-12-27 07:40 +0100
Bug#1071584: Re: linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup alphacore@arcor.de - 2024-12-28 17:00 +0100
Bug#1071584: marked as done (linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-02-20 15:50 +0100
| From | m0x7e <xm0x7e@gmail.com> |
|---|---|
| Date | 2024-05-21 18:20 +0200 |
| Subject | Bug#1071584: linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup |
| Message-ID | <IGAnv-eSMW-1@gated-at.bofh.it> |
Package: src:linux Version: 6.1.90-1 Severity: normal X-Debbugs-Cc: xm0x7e@gmail.com Dear Maintainer, I've installed Debian 12.5.0 via net-install on a Hyper-V 2016 (2024/05 updates installed) machine. The installation went well, but as soon as the machine tried to boot up with the 6.1.0-21 kernel, it always was resetting after starting the initramfs sequence. Unfortunately all debug options (debug=, debug, removing quiet/splash) didn't work out to get ANY useful log. Interesting side note: after 2-3 retries the boot is sometimes successful and the OS seems to be stable up (at least 2-3 hours as far as I tested). The fall-back Kernel 6.1.0-18 works fine. Coming up all the time with each retry. Here I've recorded a sample: https://www.youtube.com/watch?v=jE53r7ulTKw I've seen that there were others reporting issues with 6.1.0-20/21 kernel, but the focus there seems to be 3rd party software or hardware related. A possibly related bug is #1071378 while adding the parameter earlyprintk=vga didn't change anything. -- Package-specific info: ** Version: Linux version 6.1.0-21-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-21-amd64 root=UUID=db4a3fee-0b7b-4120-b0fb-9e87c31c4f6b ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Microsoft Corporation product_name: Virtual Machine product_version: Hyper-V UEFI Release v1.0 chassis_vendor: Microsoft Corporation chassis_version: Hyper-V UEFI Release v1.0 bios_vendor: Microsoft Corporation bios_version: Hyper-V UEFI Release v1.0 board_vendor: Microsoft Corporation board_name: Virtual Machine board_version: Hyper-V UEFI Release v1.0 ** Loaded modules: tls binfmt_misc nls_ascii nls_cp437 vfat fat intel_rapl_msr intel_rapl_common ghash_clmulni_intel sha512_ssse3 sha512_generic sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl hyperv_drm serio_raw drm_shmem_helper pcspkr drm_kms_helper hv_balloon hyperv_keyboard hv_utils evdev sg joydev drm fuse loop dm_mod efi_pstore configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi sr_mod crc64_rocksoft cdrom crc64 crc_t10dif crct10dif_generic hv_storvsc scsi_transport_fc hid_generic scsi_mod hid_hyperv hid hv_netvsc scsi_common crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel hv_vmbus ** PCI devices: ** USB devices: not available -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.1.0-21-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod 30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-21-amd64 recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-21-amd64 suggests: pn debian-kernel-handbook <none> ii grub-efi-amd64 2.06-13+deb12u1 pn linux-doc-6.1 <none> Versions of packages linux-image-6.1.0-21-amd64 is related to: pn firmware-amd-graphics <none> pn firmware-atheros <none> pn firmware-bnx2 <none> pn firmware-bnx2x <none> pn firmware-brcm80211 <none> pn firmware-cavium <none> pn firmware-intel-sound <none> pn firmware-intelwimax <none> pn firmware-ipw2x00 <none> pn firmware-ivtv <none> pn firmware-iwlwifi <none> pn firmware-libertas <none> pn firmware-linux-nonfree <none> pn firmware-misc-nonfree <none> pn firmware-myricom <none> pn firmware-netxen <none> pn firmware-qlogic <none> pn firmware-realtek <none> pn firmware-samsung <none> pn firmware-siano <none> pn firmware-ti-connectivity <none> pn xen-hypervisor <none> -- no debconf information
[toc] | [next] | [standalone]
| From | alphacore@arcor.de |
|---|---|
| Date | 2024-12-27 07:40 +0100 |
| Message-ID | <JYcaR-39vn-1@gated-at.bofh.it> |
| In reply to | #82537 |
Dear all, I made the following observation: I did a fresh install of Linux Mint Debian Edition (LMDE) 6 based on Debian Bookworm on my Lifebook S series notebook. It came with kernel 6.1.0-12, which worked fine. Then it updated to 6.1.0-28 and it booted into black screen after the initramfs. I upgraded to the backports kernel, which is at 6.11.5 and also upgraded firmware-linux-* from default version 20230210-5 to the backports version 20240709-2. Still booting into black screen. Removed backports kernel BUT kept backports firmware --> et voilà, I could boot the 6.1.0-28 kernel without issues! The pattern seem like: Standard kernel + standard firmware = fails Newer kernel + newer firmware = fails Standard kernel + newer firmware = works Or, simpler: If firmware level > kernel level, it works. Seems like as of 6.1.0-20, some kernel component expects newer firmware than it comes with, or there is a bug in a firmware component, and this seems to be unfixed throughout kernel 6.11.5. causing various hardware related issues like power cycling, booting into UEFI/BIOS instead of the OS or into a black screen like mine. Long story short: Install backports firmware and it should work (in theory) as a workaround.
[toc] | [prev] | [next] | [standalone]
| From | alphacore@arcor.de |
|---|---|
| Date | 2024-12-28 17:00 +0100 |
| Subject | Bug#1071584: Re: linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup |
| Message-ID | <JYHol-3tEU-1@gated-at.bofh.it> |
| In reply to | #82537 |
Unfortunately my assumption was wrong. It worked across ~10 reboots, but today the issue returned, even though still using the backported firmware.
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-02-20 15:50 +0100 |
| Subject | Bug#1071584: marked as done (linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup) |
| Message-ID | <Kig2g-D7T-49@gated-at.bofh.it> |
| In reply to | #82537 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Thu, 20 Feb 2025 15:41:30 +0100 (CET) with message-id <20250220144130.1B7CFBE2EE7@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #1071584, regarding linux-image-6.1.0-21-amd64: power cycle on hypervisor Hyper-V (2016) during bootup 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 owner@bugs.debian.org immediately.) -- 1071584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071584 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web