linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Brice Figureau <brice@tincell.com>
Cc: "Linuxppc-Dev@Lists.                  " "Linuxppc. Org"
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: ibook2r2 & strange freeze.
Date: 27 Apr 2003 01:14:32 +0200	[thread overview]
Message-ID: <1051398872.8435.15.camel@gaston> (raw)
In-Reply-To: <97719C92-7839-11D7-A81D-0003939D5F18@tincell.com>


> > Ah, that's a machine check... interesting. So either the address above
> > is bogus, or the card is crashed. In this later case, noaccel should
> > have helped, except if, for some reason, the argument was ignored
> > when setting the initial mode...
> Since the address does not seem to be bogus, could it be possible that
> my computer is broken in a certain way ? (bad memory...).
> I'll do another noaccel check.

Well, it's weird... It seems the ATI chip isn't anwsering on the bus on
a specific access.

Are you sure of that specific bit of disassembly ?

c0184554 380b0e40 addi  r0,r11,3640

Is't it 3648 instead ? (the opcode seem to indicate that). In this case,
the problem is that we are getting a machine check in radeon_fifo_wait()
while reading RBBM_STATUS register.

I have absolutely no idea what can cause this (but bad HW ?) in xmon,
if you first check out r0 (it may not be d9000000 again ...) and then
do "m d9000000.l" (or replace d9000000 by whatever it has become) and
finally tell me if you atually read a value or not.

I completely fail to understand why a problem like this would happen
with -ben9 and not -ben8. Are you absolutely sure you properly tried
-ben9 with the radeonfb from -ben8 ?

Ben.


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

  reply	other threads:[~2003-04-26 23:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 15:27 ibook2r2 & strange freeze Brice Figureau
2003-04-25 17:43 ` Benjamin Herrenschmidt
2003-04-25 17:50   ` Benjamin Herrenschmidt
2003-04-25 20:05     ` Brice Figureau
2003-04-25 23:00     ` Brice Figureau
2003-04-26 10:33       ` Benjamin Herrenschmidt
2003-04-26 20:22         ` Brice Figureau
2003-04-26 20:35           ` Benjamin Herrenschmidt
2003-04-26 20:51             ` Brice Figureau
2003-04-26 21:01               ` Benjamin Herrenschmidt
2003-04-26 22:08                 ` Brice Figureau
2003-04-26 22:13                   ` Benjamin Herrenschmidt
2003-04-26 22:32                     ` Brice Figureau
2003-04-26 22:40                       ` Benjamin Herrenschmidt
2003-04-26 22:51                         ` Brice Figureau
2003-04-26 23:14                           ` Benjamin Herrenschmidt [this message]
2003-04-27 12:39                             ` Brice Figureau
2003-04-25 20:12 ` Remco Treffkorn
2003-04-25 22:55   ` Brice Figureau
2003-04-26  7:08   ` Mich Lanners

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=1051398872.8435.15.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=brice@tincell.com \
    --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).