kernel panic : Upgraded from 2.4.x to 2.6.17.6

slack_baby · 07-22-2006, 05:28 AM

HI
this is my 3rd day ..n i m still stuck with kernel panic ... i hav search n tried every possible solution but nothing worked ...

i hav upgraded my kernel from 2.4.X(default in Slackware 10.2) to kernel 2.6.17.6 ... i m using ext3 fs n enabled ext3 fs in the kernel as builtin(no as module) ... now when i compile n install my kernel ... n reset it .. booom .... a kernel panic error...

u can see my system detail below ....

Code:

VFS: Cannot open root device "303" or unknown_block(3,3)

Please append a correct "root=" boot option

Kernel panic: VFS: Unable to mount root fs on unknown_block(3,3)

u can see my lilo.conf

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact        # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/bzImage
  root = /dev/hda3
  label = Linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
  label = Windows
  table = /dev/hda
# Windows bootable partition config ends

fstab

Code:

/dev/hda4        swap             swap        defaults         0   0
/dev/hda3        /                ext3        defaults         1   1
/dev/hda1        /mnt/c           vfat        defaults         1   0
/dev/hda5        /mnt/d           vfat        defaults         1   0
/dev/hda6        /mnt/e           vfat        defaults         1   0
/dev/cdrom       /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0

lspci

Code:

00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)
00:01.0 PCI bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000 AGP 8x] (rev c1)
02:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

ls -al /dev/hda3

Code:

brw-rw----  1 root disk 3, 3 2002-06-09 11:27 /dev/hda3

ls -al /boot/

Code:

total 9856
drwxr-xr-x   2 root root    4096 2006-07-21 08:06 ./
drwxr-xr-x  19 root root    4096 2006-07-20 01:31 ../
lrwxrwxrwx   1 root root      37 2006-07-18 23:58 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r--   1 root root  985974 2006-07-21 07:59 System.map
-rw-r--r--   1 root root  608033 2005-06-05 19:37 System.map-ide-2.4.31
-rw-r--r--   1 root root  838938 2006-07-21 07:24 System.old
-rw-r--r--   1 root root     512 2006-07-19 00:17 boot.0300
-rw-r--r--   1 root root 2310339 2006-07-21 08:06 bzImage
lrwxrwxrwx   1 root root      17 2006-07-18 23:58 config -> config-ide-2.4.31
-rw-r--r--   1 root root   41760 2005-06-05 19:37 config-ide-2.4.31
-rw-r--r--   1 root root    5032 2004-05-20 23:19 diag1.img
-rw-------   1 root root   39936 2006-07-21 08:06 map
-rw-r--r--   1 root root 2310339 2006-07-21 07:59 vmlinuz
-rw-r--r--   1 root root 1256566 2005-06-05 19:37 vmlinuz-ide-2.4.31
-rw-r--r--   1 root root 1633792 2006-07-21 07:24 vmlinuz.old

df -km

Code:

Filesystem           1M-blocks      Used Available Use% Mounted on
/dev/hda3                13951      3439      9792  26% /
/dev/hda1                19993      8870     11124  45% /mnt/c
/dev/hda5                19993     18244      1750  92% /mnt/d
/dev/hda6                20979     17831      3148  85% /mnt/e

hope u guyz could help me out

Regards
Slack BABY

Hangdog42 · 07-22-2006, 07:52 AM

This sort of error almost always comes from one of two things, the filesystem or hard disk support. Since you've compiled in the file system, its likely you didn't compile in support for your hard disk drive (in Device Drivers > ATA/ATAP/MFM/RLL support). Again, this needs to be in the kernel and not as a module.

slack_baby · 07-22-2006, 07:54 AM

thankx Hangdog42 .... i will try it n let u know ...

slack_baby · 07-22-2006, 10:05 AM

well i hav tried this n its workd .. but unfortunately .. i m starting getting other kernel panic error

Code:

Kernel Panic - not syncing: I/0 error reading memory image

any idea now ?

Hangdog42 · 07-22-2006, 10:24 AM

Hm. Googling on that error was surprisingly uninformative. I'm going to guess that this has something to do with the intial RAM disk support. Check in Device Drivers > Block Devices that you have RAM Disk support and Initial RAM Filesystem are built into the kernel. For RAM disks, I use the defaults for number of RAM disks (16) and RAM disk size (4096). You'll probably want to check on enabling loopback device support as long as your there.

slack_baby · 07-22-2006, 10:48 AM

thankx Hangdog42 once again ... let me check n will let u know

slack_baby · 07-22-2006, 11:38 AM

i enabled RAMDisk and RAMSize in a kernel n compile it ... but it didnt sovle da problem .. still getting the same error. ....

zetabill · 07-22-2006, 03:05 PM

Quote:

Originally Posted by slack_baby

ls -al /boot/

