FS#55903 - [linux] Kernel Panic when booting 4.13.4 with Lenovo Thinkpad E 530c

Attached to Project: Arch Linux
Opened by Oliver Bandel (oriba) - Saturday, 07 October 2017, 18:32 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 14:03 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Kernel Panic while booting (Lenovo Thinkpad E 530c)


Additional info:
* package version(s)

Kernel 4.13.4,
but the problem already occured with 4.13.3.(In the meantime I downgraded to older kernel).

* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  freswa (frederik)
Sunday, 13 September 2020, 14:03 GMT
Reason for closing:  Works for me
Additional comments about closing:  r8168 module works fine with recent kernels
Comment by Oliver Bandel (oriba) - Saturday, 07 October 2017, 18:34 GMT
Should be CRITICAL.
Comment by Oliver Bandel (oriba) - Saturday, 07 October 2017, 18:38 GMT
Theinstallation is with LVM and LUKS.
Comment by loqs (loqs) - Saturday, 07 October 2017, 18:47 GMT
What are the details of the kernel panic such as the function that caused it and the backtrace?
Have you tried any other 4.13.x series kernels successfully or otherwise?
Comment by Oliver Bandel (oriba) - Saturday, 07 October 2017, 21:28 GMT
I have no clue what function cused the kernel panic.
The output was so fast and long, that I only can see the rest of it.
When I had the problem with 4.13.3 I tried to use videocamera to record it all.
The camera was too slow for it.
If the standard-kernel allows slower output via boot-paramer I could try it again.

When downgrading, I used the following command:
# pacman -U /var/cache/pacman/pkg/linux-4.12.13-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/r8168-8.044.02-19-x86_64.pkg.tar.xz

That's the newest kernel before 4.13.3, that I could found in the pacman-cache.

The r8168 was necessary, because it was a dependency.
Possibly the problem is located there?

What else information can I provide and how?
Comment by loqs (loqs) - Saturday, 07 October 2017, 21:55 GMT
There should be some hopefully useful information left on the screen such as https://bbs.archlinux.org/viewtopic.php?pid=1713237#p1713237
Can you scroll back with Shift+PageUp?
Comment by Oliver Bandel (oriba) - Saturday, 07 October 2017, 22:38 GMT
ok, looks like the r8168 has to do with the problem...

...can't scroll back. It's completely dead.
Comment by loqs (loqs) - Saturday, 07 October 2017, 23:11 GMT
If you boot with the r8168 module blacklisted on the command line does the error persist?
https://wiki.archlinux.org/index.php/Kernel_modules#Using_kernel_command_line_2
Comment by Oliver Bandel (oriba) - Saturday, 07 October 2017, 23:51 GMT
When disabling the r8168-module, the system comes up. :-)

Loading...