On Sep 10, 2014, at 2:28 AM, P J P <pj.pandit@xxxxxxxxxxx> wrote: > Hi, > >> On Wednesday, 10 September 2014 12:28 PM, poma wrote: >> dr. acut? > > Can't say for sure. I added "rdshell rd.debug" parameters to the boot command line, again it throws a long list of debug messages from - /lib/dracut-lib.sh@xxx. Messages are about trying to setup /etc/sysconfig/network-scripts and dhclient(8) configurations it seems. It has snippets like > > for f in '"/$_dir"/*.sh' > '[' -e //lib/dracut/hooks/cleanup/10-kill-dhclient.sh ']' > . //lib/dracut/hooks/cleanup/10-kill-dhclient.sh > > for f in '/tmp/dhclient.*.pid' > '[' -e '/tmp/dhclient.*.pid ' ']' > continue > ... > /bin/dracut-pre-pivot@29(): exit 0 > systemd-journald[2842]: Received SIGTERM > systemd-journal (2842) used greatest stack depth: 12920 bytes left > > Note:- Systemd(1)/dracut(8) debug logs are serious information overload. They zoom past through the screen inundating it with thousands of lines, you can not even see them all. What's the point? Anything that passes by almost certainly worked correctly so you don't need to see it. It's where it gets stuck that this level of verbosity can be useful. > > Anyway…any clue? Well I have no idea what's on the screen at the time of the hang. Maybe a cell phone photo would be useful. Or maybe you should use the debug kernel which was one of Paul Wouters suggestions. Or you could go out on a limb and see if the problem is happening with 3.17rc4 non-debug which is http://koji.fedoraproject.org/koji/buildinfo?buildID=575871 There are lots of kernels. Unless you really want to do kernel troubleshooting, you might just pick a kernel that works. Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
