From: Auke Kok <auke-jan.h.kok@intel.com>
To: "Anders Grafström" <grfstrm@users.sourceforge.net>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: e100: Wait for PHY reset to complete?
Date: Tue, 31 Oct 2006 10:34:38 -0800 [thread overview]
Message-ID: <4547973E.2030704@intel.com> (raw)
In-Reply-To: <28176.212.247.11.6.1162318243.squirrel@webmail.sys.kth.se>
Anders Grafström wrote:
>>> Anders Grafström wrote:
>>>> I ran mii-diag when the LEDs went out and the register dump
>>>> said it was in loopback. It is somewhat difficult reproduce.
>>>> It seems to be timing dependent, something else has to occur
>>>> at the same time.
>>>> I must confess I have only seen it with the 2.6.13 kernel.
>>>> I have not been able to reproduce it with 2.6.18.
>>>> But I have found no change in the driver that would fix it so
>>>> I suspect the problem is still there.
>
> Now looking at mdio_ctrl(), which implements mdio_write() and mdio_read(),
> I see that this patch
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/broken-out/corruption-during-e100-mdi-register-access.patch
> most likely fixed the problem that I have experienced.
>
> "although access to the MDI registers involves
> multiple steps which must not be intermixed, nothing was defending against
> two or more threads attempting simultaneous access. The most obvious
> situation where such interference could occur involves the watchdog versus
> ioctl paths"
>
> Sorry for the noise.
cool, thanks for digging that up and taking the time to report back ;)
Auke
prev parent reply other threads:[~2006-10-31 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 17:22 e100: Wait for PHY reset to complete? Anders Grafstrom
2006-10-25 18:56 ` Francois Romieu
2006-10-25 20:18 ` Auke Kok
2006-10-25 21:26 ` Auke Kok
2006-10-25 21:57 ` Francois Romieu
2006-10-25 23:36 ` Anders Grafström
2006-10-26 1:07 ` Auke Kok
2006-10-30 19:05 ` Auke Kok
2006-10-31 18:10 ` Anders Grafström
2006-10-31 18:34 ` Auke Kok [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=4547973E.2030704@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=grfstrm@users.sourceforge.net \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 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.