LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-09-2014, 10:35 AM   #1
wvragga
LQ Newbie
 
Registered: Jul 2006
Posts: 6

Rep: Reputation: 0
Upgraded Slackware 64 current to 3.14.4 kernel panic will not boot


Greetings All,

Getting kernel panic after recent upgrade via slackpkg.

Running Slackware 64 current.
ran slackpkg udate
slackpkg-install new
slackpkg-upgrade all

Toshiba Sattelite c655
vmlinux is pointing to 3.14.4-huge

Researched issue some and saw some similar issues that were corrected after upgrading bios, so I upgraded bios to version 1.80 from 1.60 , trace is now longer but kernel panic still happening.

System is multi-boot with grub booting. Other OS Ubuntu, Win 7 64 booting fine.
Ran update-grub just in case menu showing Slackware 14.1.

Please advise on any method I can use to provide more specific info.

Thanks for an assistance!

Respects,
Ragga.
 
Old 06-09-2014, 10:37 AM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,007

Rep: Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248
Did you run lilo?
 
Old 06-09-2014, 05:11 PM   #3
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,511

Rep: Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862
If you are using the generic kernel, you'll have to make a new initrd.
 
Old 06-09-2014, 05:56 PM   #4
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware, BSD
Posts: 422

Rep: Reputation: 539Reputation: 539Reputation: 539Reputation: 539Reputation: 539Reputation: 539
Quote:
Originally Posted by wvragga
vmlinux is pointing to 3.14.4-huge
Quote:
System is multi-boot with grub booting. Other OS Ubuntu, Win 7 64 booting fine.
Ran update-grub just in case menu showing Slackware 14.1.
Are you sure that grub is booting the huge kernel? You might want to check that in the grub prompt. Do you have other kernels (e.g. generic) in the Slackware '/boot' directory?

Last edited by Philip Lacroix; 06-09-2014 at 06:00 PM.
 
1 members found this post helpful.
Old 06-10-2014, 12:21 PM   #5
wvragga
LQ Newbie
 
Registered: Jul 2006
Posts: 6

Original Poster
Rep: Reputation: 0
Greetings,
Thanks for the replies. I didn't run lilo because I was using grub. I have upgraded the kernel with the same method in the past with no issues using grub.

It was booting huge because that is what vmlinuz is pointing at.

Also, it is not a bootloader issue, I can see the kernel trying to load before the panic and it is showing 3.14.4 .

It appears that I am having an issue related to something that changed at 14.1 because I can only boot kernels prior to that. Am researching changes
And will post info as soon as I have it. .. Thanks again for your replies and have a great day!

Respects,
Ragga
 
Old 06-10-2014, 01:37 PM   #6
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,142

Rep: Reputation: 158Reputation: 158
I've been having a LOT of problems with the 3.14 kernel series with my hardware. Anything before that works fine. Not sure what has changed specifically yet. Reverted back to the 3.10 series for now.
 
Old 06-11-2014, 09:26 PM   #7
edman007
Member
 
Registered: Sep 2003
Distribution: Slamd64
Posts: 168

Rep: Reputation: 30
FYI I had the same issue, the issue is atalkd makes 3.14.4 panic... I'm not really sure why or if it's been reported to the kernel people, and I honestly don't have the time for bug hunting right now

The workaround is to turn off atalkd

Code:
chmod -x /etc/rc.d/rc.atalk

Last edited by edman007; 06-11-2014 at 09:27 PM.
 
Old 06-16-2014, 03:20 PM   #8
wvragga
LQ Newbie
 
Registered: Jul 2006
Posts: 6

Original Poster
Rep: Reputation: 0
Thanks again everyone for the responses.

I wasn't running atalkd but I thank you for the heads up on that.

I didn't have a lot of time available to troubleshoot.
All my data, home directories, etc. is on a separate drive.
I formatted the drive, did clean install of 64 14.1
(worked perfectly with boot disk including file tree made from
Usbimg2disk.sh , apparently boot disk was issue with 14.1 before.)
and upgraded via slackpkg to 64 current.

3.14.5 installed and booted perfectly.

Thanks again!

Ragga.

Last edited by wvragga; 06-16-2014 at 03:25 PM. Reason: additional matter
 
Old 06-18-2014, 10:13 AM   #9
Quicken2k
Member
 
Registered: Mar 2009
Posts: 48

Rep: Reputation: 3
Did you run mkinitrd_command_generator.sh after installing the kernel. ?
 
Old 06-19-2014, 03:28 PM   #10
wvragga
LQ Newbie
 
Registered: Jul 2006
Posts: 6

Original Poster
Rep: Reputation: 0
Greetings,

No, I did not run that script.

I have always upgraded my kernel in this same manner, via slackpkg update , slackpkg install-new, slackpkg upgrade-all and never had to run that script in the past...perhaps it is run for me as part of the upgrade process?

I recently re-installed 14.1 with a 3.10 kernel and upgraded with same method to 3.14.5 kernel without running that script without any issues.

Not sure if this indicates an issue specific to upgrade process, or to the 3.14.4 kernel?

Respects,

Ragga.
 
Old 06-20-2014, 10:43 AM   #11
Quicken2k
Member
 
Registered: Mar 2009
Posts: 48

Rep: Reputation: 3
Quote:
Originally Posted by wvragga View Post
Greetings,

No, I did not run that script.

I have always upgraded my kernel in this same manner, via slackpkg update , slackpkg install-new, slackpkg upgrade-all and never had to run that script in the past...perhaps it is run for me as part of the upgrade process?

I recently re-installed 14.1 with a 3.10 kernel and upgraded with same method to 3.14.5 kernel without running that script without any issues.

Not sure if this indicates an issue specific to upgrade process, or to the 3.14.4 kernel?

Respects,

Ragga.
That script basically scans your filesystem and generates the initrd for you which you then add to lilo. I know I had to use it or I couldn't boot
 
Old 06-23-2014, 09:18 PM   #12
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,511

Rep: Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862Reputation: 1862
The OP is running the huge kernel (which I missed when I commented the first time but Mr. Lacroix noticed and specifically mentioned), so he may not need an initrd at all. Since he's able to get 3.14.5 to boot without one, it appears that there's something goofy with 3.14.4 when presented with the OP's hardware.

I'm gonna wait for 3.14.15 or 3.14.159 myself. Runs away after that level of nerd joke.
 
Old 06-24-2014, 12:21 AM   #13
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,075

Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
I'm gonna wait for 3.14.15 or 3.14.159 myself. Runs away after that level of nerd joke.
It is forbidden to install Linux π in Slackware leet.
 
  


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
[SOLVED] Can't boot into -current partition after slackpkg upgrade-all, after kernel upgraded gabytf Slackware 7 08-12-2012 11:42 AM
Kernel panic on slackware-current 3.2.23 on Via Epia VB8001 pdags Slackware 2 07-21-2012 12:43 PM
Slackware 13 -> Current ,Kernel Panic On Reboot jodef Slackware 9 05-21-2010 09:20 AM
Kernel panic on boot with new SATA drive Slackware 12 kernel: 2.6.21.5 theapodan Linux - Hardware 3 05-18-2009 04:02 PM
Slackware-current 20080429: Kernel panic psynot Slackware 4 05-02-2008 04:57 AM

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

All times are GMT -5. The time now is 03:58 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