Created attachment 361775 [details] dmesg file which includes some info about mdadm segfaults Description of problem: During the boot process I get segfaults reported during the boot process and in some cases (dracut initramfs/kernel combinations) this results in /dev/md0 from being used which keeps the boot from completing. Version-Release number of selected component (if applicable): mdadm-3.0-4.fc12.i686 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
There is some tie in to dracut with this. I saw the same issue on an x86_64 machine where both the -23 and -33 kernels wouldn't complete booting and I ended up using mkinitrd to make an initrd img to use instead of an initramfs image from dracut.
Seem to be duplicate of bug 523862.
I agree. What I suspect is that dracut ins't including some needed library in the initramfs. When I use a mkinitrd generated initrd image I don't see any problems.
(In reply to comment #3) > I agree. Marking as duplicate then :) > What I suspect is that dracut ins't including some needed library in the > initramfs. When I use a mkinitrd generated initrd image I don't see any > problems. It crashes for me even on normal system. Mkinitrd generated images have populated mdadm.conf, not sure about dracut ones - may be it tries to scan and fails. *** This bug has been marked as a duplicate of bug 523862 ***