Code:

total 9856
drwxr-xr-x   2 root root    4096 2006-07-21 08:06 ./
drwxr-xr-x  19 root root    4096 2006-07-20 01:31 ../
lrwxrwxrwx   1 root root      37 2006-07-18 23:58 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r--   1 root root  985974 2006-07-21 07:59 System.map
-rw-r--r--   1 root root  608033 2005-06-05 19:37 System.map-ide-2.4.31
-rw-r--r--   1 root root  838938 2006-07-21 07:24 System.old
-rw-r--r--   1 root root     512 2006-07-19 00:17 boot.0300
-rw-r--r--   1 root root 2310339 2006-07-21 08:06 bzImage
lrwxrwxrwx   1 root root      17 2006-07-18 23:58 config -> config-ide-2.4.31
-rw-r--r--   1 root root   41760 2005-06-05 19:37 config-ide-2.4.31
-rw-r--r--   1 root root    5032 2004-05-20 23:19 diag1.img
-rw-------   1 root root   39936 2006-07-21 08:06 map
-rw-r--r--   1 root root 2310339 2006-07-21 07:59 vmlinuz
-rw-r--r--   1 root root 1256566 2005-06-05 19:37 vmlinuz-ide-2.4.31
-rw-r--r--   1 root root 1633792 2006-07-21 07:24 vmlinuz.old

Two things:

The item I've bolded you should delete. It's linking to the config file for the kernel you're not using. I have made this mistake before. If it doesn't work you can always relink it after.

Just in case... make a slackware boot disk in case you get funky problems that won't let you go back and relink that old config... but I've never needed that. Never hurts to be careful

That's the only reason I can think of why the kernel is having an I/O sync error.

With your new kernel you should either compile the .config file into the kernel or put it into /boot with your kernel. The kernels that don't have the config file compiled in will look for a file "config" and if it's different than what you compiled with it will complain like a child.

Let us know if that worked... it did for me.

slack_baby · 07-24-2006, 12:42 PM

hey zetabill .. i hav tried wat u said .. but it didnt work ....

any other solution ?

slack_baby · 07-24-2006, 03:07 PM

okz .. here is update ...
i have notice the two lines about kernel panic

Code:

attempt to access beyoud end of device
hda2: rw=16, want=8, limit=2
Kernel Panic - not syncing: I/0 error reading memory image

i dont know y my kernel is finding .. hda2 .. i dont hav any partition hda2 .. u can see my FSTAB above i had posted....i think this is Lilo problem ..... now how could i disabled it ?? ...

Hangdog42 · 07-24-2006, 04:53 PM

It probably isn't a LILO problem since this is specific to this kernel, and given the lilo.conf entry you posted, it would affect ALL kernels.

To be honest, I'm kind of stumped. One thing to try would be to load one of the 2.6.x stock kernels from Slackware (have a look in testing for 2.6.13). If that works, you can swipe the .config from that kernel, then run make oldconfig for your 2.6.17.6. If that works, then you can start adjusting the config until it better meets your needs.

zetabill · 07-24-2006, 06:15 PM

I agree with Hangdog42...

The only other question I'd have is whether or not you have vfat compiled into the kernel?

The only reason I ask is that your hda2 is actually an extended partition which is the sum total of hda5 and hda6 which are logical partitions. If it's complaining about hda2, then it might not know that it's an extended partition or doesn't recognize the type. This is a problem because the logical (hda5, hda6) partitions occur in the space that would be hda2... which exists before your root partition (hda3). If it can't figure out your logical partitions, then it probably can't figure out where hda2 (hda5 + hda6) ends and hda3 begins. Since your Slackware with the 2.4 kernel works fine I can only assume that the kernel your compiling sees the partitions but has no clue what they are and doesn't want to do anything for fear of overwriting data.

It's just a thought. I hope it works for you because I'm out of ideas.

Good luck.

EDIT: Cleaned up grammar.

slack_baby · 07-25-2006, 11:42 AM

yes ..zetabill i hav compiled vfat in a kernel .. infact i hav compiled all fs in kernel .. but still having same the same kernel panic ....

@Hangdog42 thankx 4 ur help... i will try to load it ...

Tailer · 07-25-2006, 01:22 PM

You need to define a root partition in lilo.conf. try root=/dev/hda<number>
Also, you better write "read-only" in the lilo.conf

slack_baby · 07-25-2006, 01:35 PM

i got something interested ...

http://tastytronic.net/pipermail/poc...ne/000254.html

http://tastytronic.net/pipermail/poc...ne/000255.html

i guess i m also having the same problem .. where i think in daniel's problem the 01:00 is the device(partition) with major 1 n minor 0 ..

in the second link u can see that dainel has solved the problem by setting ram_disk in grub .. i dont know how to do it with lilo .... need suggestiosn...