Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
06-09-2014, 09:35 AM
|
#1
|
LQ Newbie
Registered: Jul 2006
Posts: 6
Rep:
|
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.
|
|
|
06-09-2014, 09:37 AM
|
#2
|
Senior Member
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,891
|
Did you run lilo?
|
|
|
06-09-2014, 04:11 PM
|
#3
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,863
|
If you are using the generic kernel, you'll have to make a new initrd.
|
|
|
06-09-2014, 04:56 PM
|
#4
|
Member
Registered: Jun 2012
Distribution: Slackware, *BSD
Posts: 441
|
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 05:00 PM.
|
|
1 members found this post helpful.
|
06-10-2014, 11:21 AM
|
#5
|
LQ Newbie
Registered: Jul 2006
Posts: 6
Original Poster
Rep:
|
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
|
|
|
06-10-2014, 12:37 PM
|
#6
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,278
|
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.
|
|
|
06-11-2014, 08:26 PM
|
#7
|
Member
Registered: Sep 2003
Distribution: slackware-current
Posts: 175
Rep:
|
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 08:27 PM.
|
|
|
06-16-2014, 02:20 PM
|
#8
|
LQ Newbie
Registered: Jul 2006
Posts: 6
Original Poster
Rep:
|
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 02:25 PM.
Reason: additional matter
|
|
|
06-18-2014, 09:13 AM
|
#9
|
Member
Registered: Mar 2009
Posts: 48
Rep:
|
Did you run mkinitrd_command_generator.sh after installing the kernel. ?
|
|
|
06-19-2014, 02:28 PM
|
#10
|
LQ Newbie
Registered: Jul 2006
Posts: 6
Original Poster
Rep:
|
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.
|
|
|
06-20-2014, 09:43 AM
|
#11
|
Member
Registered: Mar 2009
Posts: 48
Rep:
|
Quote:
Originally Posted by wvragga
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
|
|
|
06-23-2014, 08:18 PM
|
#12
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,863
|
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.
|
|
|
06-23-2014, 11:21 PM
|
#13
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,418
Rep: 
|
Quote:
Originally Posted by Richard Cranium
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.
|
|
|
All times are GMT -5. The time now is 11:39 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|