On Mon, 23 May 2005 10:43:48 -0700 (PDT)
Doug White <[EMAIL PROTECTED]> wrote:
Note: this comment goes to all participants on this mailing list, it is
not targeted specifically towards Doug.
People, would you please trim away excess / non-relevant text when you
are quoting a message?
I don't hav
> Oh another of these wonderful races... can you go to that
> frame and "print ts"? If its NULL then someone has ripped
> out the ts out from under us since it was checked for NULL in
> the previous line!
Maybe this is a more useful kgdb session (I'm hoping)
# kgdb kernel.debug /usr/local/var
; (kgdb)
Oh another of these wonderful races... can you go to that frame and "print
ts"? If its NULL then someone has ripped out the ts out from under us
since it was checked for NULL in the previous line!
>
> > -Original Message-
> > From: Doug White [mailto:[
AIL PROTECTED]
> Sent: Sunday, May 22, 2005 3:20 PM
> To: Robin P. Blanchard
> Cc: [EMAIL PROTECTED]
> Subject: Re: RELENG_5 panic
>
> On Sat, 21 May 2005, Robin P. Blanchard wrote:
>
> > # uname -a
> > FreeBSD robinpb.homeip.net 5.4-STABLE FreeBSD 5.4-ST
On Sat, 21 May 2005, Robin P. Blanchard wrote:
> # uname -a
> FreeBSD robinpb.homeip.net 5.4-STABLE FreeBSD 5.4-STABLE #0: Tue May 17
> 00:30:47 EDT 2005
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/fastipsec i386
>
> # kgdb kernel.debug /usr/local/var/adm/crash/vmcore.44
> [GDB will not be able to d
# uname -a
FreeBSD robinpb.homeip.net 5.4-STABLE FreeBSD 5.4-STABLE #0: Tue May 17
00:30:47 EDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/fastipsec i386
# kgdb kernel.debug /usr/local/var/adm/crash/vmcore.44
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined
RELENG_5 sources from yesterday.
This was after attempting a dump -L (snapshot before dump) on a
huge (5TB) gconcat filesystem while scp'ing massive amounts of data
to it. The snapshot failed with ETOOLARGE; the system became very
sluggish after that then paniced a few minutes later.
I'm keeping
