On Thu, Aug 26, 2004 at 10:07:10AM -0700, Andrey Petrov wrote:
> On Thu, Aug 19, 2004 at 01:17:05AM +0200, ali (Anders Lindgren) wrote:

> > responsiveness seemed to degrade until I finally BREAKed it on the serial
> > console, and dropped into ddb. After typing reboot, I got:
> > 
> > db> reboot
> > syncing disks... hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> > hme0: status=20001<GOTFRAME,NORXD>
> > 
> > ..but no reboot! At this point the serial console is stone dead. The damn
> > thing doesn't even respond to BREAKs anymore, and certainly won't drop me
> 
> I'd say that it looks very much like locking problem, reboot calls
> sync and if file system locks are acquired it'll loop there, but I expect
> it to be able to break to ddb, strange.
> 
> It would be interesting to see stack trace (well it's always interesting)
> next time something happens. t or bt ddb commands.

Since he issued a BREAK to get into the console and called
reboot directly, the interrupt generating the BREAK is still
active, so it's not at all surprising that any additional
activity on the console is ignored.

Eduardo