after installing 2.6.27 on my ~amd64 box the new kernel will not boot. It gets as far and recognizing my root partion on sda3 and properly identifies the reiserfs file system but then panics saying it can't sync because it can't find init. 2.6.26 boots fine. Reproducible: Always
I get this error too.
Could one of you attach your full 2.6.27 config and also a diff against the 2.6.26 config that works with reiserfs?
Created attachment 169014 [details] My 2.6.27 config
Created attachment 169016 [details] difference between 2.6.26-gentoo-r2
(In reply to comment #2) > Could one of you attach your full 2.6.27 config and also a diff against the > 2.6.26 config that works with reiserfs? > I'm getting the error with xfs. On several different boxes as well.
Created attachment 169018 [details] diff btw config-2.6.27 and config-2.6.26-r2 Diff diff btw config-2.6.27 and config-2.6.26-r2
Created attachment 169020 [details] lshw for my machine
Created attachment 169022 [details] my config-2.6.27
I attached the config info requested as well as lshw for the machine. BTW the motherboard is Intel DQ35JO
Thanks, assigning to maintainers
Can someone take a picture of the panic and attach here
(In reply to comment #11) > Can someone take a picture of the panic and attach here > Is this even possible? The kernel doesn't boot.
You can configure to pipe the display through a serial console (ie. /dev/ttyS0) /boot/grub/menu.lst kernel /boot/vmlinuz root=/dev/sda2 softlevel=single console=ttyS0,115200n8 console=tty0 resume2=swap:/dev/sda1 video=uvesafb:off (Can ignore uvesafb setting... just a clip & paste of mine.) Hook up a second computer/laptop's serial port and get minicom or kermit running on it and connect to the /dev/ttyS0 or /dev/ttyS1 port. This is a common task for working with Coreboot (aka LinuxBIOS). Think you also need to configure a config option for the kernel to output via serial console.
or use a digital camera and upload the photo
In ref to Comment #13, see: Linux Serial Console HOWTO My basic note above will get your dmesg. To also see init processes, which I think we want here, you'll also need to add an entry into /etc/inittab for ttyS0. Really easy to do! The documentation just makes it looks hard. Once it's setup, you can add an entry into Grub as a boot option. Cheers!
I can send a digital picture if you like ( no serial port so serial console not doable without adding hw) but it is pretty uninformative. The boot process looks the same as 2.6.26 as it discovers usb ports and sata devices. It then finds sda3 (which is root) which it identifies as reiserfs and prints a few lines about the journal etc. It this tries to run init and that is where it panics with: Kernel panic - cannot sync - no init found - try setting init= as a kernel parm. I tried adding init=/sbin/init as a command line parameter but that didn't help and I got more or less the same panic with reference to /sbin/init. Seeing init services firing is not applicable since we are not getting that far. I think comparing my hw with Dave's should be the first step. That is why I attached lshw output.
Created attachment 169150 [details] lshw output Same problem here (2.6.26.-r1 is running just fine), same kernel panic with 2.6.27
Helmut's hardware is much different than mine, so assuming we are seeing the same problem, it is probably not hardware dependent. How did those having the problems configure 2.6.27? I ran make oldconfig using my config-2.6.26-r2 and then manually reviewed with make menuconfig. Any idea what could be the problem and why more aren't reporting it. I have a new box that I will try 2.6.27 on and see if it has the same issue. It is also a ~amd64 box with new Intel hardware.
I installed 2.6.27 on the new box I mentioned with more or less default config except for processor and hardware customization. The kernel booted with no problem. I will be able to compare configs between machines later and hopefully will find the culprit.
Please try disabling CONFIG_SECURITY_ROOTPLUG
That did the trick. Booting perfectly now.
OK. You do not want that "feature" enabled, its more of a sample module and is now doing what it is supposed to be doing - not letting anything run as root without the presence of a specific USB device. More documentation here: http://www.linuxjournal.com/article/6279 I think it was a bug that 2.6.26 and previous booted and worked OK while this feature was enabled. Disable CONFIG_SECURITY_ROOTPLUG and things will work as normal.
This has been fix with gentoo-sources-2.6.27-r2 (here)
