From: Pete Clements <clem@clem.clem-digital.net>
To: akpm@osdl.org (Andrew Morton)
Cc: clem@clem.clem-digital.net (Pete Clements),
klassert@mathematik.tu-chemnitz.de, linux-kernel@vger.kernel.org
Subject: Re: Correction: 2.6.16-git12 killed networking -- 3c900 card
Date: Wed, 29 Mar 2006 10:15:03 -0500 (EST) [thread overview]
Message-ID: <200603291515.k2TFF3GM001689@clem.clem-digital.net> (raw)
In-Reply-To: <20060328230132.52c79c6c.akpm@osdl.org>
Patch applied on top of previous patch to 2.6.16, no longer
seeing the timeouts.
> Pete Clements <clem@clem.clem-digital.net> wrote:
> >
> > Quoting Steffen Klassert
> > > > Had several of these with git11
> > > > NETDEV WATCHDOG: eth0: transmit timed out
> > >
> > > Is this for sure that these messages occured first time with git11?
> > > There were no changes in the 3c59x driver between git10 and git11.
> > >
> > Tried 2.6.15 and could not get a timed out condition. Looks like
> > that defect is between 15 and 16 in my case.
> >
> > Be glad to do any testing that I can.
>
> If it's noether of those then I'd expect the problem relates to the
> conversion to use the standard mii layer. Possibly we need to re-port some
> mdo reading oddity into 3c59x.c:mdio_read(), but it would take some effort
> to work out which one.
>
> You could try this shot-in-the-dark:
>
>
> diff -puN drivers/net/3c59x.c~revert-3c59x-avoid-blindly-reading-link-status-twice drivers/net/3c59x.c
> --- devel/drivers/net/3c59x.c~revert-3c59x-avoid-blindly-reading-link-status-twice 2006-03-28 22:51:52.000000000 -0800
> +++ devel-akpm/drivers/net/3c59x.c 2006-03-28 23:00:47.000000000 -0800
> @@ -3196,7 +3196,7 @@ static void mdio_sync(void __iomem *ioad
> }
> }
>
> -static int mdio_read(struct net_device *dev, int phy_id, int location)
> +static int __mdio_read(struct net_device *dev, int phy_id, int location)
> {
> int i;
> struct vortex_private *vp = netdev_priv(dev);
> @@ -3227,6 +3227,13 @@ static int mdio_read(struct net_device *
> return retval & 0x20000 ? 0xffff : retval>>1 & 0xffff;
> }
>
> +static int mdio_read(struct net_device *dev, int phy_id, int location)
> +{
> + if (location == MII_BMSR)
> + __mdio_read(dev, phy_id, location);
> + return __mdio_read(dev, phy_id, location);
> +}
> +
> static void mdio_write(struct net_device *dev, int phy_id, int location, int value)
> {
> struct vortex_private *vp = netdev_priv(dev);
> _
>
--
Pete Clements
next prev parent reply other threads:[~2006-03-29 15:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 2:12 Pete Clements
2006-03-28 14:14 ` Steffen Klassert
2006-03-28 16:44 ` Pete Clements
2006-03-29 11:47 ` Steffen Klassert
2006-03-29 14:27 ` Pete Clements
2006-03-29 1:12 ` Pete Clements
2006-03-29 2:50 ` Pete Clements
2006-03-29 6:43 ` Andrew Morton
2006-03-29 9:14 ` Steffen Klassert
2006-03-29 14:39 ` Pete Clements
2006-03-29 6:49 ` Andrew Morton
2006-03-29 14:49 ` Pete Clements
2006-03-29 19:29 ` Andrew Morton
2006-03-30 0:53 ` Pete Clements
2006-03-30 1:10 ` Andrew Morton
2006-03-30 1:19 ` Pete Clements
2006-03-30 4:51 ` Pete Clements
2006-03-30 5:09 ` Andrew Morton
2006-03-30 13:46 ` Pete Clements
2006-03-30 14:29 ` Steffen Klassert
2006-03-30 16:02 ` Pete Clements
2006-03-29 7:01 ` Andrew Morton
2006-03-29 15:15 ` Pete Clements [this message]
2006-03-29 1:07 ` Pete Clements
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=200603291515.k2TFF3GM001689@clem.clem-digital.net \
--to=clem@clem.clem-digital.net \
--cc=akpm@osdl.org \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®