Dan Nelson wrote: > > If you lean on the keyboard, or if you set up the network adapters > > as "entropy" sources, does the problem fix itself? > > If you're thinking it's /dev/random blocking on him, 5.0's output never > blocks. Its output is a PRNG periodically seeded from random data, > including interrupt timings and LAN traffic by default.
Mostly, I was thinking that the other suggestions (WITNESS, INVARIANTS, malloc flags) didn't really have any chance of being the cause of the lock-ups, and without some message on the console, it's unlikely that it was a driver tiemout, either. 8-|. If it's long enough to pause the console noticibly, the next thing to try is breaking to the debugger -- which might require an NMI card -- to see what code it's stuck in during the pause. The lack of NMI cards in most people's tool boxes is what made me not suggest that before (i.e. if the console is locked, then using the console to get to the debugger is probably out of the question). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
