Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 2004 12:07:07 -0800 (PST)
From:      Nate Lawson <nate@root.org>
To:        Larry Rosenman <ler@lerctr.org>
Cc:        cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/alpha/alpha support.s src/sys/i386/i386    swtch.s src/sys/kern kern_shutdown.c src/sys/sys systm.h
Message-ID:  <20040120120629.J96919@root.org>
In-Reply-To: <58710000.1074628113@lerlaptop-red.iadfw.net>
References:  <200401192127.i0JLRBL3041817@repoman.freebsd.org>  <20040120144505.ccsc4kog4c88sgww@www.sweetdreamsracing.biz> <58710000.1074628113@lerlaptop-red.iadfw.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Jan 2004, Larry Rosenman wrote:
> --On Tuesday, January 20, 2004 14:45:05 -0500 Kenneth Culver
> <culverk@sweetdreamsracing.biz> wrote:
> >> Except when crashdumps don't work or are 1 GB+.  There are a few things
> >> we need:
> >>
> >> * Fix crash dumps.  I can't get a dump on my laptop, ATA.
> >>
> >> * Sparse crash dumps.  We don't need non-anonymous pages, for instance.
> >>
> >> * Fix GDB backtrace output (patch posted by gallatin@ and obrien@ may be
> >> working on integrating it.)
> >>
> >> * Fix backtrace() so the output goes to the console log.  Right now, we
> >> get output that needs to be hand-transcribed or use a serial console.
> >
> > This is also very useful for when FreeBSD crashes when X is running. If X
> > is running, the only option is a serial console, as you can't see the
> > crash to transcribe it otherwise, and most people don't have the spare
> > computer to use as a serial console.
>
> Or worse, as in my Laptop, NO SERIAL PORT AT ALL :-)

Yes, your ACPI crash debugging was a real Pain In The Butt.

-Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040120120629.J96919>