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.

Did you run lilo?

If you are using the generic kernel, you'll have to make a new initrd.

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?

1 members found this post helpful.

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

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.

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

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.

Did you run mkinitrd_command_generator.sh after installing the kernel. ?

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

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.

It is forbidden to install Linux π in Slackware leet.