https://bugzilla.novell.com/show_bug.cgi?id=712958 https://bugzilla.novell.com/show_bug.cgi?id=712958#c34 --- Comment #34 from Jiri Slaby <jslaby@novell.com> 2011-08-24 15:45:40 UTC --- (In reply to comment #32)
(In reply to comment #30)
Created an attachment (id=447246) --> (http://bugzilla.novell.com/attachment.cgi?id=447246) [details] [details] Output of dmesg after -c -s and then sysrg-trigger to t
This still doesn't contain anything useful (any traces): $ head bug-712958_dmesg.out .000000 [631329.878618] .se->statistics.exec_max : 1.528704 [631329.878618] .se->statistics.slice_max : 1.122945
Why is this crap a part of sysrq-t output at all? The only option here is to increase the log buffer. It can be done by the log_buf_len kernel option. Something like log_buf_len=1000000. So if you are going to reboot, pass this in. Then, when you encounter this weird behaviour, repeat the process with dmesg+sysrq-trigger. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.