<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV86] Lockup and reboot on T61 with nouveau driver/exa" href="https://bugs.freedesktop.org/show_bug.cgi?id=68488#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV86] Lockup and reboot on T61 with nouveau driver/exa" href="https://bugs.freedesktop.org/show_bug.cgi?id=68488">bug 68488</a> from <a class="email" href="mailto:a9016009@gmx.de" title="Andre Klapper <a9016009@gmx.de>"> Andre Klapper</a> <pre>Created <a href="attachment.cgi?id=84554" name="attach_84554" title="journalctl -f _TRANSPORT=kernel">attachment 84554</a> <a href="attachment.cgi?id=84554&action=edit" title="journalctl -f _TRANSPORT=kernel">[details]</a> journalctl -f _TRANSPORT=kernel (In reply to <a href="show_bug.cgi?id=68488#c1">comment #1</a>) > Can you reproduce this at will? There are no clear steps to reproduce, but it happens often enough (at least every second day, sometimes several times a day). > If it started happening recently, was there some sort of upgrade that took place? I made a fresh install of Fedora 19 on this machine a month ago. I *think* the problem did not happen in the first one or two weeks, but that's not enough time to come up with any theories. :) > I think seeing a kernel log would be instructional. I had three reboots yesterday evening within 30 minutes (around 22:09:00, 22:18:00, 22:30:00). The attached "journalctl -f _TRANSPORT=kernel" output includes two full reboot cycles. I'll also attach "journalctl --since=yesterday -f _TRANSPORT=kernel -p err" to ease finding critical stuff. If journalctl is not the way to go, please link to instructions. I was looking at <a href="https://fedoraproject.org/wiki/How_to_debug_Xorg_problems">https://fedoraproject.org/wiki/How_to_debug_Xorg_problems</a> for my initial comment.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>