Linux kernel 2.6.17.4 panic -I/O error reading memory image
 

Ok, here's the deal.
I run slackware linux 10.2 and everything has worked perfect for six moths. A couple days ago, a upgraded my RAM from 512 MB to 1024 MB, and since the HIGHMEM support wasnt compiled into the kernel during installation six moths ago, I had to recompile the kernel. I decided to go for the latest stable kernel, 2.6.17.4 because I also wanted some more ALSA/MIDI support.I followed the How-To in the book "Slackware Essetnials 2nd Edition"(make menuconfig, make modules). Everythink seemed OK during the compiling, so I put the bzImage and the System.map into the /boot dir after making backup of the orginal vmlinuz and System.map and did a make modules_install. I tried to boot, but I get this kernel panic error:

I have googled quite alot, but I have not been able to find a solution. Some threads indicates that I have missed the support for my IDE onboard controller, but I do not know which to choos under "Device driver" in menuconfig. So, heres som facs about my MB, in case one of you guys would like to help me.

MSI: AND-760 MPX Chipset Based K7D Master.
Enhanced IDE controller (through ATA 100)

This is quite urgent, because my backup kernel is now ruined, it cant boot.

Thanks in advance,
Jorek.

Cheers.

before you build the kernel, copy the old kernel config file into /usr/src/linux-version, and issue the command.. " make oldconfig"

this will use the old kernels driver options wherever possable, and ask you about any new options.

amungst the old options, will probably be a working IDE config.

Alternativly... use pciinfo to get information about your IDE chip, and use that to config the kernel.

I have tried to rebuild the orginal kernel with the .config from the install, but this gives me the same kernel panic message.
Man, I have seriously f***ed up this computer, haven't I?

And BTW, using Slax now, there is no such command as pciinfo.
I can try it in few minutes in Slack. But if I get the IDE controller's name, what shall I look for in menuconfig?

BTW2: Here's the output of lspci:

Maybe the RAM chip is borked? Try booting the new kernel with only 512 meg and see if it works.

Thanks for your reply. I tried to use both the new and the old kernel with ony 512 MB RAM, and it still won't boot. Live-CD's like Slax uses all the 1024 megs of RAM, so i guess there is nothing wrong with the RAM chip.

Cheers,
Jorek

Ok, here's an little update:
I looked a bit closer to the boot sequence, here's an outcut:
Note: I do not have a partition hda2 on my hard-drive.:Pengy:

This is my .config file from the /usr/src/linux-2.6.17.4 dir.
It is too long for one post, so I divide it into sections.


Hope this will make sense to someone:)

Cheers,
Jorek

Hope this will make sense to someone:)

Cheers,
Jorek

try adding

mem=1024

to the kernel line in grub.

Hi!
I use LILO, is there any "mem =" line I can use in lilo.conf?

I don't think that this is a memory problem. I think that there is something wrong with your kernel image. Are you running initrd? If so you have to re-create it after compiling a new kernel.
Take a look at your /etc/lilo.conf and and under /boot directory to see if you find anything related to initrd.

Regards

Hi! Thanks for your reply! I'm not using initrd at the moment, but I think that it will do the trick ;) I'm off to a trip to Greece, right now, so I won't be able to test it.
When I arrive back /home, I will give test it and let you guys know how it went.

But thanks to everyone who has participated in this thread and escpesialy bathory;)

Solution
 

Hey,

I came across your question when searching on google.

Then answer is:

CONFIG_PM_STD_PARTITION="/dev/hda2"

You need to match that to your /boot partition

Then you should be fine.

Regards,
HushPe

Mac OS X, and Linux user (and Windows - sadly enough)

Hi again guys. I'm back.
I'm going to try both solutions first thing in the morning (kinda late where I'm located). Need some sleep.;)

I just wonder, this it the enrty in my .conf:
CONFIG_PM_STD_PARTITION="/dev/hda2"

Just like you said HushPe.

So, if I get this right, I just change the

"/dev/hda2"

part to

"/dev/hda8/"

Since hda8 is my root partition, right?

Anyways, thanks to everyone who has participated in this thread.

God, I really need some sleep...

Okey, now it works perfectly thanks to HushPe.
His solution made the trick.

Thanks man.

No worries...

Just a note for other users:

If your boot partition is different to your root partition, that is what I set mine to was my /boot partition. - Just in case it doesn't work.

Cheers,
HushPe