From: "Jon Nelson" <jnelson@jamponi.net>
To: "Michael Chan" <mchan@broadcom.com>
Cc: "Jarek Poplawski" <jarkao2@o2.pl>,
netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: tg3: strange errors and non-working-ness
Date: Thu, 15 Nov 2007 14:21:01 -0600 [thread overview]
Message-ID: <cccedfc60711151221p322894f8i94c540fefb0e4827@mail.gmail.com> (raw)
In-Reply-To: <1195158200.6360.17.camel@dell>
On 11/15/07, Michael Chan <mchan@broadcom.com> wrote:
> On Thu, 2007-11-15 at 13:17 -0600, Jon Nelson wrote:
>
> > Is this what you mean? I pulled this from the quoted text:
> >
> > Nov 10 22:45:52 frank kernel: NETDEV WATCHDOG: eth0: transmit timed out
> >
>
> Right. This explains the reset at 22:45:52, but not the earlier reset
> at 22:24:40. Link never came up after that earlier reset.
>
> Is this a new problem introduced by a new driver? I notice you are
> using tg3 3.65. Have you used newer versions or older versions?
This is not a new problem - these cards have done this or something
like it for as long as I've had them*. They work just fine in 100 MBit
mode but not in all of my machines, and in none of them at gig-e.
I've tried every version of the driver since SUSE 9.1 without much
luck (at least as far back as 2.6.9). I'd try a newer driver, esp. if
I could make it compile on 2.6.22.12 (I prefer but do not require to
stay with the stock distro kernel, modules notwithstanding).
NOTE: to avoid list noise, I can make a bug out of this on
bugzilla.kernel.org and we can proceed from there if that is
preferred.
[*] Actually, they worked OK in 2.4.something way-back-when but only
for short durations at gig-e speeds.
--
Jon
next prev parent reply other threads:[~2007-11-15 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cccedfc60711131057y41630b99h44e1c611f3e92fda@mail.gmail.com>
2007-11-15 9:47 ` Jarek Poplawski
2007-11-15 19:23 ` Michael Chan
2007-11-15 19:17 ` Jon Nelson
2007-11-15 20:23 ` Michael Chan
2007-11-15 20:21 ` Jon Nelson [this message]
2007-11-15 22:11 ` Jarek Poplawski
2007-11-16 2:12 ` Jon Nelson
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=cccedfc60711151221p322894f8i94c540fefb0e4827@mail.gmail.com \
--to=jnelson@jamponi.net \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.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
all inboxes | Powered by JetHome®