Subject: Re: sparc64 / 2.0.1 and thread crashes (was: Re: Ultra 5 / 2.0 / panic: lockmgr: no context)
To: Gert Doering <gert@greenie.muc.de>
From: Chuck Silvers <chuq@chuq.com>
List: port-sparc64
Date: 02/08/2005 06:46:24
On Tue, Feb 08, 2005 at 09:37:36AM +0100, Gert Doering wrote:
...
>   - rebuilt kernel with a backport of the -current thread changes
>     (the L_SA_SWITCHING stuff), rebuilt libpthreads.so with 
>     PTHREAD_MLOCK_KLUDGE.  Rebooted this kernel, waited.
> 
>     Machine did not crash "in the usual way", but it ended up being
>     unusable in other ways: 
> 
>       * "top" displayed "[ioflush]" taking 100% CPU usage (indefinite)
>       * typing "sync" made "sync" appear in top, sharing 100% CPU usage
>         with "[ioflush]" (both using 50%, obviously)
>       * trying to umount a not-in-use filesystem (to see whether it would
>         trigger anything) led to "umount" hanging, consuming CPU
>       * assuming that "clamav-milter" might be the culprit, I tried to
>         kill it.  Various signals were ignored, "kill -9" led to a kernel
>         fault:
> 
> data fault: pc=11a0434 addr=0
> kernel trap 30: data access exception
> Stopped in pid 27070.1 (kill) at        netbsd:lwp_continue+0x20:       ld              [%l0 + 0x44], %g1
> db> 

this crash is already reported as PR 26771.  I'll look into it soon.


-Chuck