From: Karen Shaeffer <shaeffer@neuralscape.com>
To: Ayaz Abdulla <AAbdulla@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
jgarzik@pobox.com, manfred@colorfullife.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] forcedeth: msi interrupts
Date: Sat, 7 Jun 2008 18:33:12 -0700 [thread overview]
Message-ID: <20080608013312.GA19130@synapse.neuralscape.com> (raw)
In-Reply-To: <F72FA20C31DD4F4C997B91C5B3690A090B146108@hqemmail07.nvidia.com>
On Sat, Jun 07, 2008 at 12:28:35PM -0700, Ayaz Abdulla wrote:
> Karen,
>
> Is the switch in forced mode? That would explain the mismatch. I can
> look into a fix to workaround the hang.
>
> Please open a bugzilla bug as you recommend. Emails get deleted after a
> couple of weeks and it is better to have a permanent location to track
> issues like this.
>
> Thanks,
> Ayaz
Hi Ayaz,
Thank you for responding.
No, the switch vlan port is configured for 100 Mb autoneg on. The NIC
is configured with a boot time script using ethtool for 100 Mb autoneg on.
The result is always the same. The switch port links at 100 Mb full duplex,
and the NIC links at 100 Mb half duplex.
One can configure the NIC for 100 Mb autoneg off full duplex. And then
the link mismatch does not occur. And I have never seen the failure
in this case. But end users in the field sometimes just don't pay attention
and end up with the mismatch, so the failure was first discovered by an
end user.
At 1000 Mb, the link mismatch never happens. I've only seen this failure at
100 Mb.
The bug has been opened with ID 10885. I don't work with that project anymore,
but I'll definitely follow up with the appropriate folks, when this issue
is resolved. I am sure they will be very interested in a resolution.
Thanks,
Karen
--
Karen Shaeffer
Neuralscape, Palo Alto, Ca. 94306
shaeffer@neuralscape.com http://www.neuralscape.com
next prev parent reply other threads:[~2008-06-08 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 20:51 [PATCH] forcedeth: msi interrupts Ayaz Abdulla
2008-06-04 22:18 ` Andrew Morton
2008-06-04 23:00 ` Karen Shaeffer
2008-06-06 17:15 ` Ayaz Abdulla
2008-06-06 20:19 ` Andrew Morton
2008-06-06 18:04 ` Ayaz Abdulla
2008-06-06 21:10 ` Andrew Morton
2008-06-06 21:19 ` Ayaz Abdulla
2008-06-06 21:40 ` Karen Shaeffer
2008-06-07 18:31 ` Karen Shaeffer
2008-06-07 19:28 ` Ayaz Abdulla
2008-06-08 1:33 ` Karen Shaeffer [this message]
2008-06-08 2:01 ` Karen Shaeffer
2008-06-07 19:24 ` Ayaz Abdulla
2008-06-06 18:03 ` Ayaz Abdulla
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=20080608013312.GA19130@synapse.neuralscape.com \
--to=shaeffer@neuralscape.com \
--cc=AAbdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=manfred@colorfullife.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).