|
4.2-0.dmz.1-liquorix-amd64: BUG: Unable to handle kernel NULL pointer dereference
Hi damentz,
I cannot boot 4.2-0.dmz.1-liquorix-amd64 on my system. Any idea what might be the problem? "Failed to find cpu0 device node" seems to indicate that the kernel can't find the CPU (click on the image to enlarge it): 
Do you have any idea what might be going on? My system is: :: Code ::
~$ inxi -bxx System: Host: xbox-am1m Kernel: 4.1-7.dmz.1-liquorix-amd64 x86_64 (64 bit gcc: 4.9.3) Desktop: Xfce 4.12.3 (Gtk 2.24.28) dm: lightdm Distro: Ubuntu 15.10 wily Machine: System: ASUS product: All Series Mobo: ASUSTeK model: AM1M-A v: Rev X.0x Bios: American Megatrends v: 1301 date: 08/19/2015 CPU: Quad core AMD Athlon 5350 APU with Radeon R3 (-MCP-) speed/max: 800/2100 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] bus-ID: 00:01.0 chip-ID: 1002:9830 Display Server: X.Org 1.17.2 driver: radeon Resolution: 1440x900@59.89hz GLX Renderer: Gallium 0.4 on AMD KABINI (DRM 2.42.0, LLVM 3.6.2) GLX Version: 3.0 Mesa 11.1.0-devel (git-6ba291d 2015-09-20 vivid-oibaf-ppa) Direct Rendering: Yes Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168 Drives: HDD Total Size: 1000.2GB (50.8% used) Info: Processes: 184 Uptime: 6 min Memory: 615.9/7418.8MB Init: systemd v: 225 runlevel: 5 default: 2 Gcc sys: 5.2.1 Client: Shell (bash 4.3.421 running in xfce4-terminal) inxi: 2.2.19 Back to top |
|||||
|
booting 4.2-0.dmz.1-liquorix-amd64
:: Quote :: cannot boot 4.2-0.dmz.1-liquorix-amd64
I can't confirm, 4.2-0.dmz.1-liquorix-amd64 boots correcly on my Debian/Sid system and so does linux-image-4.2.0-trunk-amd64 from Debian/experimental too. :: Code ::
System: Host: debian Kernel: 4.2-0.dmz.1-liquorix-amd64 x86_64 (64 bit gcc: 4.9.3) Desktop: Xfce 4.12.0git-8a63c01 (Gtk 2.24.28) dm: lightdm Distro: Debian GNU/Linux stretch/sid Machine: System: Acer product: TravelMate 4530 v: V1.11 serial: LXTPN0C01491707B691601 Mobo: Acer model: Elgon serial: LXTPN0C01491707B691601 Bios: Acer v: V1.11 date: 08/06/2008 Chassis: type: 10 serial: LXTPN0C01491707B691601 CPU: Dual core AMD Athlon X2 QL-64 (-MCP-) speed: 2100 MHz (max) Back to top |
|||||
|
Re: booting 4.2-0.dmz.1-liquorix-amd64
I wish to add that I can boot 4.2.0-10-lowlatency from the Ubuntu wily repo just fine and not have the "Failed to find cpu0 device node" error message.
So it looks like this is isolated to 4.2-0.dmz.1-liquorix-amd64 on my particular setup, because I can boot 4.1-7.dmz.1-liquorix-amd64 from my first post without problems as well. :: Jos.v.W. wrote :: :: Quote :: cannot boot 4.2-0.dmz.1-liquorix-amd64
I can't confirm, 4.2-0.dmz.1-liquorix-amd64 boots correcly on my Debian/Sid system and so does linux-image-4.2.0-trunk-amd64 from Debian/experimental too. <snip> If you're trying to reproduce my issue, then it's really hard to confirm something that 1) is not run on the same distro (yours is Debian stretch/sid, mine is Ubuntu wily) and that 2) is not run on the same hardware, right? Comparing apples and oranges is foolhardy at best in this case. Moreover, I did say that :: Quote :: I cannot boot 4.2-0.dmz.1-liquorix-amd64 on my systemBack to top |
|||||
|
Boot Kernel Panic on AMD E1 CPU with Liquorix 4.2 64 bit and Failed to find CPU device on Core2Duo
Hi all. I can confirm the crash.
On my Toshiba Satellite with an AMD E1 CPU, 64 bit, Liquorix 4.2 fails to boot with a kernel panic. 
:: Code ::
System: Host: ToshSam Kernel: 4.1-7.dmz.1-liquorix-amd64 x86_64 (64 bit gcc: 4.9.3) Desktop: Gnome 3.16.3 (Gtk 3.16.6-1) dm: gdm3 Distro: Debian GNU/Linux stretch/sid Machine: System: TOSHIBA product: SATELLITE C50D-B v: PSCN4E-00X00QEN serial: 8E064757P Mobo: TOSHIBA model: ZBWAE v: 1.00 serial: Desktop Bios: Documents v: Downloads rv Videos date: Libs rom size: info.txt Chassis: Music type: Pictures v: Public serial: Templates CPU: Dual core AMD E1-6010 APU with AMD Radeon R2 Graphics (-MCP-) speed/max: 1000/1350 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R2 Graphics] bus-ID: 00:01.0 chip-ID: 1002:9853 Display Server: X.org 1.17.2 drivers: ati,radeon (unloaded: fbdev,vesa) tty size: 149x37 Advanced Data: N/A for root Network: Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8136 Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:0036 Drives: HDD Total Size: 15.6GB (65.8% used) Info: Processes: 197 Uptime: 26 min Memory: 781.2/3323.8MB Init: systemd v: 226 runlevel: 5 Gcc sys: 5.2.1 alt: 4.9 Client: Shell (bash 4.3.421 running in gnome-terminal-) inxi: 2.2.28 On my MacBook Pro with an Intel Core2Duo, 64 bit, Liquorix 4.2 boots but presenting an error about the CPU node. Despite that, both CPUs seems to be working fine. 
:: Code ::
System: Host: MacSam Kernel: 4.2-0.dmz.1-liquorix-amd64 x86_64 (64 bit gcc: 4.9.3) Desktop: Xfce 4.12.3 (Gtk 2.24.28) dm: gdm3 Distro: Debian GNU/Linux stretch/sid Machine: System: Apple product: MacBookPro7 1 v: 1.0 serial: WQ023GLSATM Mobo: Apple model: Mac-F222BEC8 serial: C0202240607DD7HAB Bios: Apple v: MBP71.88Z.0039.B0E.1111071400 date: 11/07/11 Chassis: type: 10 v: Mac-F222BEC8 serial: WQ023GLSATM CPU: Dual core Intel Core2 Duo P8600 (-MCP-) speed/max: 1596/2394 MHz Graphics: Card: NVIDIA MCP89 [GeForce 320M] bus-ID: 04:00.0 chip-ID: 10de:08a0 Display Server: X.org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa) tty size: 139x41 Advanced Data: N/A for root Network: Card-1: Broadcom BCM4322 802.11a/b/g/n Wireless LAN Controller driver: b43-pci-bridge bus-ID: 02:00.0 chip-ID: 14e4:432b Card-2: Broadcom NetXtreme BCM5764M Gigabit Ethernet PCIe driver: tg3 v: 3.137 bus-ID: 03:00.0 chip-ID: 14e4:1684 Drives: HDD Total Size: 120.0GB (40.0% used) Info: Processes: 189 Uptime: 29 min Memory: 2037.3/3699.3MB Init: systemd v: 226 runlevel: 5 Gcc sys: 5.2.1 alt: 4.8/4.9 Client: Shell (bash 4.3.421 running in xfce4-terminal) inxi: 2.2.28 They are both on Debian Sid and both are booting using UEFI/EFI Back to top |
|||||
|
Hi megaf,
Thank you for sharing your report. From your first image, it looks like the output has been cut off from the top, where it does not show the BUG (Unable to handle kernel NULL pointer dereference in my case) that triggered the kernel oops/panic. The rest of the message, particularly the Call Trace, matches mine, which suggests that this might indeed be a bug that is triggered at a certain condition, but I know not what for the moment. Moreover, this occured in Debian as well, which removes the possibility of this being a Ubuntu-only issue. On 4.2-0.dmz.1-liquorix-amd64, this is the first time I have noticed the "Failed to find cpu0 device node" error message. I have searched online and found several posts regarding the error but said posts have the error occurring in 32-bit only. See [1]. But here we see the error occurring in 64-bit as well, from your second screenshot and mine. BTW, in case anyone is wondering, I boot with printk.time=1 that's why I have those timing data after each message in which Liquorix has it off by default. [1] bbs.archlinux.org/viewtopic.php?id=199901 Back to top |
|||||
|
So, it looks like the CONFIG_OF (Device Tree and Open Firmware support), option is definitely causing problems. In Arch, it seems that the distribution kernel had these options merged in early (they were not available initially using make oldconfig when Liquorix 4 .1 was first released).
I'll try turning that off and see what happens. Also, the RCU configuration changed and might be causing problems (another make oldconfig oversight of mine). I reset it to for no call-back on all CPUs, this may resolve the null pointer dereference you guys are getting as well. And finally, 4.2.1 came out... that should have some nice fixes as the first round of stable patches. In the meantime, you guys can pull the latest 4.1.x kernel from the past repo. Back to top |
|||||
|
Yeah, just got a similar kernel panic on 64-bit, AMD A6 APU, with the 4.2-1 kernel backported for MEPIS 12 (wheezy base)
It seems to be affecting AMD CPU, if you can trust the small sample size. Oh well, at least I patched Jessie's fglrx-driver and broadcom-sta to build on the 4.2 kernel... Back to top |
|||||
|
Megaf, braveheartleo, and stevepusser - could you try the latest version in the repository? Version 4.2-1.dmz.2.
Back to top |
|||||
|
:: damentz wrote :: Megaf, braveheartleo, and stevepusser - could you try the latest version in the repository? Version 4.2-1.dmz.2.My AMD E1-2500 APU is able to boot the 4.2-1.dmz.2 version: :: Code :: $ inxi -SMCxxx
System: Host: mx1 Kernel: 4.2-1.dmz.2-liquorix-amd64 x86_64 (64 bit gcc: 4.9.3) Desktop: Xfce 4.12.2 (Gtk 2.24.25) info: xfce4-panel dm: lightdm Distro: MX-15-a1_x64-mx Fusion 1 July 2015 Machine: Mobo: Gateway model: SX2185 Bios: American Megatrends v: P11-A4 date: 09/17/2013 CPU: Dual core AMD E1-2500 APU with Radeon HD Graphics (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 5589 clock speeds: min/max: 800/1400 MHz 1: 800 MHz 2: 1400 MHz I never tried the 4.2-0.dmz.1 version, so I don't know if would have failed with it or not. Back to top |
|||||
|
:: damentz wrote :: Megaf, braveheartleo, and stevepusser - could you try the latest version in the repository? Version 4.2-1.dmz.2.hi damentz, 4.2-1.dmz.2-liquorix-amd64 now boots on my system, and I no longer see the "Failed to find cpu0 device node" error message, likely caused by the CONFIG_OF=y kernel config. Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||