From: "John Bäckstrand" <sandos@home.se>
To: "'Zwane Mwaikambo'" <zwane@arm.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [BUG] R8169 on 2.6.0-test9
Date: Mon, 27 Oct 2003 11:37:00 +0100 [thread overview]
Message-ID: <070c01c39c76$4579ccb0$034d210a@sandos> (raw)
In-Reply-To: <Pine.LNX.4.53.0310261954230.20169@montezuma.fsmlabs.com>
>> >The r8169 gigabit ethernet card causes lockups on both 2.4.22 and
>> 2.6.0-test9.
>>
>> It does it even on 2.4.20 and using the 8139cp. Heres lspci -vvv,
>> starting to wonder if this card is special/odd/unsupported or if its
>> just this hardware not being happy.
>
>This is bug report is somewhat confusing, are you using r8169.c
>(CONFIG_R8169)?
I have tried the r8169 driver on 2.4.22 and 2.6.0-test9, and r8139cp on
2.4.20. On 2.4.22, it printed "too much work at interrupt" forever after
3-60 seconds of connection to a lan. I commented the printk out, that didnt
help though. The behaviour is exactly the same on 2.6.0-test9 and 2.4.20, a
few seconds after "ifconfig eth1 up" the machine hangs, though on 2.4.20
atleast there was no printk message seen. ifconfig shows it does receive and
send a few packets before it hangs, atleast on 2.4.22. The 8169 cards have
been confirmed to be working, but not on this particular motherboard though.
---
John Bäckstrand
next prev parent reply other threads:[~2003-10-27 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 23:43 [BUG] R8169 on 2.6.0-test9 John Bäckstrand
2003-10-27 0:55 ` Zwane Mwaikambo
2003-10-27 10:37 ` John Bäckstrand [this message]
2003-10-27 20:39 ` Zwane Mwaikambo
2003-10-27 22:03 ` SV: " John Bäckstrand
-- strict thread matches above, loose matches on Subject: below --
2003-10-26 20:40 John Bäckstrand
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='070c01c39c76$4579ccb0$034d210a@sandos' \
--to=sandos@home.se \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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