Kernel 2.6.10 Error

[Megatron X]

Everytime I try to compile kernel 2.6.10 on my desktop pc w/Debian (testing) I get the following error:

include/linux/irq.h:71: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions, see
<URL:file:///usr/share/doc/gcc-3.3/README.Bugs>.
make[4]: *** [drivers/media/dvb/ttpci/budget-patch.o] Error 1
make[3]: *** [drivers/media/dvb/ttpci] Error 2
make[2]: *** [drivers/media/dvb] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2


On my laptop this has not happened yet. Can someone please help me?
Yes this is my first time compiling and only compiling a kernel.

Thank you.

[bwkaz]

See the Sig11 FAQ (http://www.bitwizard.nl/sig11/) -- it lists a few reasons why gcc might be segfaulting when you compile a kernel.

[psi42]

Do you get the error at the same point in the compilation every time?

[Megatron X]

Originally posted by psi42
Do you get the error at the same point in the compilation every time?
I finish doing "make" today to see if the error will stop at the same point and it seems not. Here's the other error:

drivers/scsi/aic7xxx/aic79xx_core.c:
In function `ahd_pause_and_flushwork':
drivers/scsi/aic7xxx/aic79xx_core.c:7062:
internal compiler error:
Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions, see
<URL:file:///usr/share/doc/gcc-3.3/README.Bugs>.
make[3]: *** [drivers/scsi/aic7xxx/aic79xx_core.o] Error 1
make[2]: *** [drivers/scsi/aic7xxx] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2

This only happens on my desktop pc.

bwkaz: Than you for the link. I had a lot of Segmentation fault's in SuSE 9.1 when playing games for unknown reasons.

[bwkaz]

Originally posted by Megatron X
I finish doing "make" today to see if the error will stop at the same point and it seems not. As the FAQ says, if the kernel compile segfaults in a different spot each time, then it may be hardware related. This is due to the fact that very similar compilers (gcc), compiling very similar datasets (the kernel), seems to work for everybody else. ;)

(If it stops in the same place every time, then it's less likely to be hardware, but either way it's hard to say for sure.)

Is your CPU overclocked at all? How about your memory? What about the PCI bus?

[Megatron X]

Originally posted by bwkaz
As the FAQ says, if the kernel compile segfaults in a different spot each time, then it may be hardware related. This is due to the fact that very similar compilers (gcc), compiling very similar datasets (the kernel), seems to work for everybody else. ;)

(If it stops in the same place every time, then it's less likely to be hardware, but either way it's hard to say for sure.)

Is your CPU overclocked at all? How about your memory? What about the PCI bus?

I checked my BIOS and put the MHZ (whatever) on my CPU to 100. Then I did "make" and everything went well just like on my laptop. Now I get this message after doing "make install":

GRUB is installed. To automatically switch to new kernels, point your
default entry in menu.lst to /boot/arch/i386/boot/bzImage-2.6.10


Thank you very much.

[Megatron X]

I finished editing my Grub's menu.lst and when I reboot into the new kernel (linux-2.6.10) I get the following error:


initrd-tools: 0.1.74
modprobr: Can't open dependencies file /lib/modules/2.6.10/modules.dep
(No such file or directory)
modprobr: Can't open dependencies file /lib/modules/2.6.10/modules.dep
(No such file or directory)
pivot_root: No such file or directory
/sbin/init: 426: cannot open dev/console: No such file
Kernel panic - not syncing: Attempted to kill init!

What did I do wrong? :confused: :confused:

[bwkaz]

Hmmm... modules.dep gets created by depmod, which is run at the end of make modules_install. Did you do that step? I don't know whether make install does modules_install or not (I've never used it -- I prefer to manually copy bzImage and System.map to /boot, because I can change their names to match the kernel version, and updating grub's menu.lst is also better done manually).

[Megatron X]

Originally posted by bwkaz
Hmmm... modules.dep gets created by depmod, which is run at the end of make modules_install. Did you do that step? I don't know whether make install does modules_install or not (I've never used it -- I prefer to manually copy bzImage and System.map to /boot, because I can change their names to match the kernel version, and updating grub's menu.lst is also better done manually).
I did make modules_install and everything went fine.
When I booted to the new kernel it seems like it looks for initrd. I'm "guessing" without that it won't boot to the new kernel.
In my /boot directory there is a initrd.img-2.6.8-1-386, but for the new kernel that I compiled there is no initrd.img at all. :confused:

[bwkaz]

Ah, OK, that's it.

Look at the various drivers that you will need to have running to get your root filesystem mounted. This will be the drivers for your root filesystem itself, the drivers for your IDE controller, and some other basic boot-time drivers that aren't usually able to be turned into modules.

If you build all of those drivers into the kernel, you shouldn't need any initrd at all.

If you want to keep any of them as modules for whatever reason, you can try running the mkinitrd script with the appropriate arguments to point it at the kernel source tree -- I don't know what those arguments are, though, because I don't use an initrd. ;) It should have either a manpage or a --help option, though.

[Megatron X]

Originally posted by bwkaz
Ah, OK, that's it.

Look at the various drivers that you will need to have running to get your root filesystem mounted. This will be the drivers for your root filesystem itself, the drivers for your IDE controller, and some other basic boot-time drivers that aren't usually able to be turned into modules.

If you build all of those drivers into the kernel, you shouldn't need any initrd at all.

If you want to keep any of them as modules for whatever reason, you can try running the mkinitrd script with the appropriate arguments to point it at the kernel source tree -- I don't know what those arguments are, though, because I don't use an initrd. ;) It should have either a manpage or a --help option, though.
Ok. Thank you. :)

[Megatron X]

bwkaz,
After messing around with the kernel source and figuring out on how to edit the grub's
menu.lst (which I was making mistakes) it seems like I have a problem.
When I boot to kernel 2.6.10 everything goes well until I get this error:

VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS:
Unable to mount root fs on unknown-block(0,0)

Do I have to remove the old 2.6.8 lines on grub's menu.lst? :confused:

[crabbyman6]

This may be a stupid question, but did you then point your menu.lst file to find the initrd file? Something like
initrd /boot/initrd.img-2.6.8-1-386
after the kernel line. You should be able to leave your old kernel in the menu.lst and have it boot up just fine.

[Megatron X]

Originally posted by crabbyman6
This may be a stupid question, but did you then point your menu.lst file to find the initrd file? Something like
initrd /boot/initrd.img-2.6.8-1-386
after the kernel line. You should be able to leave your old kernel in the menu.lst and have it boot up just fine.

I made a debian package file of the kernel after make menuconfig and installed it. There was no initrd.img file or line in both /boot or grub's menu.lst.
For one I have no clue on how to make an initrd.img and "if" a initrd.img file is made after compiling the kernel I have no clue to where to find it.

[wlr2]

after you do the menuconfig, the make, and make modules_install install you then have to make the initrd.img for your new kernel.

mkdir /lib/modules/2.6.8.1/boot/

cp -a
/lib/modules/2.6.8.1/kernel/security/capability.ko /lib/modules/2.6.8.1/boot/

mkinitrd -o /boot/initrd.img-2.6.8.1 2.6.8.1

that will make your initrd file for you.
how ever. I too am getting the same kernel panic that you listed above. I have built everything just as it should have been, but i get the error that /lib/modules/2.6.8.1/modules.dep is not there......
BUGGER!!!!

[Megatron X]

Originally posted by wlr2
after you do the menuconfig, the make, and make modules_install install you then have to make the initrd.img for your new kernel.

mkdir /lib/modules/2.6.8.1/boot/

cp -a
/lib/modules/2.6.8.1/kernel/security/capability.ko /lib/modules/2.6.8.1/boot/

mkinitrd -o /boot/initrd.img-2.6.8.1 2.6.8.1

that will make your initrd file for you.
how ever. I too am getting the same kernel panic that you listed above. I have built everything just as it should have been, but i get the error that /lib/modules/2.6.8.1/modules.dep is not there......
BUGGER!!!!
Thank you. mkinitrd -o /boot/initrd.img-2.6.10 2.6.10 worked. The only problem I have is with the mouse not working.

Thank you. :D