Date: Fri, 16 Jul 2004 17:58:11 +0200 From: "Willem Jan Withagen" <wjw@withagen.nl> To: "Scott Long" <scottl@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: spin lock sched lock held by 0xffffff007b712250 for > 5 seconds Message-ID: <0b5b01c46b4d$b24cd4d0$471b3dd4@digiware.nl> References: <0b4001c46b49$d146f6d0$471b3dd4@digiware.nl> <40F7F97D.80801@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Scott Long" <scottl@freebsd.org> > 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> > > > > But there no way to get any response. > > Is your kernel built with both KDB and DDB? from /usr/src/amd64conf/OPTERON.amd64 # Debugging for use in -current options KDB # Enable kernel debugger support. options KDB_TRACE options DDB # Support DDB. options GDB # Support remote GDB. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b5b01c46b4d$b24cd4d0$471b3dd4>