Date: Mon, 08 Feb 1999 16:16:52 -0800 From: Mike Smith <mike@smith.net.au> To: tcobb@staff.circle.net Cc: current@FreeBSD.ORG Subject: Re: Tracking a Fatal Double Fault Message-ID: <199902090016.QAA01652@dingo.cdrom.com> In-Reply-To: Your message of "Mon, 08 Feb 1999 19:12:11 EST." <A0CFA284C004D211B7EE0060082F32A412E142@freya.circle.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> The machine is running a custom kernel, but nothing > very unusual. My instinct is that it may be related to > something with the 3c905B 3COM cards that I reported > earlier, I'm trying with Intel EtherExpresses right now > and getting no fault problems. > > The double-fault does not occur consistently, unfortunately, > and typically only occurs during my rc.local stuff (loading > a bunch (100+) of chrooted daemons) on boot-up. > > Would the eip/esp/ebp values be worth sending? They're meaningless without your kernel, but even then all you're going to be able to tell is where in the fault handler things died; you won't know the address of the original fault. There's nothing immediately obvious in the xl driver that would suggest that it uses excessive kernel stack either. 8( Maybe someone has some clues on measuring stack usage (or simply on how to increase the kernel stack allocation...). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199902090016.QAA01652>