public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Howard <faxguy@howardsilvan.com>
To: c-d.hailfinger.kernel.2004@gmx.net
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.7-rc1 breaks forcedeth
Date: Sun, 30 May 2004 08:57:15 -0700	[thread overview]
Message-ID: <20040530155715.GA2612@bilbo.x101.com> (raw)

I use the forcedeth driver for my nVidia ethernet successfully with 
kernel 2.6.6.  I recently tested 2.6.7-rc1, and when using it the 
ethernet does not work, and I see this in dmesg:

eth1: forcedeth.c: subsystem: 01043:80a7 bound to 0000:00:04.0
NETDEV WATCHDOG: eth1: transmit timed out
NETDEV WATCHDOG: eth1: transmit timed out
NETDEV WATCHDOG: eth1: transmit timed out
NETDEV WATCHDOG: eth1: transmit timed out
NETDEV WATCHDOG: eth1: transmit timed out

I can ping localhost and the device's IP number, but I cannot ping 
other systems' IP numbers.

Thanks.

Lee.

             reply	other threads:[~2004-05-30 15:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30 15:57 Lee Howard [this message]
2004-05-30 17:20 ` 2.6.7-rc1 breaks forcedeth Jeff Garzik
2004-05-30 22:59   ` Lee Howard
  -- strict thread matches above, loose matches on Subject: below --
2004-05-30 17:54 Luis Miguel García Mancebo
2004-05-30 20:47 ` Jeff Garzik
2004-05-31  0:29 jjluza
2004-06-05 23:41 Luis Miguel García Mancebo
2004-06-05 23:50 ` Linus Torvalds
2004-06-06  1:59 ktech
2004-06-06  3:14 ` Linus Torvalds
2004-06-06  8:36   ` Manfred Spraul
2004-06-06 17:04     ` Linus Torvalds
2004-06-06 18:13       ` Jeff Garzik
2004-06-06 18:21   ` Jeff Garzik
2004-06-06 18:32     ` Linus Torvalds
2004-06-06 12:10 ktech
2004-06-06 12:53 ` Vincent van de Camp
2004-06-06 13:40   ` Manfred Spraul
2004-06-06 14:17 ` Manfred Spraul
     [not found] <E1BWxTh-0002dx-KR@mb06.in.mad.eresmas.com>
2004-06-06 13:31 ` Daniel Schmitt
2004-06-06 13:49 jjluza
2004-06-16 18:40 David Mansfield

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=20040530155715.GA2612@bilbo.x101.com \
    --to=faxguy@howardsilvan.com \
    --cc=c-d.hailfinger.kernel.2004@gmx.net \
    --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