| Summary: | sys-kernel/gentoo-sources-2.6.38-r2 fails to boot where -r1 succeeds, with no config changes | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Denis I. Polukarov <dipolukarov> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | marcus.disi |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | [2.6.38-r2 regression] [2.6.39] | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Config file of kernel
emerge --info photo of the error, don't mind the reflection :) kernel config emerge --info photo of the error (jpg) grub.conf |
||
|
Description
Denis I. Polukarov
2011-04-18 08:38:40 UTC
Created attachment 270343 [details]
Config file of kernel
Created attachment 270345 [details]
emerge --info
I experience the same problem (I use gpt tables and grub2).
sys-boot/grub-1.98-r2
it lists correct the partitions on the SSD and then kernel panic:
not syncing vfs, unable to mount root fs on unknown-block(8,3)
menuentry "Funtoo Linux - vmlinuz-2.6.38-gentoo-r2" {
insmod part_gpt
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 751dc9c9-a27d-4bb7-b92e-22cded53d6f8
linux /vmlinuz-2.6.38-gentoo-r2 rootfstype=ext4 root=/dev/sda3
set gfxpayload=keep
}
gentoo-sources-2.6.38-r1, same config, no problem
I found this one on grub-wiki: http://grub.enbug.org/TestingOnUEFI under "Corrupted initial RAM disk" usb 2-5: new high speed USB device using ehci_hcd and address 3 md: autorun … md: … autorun DONE. RAMDISK: Couldn't find valid RAM disk image starting at 0. VFS: Cannot open root device "sda3" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid:1, comm: swapper Not tainted 2.6.36-020636-generic #201010210905 The initial RAM disk is corrupted by grub 1.98, please see the problem description. Solution : upgrade to grub 1.99 RC1. The "newreloc" feature takes cares to avoid overwriting the memory. And here: http://www.mail-archive.com/bug-grub@gnu.org/msg12597.html I do not use any initramfs... EFI and ext2 support is build into my kernel. I'll post the config later. Also, it works fine with -r1, this seems to be another problem? (In reply to comment #3) > I experience the same problem (I use gpt tables and grub2). > sys-boot/grub-1.98-r2 Can you post your .config and emerge --info output? This seems like a kernel regression, but because GRUB seems to be involved, I think that base-system herd should be CC'ed too, just in case. (In reply to comment #3) > it lists correct the partitions on the SSD and then kernel panic: > not syncing vfs, unable to mount root fs on unknown-block(8,3) Can you get a copy of the boot log until the kernel panic(maybe a serial console)? (In reply to comment #0) > After update from sys-kernel/gentoo-sources-2.6.38-r1 to > sys-kernel/gentoo-sources-2.6.38-r2 (.config from 2.6.38-r1 not changed) system > fail to boot: bootscreen is not progress, CapsLock & ScrollLock on keyboard > blink. How far does the 'boot sequence' go? Do you get the same error as Marcus? Maybe your GRUB conf could help too. I went through the 2.6.38.3 Changelog, but I didn't find any 'suspicious' commit that could cause this bug. If any of you has the time and wants to do a bisect, it would probably help(the commits from 2.6.38.2 to 2.6.38.3 are not too many, I think). Btw, have you tried any of the 2.6.39-rcs? Chances are that if a commit in 2.6.38.3 caused this bug, it'll be in 2.6.39 too, thus you'll be able to reproduce the bug with 2.6.39 too. I couldn't find any thread related to this bug in LKML discussions either. Created attachment 270577 [details]
photo of the error, don't mind the reflection :)
Created attachment 270579 [details]
kernel config
Created attachment 270581 [details]
emerge --info
I downloaded 2.6.39-rc4 from kernel.org copied my .config make oldconfig (all default) make && make modules_install && make install works fine ^^ Created attachment 270591 [details]
photo of the error (jpg)
should have chosen the type -.-
(In reply to comment #9) > I downloaded 2.6.39-rc4 from kernel.org > copied my .config > make oldconfig (all default) > make && make modules_install && make install > works fine ^^ That's good. :) Well, 2.6.38.4-rc1 just got released btw, which is likely to include the change from .39-rc4 that fixed the bug(although we don't know what that was? :P). If you want, give it a try, or you can wait for the official 2.6.38.4 release(and the genpatches release containing it), and test it. I'll add [2.6.39] to the whiteboard for the moment, although it would be better if Denis confirmed that .39-rc4 fixes the issue for him too. (In reply to comment #5) > How far does the 'boot sequence' go? Do you get the same error as Marcus? > Maybe your GRUB conf could help too. Progress of 'boot sequence' - 0% , keyboard start blink after displaying standart 'boot screen' of gentoo-splash. I don't use gpt tables. String of kernel params from grub.conf: kernel /boot/vmlinuz-2.6.38-gentoo-r1 root=/dev/md3 md=3,/dev/sda3,/dev/sdb3 udev clocksource=hpet splash=silent,fadein,theme:natural_gentoo console=tty1 radeon.modeset=1 and i've attach grub.conf too. Created attachment 270617 [details]
grub.conf
(In reply to comment #12) > (In reply to comment #5) > > How far does the 'boot sequence' go? Do you get the same error as Marcus? > > Maybe your GRUB conf could help too. > Progress of 'boot sequence' - 0% , keyboard start blink after displaying > standart 'boot screen' of gentoo-splash. I don't use gpt tables. > String of kernel params from grub.conf: > > kernel /boot/vmlinuz-2.6.38-gentoo-r1 root=/dev/md3 md=3,/dev/sda3,/dev/sdb3 > udev clocksource=hpet splash=silent,fadein,theme:natural_gentoo console=tty1 > radeon.modeset=1 > > and i've attach grub.conf too. I would turn off all splash screen to see at least the error output until the keyboard flashes (my LEDs on the laptop were blinking too, btw.) @Denis Try booting without using a splash screen, as Marcus said, and can you also try booting with a 2.6.39-rc kernel? 2.6.38-r3 boots without problems here as well... @Stratos 38-r5 & 39-rc7 boot failed. md: ...autorun DONE md: loading md3: /dev/sda3 md: cold not open unknown-block(8,3) md: ... md: starting md3 failed VFS: ... kernel panick |
