RE: 2.9 panic: tsleep (2072)

[Don Slutz <DSlutz@arrayinc.com>]

I have been checking into this issue and now I am sure that 2072 is the same
bug as 1983 (and 1947).  Please close with this info.

Thanks,
   -Don Slutz

-----Original Message-----
From: Don Slutz 
Sent: Friday, September 21, 2001 1:32 PM
To: 'Artur Grabowski'; Don Slutz
Cc: 'bugs@openbsd.org'
Subject: RE: 2.9 panic: tsleep


All I know for sure is that all xterm/telnet and console users can no longer
access any file system.  Also at some point you cannot switch console
sessions nor get into ddb.  It is true that some processes continue to
function, but my guess is that they are not using any local disks.  (ping
still works, xterm still echo characters, etc).
   -Don
P.S. Sorry about the slow respose but this e-mail got lost in the middle of
virus detected in e-mail messages.


-----Original Message-----
From: Artur Grabowski [mailto:art@blahonga.org]
Sent: Monday, September 17, 2001 6:43 PM
To: Don Slutz
Cc: 'bugs@openbsd.org'
Subject: Re: 2.9 panic: tsleep


Don Slutz <DSlutz@arrayinc.com> writes:

> >Description:
>         System hangs which leads to a "panic: tsleep" if sync requested
via
>         ddb>

Yes, boot sync is known to sometimes cause a panic. There is not much we can
do about it.

The tsleep panic is irrelevant. The question is why you have to break into
ddb and reboot the system. What do you mean that your system hangs?

//art