Date: Mon, 24 Nov 2008 13:56:22 -0800 From: Sam Leffler <sam@freebsd.org> To: David Christensen <davidch@broadcom.com> Cc: "freebsd-net@FreeBSD.org" <freebsd-net@freebsd.org>, "freebsd-drivers@freebsd.org" <freebsd-drivers@freebsd.org> Subject: Re: Gathering Hardware State During a Driver Initiated Kernel Panic Message-ID: <492B2306.60404@freebsd.org> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933940B2DEFE@IRVEXCHCCR01.corp.ad.broadcom.com> References: <5D267A3F22FD854F8F48B3D2B52381933940B2DEFE@IRVEXCHCCR01.corp.ad.broadcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Christensen wrote:
> Is there a method or callback in FreeBSD where a driver can
> be notified that it has caused a kernel panic in order to
> generate a dump of internal hardware state information? I've
> written a sysctl call for manual intervention and can handle
> some "expected" hardware events completely in the driver but
> I don't know of a way to get control again in cases where the
> driver wasn't expecting a failure.
>
Not sure how one can deduce a driver is at fault but you might define a
ddb command for the driver and invoke that on panic using the ddb script
mechanisms (see ddb(4)).
Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?492B2306.60404>