on 17/05/2011 15:23 Jeremy Chadwick said the following: > So for Charles' situation, the next time it happens what would be useful > for him to provide? The best I could come up with was to induce doadump > then reboot to get the system up/working again, and then use kgdb > after-the-fact.
This is one of the best things to do, if possible. In this case all the potentially useful info would be preserved. Less drastic approach to hanged I/O debugging is to find out where processes/threads are actually stuck. E.g. using procstat -kk. -- Andriy Gapon _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
