From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ludo Van Put <ludo.vanput@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Oops in IDE probing on ppc_440 when PCI is enabled in strapping
Date: Tue, 15 Sep 2009 19:44:55 +1000 [thread overview]
Message-ID: <1253007895.8375.212.camel@pasglop> (raw)
In-Reply-To: <5edaeed70909150157n59745b92qe9abf2ed13147288@mail.gmail.com>
On Tue, 2009-09-15 at 10:57 +0200, Ludo Van Put wrote:
> Thnx for the suggestion, but the ide_insw is in fact of copy of the
> _insw assembly routine, and it gets passed
> the effective address, without the _IO_BASE offset.
>
> I was thinking about TLB stuff. I'm not a u-boot expert, but could it
> be that I need to tweak/reconfigure u-boot so I can access the address
> returned from ioremap64?
No. If you pass the right physical address to ioremap64, the result
should be useable as-is. The TLB entries will be faulted in
automatically by the kernel when doing accesses.
At this stage, I can't say what's wrong, it looks like you may be
accessing the wrong virtual address or something like that. Hard to
tell. It's a data access exception, not a machine check, so that means
that in some ways, the virtual address accessed by ide_insw is not
mapped by the kernel page tables, which is what the kernel TLB miss
handler uses to populate the TLB.
2.6.10 is so old, that I really have little memories of what is going on
in that area and I'm afraid am of little help here. If you have a HW
debugger such as a BDI, you may want to trace through the access, what
kind of TLB faults it generates and why the TLB miss handler doesn't
handle it.
Cheers,
Ben.
prev parent reply other threads:[~2009-09-15 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 12:36 Oops in IDE probing on ppc_440 when PCI is enabled in strapping Ludo Van Put
2009-09-14 12:51 ` Josh Boyer
2009-09-14 13:08 ` Ludo Van Put
2009-09-15 0:42 ` Benjamin Herrenschmidt
2009-09-15 8:57 ` Ludo Van Put
2009-09-15 9:44 ` 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=1253007895.8375.212.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ludo.vanput@gmail.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).