<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV34] failed to idle channel 0xcccc0000" href="https://bugs.freedesktop.org/show_bug.cgi?id=70388#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV34] failed to idle channel 0xcccc0000" href="https://bugs.freedesktop.org/show_bug.cgi?id=70388">bug 70388</a> from <a class="email" href="mailto:rosti.bsd@gmail.com" title="Rostislav Krasny <rosti.bsd@gmail.com>"> Rostislav Krasny</a> <pre>(In reply to <a href="show_bug.cgi?id=70388#c8">comment #8</a>) > Depending on circumstances, you might find it in /var/log/messages, or if > you can ssh in while the machine is "hung", just run dmesg, or if you can't, > set up netconsole. The /var/log/messages contains the same output to that of journalctl. journalctl is the systemd way of working with the system logs. dmesg also doesn't have much information about this crash. I will attach a dmesg2.txt and a journalctl2.txt files in the next messages. The nouveau Bugs wiki (<a href="http://nouveau.freedesktop.org/wiki/Bugs/">http://nouveau.freedesktop.org/wiki/Bugs/</a>) suggests to add log_buf_len=1M into the kernel parameters. But I doubt it would help in my case, would it? Maybe there is some other kernel/mesa parameter that will change the log level to something more informative?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>