From: Lee Howard <faxguy@howardsilvan.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: c-d.hailfinger.kernel.2004@gmx.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc1 breaks forcedeth
Date: Sun, 30 May 2004 15:59:01 -0700 [thread overview]
Message-ID: <20040530225901.GA2399@bilbo.x101.com> (raw)
In-Reply-To: <40BA17DF.4040706@pobox.com>; from jgarzik@pobox.com on Sun, May 30, 2004 at 10:20:31 -0700
On 2004.05.30 10:20 Jeff Garzik wrote:
> Lee Howard wrote:
>> 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.
>
>
> Well, there are zero changes to the driver itself, so I would guess
> ACPI perhaps...
>
> Try booting with 'acpi=off' or 'noapic' or 'pci=noacpi' or similar...
I didn't have ACPI built-in to the kernel. So, I added it, and then
the network started working again.
So, in 2.6.6 I didn't need ACPI to have network access, but with 2.6.7
I do. Is this a bug or a feature?
Lee.
next prev parent reply other threads:[~2004-05-30 22:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 15:57 2.6.7-rc1 breaks forcedeth Lee Howard
2004-05-30 17:20 ` Jeff Garzik
2004-05-30 22:59 ` Lee Howard [this message]
-- 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=20040530225901.GA2399@bilbo.x101.com \
--to=faxguy@howardsilvan.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.