From: Benjamin Herrenschmidt <bh40@calva.net>
To: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org
Subject: Re: Blue G3 and machine check
Date: Thu, 25 Mar 1999 13:10:50 +0100 [thread overview]
Message-ID: <19990325131050.003668@mail.mipsys.com> (raw)
In-Reply-To: <199903242312.KAA31937@tango.anu.edu.au>
On Thu, Mar 25, 1999, Paul Mackerras <paulus@cs.anu.edu.au> wrote:
>Did the original poster say whether the machine checks were on config
>space accesses or I/O or memory space accesses? It's common enough
>for drivers written for intel linux to go probing I/O ports to try to
>find devices to talk to.
The original poster wrote that the machine check happens when reading
config space on a non-existent device thru the PCI<->PCI bridge. The
proposed fix was simply to add two globals "machine_check_expected" and
"machine_check_received". The first one set to true before the probe, and
the machine check exception handler incrementing the second one when the
first one is true.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-03-25 12:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 13:35 Blue G3 and machine check Benjamin Herrenschmidt
1999-03-15 16:42 ` Ryuichi Oikawa
1999-03-15 17:09 ` Geert Uytterhoeven
1999-03-24 9:30 ` Gabriel Paubert
1999-03-24 23:12 ` Paul Mackerras
1999-03-25 11:20 ` Gabriel Paubert
1999-03-25 16:46 ` Apple Job Posting and Good News for LinuxPPC developers Kevin B. Hendricks
1999-03-25 19:12 ` David Edelsohn
1999-03-26 11:31 ` Gabriel Paubert
1999-03-26 16:13 ` David Edelsohn
1999-03-27 6:27 ` Guy Sotomayor
1999-03-27 20:44 ` David Edelsohn
1999-04-02 12:11 ` Holger Bettag
1999-04-02 17:11 ` David Edelsohn
1999-04-02 22:19 ` Douglas Godfrey
1999-04-03 17:42 ` Holger Bettag
1999-04-05 16:11 ` Gabriel Paubert
1999-04-05 16:06 ` Gabriel Paubert
1999-04-06 5:53 ` Douglas Godfrey
1999-03-26 6:08 ` Nathan Hurst
1999-03-26 13:51 ` sean o'malley
1999-03-28 5:08 ` Cort Dougan
1999-03-26 20:33 ` N.G. Temme
1999-03-29 23:44 ` Blue G3 and machine check Paul Mackerras
1999-03-30 11:41 ` Gabriel Paubert
1999-03-31 16:20 ` Ryuichi Oikawa
1999-03-31 18:39 ` Gabriel Paubert
1999-04-05 16:36 ` Ryuichi Oikawa
1999-04-05 17:11 ` Gabriel Paubert
1999-04-04 1:17 ` Joel Klecker
1999-04-09 5:58 ` Joel Klecker
1999-04-09 16:12 ` Ryuichi Oikawa
1999-03-25 12:10 ` 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=19990325131050.003668@mail.mipsys.com \
--to=bh40@calva.net \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.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).