On Wed, May 15, 2002 at 05:05:01PM -0500, Lista de NetBSD Users wrote:
> On Wed, 15 May 2002, Manuel Bouyer wrote:
> > On Tue, May 14, 2002 at 10:23:12PM -0500, Lista de NetBSD Users wrote:
> > > My server is active yet and the problem occurs in this moment,
> > > but the kernel was not compiled with DDB and I cant have root
> > > access.
> >
> > Check if syslogd is taking a significant amout of CPU (with top for
> > example); if it does not then it's another problem.
> 
> I hope this give some answer.
> 
> Thanks
> 
> Heron Gallegos
> 
> load averages:  0.20,  0.19,  0.17                                                      16:37:38
> 13 processes:  12 sleeping, 1 on processor
> CPU states:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
> Memory: 4800K Act, 1696K Inact, 144K Wired, 103M Free, 512M Swp free
> 
>   PID USERNAME PRI NICE   SIZE   RES STATE     TIME   WCPU    CPU COMMAND
>   207 root      10    0   220K  420K sleep     0:06  0.00%  0.00% cron
>  5351 root       2    0   344K 1184K sleep     0:05  0.00%  0.00% sshd
>   117 root       4    0   104K  408K sleep     0:03  0.00%  0.00% syslogd

Hum, it looks like it doens't use any CPU at this point, to it's likely not
the same bug.
Could you, when this occurs again
1) do a ps -axl and post the syslog line 
2) keep a root shell around a kill -ABRT syslogd, to get a core dump ?

BTW, killing syslogd should make things working again

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--