From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tony.P.Lee@nokia.com
Cc: alan@lxorguk.ukuu.org.uk, kessler@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18y
Date: Fri, 15 Mar 2002 14:44:28 +0000 (GMT) [thread overview]
Message-ID: <E16lswW-0003oV-00@the-village.bc.nu> (raw)
In-Reply-To: <4D7B558499107545BB45044C63822DDE3A2037@mvebe001.NOE.Nokia.com> from "Tony.P.Lee@nokia.com" at Mar 14, 2002 06:14:23 PM
> 1) If anyone is going to add this to the kernel, please make sure
> printk_improve also log the TSC, current_process_id (if avail), etc. =20
> Very useful for performance profiling and failure analysis.
We always have a guess at the current pid (current->pid is always safe
to talk about but in an IRQ its of questionable value. Since it tells you
what was running when it blew up it does sometimes help with stack
scribbes/overruns)
> 3) After that you need to get special BIOS so that we can log the=20
> buffer to a section of memory that is preserved after reset. =20
> With this, you can easily postmortem diagnostic any problem that=20
> crash the kernel/ISR/Driver. This is much easily to do in=20
> embedded projects as compare to PC, since we control the BIOS.
I've found that a lot of the 3dfx voodoo 4/5 boards are not cleared by
the firmware on boot up. This allows you to hide about 24Mb of logs in
the top of the card ram and recover it after a soft boot.
Alan
next prev parent reply other threads:[~2002-03-15 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 2:14 [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18y Tony.P.Lee
2002-03-15 14:44 ` Alan Cox [this message]
2002-03-18 21:48 ` Larry Kessler
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 1:17 [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18 Larry Kessler
2002-03-15 1:49 ` [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18y Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16lswW-0003oV-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Tony.P.Lee@nokia.com \
--cc=kessler@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).