Date: Sat, 15 Jan 2000 15:26:25 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Alexander Leidinger <Alexander@leidinger.net> Cc: peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: crash with ffs_softdep.c 1.52 Message-ID: <20000115152625.T508@fw.wintelcom.net> In-Reply-To: <200001151911.UAA01264@Magelan.Leidinger.net>; from Alexander@leidinger.net on Sat, Jan 15, 2000 at 08:11:35PM %2B0100 References: <20000115150138.25C5D1CD4@overcee.netplex.com.au> <200001151911.UAA01264@Magelan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Alexander Leidinger <Alexander@leidinger.net> [000115 12:17] wrote:
> On 15 Jan, Peter Wemm wrote:
> > Alfred Perlstein wrote:
> >> * Alexander Leidinger <Alexander@Leidinger.net> [000115 06:17] wrote:
> >> > Hi,
> >> >
> >> > unfortunally no core dump, but I'm able to reproduce it (I just have to
> >> > enable softupdates).
> >>
> >> how? It looks like splbio is not up but the softdep lock is held.
>
> ^^^^
> I just have to enable softupdates on /home, /var, /usr, /usr/obj to
> get a panic at "Additional daemons: syslogd" while booting.
> If I disable softupdates at /var I'm able to log in (X11) and dial out
> -> panic (because of fetchnews/fetchmail/whatever are accessing
> something).
>
> > The best thing is to look at this global variable for lkt_held:
> > static struct lockit {
> > int lkt_spl;
> > pid_t lkt_held;
> > } lk;
> >
> > and see which process held the lock. Do a traceback on that process as well..
>
> How do I do this with _DDB_ (step by step please, I'm not very
> experienced with it), I get no core dump? Do I have to boot a
> debug-kernel?
http://www.freebsd.org/handbook/kerneldebug.html
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000115152625.T508>