Hi Blake, Blake Irvin wrote: > I am directly on the console. cde-login is disabled, so i'm dealing > with direct entry. > >> Are you directly on the console, or is the console on >> a serial port? If you are >> running over X windows, the input might still get in, >> but X may not be displaying. >> 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...) > Typing ctrl-c, and having process killed because of it are 2 different actions. The interpretation of ctrl-c as a kill character is done in a streams module (ldterm, I believe). This is not done at the device interrupt handler. I doubt you need to examine interrupts. I was only saying that you could try what I recommended to get a dump. The f1-a is handled at the driver during interrupt handling, so it should get processed. I have done this many times, so I am sure it works.
>> If the deadman timer does not trigger, the clock is >> almost certainly running, and your machine is >> almost certainly accepting keyboard input. >> > That's good to know. I just enabled deadman after the last freeze, so > it will be a bit before I can test this (hope I don't have to). > > thanks! > Blake > > >> Good luck, >> max >> _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
