Hello,

Forwarding to the bug address to have this info in the buglog. Please always 
keep the bug address on Cc: to increase the bus factor.

Best regards
Uwe

On 2/28/26 16:19, [email protected] wrote:
> Dear Uwe,
> 
> Thank you for the informative response.
> 
> Yes, the boot failure occurred more than once and was primarily observed with 
> 6.12.73+deb13-amd64. Earlier kernels such as 6.12.69+deb13-amd64 have booted 
> more reliably on this system.
> 
> The failure happens very early in the boot process, typically after:
> 
> "Loading Linux"
> "Loading initial ramdisk"
> 
> and occasionally produces EFI stub errors related to kernel decompression. 
> The issue appears somewhat non deterministic, which may align with your 
> suggestion regarding EFI stub memory randomization or firmware memory 
> reservation behavior. 
> 
> * I would also like to note that the system had previously been overclocked. 
> The RAM was undervolted and the CPU slightly overvolted. I have since 
> reverted BIOS settings to defaults while continuing testing to rule out 
> hardware instability.
> 
> After reverting the BIOS configuration to optimized defaults, overall system 
> stability has improved significantly. Boot reliability has increased and the 
> frequency of early boot failures appears reduced. I am continuing testing 
> under default settings to determine whether the remaining behavior is 
> reproducible independent of the previous overclock configuration.
> 
> 
> Hardware information:
> 
>   *
> 
>     Motherboard: ASUS Sabertooth Z77
> 
>   *
> 
>     CPU: Intel Core i7-3770K (Ivy Bridge)
> 
>   *
> 
>     Firmware: UEFI
> 
>   *
> 
>     RAM: PNY DDR3 1866Mhz (testing currently underway due to suspected 
> instability)
> 
>   *
> 
>     GPU: NVIDIA 3060 OC (proprietary driver)
> 
> 
> I have attached kernel logs collected from successful boots of both kernels 
> as requested.
> 
> I will also review the power management debugging documentation you had 
> referenced and report back if additional findings appear.
> 
> Please let me know if further diagnostics  would be helpful.
> 
> 
> Best regards,
> Donovan
> 
> 
> 
> --
> Secured with Tuta Mail:
> https://tuta.com/free-email <https://tuta.com/free-email>
> 
> 
> Feb 27, 2026, 16:56 by [email protected]:
> 
>     Control: tag -1 + moreinfo
> 
>     Hello,
> 
>     On Sun, Feb 22, 2026 at 03:18:02AM +0100, [email protected] wrote:
> 
>         Package: linux-image-6.12.73+deb13-amd64
>         Version: 6.12.73+deb13-amd64
>         Severity: important
> 
> 
> 
>         Dear Debian Kernel Team,
> 
> 
>         I would like to report several boot and power-management issues 
> observed after installing kernel version 6.12.73+deb13-amd64 on older Ivy 
> Bridge hardware.
> 
>         System Information
> 
> 
>         Motherboard: ASUS Sabertooth Z77
>         CPU: Intel Core i7-3770K (Ivy Bridge)
>         Firmware: UEFI (legacy-compatible board)
>         Distribution: Debian (stable branch)
>         Architecture: amd64
>         GPU: NVIDIA (proprietary driver installed)
> 
> 
>         Problem Description
> 
>         After upgrading to kernel 6.12.73+deb13-amd64, the system exhibits 
> multiple boot and runtime problems:
> 
> 
>         Boot failures occur intermittently with the following messages:
> 
> 
> 
>         EFI stub: ERROR: Failed to decompress kernel
>         EFI stub: ERROR: efi_stub_entry() failed
> 
> 
>     That is really surprising. This happens very early in the boot process
>     and if there was a problem in that code, this wouldn't be the only
>     report. The efi stub randomizes the memory location, that is the only
>     non-deterministic thing I'm aware of that could explain that (maybe in
>     combination with a BIOS issue where a memory area isn't marked as
>     reserved). Did that happen more than once and only with
>     6.12.73+deb13-amd64?
> 
>         During successful boots, ACPI-related errors appear in dmesg 
> involving unresolved symbols and SATA controller initialization (_GTF/DSSP 
> related messages).
> 
> 
>     That is unfortunately normal and most of the time no problem. I would
>     expect you have these with earlier kernels, too.
> 
>         System suspend behavior is unreliable:
>         *When placing the system into sleep mode, the computer immediately 
> wakes without user interaction.
> 
> 
>     
> https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html#a-test-modes-of-hibernation
>     contains some debug ideas. I'm not sure how up-to-date this document is,
>     but it is worth a try.
> 
>         Please let me know if additional logs, dmesg output, or hardware 
> information would be helpful for debugging.
> 
> 
>     Can you please provide a kernel log for both 6.12.69+deb13-amd64 and
>     6.12.73+deb13-amd64?
> 
>     Best regards
>     Uwe
> 
> 

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to