linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: gewrgiou@imbc.gr
Cc: rshapiro@bbn.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: beige g3 rage II xf4.0.1 and miBoot
Date: Thu, 28 Sep 2000 23:07:30 +0200 (CEST)	[thread overview]
Message-ID: <200009282107.XAA00763@piglet.grunz.lu> (raw)
In-Reply-To: <Pine.LNX.4.21.0009282015220.15193-100000@idd-01.imbc.gr>


On  28 Sep, this message from Kostas Gewrgiou echoed through cyberspace:
> PS> Any ideas why writing to a disabled pci device in ppc crashes
> the machine but not the x86 ones ? Is this something that can be fixed
> in the kernel or an arch thing ?

Accessing config registers or device resources?

Accessing config registers should work ok, if not, there's something
_really_ wrong somewhere.

Accessing resources that are not enabled, yes, you get a machine check,
because the device will not answer your accesses, so the bus will hit a
timeout, which will be signaled to the processor (was that a PCI master
abort?), in a way that the processor will throw a machine check
exception.

And that machine check exception is not recovered from (would that even
be possible?), hence a plain old kernel panic.

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-09-28 21:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-28 15:03 beige g3 rage II xf4.0.1 and miBoot R Shapiro
2000-09-28 17:23 ` Kostas Gewrgiou
2000-09-28 19:25   ` Geert Uytterhoeven
2000-09-28 21:07   ` Michel Lanners [this message]
2000-09-28 22:57     ` Benjamin Herrenschmidt
2000-09-29 19:27     ` Michael Schmitz
2000-09-29 17:33   ` Michael Schmitz
2000-09-29 19:09     ` Michel Dänzer
2000-09-29 19:44       ` Michael Schmitz
2000-09-30 13:51         ` Kostas Gewrgiou
2000-10-01 17:05           ` Michael Schmitz
2000-10-02  9:52             ` Michel Dänzer
2000-10-02 13:24               ` Michael Schmitz
2000-09-28 21:31 ` Claus
2000-09-28 21:59   ` R Shapiro
2000-09-29  7:51     ` Timothy A. Seufert
2000-09-29  2:13 ` Ethan Benson

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=200009282107.XAA00763@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=gewrgiou@imbc.gr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=rshapiro@bbn.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).