Re: Kernels 3.13.9-200.fc20.x86_64 and 3.1389-200.fc20.x86_64 hang at startup on DELL Precision T3610.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Rolf,

Thank you for your help but I am not sure to understand the bugzilla...

I have this:

# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.13.6-200.fc20.x86_64 root=/dev/vgroot/lvroot ro LANG=en_US.UTF-8

Dracut give me this:

# dracut --print-cmdline
 rd.lvm.lv=vgroot/lvswap
 rd.lvm.lv=vgroot/lvroot
 rd.lvm.lv=vgroot/lvusr
rd.md.uuid=86747433:fac1057d:05aa9f4f:a619b0af rd.md.uuid=bf54d312:dc90d70e:6cd367c7:c949a9f3 resume=/dev/mapper/vgroot-lvswap root=/dev/mapper/vgroot-lvroot rootflags=rw,relatime,data=ordered rootfstype=ext4

where can I add the the dracut cmdline (grub.conf, darcut.conf) ?

Best regards.

Francis

On 04/10/2014 10:02 AM, Rolf Fokkens wrote:
I think this is related:

https://bugzilla.redhat.com/show_bug.cgi?id=1084766

Op 10/04/14 09:46 schreef Rolf Fokkens <rolf@xxxxxxxxxxxxxx>:

Same problem here, but I think it is caused by the latest dracut.
Creating a new initramdisk for older kernels (and booting it) results in
the same problem.

Op 10 apr. 2014 om 09:13 heeft Francis SOUYRI <francis.souyri@xxxxxxx>
het volgende geschreven:

Hello,

I juste updated my PC to the kernel-3.13.9-200.fc20.x86_64 and before
the kernel-3.13.8-200.fc20.x86_64 but on my DELL Precision T3610 with
these kernels the system hang with the last messages:

Reached target Paths
Reached target Basic System
Random non blocking pools initialized

I have no problem with the kernel-3.13.6-200.fc20.x86_64.

Best regards.

Francis
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test





[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux