Thanks Max and Chris. I don't really want the problem to occur again, of course, but I'll be prepared if it does.
On Wed, Dec 3, 2008 at 6:46 PM, Chris Siebenmann <[EMAIL PROTECTED]> wrote: > You write: > | > If keyboard input is not getting in, your machine is probably wedged > | > at a high level interrupt, which sounds doubtful based on your > | > problem description. > | Out of curiosity, why do you say that? I'm no expert on interrupts, so > | I'm curious. It DOES seem that keyboard entry is ignored in this > | situation, since I see no results from ctrl-c, for example (I had left > | the console running 'tail -f /var/adm/messages'. I'm not saying your > | are wrong, but if I should be examining interrupt issues, I'd like to > | know (I have 3 hard disk controllers in the box, for example...) > > ^C handling requires a great deal of high-level kernel infrastructure > to be working, far beyond basic interrupt handling. To get much visible > reaction in a situation where nothing is producing output, for example, > the system has to be able to get all the way to running your shell so > that it can notice that tail has died and print the shell prompt. By > contrast, if the console echoes '^C', you have a fair amount of > interrupt handling. > > The Solaris kernel debugger hooks in to the system at a fairly low > level (I believe significantly lower than all of the things that have > to be working to even echo '^C', much less get all the way to executing > user-level code). Thus, you can get into it and force-crash your system > even if it is otherwise fairly dead, so I think that trying is well > worth it in your situation. > > --- > "I shall clasp my hands together and bow to the corners of the > world." > Number Ten Ox, "Bridge of Birds" > Chris Siebenmann > [EMAIL PROTECTED] >
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
