Blue G3 and machine check

[Benjamin Herrenschmidt]

On Thu, Mar 25, 1999, Paul Mackerras <paulus at 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 at 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.   ]]