Debian Configuration :: Boot Kernel Panic After Upgrade To Backport 2.6.39
Aug 21, 2011
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:"
"Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
I have a system that was upgraded from Debian 7 to 8. Unfortunately it is not able to boot from the new kernel 3.16. Only the old 3.2 kernel is able to boot. I could transfer a backup, install it in Virtualbox, redo the upgrade and I can reproduce the error..The last error before "panic" is this line
Code: Select all 59.073579] Freeing unused kernel memory: 216K (ffff8800017ca000 - ffff880001800000) Loading, please wait... [  59.226154] systemd-udevd[53]: starting version 215 [  59.326564] random: systemd-udevd urandom read with 4 bits of entropy available Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... /init: .: line 210: can't open '/scripts/init-premount/ORDER' [  59.552148] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
I installed 2.6.38 from backports. It boots OK, and among the start-up messages it says it has started kdm, but then it offers only a console login prompt, no GUI. I assumed (perhaps optimistically?) that newer kernels would be backward-compatible, and that any dependencies on other software would be enforced by the package mechanisms. Running amd64, Squeeze, KDE.
I've been trying to get Ubuntu on my beloved 4 year old Acer desktop that's been chugging like a tank. However, after either a fresh install or upgrade, I would get the following error:"Kernel panic - not syncing: VFS: Unable to mount to root FS on unknown-block(0,0)".I've looked here and there, and one of the issues it would seem is the kernel not recognizing my hard drive if I'm correct. One of the suggestions was to upgrade the kernel however, I have no idea how to do such a thing if I can't get into the OS.
I am using a kernel with no initrd. I have had this kind of panic before. Usually it means that the kernel can access the hard drive because the driver for the controller or filesystem isn't built into the kernel.
The kernel is 2.6.34 vanilla.
My IDE controller is a Silicon Integrated Systems SiS 5513, and I built the driver for it into the kernel BLK_DEV_SIS5513=y
My /boot (hda1) is ext2, and everything else is ext3
EXT2_FS=y EXT3_FS=y
My grub entry (hda2 is my root partition) kernel (hd0,0)/vmlinuz root=/dev/hda2
i immigrate to Debian Squeeze. So, for each time i want to start debian i have a kernel panic and ( mouse + keyboard blocked ), I can't use anything.Here is my kern.log pastebin
I am currently having issues with system freeze when unmounting portable hard drives. This happens almost every single time. Normal USB sticks are fine and do not produce the freeze. I am using kernel 3.0.0-rc6, however the issue also persists when switching back to 2.6.39. This is the error message i get when freeze occurs, reverting to terminal output:
I installed the 32 bit version of Debian Jessie (8.0) on an Asus X205TA. The Asus X205TA laptop is quirky like a lot of Intel Baytrail Atom laptops/tablets in that it has 32 bit EFI but a 64 bit capable CPU, and installing Linux on them is an exercise in frustration. Jessie is probably the first distro to support 32bit EFI out of the box, and the install went surprisingly smoothly. As expected the sound and built in WIFI does not work, but everything else seems to work well.
I spent half a day compiling the 4.03 kernel but it crashes on boot, and I ended uninstalling it in frustration.
Is there any backport of the 4.0 (or 4.1 which is currently a release candidate) for Jessie? Debian also seems to have pulled the kernel image off of their "experimental" repository.
In trying to get something else working, I installed a newer version of the kernel from backports (I'm on 2.6.26 lenny and the backport kernel is 2.6.32). That failed, so I want to remove the backport kernel completely.
I tried:
Code:
and got:
Code:
Accept this solution? [Y/n/q/?]
I don't really understand how these metapackages work and I don't want to accidentally remove my currently-working kernel.
What's the correct way to remove all packages related to the backports kernel and leave the existing lenny ones alone?
On my raspberry pi 3 with debian jessie I'd like to install a new version of ejabberd (xmpp/jabber server). For some platforms, the latest version 16.02 is available under jessie-backports, but for armhf, it is not: in the table at the bottom of <https://packages.debian.org/jessie-backports/ejabberd>, next to armhf is the version 16.01 listed in red, instead of 16.02 in green as for amd64 etc. What do these colours mean, and why the difference in versions? Will 16.02 become available for armhf as well in the (near) future, or is this an indication of a more serious problem?
Jessie's older version 14.07 does not offer the features I need, and 16.01 does not run at all; hence my hopes are pinned on 16.02.
Just added Squeeze multimedia repositories in source list,but get this after reload :
W: GPG error: ftp://ftp.debian-multimedia.org squeeze Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907
However,update for Audacity & Mplayer showed in Update Manager,and I successfully updated.
Because I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here: [url]
So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. I updated UUIDs in grub's configuration as suggested in this thread:[url]
But now it fails to boot with the following error:
Code:
I checked the filesystem on this partition and its fine. I tried to recreate the initramfs from Knoppix:
Code:
But it didn't change anything.
How can I either fix it or install a different kernel on this drive so I could boot into it and re-install my default kernels?
I'm on Wheezy with version 304.117 of the proprietary nvidia driver installed and working, but an application I have needs a newer version of the driver. I'm trying to install the 319.82 version in backports by following the instructions given here, but when I issue the command to install nvidia-kernel-dkms, I get the following:
The following NEW packages will be installed: Â libgl1-nvidia-glx-i386:i386{a} nvidia-driver{a}
The following packages will be REMOVED: Â libgl1-nvidia-alternatives{u} libglx-nvidia-alternatives{u} Â libxvmcnvidia1{u} nvidia-glx{u}
The following packages will be upgraded:  glx-alternative-nvidia glx-diversions libgl1-nvidia-glx  libgl1-nvidia-glx:i386 libnvidia-ml1 nvidia-alternative  nvidia-installer-cleanup nvidia-kernel-dkms nvidia-settings  nvidia-smi nvidia-vdpau-driver xserver-xorg-video-nvidia
The following partially installed packages will be configured: Â mint-flashplugin-11:i386 12 packages upgraded, 2 newly installed, 4 to remove and 151 not upgraded. Need to get 32.3 MB of archives. After unpacking 9,440 kB will be freed.
The following packages have unmet dependencies: Â glx-alternative-mesa : Depends: glx-diversions (= 0.2.2) but 0.5.1~bpo70+1 is to be installed. Internal error: found 2 (choice -> promotion) mappings for a single choice. Internal error: found 2 (choice -> promotion) mappings for a single choice.
The following actions will resolve these dependencies:
   Remove the following packages:                   1)   glx-alternative-mesa                       2)   glx-alternative-nvidia                      3)   libgl1-nvidia-glx                         4)   libgl1-nvidia-glx:i386                      5)   nvidia-alternative                        6)   nvidia-kernel-dkms                       Â
