Bug 204883 - bad rip value kernel panic in 5.3.0
Summary: bad rip value kernel panic in 5.3.0
Status: NEW
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-17 01:10 UTC by TONY DIEP
Modified: 2020-02-09 09:36 UTC (History)
6 users (show)

See Also:
Kernel Version: 5.3.0
Tree: Mainline
Regression: No


Attachments
kernel panic message. bad rip value. (1.87 MB, image/jpeg)
2019-09-17 01:10 UTC, TONY DIEP
Details
KP (3.06 MB, image/jpeg)
2019-09-22 22:00 UTC, Ben M
Details
Kernel panic bad RIP value (696.04 KB, image/jpeg)
2019-09-27 16:57 UTC, whamburg
Details
attachment-32400-0.html (1.16 KB, text/html)
2019-09-27 22:32 UTC, TONY DIEP
Details

Description TONY DIEP 2019-09-17 01:10:43 UTC
Created attachment 285013 [details]
kernel panic message. bad rip value.

kernel panic in 5.3.0
System won't boot
bad rip value.
Comment 1 Ben M 2019-09-22 04:15:00 UTC
I am experiencing the same thing, tried both 5.3.0 and 5.3.1, get the same "bad rip value" error.
Comment 2 Ben M 2019-09-22 22:00:59 UTC
Created attachment 285091 [details]
KP
Comment 3 whamburg 2019-09-27 16:52:25 UTC
Got the same kernel panic on a Lenovo Thinkpad E585, BIOS 1.54.
Last working kernel is 5.2.14.
Comment 4 whamburg 2019-09-27 16:57:27 UTC
Created attachment 285217 [details]
Kernel panic bad RIP value
Comment 5 whamburg 2019-09-27 21:52:44 UTC
All of this is Realtek related!

Ok, found a solution for me:
exclude module r8169 from load per kernel parameter in grub
add "module_blacklist=r8169" to your kernel parameters and
the realtek module from net/phy is loaded then.
Works for me for 5.3.1 and 5.2.14!
IMHO module r8169 is obsolete in kernels > 5.3. 
I use the kernel rpms from elrepo-kernel.
Comment 6 TONY DIEP 2019-09-27 22:32:45 UTC
Created attachment 285219 [details]
attachment-32400-0.html

Awesome troubleshooting

On Fri., Sep. 27, 2019, 5:52 p.m. , <bugzilla-daemon@bugzilla.kernel.org>
wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=204883
>
> --- Comment #5 from whamburg (w.hamburg@t-online.de) ---
> All of this is Realtek related!
>
> Ok, found a solution for me:
> exclude module r8169 from load per kernel parameter in grub
> add "module_blacklist=r8169" to your kernel parameters and
> the realtek module from net/phy is loaded then.
> Works for me for 5.3.1 and 5.2.14!
> IMHO module r8169 is obsolete in kernels > 5.3.
> I use the kernel rpms from elrepo-kernel.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 7 whamburg 2019-09-27 23:09:21 UTC
Bad news, LAN does not work with exclude r8169 module. The realtek module was loaded but it does not work. Now back to 5.2.14 kernel! :-(
5.3.1 starts with excluded r8169 module, but then wifi works only.

Not so good.
Comment 8 Ben M 2019-09-27 23:13:37 UTC
So just an FYI, by blacklisting the driver, you loose network access with that NIC. I confirmed that I can now boot, but have no network access. I just built/installed the Realtek driver, and can now boot and have network access on 5.3

Steps I took:

1) While still on 5.2 kernel, grab the source code for my Realtek card

wget https://github.com/mtorromeo/r8168/archive/8.047.04.tar.gz

2) Install 5.3 kernel
3) Add kernel param to blacklist r8169
4) Boot into 5.3
5) Untar and build kernel

tar xfvz 8.047.04.tar.gz
cd r8168-8.047.04/
./autorun.sh

6) Confirm new module is loaded:

lsmod | grep r81
ethtool -I enp6s0

7) Reboot, and have a working 5.3 along with working network access.
Comment 9 Heiner Kallweit 2019-10-25 11:43:42 UTC
The issue has been reported before and is caused by a regression in the module loading subsystem. It's not an issue with r8169.
Until the root cause is fixed just make sure (e.g. configure a soft dep) that the PHY driver module (realtek.ko) is loaded before r8169.
Comment 10 Sebastian 2020-02-04 12:20:19 UTC
I'm experiencing this issue on 5.4.x - could you tell me how can i configure soft dependency to solve this problem?
Comment 11 Heiner Kallweit 2020-02-04 20:03:20 UTC
On 5.4 the softdep is included already. If you get an oops at boot, then most likely r8169.ko is in initramfs but realtek.ko is not. So either remove r8169.ko from initramfs (if network isn't needed to load rootfs) or add realtek.ko to it.
Comment 12 Sebastian 2020-02-09 08:36:42 UTC
(In reply to Heiner Kallweit from comment #11)
> On 5.4 the softdep is included already. If you get an oops at boot, then
> most likely r8169.ko is in initramfs but realtek.ko is not. So either remove
> r8169.ko from initramfs (if network isn't needed to load rootfs) or add
> realtek.ko to it.

Thx - seems to work ;)
Comment 13 Heiner Kallweit 2020-02-09 09:36:43 UTC
On 09.02.2020 09:36, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=204883
> 
> --- Comment #12 from Sebastian (sebo.poczta@wp.pl) ---
> (In reply to Heiner Kallweit from comment #11)
>> On 5.4 the softdep is included already. If you get an oops at boot, then
>> most likely r8169.ko is in initramfs but realtek.ko is not. So either remove
>> r8169.ko from initramfs (if network isn't needed to load rootfs) or add
>> realtek.ko to it.
> 
> Thx - seems to work ;)
> 
Good to know, thanks for the feedback!

Note You need to log in before you can comment on or make changes to this bug.