linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: jfaslist <jfaslist@yahoo.fr>
Cc: linuxppc64-dev@ozlabs.org
Subject: Re: Maple freezing on PCI Target-Abort
Date: Thu, 04 May 2006 09:05:55 +1000	[thread overview]
Message-ID: <1146697555.6652.85.camel@localhost.localdomain> (raw)
In-Reply-To: <4458C89B.9070505@yahoo.fr>


> Setting the CPC925 according to item 3, fixes the problem. I give this 
> for the record, since the fix should be in PIBS, I think.
> I still don't like the fact that a user process causing the condition 
> causes the system to enter the "mon" debugger rather than being killed 
> w/ SIGBUS/SIGSEGV. I guess the correct way for a fix would be to write a 
> Maple specific machine_check exception?

Wasn't that fixed ? The current kernel will send a SIGBUS to userland.
The problem however is that in some cases, MC can be asynchronous in
which case I suppose it's possible that userland triggers a condition
that will cause a machine check later on in kernel mode. In any way,
userland direct mapping of MMIO is a root only facility...

Ben.

      parent reply	other threads:[~2006-05-03 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43E23B4A.4020402@yahoo.fr>
     [not found] ` <1138930958.4934.102.camel@localhost.localdomain>
     [not found]   ` <43E37DAC.4030606@yahoo.fr>
     [not found]     ` <1139011975.8543.4.camel@localhost.localdomain>
2006-05-03 15:13       ` Maple freezing on PCI Target-Abort jfaslist
2006-05-03 15:40         ` Segher Boessenkool
2006-05-03 23:05         ` Benjamin Herrenschmidt [this message]

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=1146697555.6652.85.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=jfaslist@yahoo.fr \
    --cc=linuxppc64-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).