[Code] ....
Accept this solution? [Y/n/q/?] q
The mint-flashplugin problem is a separate issue which I've had for a while. I assume that it can be ignored for the purposes of this post.
If I'm reading the aptitude output above correctly, it's telling me that the only way to "resolve" the conflict is by uninstalling all nvidia support, leaving me with no driver at all. Is that right?
I have a MyBookLive where i installed a Debian 2.6 kernel. The system is running fine so far. Because of an error message when apt-get upgrade (udev) i tried to upgrade to 3.16. Here's what i did:
- apt-get install linux-image-xx - apt-get install linux-source-xx - extract the source - copied the old .config from running 2.6 kernel over to the 3.16 directory - make oldconfig - make uImage - make modules - make modules_install - copied uImage to /boot
No error messages because its a headless device - its just not booting up.
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
Today I upgraded one of my computers with the following command
% yum upgrade
Before the upgrade the computer was running CentOS 5.3 with the versionlock plugin and kernel 2.6.18-128. The update went smoothly (no dependency problems).
If I try to reboot with the new kernel (2.6.18-194), I get the following:
Found volume group VolGroup00 using metadata type lvm2 2 logical groups in VolGroup00 now active mount: error mounting /dev/root on /sysroot as ex3t: No such device setuproot: moving /dev failed: No such file or directory
[Code].....
If I reboot with the previous kernel (2.6.18-128), everything is fine.
I have gone through all the kernel config options repeatedly, but everytime I get the same error after running my configured kernel.
To begin with, after unpacking the kernel I get Undefined video mode numer: 305 and then a selection of video modes appears.
Why are the standard settings in my lilo 1024x768x256 (vga 773) not accepted?
VFS: Cannot open root device "808" or unknown block(8,8) Please append a correct "root"=" boot option; here are the available partitions: Kernel panic- not syncing :VFS: Unable to mount root fs on unknown block(8,8)
My partitions are ext2, and this format (as well as other formats) are compiled in the kernel.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
Intel Core i7-5500U with Intel HD Graphics.So I updated to the backports kernel and backports intel xorg drivers and I have the weirdest thing.Everything is stuttery even cinnamon desktop effects are no longer smooth. If I boot back to 3.16, everything is butter (except the screen corruption). Even my favorite wine game dropped 25% in fps.
I remember that on windows, if the cpu is too slow (pstate_min_speed), graphics is also stuttery. However, increasing /sys/devices/system/cpu /intel_ pstate/min_perf_pct even to 100% didn't do the trick. I suspect, that this measure is causing it: URL....
how to increase the performance again? I just found out, after running glxgears (with about 40 fps), that xrandr shows an available framerate of 40fps
xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1920x1080 60.00*+ 59.93 40.00
I guess that's what makes it feel slow. Do you know how to get that back up to 60 (fixed)? It seems like the screen refresh rate set in xrandr has no effect on the problem. When I boot, glxgears runs with 60 fps and everything is fine. After a while, it drops to 40 and the whole desktop keeps stuttering. if I change the resolution with xrandr and then change it back, it goes to 60 again for a while
 Attributes:   coresize      = "1028096"   initsize      = "0"   initstate      = "live"   refcnt       = "5"   taint        = ""   uevent       = <store method only>
