LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Zenwalk
User Name
Password
Zenwalk This forum is for the discussion of Zenwalk Linux.

Notices


Reply
  Search this Thread
Old 03-13-2019, 10:24 AM   #1
sconti555
LQ Newbie
 
Registered: Feb 2006
Posts: 10

Rep: Reputation: 0
Question Kernel 4.19.28 panic


Dear ZenWalkers:

Over the last few weeks or so I've been unable to update the kernel files in my otherwise up-to-date ZW distribution without invariably inducing kernel panic at boot. This happens regardless of the update method (i.e. in init 2 via netpkg or using xnetpkg from Xfce) and whether I perform a bulk OS package upgrade or just leave the kernel files last to be upgraded after successfully rebooting.

The kernel my machine is able to run on is the one included in the latest (mid-December) OS .iso: that is version 4.19.8. The latest one available at this time is version 4.19.28. Is anyone else having the same issue?

Many thanks in advance for any insight you can shed.

All the best,

--
sconti555
 
Old 03-14-2019, 07:48 AM   #2
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,154
Blog Entries: 9

Rep: Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675
Do you have any idea whereabouts the panic occurs? If it's not too early in the boot process, the panic messages might give somebody a clue. Try to photograph or transcribe them and post the result. Has anything else changed on your system apart from installing a new kernel?

I certainly wouldn't expect a thing like that to vary with the update method. It's more likely that there is an incompatibility between the kernel itself and your hardware. I had a similar problem with my last computer which wouldn't boot any kernels later than 4.13. In the end I had to download the kernel git tree and bisect it to find the change in the code that caused all the trouble. Once I had done that, I could reverse the change with a patch.
 
Old 03-15-2019, 11:03 AM   #3
sconti555
LQ Newbie
 
Registered: Feb 2006
Posts: 10

Original Poster
Rep: Reputation: 0
Hi hazel:

Thank you for your follow-up.

At present I circumvented the problem by downgrading the kernel files to their mid-December .iso version. Prior to that, an upgrade would break the kernel at boot pretty immediately; I haven't thought of taking a picture of the screen at that point: next time I try an upgrade I will post one though.

The kernel files are the most likely responsible in that, after re-imaging my computer, I have first upgraded all installed packages through netpkg so that, following a successful reboot, the only files needing upgrade where the 3 kernel-related files in the .iso. Upgrading them whether through xnetpkg or from init 2 led to exactly the same kernel panic at reboot (following lilo -c -v of course).

My limited Linux knowledge prevents me from bisecting the latest kernel source as you did; I do however appreciate that this would be the most informative way forward (barring the aforementioned pic).

--
sconti555

Last edited by sconti555; 03-15-2019 at 11:05 AM. Reason: Typo corrections
 
Old 03-16-2019, 10:11 AM   #4
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,154
Blog Entries: 9

Rep: Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675Reputation: 1675
Quote:
Originally Posted by sconti555 View Post
My limited Linux knowledge prevents me from bisecting the latest kernel source as you did; I do however appreciate that this would be the most informative way forward (barring the aforementioned pic).
I thought much the same when someone first suggested it! But it turned out not to be difficult at all, just rather laborious. Here is the account of what I did.
 
Old 03-18-2019, 12:08 PM   #5
sconti555
LQ Newbie
 
Registered: Feb 2006
Posts: 10

Original Poster
Rep: Reputation: 0
It actually turns out that I read through your blog entry on bisecting the kernel a few minutes after posting my previous message!

At present I'm afraid I have to defer following your instructions; not so much out of laziness, but rather having to prioritise using my pc rather than 'playing' with it. It's a bit of a shame as I'm aware I'd be learning lots from that kind of work; however, for the time being I just have to make do with a blacklisted set of kernel files.

Many thanks nevertheless, hazel!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Determining cause of Linux kernel panic "Kernel panic - not syncing: Fatal exception" gladman002 Linux - Kernel 1 09-07-2015 08:04 PM
PANIC! KERNEL panic.... Solean Slackware 2 05-03-2003 12:27 AM
Kernel Panic Kernel Panic!!! aditya Linux - Newbie 5 09-08-2002 11:46 PM
kernel panic (narius panic) narius Linux - Newbie 3 06-20-2002 03:56 PM
Kernel panic making me panic! Linux_N0oby Linux - Software 19 05-29-2002 12:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Zenwalk

All times are GMT -5. The time now is 08:34 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration