From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch] 2.6.0 MCA TLB error recovery
Date: Fri, 19 Dec 2003 18:07:04 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107185743501256@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107181047921141@msgid-missing>
> >It looks like salinfo_log_wakeup() is called right before
> >ia64_log_print() ... so I'm not sure why the salinfo_decode
> >daemon kept on snoozing. Keith: am I missing something obvious?
>
> From the top of salinfo_log_wakeup()
>
> * ... MCA and INIT events are
> * not irq safe, do not call any routines that use spinlocks,
> they may deadlock.
Okay ... that was pretty danged obvious! Thanks for pointing
it out so gently :-)
> MCA and INIT records are noted but it is not safe to call up() from
> those interrupts, so the daemon cannot be woken. This has not been a
> problem in the past because MCA and INIT were not recoverable, the
> records are picked up on the next boot. Once my patches are
> in David's
> tree, I will update salinfo to periodically check for any MCA or INIT
> records and kick the daemon. There was no point before, I had no way
> of testing this case.
Sounds good. Salinfo-0.4 is beautiful by the way. Getting all the
bits decoded from processor state parameter and ipsr/xpsr etc. is great.
-Tony
next prev parent reply other threads:[~2003-12-19 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 5:06 [patch] 2.6.0 MCA TLB error recovery Keith Owens
2003-12-19 18:07 ` Luck, Tony [this message]
2003-12-19 23:22 ` David Mosberger
2003-12-20 0:03 ` Luck, Tony
2003-12-20 0:04 ` Luck, Tony
2003-12-20 0:26 ` Keith Owens
2003-12-20 0:32 ` David Mosberger
2003-12-20 2:56 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 23:37 Luck, Tony
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=marc-linux-ia64-107185743501256@msgid-missing \
--to=tony.luck@intel.com \
--cc=linux-ia64@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