I have a problem. I'm using the latest Debian stable, Lenny. I am trying to get my usb wifi card working. The Debian wiki advised me to upgrade my kernel to 2.6.30 using backports, because the drivers for my wifi chip are supposedly in the newer kernel.
So thats what I did. The install went fine. However, after rebooting the computer hangs when it is starting gdm. Only the desktop background appears with some fuzzy stripe over it, the mouse doesn't respond. Pressing ctrl+alt+f1 does nothing. I can only restart with ctrl+alt+del.
I can still use the computer with the old kernel. No problems there. I tryed disabling GDM and rebooting again with the new kernel. It boots up and works fine on command line. However when I type startx it hangs, just like before.
I'm not an expert, but I'm suspecting there might be problems with the graphic drivers in the new kernel. When I installed lenny at first, X started fine. However 3d acceleration was not functioning. I got help from IRC, I had to install some package to enable direct rendering. Don't remember which one anymore.
Here's what lspci gives for VGA: 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS
this is what i did i downloaded the latest stable kernel archive from kernel.org and extracted the archive into the download directory (i don't think that matters though) then i downloaded and installed the ncurses archive (needed for menuconfig) then i opened a terminal and navigated to the directory that was extracted from the archive and issues the floowing commands
Testing distribution. Installed Linux 3.0 but left 2.6.32 on as backup. When I boot into the old kernel, wireless mostly works OK, but never when I boot with the new kernel.
Results of dmesg|grep wlan0 on 2.6:
[ 22.005102] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.196774] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.644779] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 30.688053] wlan0: direct probe to AP 00:19:5b:06:9f:ba (try 1) [ 30.694053] wlan0: direct probe responded
[Code]...
Noticing the Access Point looked like it needed the MAC address, I ran iwconfig wlan0 ap <MACADDRESS> and sometimes it will work, and wicd can connect to the access point. But sometimes the command fails to run.
Yesterday i was prompted by my update manager to update some packages. I really don't remember which but i updated.
After reboot the box now kernel panics. I don't believe i get a ubuntu splash screen, and at this point i can't figure out how to get to my grub, in case a kernel was upgraded and it's possible to boot to different kernel.
i noticed some words like 'mantis', 'oops' and 'dvb_core' was a part of the text i get on the screen.
Can this be because of a dvb* upgrade that breaks something important ?
If needed, i should be able to boot via liveCD, or i could take a picture of the errors.
I ran an upgrade to 11.04. It boots fine into KDE, then panics (flashing Caps lock) about a minute later. The Live CD runs fine. Here's the part of my syslog that looks related:
Sometimes a kernel image seems to have the same version as the backported kernel image, for example: linux-image-2.6.32-bpo.5-amd64 linux-image-2.6.32-5-amd64
I learned yesterday that doing a massive upgrade on my system while moving was a BAAAD idea.The upgrade process was going along just fine, it was all downloaded and was actually installing that last time I saw it. I unplugged my laptop to move a bookcase out, and completely forgot to plug it back in. After I got back from moving a load, I found my computer was off. I tried to boot up, and I got an error that kind of freaked me out. It reads as follows:
Code:kernel panic not syncing vfs unable to mount root fs on unknown-block(0,0)I'm able to get to grub just fine, and my windows partition loads up just fine, but any of the linux kernels fail similarly when I attempt to load them.I'm sure that I can fix this, I just have no idea how. Probably has something to do with a live cd.
I had 9.10 installed on my IBM Lenovo Thinkpad, x301. I was performing updates as normal, and chose the Upgrade button to upgrade me to 10.04. Everything started fine, but upon reboot, no bueno, Kernel Panic!
The exact message was "Kernel Panic ubuntu - not synching VFS Unable to mount root fs".
I thought this was a grub issue. Since grub2 now is installed... But it was not. I think it ended up being a problem with some of my configuration files.
I have three kernels I tried: 1. 2.6.32-22 2. 2.6.31-21 3. 2.6.31-20
The first threw me into the kernel panic. The second would hang on "init crypto disks" The third would hang on "checking battery state"
I noticed (from reading another thread) that while these are loading up that you can click on alt-ctl-F1 thru F6 and get prompt. (I also had my home directory encrypted, thought that was part of the problem, but it wasnt).
Once I get passed the loging, I am able to poke around. I tried manually start Gnome via "sudo service gdm start", but it failed. Said it was missing a configuration file. Then I tried on "sudo dpkg-reconfigure gdm" and it would not work. Saying some configuration files are missing or broken. It also said something about dpkg --configure -a, I am assuming this configures everything...
So I tried "sudo dpkg --configure -a" And selected 'y' to every option. Which basically installs the package creators default settings, and viola! Works.
Just wanted to share that knowledge for the other stuck in the upgrade hell.
Normally I would just copy my files off and reinstall, but it was encrypted... Another headache. I guess good in case someone stole my laptop.
i used dual boot system (xp + ubuntu 10.04) and decided to replace them with jolicloud os and then it started In about 86% of jolicloud install it showed me error of hdd partition. I tried different versions of partion type, used also option to install on entire hdd - none of my tries actually worked (also with many hdd formating tries) so I was able to use only usb as live user for Jolicloud, and i burned ubuntu iso on disk - on boot up showed boot up error, i checked BIOS and everything seemed to be ok with boot order. So after many tries i took my old Gutsy Gibon 7.10 live cd. I first updated it with LTS version (8.04 Hardy Heron) and after that I updated it to 10.04 but it seemed to not finish when i saw some error in terminal and installer was exiting 13 minutes before finish then it had kernel panic - fuuuuck! After that i tried to download small versions of linux like Austrumi and puppy linux , but it showed me boot error or cd didnt even open install dialog without showing boot error.
