General :: Kernel Panic In 64bit Arch Linux After Kernel Recompile - 2.6.35-rc3
Jun 15, 2010
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
Kernel Output:
Code:
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
Update manager downloaded and installed latest kernel (Ubuntu, Linux 2.6.31 -16 -generic). When I tried to restart I get the message { 1.661235}Kernel panic - not syncing: VFS: unable to mount root fs on unknown - block(8,38). Everything works fine on previous update.
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel. Red Hat nash version 4.2.1.13 starting sda: assuming drive cache: write through sda: assuming drive cache: write through mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd-dev failed: 2 Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info: Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
I am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)" I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
i recently buy an MSI 770-45 motherboard with 4gb (2x2gb) Gskill 1600Mhz Ram. The CPU is an athlon2 x4 620, everything tested and working fine except i can`t get lenny or squeeze 64bit linux running because of kernel panics when creating ext3/ext4 partitions during install or running fsck on the system i installed on another PC and moved to this one. The boot shows a screen related to IOMMU problem saying must enable it in bios but no option related to it and no memory remapping also. The question is how i can get IOEMMU working with 4gb of RAM (if i remove one of the two modules everything is fine). I`ve tryed ioemmu=memapper/off/noagp/soft and any thing i found on the web, moving to test debian installation was my last hope really before starting to use the 32bit one, i am planning to add more RAM which with this version is just can`t be.
I was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
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
I wish to recompile serial_core module to make a change in the way ioctl works. I don't wish to rebuild the whole kernel package. Can someone point me to the proper method?? I know I will need to download the kernel headers etc. But I would like to avoid the unneeded compiles of things I don't need to recompile.
I am using FC9, I want to write a module that will always show current time after booting.But for that I need not only to load module using insmod/modprobe, but also to compile that module during boot time.How can I perform this 2 steps correctly.
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:
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
I'm trying to install the "kernel26-headers" package in Arch so I can (try to) compile the Intel 865G graphics drivers from off their website (I can't get H/W acceleration working with xf86-video-intel, but I know the thing has a GPU, because if I boot a Knoppix CD that I have, it enables Compiz by default, and it works damn well).
Any time I try "pacman -S kernel26-headers" I just get a bunch of errors spat back at me code...
Now, I have tried enabling all the US mirrors (HTTP and FTP), and I have even tried a couple of FTP servers in Canada and even Great Britain. None of them seem to work at all!
Since new kernel 3.0 update I cannot rebuild vmware modules
Quote:
sudo vmware-modconfig --console --install-all Unable to initialize kernel module configuration
how to do that. Where do I insert the "CONFIG_LOCALVERSION" line.
Quote:
Same here. This seems to be due to the kernel version being "3.0" instead of "3.0.0". Recompiling the Kernel (and all modules based on it, e.g. nvidia) with CONFIG_LOCALVERSION=".0-ARCH" allows me to compile the modules and run VMware.
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
I have a asus M51 Se that not work with 4GB of memory ram, due to a bug of bios. Only work with one slot of 2GB. I find this link https://bugs.launchpad.net/ubuntu/+s...ux/+bug/316079 that help to solve my problem. But for that I have to change a file.
My question is I need to recompile the kernel that I have? if yes, how can i make that without installing other kernel.
I tried to run some virtual machine using Virtual Machine Manager but the guest OS (windows server 2003) was not able to "see" the rest of my network. I believe VMM did some NAT-ing (192.168.122.x subnet) so i'm not able to "see" my network. I tried various network setting in VMM but couldnt get it to pull my network IP (192.168.1.x subnet).So i installed VirtualBox as a work around because i know VB work when i tried it on my windows machine. I ran into some issue getting VB to run, i think it was that i need to compile the kernel to "optimize" it for VB. I am fairly new to linux so that the impression that i get when i research for the fix to get VB working. In some of the forum post people suggest few things and it seem to me like it to compile the kernel. After a few hours of working i finally got it to compile but the computer crashed during compilation.
I am guess what happened is that i was trying to optimize the kernel for VB but the version of kernel i was using (2.6.18-164.6.1.el5xen) is already optimized for xen (VMM) so it crashed. I am looking to restore or recompile the 2.6.18-164.6.1.el5xen kernel. I am not sure if this is the right thing to do to fix it. With my limited knowledge of linux that all i can think of.
I am working with OpenCL (note that is different from OpenGL) and recently upgraded from nvidia driver 190.29 to 195.36.15 . After a bit of experimentation i decided to downgrade back to 190.29
However after i did this X complains that i have nvidia kernel module 190.42 and it does not match with nvidia drive 190.29 . Could some one tell me how to recompile the kernel module for 190.29??
I use gentoo linux and some minutes ago I thought to upgrade my kernel version. I had 2.6.36-r5 and I want to set 2.6.37-r4. After merging gentoo-sources I did this:
# cd /usr/src/linux # make menuconfig # make && make modules_install # mount /boot # cp arch/i386/boot/bzImage /boot/bzImage-2.6.37-gentoo-r4 # module-rebuild populate # module-rebuild rebuild
At the end I changed the /boot/grub/grub.conf file. The last two commands are for reinstall modules that are not included in the kernel source. After rebooting the system this is what it printed out and stop loading.
sd 2:0:0:0: [sda] Attached SCSI disk EXT3-fs (sda3): error: couldn't mount because of unsupported optional features (240) List of all partitions: 0800 313474754 sda driver: sd 0801 56196 sda1 0802 2104515 sda2 0803 310407930 sda3 0810 48843636123 sdb driver: sd 0811 48843636123 sdb1
No filesystem could mount root, tried ext3 vfat msdos iso9660 Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3) Pid: 1, comm: swapper Not tainted 2.6.37-gentoo-r4 #1 Call trace ? printl+0xf/0x11 panic+0x50/0x146 mount_block_root+0x161/0x170
This has got me stumped. I expected to do /etc/init.d/vboxdrv setup after the upgrade from 11.3 to 11.4 but the command fails. The log is (it seems to repeat so I only quote the final bits to make it fit into the wordcount limit):
Code: make KBUILD_VERBOSE=1 -C /lib/modules/2.6.37.1-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
I installed the latest security update for squeeze. It entailed an update of the kernel. Now when it boots, it give continuous kernel error messages about "can't enumerate usb .... " I have a custom kernel compiled from source (not sure about the patch level) from the same kernel 2.6.32. It seems to work OK. Should I worry about the security of this custom kernel or should I try to recompile it? I don't really know how to do any patching of the kernel source.
we are facing the problem related to Kernel panic in linux . Could u send me details of kernel panic . Why the kernel panic occur and how to resolve this problen
I've been playing around in attempt to see how small a usable kernel I can build. The theory is that it should mainly be useful for preparing a recovery disk or some such thing; disk drivers and a few network drivers are what goes in.
I built the kernel with the attached config. It boots, reaches the hdd (if I specify root as /dev/sda5 manually), then dies when it tries to start Plymouth (something about catching a SEGV signal). What needs to be enabled to run Plymouth? Alternatively, has anyone managed to remove plymouth from boot on Maverick?
(That would require a modified mountall version, I know.) I'm using the mainstream kernel 2.6.32.27 sources on Maverick (yes, I know Maverick uses 2.6.35; but this does boot).
Hardware: Wireless-RTL8192SE b/g/n, uses an out-of-tree driver (r8192se_pci, from Realtek; Ubuntu builds in an older version of this driver); r8169 works for ethernet; ATI Radeon Mobility 3200 graphics, AMD Neo X2 cpu; SATA hd in AHCI mode.
I have a server with Debian on it that I regularly reboot after upgrades. Sometimes (on schedule) fsck will check a disk when the computer is booting. With the exception of sitting in front of the console to observe the fsck, how can I determine the difference between a problematic halt and an fsck (besides waiting out the fsck, hoping it is an fsck)?When I send the computer down to reboot, I will usually have a terminal window open pinging the computer so I know when it has come back up. My first thoughts drifted to fantasizing about hacking fsck to respond to pings with some special magic byte so you could tell via ping that a computer was fsck-ing, but I'm thinking there have got to be easier ways..
I have just tried to update my kernel from 2.6.24.5 to 2.6.39-rc3 on a Slackware 12.1 distribution. I have successfully updated the kernel before, but it was from a newer distribution and newer kernel(Slackware 13.1 and 2.6.33.4). After I updated and rebooted, I got the following error:
Code: List of all partitions: 0300 4194302 hda driver: ide-cdrom 0800 312571224 sda driver: sd 0801 244197560 sda1 00000000-0000-0000-0000-000000000sda1 0802 68372640 sda2 00000000-0000-0000-0000-000000000sda2 No filesystem could mount root, tried: romfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (8,1) Pid: 1, comm: swapper Not tainted 2.6.39-rc3-smp #1 .....