On Fri, 27 Jul 2018, Martin Husemann wrote:
For debugging: make sure you have the debug and xdebug sets installed. Make the system accessible via ssh. When the problem happens again: from another machine ssh in, pgrep for the X server, use gdb -p to attach to it and get a backtrace."ssh in" won't work - the machine is non-responsive to network. :( Also, unfortunately, the only "other machine" I have is a Windoze laptop; I doubt that it would be a suitable place on which to run the "gdb -p" command.Oh, so the kernel driver actually locks up? Notebook or desktop? Next suggestion would be serial console and try to enter ddb ...
The problem machine is a desktop. It has a serial port. Unfortunately the Windoze laptop does not, so nothing to which the other end of a serial cable could be attached.
+------------------+--------------------------+----------------------------+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee dot com | | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd dot org | +------------------+--------------------------+----------------------------+