Booting with custom kernel crashes after update

Question

Hello,
I have a custom 2.6.33 kernel compiled and installed without the use of abs on my system. Some time ago when on one of my updates pacman complained that it cannot install arc's 2.6.33, because the name of the folder it needed for the kernel in /lib/modules already existed(from my kernel). I simply backed mine somewhere else, and then updated with pacman, and overwrote the new folder with the backed one. However, after today's update, my custom kernel won't boot! I noticed that pacman intends to do kernel changes again, so I readied myself for repeating the sequence of actions from the last time, but now pacman did the update without complaining. However, on my next reboot I got a "scsi_mod: module already loaded" error, and boot hanged. After a second try, the error didn't seem to even show up again, but boot would still hang(with a long text ending in "---[ end trace 8336ecf974ba482a]---"). I checked my bzImage, the grub menu file, and there aren't any changes. Any help please?
Last edited by Mitio (2010-04-29 21:26:39)

Answer 1

fsckd: the folders 2.6.27-lts, 2.6.32-ARCH, 2.6.33-ARCH, and the pacman-installed folder I turned to backup 2.6.33-ARCH_back2;
Anyway, I fell back to the 2.6.32 kernel temporary, so this isn't really an urgent matter, but I am still curious what caused this. Oh and karol, I don't believe this is caused by kernel crash, as loading the kernel finishes and then I get the error some time after starting udev and before the services from rc.d(sorry for the misleading topic subject, I corrected it).
Last edited by Mitio (2010-04-29 21:27:56)