http://bugzilla.kernel.org/show_bug.cgi?id=6626
------- Additional Comments From [EMAIL PROTECTED] 2006-05-31 00:39 ------- Dmesg is a bit late for the last freeze as the ring buffer has run out already. I still attach the output, but the first message is already after the restart of the system. I also attach /var/log/syslog and /var/log/messages and kern.log from the time of the crash. However, as I have written above, there is (at leat to my eyes) no relevant message in it. I always check syslog, messages and kern.log directly after such a crash and it always seems that the crash is instantaneous. No time for the kernel to write any relevant message. That´s why I asked if there is einer a method to increase kernel syslog messages (some kind of debug modus) or some other method to identify the culprit that freezes the system. According to syslog messages the last freeze occured yesterday between 13:48 and 13:58 (I was having lunch). When I came back, I saw the screensaver frozen with one dia (it´s an opengl dia show). My reboot was at 14:28. Such a freeze is typical. Sometimes I have this kind fo freeze in an opengl game. In this case the system sound very briefly stutters, then fails and the computer is frozen. (Don´t know if this helps...) Very grateful for any help to identify and finally remedy the problem. (It´s awful to always have these freezes and thus sometimes data loss!) Thanks, Michael P.S.: Next freeze, I will take a dmesg output directly, but 1.) I don´t know when this will be (in 1 hour or in a week) and 2.) I´m afraid there won´t be any more details in it than before. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
-- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
