Ok, I went back and found what looks like a glaring error. The old config had the CONFIG_PHYSICAL_START=0x1000000 under processor options, the new one was missing a zero. A ha! sez I and "fixed" it. Nope. I get the exact same panic.
Setting CONFIG_EXT2_FS_XATTR=y doesn't help either. On a related note, I see that CONFIG_NR_CPUS only allows for 8 in the 30 kernel. Trying any other number leads to an error "Invalid Number" , whereas for the 29 kernel, 64 seems to be the default. On 10/21/09, Maxim Wexler <maxim.wex...@gmail.com> wrote: >> To me, that looks like /dev/sda1 (which is what the kernel is using as >> root=) doesn't contain any of the following: >> /sbin/init >> /etc/init >> /bin/init >> /bin/sh >> >> Noting that the kernel output implied that it was an ext2 filesystem, >> that looks like it mounted your /boot as /, which fails as there isn't >> any init available on it. > > The partitioning scheme and fs hasn't changed. Just the kernel. It > wasn't a problem before. Also, I don't think the fs id is significant > since, if you look at the photo attached to the bug report, ext3 is > involved in that case. In the new config have CONFIG_EXT2_FS_XATTR is > not set, whereas it's set 'y' in the old. Maybe that's it. The > <help> page says choose N if unsure, which is what I did this time. > I'll wait to hear back from the group and give it another try. > > mw >
