Created attachment 285013 [details] kernel panic message. bad rip value. kernel panic in 5.3.0 System won't boot bad rip value.
I am experiencing the same thing, tried both 5.3.0 and 5.3.1, get the same "bad rip value" error.
Created attachment 285091 [details] KP
Got the same kernel panic on a Lenovo Thinkpad E585, BIOS 1.54. Last working kernel is 5.2.14.
Created attachment 285217 [details] Kernel panic bad RIP value
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.
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.
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.
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.
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.
I'm experiencing this issue on 5.4.x - could you tell me how can i configure soft dependency to solve this problem?
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.
(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 ;)
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!