Date: Sun, 24 May 1998 11:43:24 -0700 From: Mike Smith <mike@smith.net.au> To: sfarrell@farrell.org Cc: freebsd-stable <stable@FreeBSD.ORG> Subject: Re: more 2.2.6-stable crashes Message-ID: <199805241843.LAA07589@antipodes.cdrom.com> In-Reply-To: Your message of "24 May 1998 13:36:20 CDT." <87lnrrbjob.fsf@karma.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > so I'm still having serious stability problems with 2.2.6-Stable. My > last message was not very information-packed, but I'll do better this > time. One suggestion I had was to rebuild my linux LKM (as the > problem happened 100% when running linux stuff)... I've done this, and > it has not helped. ... > the trace didn't seem to useful to me, so i didn't bother to include > all the addresses: (i'm doing something wrong, right?) > > _end() > _execv() > _syscall() > _Xsyscall() > ---syscall() The trace is actually pretty critical - it would be very useful to know whereabouts in execv() it's actually exploding. > I have a 128MB core file with debugging symbols. Tell me what you > want me to do with it... Feed it to gdb, and tell us where in execv() it's falling over. Find out what it's trying to exec. If you have the core and the matching kernel executable, gzip them and put them somewhere we can get at them. -- \\ 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-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805241843.LAA07589>