On Tue, Jul 17, 2012 at 11:04:47PM +0000, John Burrell wrote: > > > > > > On Tue, Jul 17, 2012 at 09:24:50PM +0000, John Burrell wrote: > > > Any suggestions which keys sequences to try? The only one I've found to > > > work so far is > > > Alt+sysRQ+b which reboots the machine - not a lot of use really. > > > > > To have a better chance of saving the logs : > > Alt-SysRQ-s (sync), wait for a second or so > > Alt-SysRQ-u (umount), wait briefly > > Alt-SysRQ-b > > Thanks, I'll do that. Is that sequence going to add to dmesg? You say 'logs' > - which logs exactly?
I believe that dmesg is never saved, and I think I set the loglevel to remove some of the debug noise ( a quick look at my server scripts for 7.1 failed to confirm that - I'm still in the server branch of my buildscripts until I fix all the issues :), so I can't point to exactly where/how it is now set, In the context of *saving* data from the problematic boot, all of the logs (and, indeed, any other files being written at hte time). To try to solve the problem, whichever make sense - I guess that's just the system log, and (after running 'startx') the Xorg log. If they get saved, you can always take a look in all the logs, just in case anything odd appears. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
