From: Christian Kujau <evil@g-house.de>
To: russell@coker.com.au
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: de2104x tulip driver bug in 2.6.0-test9
Date: Fri, 21 Nov 2003 16:32:04 +0100 [thread overview]
Message-ID: <3FBE2FF4.5010904@g-house.de> (raw)
In-Reply-To: <200311212051.32352.russell@coker.com.au>
Russell Coker wrote:
> 00:14.0 Ethernet controller: Digital Equipment Corporation DECchip 21041
> [Tulip Pass 3] (rev 11)
>
> Above is the lspci output for my PCI Ethernet card. Below is what happens
> when I try to boot 2.6.0-test9. 2.4.x kernels have been working well on the
> same card for a long time, so the hardware seems basically OK.
>
> Configuring network interfaces... eth0: set link BNC
> eth0: mode 0x7ffc0040, sia 0x10c4,0xffffef09,0xfffff7fd,0xffff0006
> eth0: set mode 0x7ffc0000, set sia 0xef09,0xf7fd,0x6
> eth0: timeout expired stopping DMA
could this be anyhow related to this:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106766135110165&w=2
there is a thread on linuxppc-dev too, as this is ppc specific:
http://lists.linuxppc.org/linuxppc-dev/200311/msg00001.html
it looks similar, but here on ppc32 i got no oops :-(
Christian.
--
BOFH excuse #27:
radiosity depletion
next prev parent reply other threads:[~2003-11-21 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 9:51 de2104x tulip driver bug in 2.6.0-test9 Russell Coker
2003-11-21 15:32 ` Christian Kujau [this message]
2003-11-21 15:47 ` Russell Coker
2003-11-21 18:50 ` [PATCH/CFT] de2104x fixes Jeff Garzik
[not found] ` <200311221305.25718.russell@coker.com.au>
2003-11-22 12:07 ` Jeff Garzik
2003-11-25 12:57 ` Rask Ingemann Lambertsen
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=3FBE2FF4.5010904@g-house.de \
--to=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=russell@coker.com.au \
/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