[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cccedfc60711151221p322894f8i94c540fefb0e4827@mail.gmail.com>
Date: Thu, 15 Nov 2007 14:21:01 -0600
From: "Jon Nelson" <jnelson@...poni.net>
To: "Michael Chan" <mchan@...adcom.com>
Cc: "Jarek Poplawski" <jarkao2@...pl>, netdev <netdev@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: tg3: strange errors and non-working-ness
On 11/15/07, Michael Chan <mchan@...adcom.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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists