Re: Kernels 3.13.9-200.fc20.x86_64 and 3.1389-200.fc20.x86_64 hang at startup on DELL Precision T3610.
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 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Kernels 3.13.9-200.fc20.x86_64 and 3.1389-200.fc20.x86_64 hang at startup on DELL Precision T3610.
I think this is related: https://bugzilla.redhat.com/show_bug.cgi?id=1084766 Op 10/04/14 09:46 schreef 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 >>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@lists.fedoraproject.org >> To unsubscribe: >> https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Kernels 3.13.9-200.fc20.x86_64 and 3.1389-200.fc20.x86_64 hang at startup on DELL Precision T3610.
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 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@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Sunday 13th of October: SSD cache test day
On 10/12/2013 10:58 PM, Reartes Guillermo wrote: Maybe that can be enhanced to say "cset.uuid" instead of just "uuid" / "set uuid"? (for which i confused it with dev.uuid shown by blkid, since i never used bcache before). cset.uuid can be obtained from the output of "bcache-show-super". Cheers. Thanks, I updated the text! Rolf -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Let's stop using wiki for test results
Hi, Tomorrow (sunday) there's an SSD cache Test day. I do like not using the wiki for testresults, but is this tool online available to be used for tomorrow's test day? Rolf On 10/11/2013 06:53 PM, "Jóhann B. Guðmundsson" wrote: On 10/11/2013 04:47 PM, Adam Williamson wrote: Well, 'we' didn't, really. Josef just thought it would be a useful thing to have, so he wrote it, and someone running a test day wound up using it. There was no strategic meeting or grand conspiracy or plan or something. This is how stuff happens in tech, usually: stuff gets done because people just...do it. Not really but OK Now we have seen test days where we used the wiki to track results and test days where we used josef's little tool to track results, and people seem to like the tool, so maybe now we'll make it more clear to people running test days that they have the option of using the tool to track the results. That's really the sum total of what's going on. Anything beats the wiki really so if it's in ready enough shape we should just move to that one instead. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] Sunday 13th of October: SSD cache test day
Hi All,
The Fedora SSD Cache is this sunday October 13th 2013. This Fedora Test
Day will focus on bcache based SSD Caching in Fedora 20.
https://fedoraproject.org/wiki/Test_Day:2013-10-13_SSD_Cache
If you're interested in trying out the new bcache SSD caching
functionality step by step instructions are available for:
- bcache on physical hardware
- bcache in a virtual machine
- non-root FS on bcache (with or without LVM)
- root FS on bcache (wtih or without LVM)
The objective of this Test day is to demonstrate a working Fedora 20
system using bcache. Te be more specific:
* The system boots OK; after booting bcache is operating as expected
* The system updates ("yum update") OK. After updating specifically
the kernel the system boots OK.
* The system is bootable when the caching device is disabled.
Although testing on real hardware is closest to "the real thing",
testing in a VM may also provide good insights on the proper working of
bcache (except for performance).
If you can't make the date of the test day, adding test case results to the
wiki anytime next week is fine as well. Though if you do plan on showing up to
the test day,
please add your name to the participant list on the wiki, and when the day
arrives, pop into #fedora-test-day on freenode and give us a shout! If you
can't make the date
of the test day, adding test case results to the wiki anytime next week is fine
as well. Though if you do plan on showing up to the test day, add your name to
the
participant list on the wiki, and when the day arrives, pop into
#fedora-test-day on freenode and give us a shout!
The Wiki page is still under development, so expect some improvements
before sunday.
Thanks,
Igor Gnatenko
Rolf Fokkens
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
