All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] BUG 2.6.12-rc3-pa1 PCI mmap panic
Date: Mon, 02 May 2005 09:51:50 -0500	[thread overview]
Message-ID: <1115045510.5006.7.camel@mulgrave> (raw)
In-Reply-To: <20050502041244.GA1601@colo.lackof.org>

On Sun, 2005-05-01 at 22:12 -0600, Grant Grundler wrote:
>         Memory at c0800000 (64-bit, non-prefetchable) [size=1M]
>         Memory at c0000000 (64-bit, prefetchable) [size=8M]

Exactly ... that's the 3rd gigabyte; I assume there's no physical memory
there, so the pfnnid_map is 0xff (except the bit where the io region
check works).

However, there's a total screw up here: 0xc0000000 is outside of our
premapped I/O region (0xf0000000-0xffffffff) so one of our assumptions
about pa is broken; either the mercury doesn't obey the I/O window rules
and we need to update the OS, or the card has the wrong address.

> Now the system just resets. No tombstone of any kind. :^(
[...]
> CPU0 IOAQ 0x1010aadc $$remoI+350
> CPU0 GR02 0x1010d110 __udivdi3+198
> 
> CPU1 IOAQ 0x101011b0 flush_data_cache_local+8
> CPU1 GR02 0x10113b04 update_mmu_cache+94
> 
> 
> Looks like CPU1 died right away trying to flush an uncacheable region.
> No surprise that didn't work too well.
> 
> And no clue what's up with CPU0.

CPU0 was probably executing a different thread when it was halted by the
HPMC.

flushing an uncacheable area doesn't cause a HPMC, but flushing a non-
existent (and non-responding) area would ...

James


_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-05-02 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01  7:49 [parisc-linux] BUG 2.6.12-rc3-pa1 PCI mmap panic Grant Grundler
     [not found] ` <4274FC81.4060906@tiscali.be>
2005-05-01 17:24   ` Grant Grundler
2005-05-01 19:24 ` James Bottomley
2005-05-02  0:08   ` Grant Grundler
2005-05-02  0:31     ` James Bottomley
2005-05-02  4:12       ` Grant Grundler
2005-05-02 14:51         ` James Bottomley [this message]
2005-05-02 16:00           ` Grant Grundler

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=1115045510.5006.7.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.