<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [g43] Missed irq leading to hard lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=79009#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [g43] Missed irq leading to hard lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=79009">bug 79009</a> from <a class="email" href="mailto:rah@settrans.net" title="Bob Ham <rah@settrans.net>"> Bob Ham</a> <pre>I realise now that the behaviour I reported previously was mis-remembered. It is not the case that the machine locks hard after X hangs and I switch to the console and back. I tried to do this recently and no hard-lock occurred. Instead, it was the case that the machine would lock hard if X hanged, I switched to the console and then *restarted* X. Recently, there was a serendipitous event which may shed light on the problem. There was a hang while two user sessions were running. That is, one user had been logged in and another user came along, selected "New Login" from the xscreensaver password dialog and then logged in to another GNOME 3 session themselves. In the process list, there were two processes named X, running on different VTs. In this state, there was the usual hang. However, I managed to switch between the different X sessions. After the hang, I switched from the active X session to the console and then switched again to the other X session. After switching to the other X session, the display was still active but only for a few moments. That is, IIRC, some animated parts of web pages were moving on the screen but then after a few moments the display froze. (In reply to <a href="show_bug.cgi?id=79009#c4">comment #4</a>) > (In reply to <a href="show_bug.cgi?id=79009#c3">comment #3</a>) > > > It would be really useful to get the kernel > > > and userspace stack traces of the stuck processes. > > > > What do you mean? I'm not sure which processes you're referring to. > > All of them. sys-rq-t (echo t > /proc/sysrq-trigger) The next time there is a hang, I will do this.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>