Subject: Re: -current kernel hangs on amd64
To: Mindaugas R. <rmind@netbsd.org>
From: Kurt Schreiner <ks@ub.uni-mainz.de>
List: current-users
Date: 10/10/2007 22:26:49
Hi,

On Wed, Oct 10, 2007 at 05:54:22PM +0300, Mindaugas R. wrote:
> Hi,
> 
> Kurt Schreiner <ks@ub.uni-mainz.de> wrote:
> > Hi,
> > 
> > trying "build.sh -j 8 ..." w/ a kernel build from -current
> > cvs update'd an hour or so ago (userland two or three weeks
> > old) and using the new scheduler results in:
> > 
> > NetBSD/amd64 (isunopti) (console)
> > 
> > login: Stopped in pid 8208.1 (nbmake) at       netbsd:breakpoint+0x1:  ret
> > db{0}> bt
> > breakpoint() at netbsd:breakpoint+0x1
> > Xintr_ioapic_edge4() at netbsd:Xintr_ioapic_edge4+0xd7
> > --- interrupt ---
> > mutex_spin_retry() at netbsd:mutex_spin_retry+0x65
> > sched_nextlwp() at netbsd:sched_nextlwp+0xcc
> > mi_switch() at netbsd:mi_switch+0x1d5
> > sleepq_block() at netbsd:sleepq_block+0x11a
> > cv_wait_sig() at netbsd:cv_wait_sig+0x124
> > pipe_read() at netbsd:pipe_read+0x32d
> > dofileread() at netbsd:dofileread+0x89
> > sys_read() at netbsd:sys_read+0x99
> > syscall_plain() at netbsd:syscall_plain+0x1cb
> > 
> > Here the machine hangs hard and has to be power cycled...
> 
> Have you compiled the kernel with LOCKDEBUG and DIAGNOSTIC options? It would
> be good to see what is the output of "show sched" in DDB, if possible.
Not yet, I'll do that tomorrow (at work) and post the "results". The hang can
be reproduced very easy by just doing "build.sh -j 8 ..." (tried this afternoon
-after userland was build.sh'ed -j8 running a kernel with the old scheduler w/o
problems- output of bt was the same, but I've had no time to investigate further).

Kurt