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

[Francis SOUYRI]

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

[Rolf Fokkens]

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(a)apec.fr&gt; 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(a)lists.fedoraproject.org
>  To unsubscribe:
>  https://admin.fedoraproject.org/mailman/listinfo/test

[Rolf Fokkens]

I think this is related:

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

Op 10/04/14 09:46 schreef Rolf Fokkens <rolf(a)rolffokkens.nl&gt;:

> 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(a)apec.fr&gt;
> >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(a)lists.fedoraproject.org
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/test

[Francis SOUYRI]

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(a)rolffokkens.nl&gt;:
>
> > 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(a)apec.fr&gt;
> >> 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(a)lists.fedoraproject.org
> >> To unsubscribe:
> >> https://admin.fedoraproject.org/mailman/listinfo/test
>
>

[poma]

On 10.04.2014 11:25, Francis SOUYRI wrote:
>  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) ? 
Specify a space-separated LVM & MD UUIDs listed with
# dracut --print-cmdline
in dracut configuration file
e.g.
/etc/dracut.conf.d/kernel_cmdline.conf:
kernel_cmdline="rd.lvm.lv=...  rd.md.uuid=..."

Afterwards
# dracut --force
# reboot


poma

[poma]

On 10.04.2014 14:15, poma wrote:
>  On 10.04.2014 11:25, Francis SOUYRI wrote:
> > 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) ?
>  
>  Specify a space-separated LVM & MD UUIDs listed with
>  # dracut --print-cmdline
>  in dracut configuration file
>  e.g.
>  /etc/dracut.conf.d/kernel_cmdline.conf:
>  kernel_cmdline="rd.lvm.lv=...  rd.md.uuid=..."
>  
>  Afterwards
>  # dracut --force
>  # reboot
>   
Within the lower kernel version:
# dracut --kver 3.13.9-200.fc20.x86_64 --force
# reboot


poma

[Rolf Fokkens]

I added the output of "dracut --print-cmdline" (specifically the rd.md.uuid=...
parts) to 'linux ...' lines in grub2.cfg, which works.

As an alternative I also added a simple 'rd.auto=1' which (may not be the
preferred solution but) works as well.

On 04/10/2014 02:31 PM, poma wrote:
>  On 10.04.2014 14:15, poma wrote:
> > On 10.04.2014 11:25, Francis SOUYRI wrote:
> >> 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) ?
> > Specify a space-separated LVM & MD UUIDs listed with
> > # dracut --print-cmdline
> > in dracut configuration file
> > e.g.
> > /etc/dracut.conf.d/kernel_cmdline.conf:
> > kernel_cmdline="rd.lvm.lv=...  rd.md.uuid=..."
> >
> > Afterwards
> > # dracut --force
> > # reboot
> >
>  Within the lower kernel version:
>  # dracut --kver 3.13.9-200.fc20.x86_64 --force
>  # reboot
>
>
>  poma
>
>

[poma]

On 10.04.2014 19:11, Rolf Fokkens wrote:
>  I added the output of "dracut --print-cmdline"
> (specifically the rd.md.uuid=... parts) to 'linux ...' lines in grub2.cfg, which
> works.
>  
>  As an alternative I also added a simple 'rd.auto=1' which (may not be the
> preferred solution but) works as well. 
Yeah, it also works.

$ cat /etc/dracut.conf.d/kernel_cmdline.conf
kernel_cmdline="rd.auto=1"

# dracut --kver 3.13.9-200.fc20.x86_64 --force

# lsinitrd --kver 3.13.9-200.fc20.x86_64 --file
etc/cmdline.d/01-default.conf
rd.auto=1

Appending to the bootloader config what is considered as system wide
settings is rather obsolete method particularly in relation to the
systemd usage, and the dracut usage also.
This should be used only for temporary manual overrides.
However configuration fragmentation is specific to the world of Linux
distributions.
Old habits die hard.


poma