Date: Fri, 28 Oct 2005 17:06:14 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: bharmaji@gmail.com Cc: freebsd-drivers@freebsd.org Subject: Re: Recommended ways to log driver operations Message-ID: <20051028.170614.58438314.imp@bsdimp.com> In-Reply-To: <67beabb0510281557k5d237a0br9b586bdde35c6971@mail.gmail.com> References: <67beabb0510171825q1e124bf6v2adbe0c9f235a6ae@mail.gmail.com> <20051017.210955.104032631.imp@bsdimp.com> <67beabb0510281557k5d237a0br9b586bdde35c6971@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <67beabb0510281557k5d237a0br9b586bdde35c6971@mail.gmail.com>
Bharma Ji <bharmaji@gmail.com> writes:
: Resurrecting a recent thread...
: Thanks for your resposne. ktr and alq are unfortunately not availabe on the
: freebsd version that I am using.
: I have reduced my requirements for the logging facility. Now all I require
: is that the log be persistent. The problem that I face is that in the event
: of a kernel panic - the driver messages are all lost.Is there a way to write
: the messages to the disk while the driver is executing.(seems to much to ask
: probably - but someone somewhere would have thought of a way around it)
If all you want is for them to be persistant, then printf will put
them into the dmesg buffer which you can extract via the debugger from
either a core file or a live system that's paniced. If there's
sufficient time between the last printf and a panic, then syslog will
have flushed it to disk...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051028.170614.58438314.imp>