From: Felix Radensky <felix@embedded-sol.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Machine check in 4xx ethernet driver
Date: Mon, 9 Mar 2009 08:00:50 -0700 (PDT) [thread overview]
Message-ID: <22413434.post@talk.nabble.com> (raw)
In-Reply-To: <20090309111436.GA2256@yoda.jdub.homelinux.org>
Josh Boyer-4 wrote:
>
> On Mon, Mar 09, 2009 at 03:53:25AM -0700, Felix Radensky wrote:
>>
>>
>>
>>Josh Boyer-4 wrote:
>>>
>>> On Mon, Mar 09, 2009 at 12:47:02AM -0700, Felix Radensky wrote:
>>>>
>>>>Hi,
>>>>
>>>>I'm getting machine check exception when trying to dump
>>>>emac registers on 405EX Kilauea board. The kernel is 2.6.29-rc7
>>>>The problem seems not new, I can reproduce it on 2.6.25 Denx kernel
>>>
>>> I've not looked at what that code path does, but the EMAC regs are
>>> in DCR space, not MMIO. Using memcpy_fromio there seems odd.
>>>
>>>
>>
>>At least on 405EX MAL registers are in DCR space, but EMAC and RGMII
>>ones are in MMIO space.
>
> Ah, quite right. No coffee yet this morning.
>
> You'll need to look at the code path ethtool is forcing. Perhaps it's
> doing
> something stupid.
>
>
Bad quoting in previous message, sorry.
The problem goes away if I replace memcpy_fromio() by memcpy().,
but register values seem wrong. Why would memcpy() work when
memcpy_fromio() doesn't ?
--
View this message in context: http://www.nabble.com/Machine-check-in-4xx-ethernet-driver-tp22408005p22413434.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2009-03-09 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 7:47 Machine check in 4xx ethernet driver Felix Radensky
2009-03-09 10:38 ` Josh Boyer
2009-03-09 10:53 ` Felix Radensky
2009-03-09 11:14 ` Josh Boyer
2009-03-09 13:13 ` Felix Radensky
2009-03-09 15:00 ` Felix Radensky [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=22413434.post@talk.nabble.com \
--to=felix@embedded-sol.com \
--cc=linuxppc-dev@ozlabs.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).