On 11/13/10 2:13 PM, Robert Watson wrote:
On Sat, 13 Nov 2010, Garrett Cooper wrote:
Isn't there also DEADLKRES that might be helpful in this case (if
Alex is really dealing with a livelock in the kernel)...?
The deadlock resolver is compiled into the GENERIC kernel on
-CURRENT, so I'm assuming it hasn't helped (or perhaps is even part
of the problem). I think the best thing to do at this point is to
try to get into DDB. Of the schemes I suggested to work around the
X11 issue, switching to a virtual console before starting Chromium
may work best, since it will continue to use the local X server, etc.
An alternate way of handling this:
Turn on the VNC X server and use that from a remote place, leaving the
console free.
Robert
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"