From: Borislav Petkov <bp@alien8.de>
To: "Francis St. Amant" <Francis.St.Amant@riverbed.com>
Cc: Borislav Petkov <bp@amd64.org>,
David Miller <davem@davemloft.net>,
"Luck, Tony" <tony.luck@intel.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Edac Mailing List <linux-edac@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 2/2] events/hw_event: Create a Hardware Anomaly Report Mechanism (HARM)
Date: Thu, 31 Mar 2011 09:43:18 +0200 [thread overview]
Message-ID: <20110331074318.GB27618@liondog.tnic> (raw)
In-Reply-To: <05E7F0869FB1C54AA467D77BC9C9E63F3FF7EEC289@MAILBOXES.nbttech.com>
On Wed, Mar 30, 2011 at 01:00:46PM -0700, Francis St. Amant wrote:
> If it's not easy from your side, I can go to our IT and ask if they
> can revive Arthur's account just to send this one unsubscribe :)
Well, if you have some idle time you could give that a try :).
> FWIW on the below email, I do agree that some way to save OOPS output
> is very useful. In our case Arthur created a special serial driver
> which wrote to EEPROM instead of console--besides not endangering the
> disk, a lot less SW has to be executed to save the data. Then we fetch
> it back on next boot.
Yeah, the problem is, we want to have this working for the majority of
machines out there. I'm assuming there should be some kind of EEPROM
memory available for BIOS to store its config or so which we could
hijack. But I don't know for sure - I'll have to research this a bit.
And besides, interfering with BIOS is almost always bound to fail.
Hmmm...
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2011-03-31 7:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1300996141.git.mchehab@redhat.com>
2011-03-24 20:32 ` [PATCH RFC 2/2] events/hw_event: Create a Hardware Anomaly Report Mechanism (HARM) Mauro Carvalho Chehab
2011-03-24 22:39 ` Borislav Petkov
2011-03-25 10:20 ` Mauro Carvalho Chehab
2011-03-25 14:13 ` Borislav Petkov
2011-03-25 21:22 ` Mauro Carvalho Chehab
2011-03-25 22:37 ` Tony Luck
2011-03-26 11:56 ` Mauro Carvalho Chehab
2011-03-28 17:03 ` Borislav Petkov
2011-03-28 19:44 ` Mauro Carvalho Chehab
2011-03-30 17:27 ` Luck, Tony
2011-03-30 17:51 ` Borislav Petkov
2011-03-30 18:30 ` Francis St. Amant
2011-03-30 19:50 ` Borislav Petkov
2011-03-30 20:00 ` Francis St. Amant
2011-03-31 7:43 ` Borislav Petkov [this message]
2012-01-26 23:05 ` [PATCH 1/3] events/hw_event: Create a Hardware Events Report Mecanism (HERM) Mauro Carvalho Chehab
2012-01-26 23:05 ` [PATCH 2/3] events/hw_event: use __string() trace macros for events Mauro Carvalho Chehab
2012-01-26 23:05 ` [PATCH 3/3] hw_event: Consolidate uncorrected/corrected error msgs into one Mauro Carvalho Chehab
2011-03-24 20:32 ` [PATCH RFC 1/2] edac: Move edac main structs to include/linux/edac.h Mauro Carvalho Chehab
2011-03-24 20:54 ` Mauro Carvalho Chehab
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=20110331074318.GB27618@liondog.tnic \
--to=bp@alien8.de \
--cc=Francis.St.Amant@riverbed.com \
--cc=bp@amd64.org \
--cc=davem@davemloft.net \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tony.luck@intel.com \
/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).