FS#34358 - [linux] 3.8.x -3.9.x System Hangs Without Any message at Boot
Attached to Project:
Arch Linux
Opened by Sudhir Khanger (donniezazen) - Monday, 18 March 2013, 16:33 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 06 August 2013, 13:45 GMT
Opened by Sudhir Khanger (donniezazen) - Monday, 18 March 2013, 16:33 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 06 August 2013, 13:45 GMT
|
Details
Description: I did a clean installation of ArchLinux on
Thinkpad T420i using EFISTUB/rEFInd. System hangs as soon as
it tries to load kernel. The issue exist on both
linux-3.7.10-1 and linux-3.8.3-2 on my system. When I try to
boot fallback it takes me back to rEFInd screen and if I
then click stock kernel it boots fine. I have to try to boot
fallback a few times for this to work. I have followed
beginners guide very closely and seems to have followed
instructions properly.
Additional info: * package version(s) linux-3.7.10-1 linux-3.8.3-2 * config and/or log files etc. Please let me know what log files do I need to provide. * forum discussion https://bbs.archlinux.org/viewtopic.php?id=156670 Steps to reproduce: Just try to boot stock kernels. Thanks. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Tuesday, 06 August 2013, 13:45 GMT
Reason for closing: No response
Tuesday, 06 August 2013, 13:45 GMT
Reason for closing: No response
I did not have the issue with linux-3.7.10-1. I first see the issue with linux-3.8.3-2.
- I have NO rEFInd. Just plain old toshiba laptop.
- I've NOT tested on 3.7.10. i've updated 3.7.4 -> 3.8.4 right now and see the issue.
- Issue in NOT reproduceable on 3.7.4 and 3.6.10 kernels with mkinitcpio 0.13.0-1.
- Issue IS reproduceable on 3.8.4-ARCH kernel.
"fallback"-initrd does NOT helps.
Rollback rootfs (via lvm snapshot) does NOT helps.
Downgrade kernel and initramfs -- helps 100%.
earlyprintk loglevel=7 shows nothing related.
------ My /etc/mkinitcpio.conf: -------
MODULES="reiserfs ext2 ext4 btrfs"
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block keyboard encrypt lvm2 filesystems fsck"
COMPRESSION="xz"
----------------------------------
As you can see, there are luks-encrypted LVM. And LVM contains snapshots of rootfs, /var, etc.
I've tried to boot OS in different configurations. Conclusions:
- According to HDD LED and loglevel=7, boot silently stops after LVM2 activation and before "fsck". (If snapshots enabled, activation takes some time (30-40 seconds), so i'm sure, that lvm is activated before the hang.)
- 100% same behaviour if i pass INVALID initrd to loaded kernel. For example, boot 3.6.10-ARCH kernel with 3.8.4-ARCH initramfs: it will ask password, it will activate LVM and it will silently hang.
- kparams "loglevel=7", "debug" shows nothing related to this problem (or nothing at all).
- Problem is NOT related to systemd/rootfs/etc. As said erlier, downgraded kernels can boot everything ok.
- Problem inside initramfs and somehow related to kernel version.
Is any way to debug initrd hooks?
kernel params += "disablehooks=lvm2 break=y"
In busybox console:
$ mkdir /run/lvm
$ lvmetad
$ lvm
> vgchange -a y
> ^D
$ ^D
And system boots OK with some early warnings about lvmetad (already running).
I've tried kernel parameters like initcall_debug, debug, udev.loglevel=7, etc, but they shows nothing interesting.
If I exit from busybox without lvm activation, /init will NOT find root device and return me back into busybox console after 10 seconds.
Ideas?
I would be happy to provide any information which might be helpful although I can't think what that might be.
@Vasya Pupkin (shahid)
That's not the same bug. It is a different problem (which is also discussed on the forums and reported, I think) related specifically to LVM.
The symptoms you are seeing are different. You are getting much further in the boot process. This bug report concerns an issue which occurs earlier in the process.
EDIT: shahid, see https://bugs.archlinux.org/task/33851.
Too bad this isn't assigned. This is probably linked to the rEFInd/gummiboot bugs as well but it is likely something in the kernel. (The developer of rEFInd seems to think something about the way the kernel is being compiled or the compiler.)
The developer of rEFInd advised me to request this bug be reopened. https://bbs.archlinux.org/viewtopic.php?pid=1256680#p1256680
EFI v2 (64bit Atom-Board) works fine with EFI-Stub and refind. No such issues there.
EDIT: Lenovo have fixed the boot error they were responsible for. The problem with rEFInd + STUB loader remains. rEFInd -> grub -> kernel works fine but rEFInd -> STUB loader fails every time.
I can reproduce the issue with a direct EFI boot menu entry as well as using the EFI stub loader from a rEFInd menu. As usual, grub via rEFInd works fine.