Date: Fri, 16 Jul 2004 12:21:09 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Willem Jan Withagen <wjw@withagen.nl> Cc: freebsd-current@freebsd.org Subject: Re: spin lock sched lock held by 0xffffff007b712250 for > 5 seconds Message-ID: <Pine.NEB.3.96L.1040716121933.4361A-100000@fledge.watson.org> In-Reply-To: <0b4001c46b49$d146f6d0$471b3dd4@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Jul 2004, Willem Jan Withagen wrote: > After todays kernelbuild the system seem to be a lot better... > It can take quite some buildworld abuse, but still: > > spin lock sched lock held by 0xffffff007b712250 for > 5 seconds > panic: spin lock held too long > cpuid = 1; > KDB: enter: panic > > But I'm not shure what I could/should do now, since the KDB > introduction. Normally I'd expect to see: db> We have trouble entering the debugger when in a critical section/and or have sched_lock held -- I think this is because we try to halt the other CPUs and that gets nastily stuck in some form. We need to fix this. This could well be a symptom of some of the other hangs we've been seeing, and I've seen similar things on my test box with preemption enabled. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040716121933.4361A-100000>