On Sep 11, 2014, at 2:51 AM, P J P <pj.pandit@xxxxxxxxxxx> wrote: > Hello Chris, > >> On Wednesday, 10 September 2014 9:15 PM, Chris Murphy wrote: >> 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. > > Yes, I've resorted to 3.15 for now. Will look at 3.16 again later, got a sosreport yesterday by trying 3.16 on a F20 VM. If you can reproduce this hang in a VM things are much easier to troubleshoot by setting up a serial console; and then booting the VM with params: rd.debug rdudevdebug systemd.log_level=debug systemd.log_target=console console=ttyS0,38400 That'll be extremely verbose, but at least you can scroll. Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
