linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: When are machine checks suppose to be recoverable?
Date: Thu, 18 Aug 2005 07:44:47 +1000	[thread overview]
Message-ID: <1124315089.8857.41.camel@gaston> (raw)
In-Reply-To: <76E28B16-5706-48C8-B92A-349C4F40FA76@freescale.com>

On Wed, 2005-08-17 at 09:00 -0500, Kumar Gala wrote:
> David's 8250 cleanup patch made me wondering when are machine checks  
> suppose to recoverable?  General class of conditions is what I'm  
> looking for here.
> 
> Is David's case due to some PCI master abort or something else?

Might be some issue on SMP machines... 

Ben.

  reply	other threads:[~2005-08-17 21:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 16:21 [PATCH] Use platform device for 8250 registration David Woodhouse
2005-08-17  6:30 ` Kumar Gala
2005-08-17  6:34   ` Benjamin Herrenschmidt
2005-08-17  7:31   ` David Woodhouse
2005-08-17 13:54     ` Kumar Gala
2005-08-17 15:05     ` Tom Rini
2005-08-17 15:22       ` Kumar Gala
2005-08-17 15:30         ` Tom Rini
2005-08-17 16:16           ` Kumar Gala
2005-08-17 16:27             ` Matt Porter
2005-08-17 16:35               ` Tom Rini
2005-08-17 16:27             ` Tom Rini
2005-08-17 11:11 ` Russell King
2005-08-17 16:39   ` David Woodhouse
2005-08-17 16:46     ` Russell King
2005-08-17 14:00 ` When are machine checks suppose to be recoverable? Kumar Gala
2005-08-17 21:44   ` Benjamin Herrenschmidt [this message]
2005-08-17 22:30     ` David Woodhouse
2005-08-18  3:42       ` Kumar Gala
2005-08-23  2:56         ` Marcelo Tosatti
2005-08-23 16:43           ` David Woodhouse
2005-08-23 17:04             ` Kumar Gala
2005-08-23 23:10               ` David Woodhouse

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=1124315089.8857.41.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=dwmw2@infradead.org \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).