Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53010 - [linux] kernel panic immediately on boot, possibly acpi-related

Attached to Project: Arch Linux
Opened by foophoof (foophoof) - Saturday, 18 February 2017, 17:54 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 15 October 2017, 16:28 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The 4.8.13 -> 4.9.6 linux kernel update causes my home server to panic immediately on boot. If I boot with acpi=off it boots to the terminal. Attached is the boot log from a boot of the 2017.02.01 "official" archiso, with everything disconnected except for USB keyboard, VGA screen, USB thumbdrive with archiso, Ethernet cables (for IPMI and SOL, which is how I got the output).

My hardware:

- Intel S2600CP Motherboard
- Dual E5-2670 SR0KX
- 128GB (16 x 8GB) 2Rx4 PC3L-10600R ECC DIMM

I've tried the USB drive on other machines, and it boots fine, and I've tried booting NixOS (with 4.8 kernel) and FreeBSD on this server, both booted fine, so I'm suspecting something in the 4.9 kernel.

I've had Arch Linux running fine on this server for a few months, I can't quite remember exactly what I upgraded recently, the only thing I can remember is the new Kernel version.

When I try to boot in UEFI mode (which is how I've normally booted), I just get a black (with backlight) screen after the "Arch Linux" / "EFI Default Loader" menu. I've used earlyprintk to try to get a little more output and to get things sent to the serial console (since I'm capturing the output using sol).
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Sunday, 15 October 2017, 16:28 GMT
Reason for closing:  No response
Comment by Doug Newgard (Scimmia) - Monday, 20 February 2017, 16:33 GMT
Have you reported this upstream? Reporting upstream bugs here, especially kernel bug, doesn't do much.
Comment by mattia (nTia89) - Tuesday, 03 October 2017, 20:26 GMT
is this issue still valid with newer kernel version?

Loading...