Date: Mon, 16 Aug 2004 15:44:13 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: freebsd-current@freebsd.org Subject: Re: Panic: APIC: Previous IPI is stuck (on recent current) Message-ID: <p06110406bd46bbdcb832@[128.113.24.47]> In-Reply-To: <1092682635.891.2.camel@taxman> References: <p06110405bd46a242b81d@[128.113.24.47]> <1092682635.891.2.camel@taxman>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:57 PM +0200 8/16/04, Stefan Ehmann wrote: >On Mon, 2004-08-16 at 20:23, Garance A Drosihn wrote: > > >> There is a 1-gig dump file sitting here. I don't know who would >> be the most interested in this, or what I should do with it. If >> you need more information, let me know what to do. >> >> I tried following the advice at >> >> >>http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html >> >> but that web page suggests: >> gdb -k kernel.debug /var/crash/vmcore.0 >> >> and the gdb that I have replied: >> gdb: unrecognized option `-k' > >Try kgdb instead. This should probably be fixed in the handbook. Thanks. I tried `kgdb', and it seems to work. I can get a backtrace, at least. But it would probably be better for someone who knows what they are doing to debug this. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06110406bd46bbdcb832>