On Wed, Dec 30, 2009 at 05:22:33PM +0100, Heiko Baums wrote: > Hi, > > I already filed a bug report but thought it couldn't harm or even be > good to post it to the mailing list, too. > > Since the update to kernel26 2.6.32.2-2 from [core] I can't boot this > kernel anymore. I always get a kernel panic with these messages: > > Failed to execute /init > Kernel panic - not syncing: No init found. Try passing init= option to > kernel. Pid: 1, comm: swapper Not tainted 2.6.32-ARCH #1 > Call Trace: > [<ffffffff813301c2>] ? panic+0x8a/0x14b > [<ffffffff8100a28d>] ? init_post+0xad/0x100 > [<ffffffff81502747>] ? kernel_init+0x19d/0x1a8 > [<ffffffff8101311a>] ? child_rip+0xa/0x20 > [<ffffffff815025aa>] ? kernel_init+0x0/0x1a8 > [<ffffffff81013110>] ? child_rip+0x0/0x20 > > I found out that the reason for this is an outdated package in [core]. > I don't know yet which package exactly but I guess it's mkinitcpio. > After upgrading the system to [testing] and generating a new > kernel26.img the system boots again. > > So, please, either move the packages currently in [testing] to [core] > or move kernel26 2.6.32.2-2 back to [testing]. The first would be the > best solution I think. > > See also my bug report: http://bugs.archlinux.org/task/17649 > i just updated my system yesterday to kernel 2.6.32.2-2. I faced no problem. It is running as usual.After reading your mail, i looked in the pacman update log and found that only kernel and virtualbox were updated.Virtualbox is running fine also. and I don't use testing. About the kernel panic message,"Failed to execute /init" it means either the init script in the initrd image is messed up and it is not set executable or the /sbin/init executable in your system is missing ! you have to uncompress the kernel23.img file and take a look at init.
