public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* tulip driver BROKEN in 2.4.5-pre4
@ 2001-05-21  1:37 J Brook
  2001-05-23 21:39 ` Lukasz Trabinski
  0 siblings, 1 reply; 5+ messages in thread
From: J Brook @ 2001-05-21  1:37 UTC (permalink / raw)
  To: linux-kernel

Okay, so Jeff Garzik already knows about this - I told him last week -
but seeing as how the code has made it to a Linus pre-release without
a fix I thought I'd better post the breakage description to l-k!

The symptoms are:
In 2.4.5-pre4 (and 2.4.4-ac8 and above - note: I didn't try -ac7)
system boots up normally, card is recognised etc, but all networking
services fail because it's not possible to talk to the network. The
system appears to be stable apart from the bug (possible to compile
kernels, run X, etc.), but nothing gets to or from the network.

I'm using the "DECchip Tulip (dc21x4x) PCI support" option to get the
driver for the PCI card which has a Digital 21041 chip in it.

FWIW I think it might be related to the selection of full- or
half-duplex. 2.4.4-ac6 (which works fine) says:
  Port selection is half-duplex
when I run tulip-diag, whereas 2.4.5-pre4 says
  Port selection is full-duplex

My system is RH7.1 (using gcc-2.96 not kgcc)
Duron 750, KT133 chipset (not kt133a!)

Network card details (it is a PCI):
Kingston KNE40BT (1995)
  Digital 21041-AA  DC1017BA
  21-40756-01  Dec 1994
  S15313-02
  A 9615

 More details on request. And I'm willing to test patches...

    John
----------------
jbk@postmark.net


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: tulip driver BROKEN in 2.4.5-pre4
@ 2001-05-21  9:54 Studierende der Universitaet des Saarlandes
  2001-05-24  2:24 ` Johan Kullstam
  0 siblings, 1 reply; 5+ messages in thread
From: Studierende der Universitaet des Saarlandes @ 2001-05-21  9:54 UTC (permalink / raw)
  To: jbk; +Cc: linux-kernel

Could you post the output of

#tulip-diag -mm -aa -f

with the broken driver?
Some code that's required for Linksys Tulip clones was moved from pnic
specific part into the generic part, perhaps that causes problems.

--
	Manfred

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: tulip driver BROKEN in 2.4.5-pre4
@ 2001-05-21 11:50 J Brook
  0 siblings, 0 replies; 5+ messages in thread
From: J Brook @ 2001-05-21 11:50 UTC (permalink / raw)
  To: linux-kernel; +Cc: manfred

> Could you post the output of
> 
> #tulip-diag -mm -aa -f
> 
> with the broken driver?
> Some code that's required for Linksys Tulip clones was moved
> from pnic specific part into the generic part, perhaps that
> causes problems.

Here is the output from the kernels I've tested to try to get the
driver working:

2.4.4-ac6, this kernel works!

tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000 ffffffff ffffffff 0129f000 0129f200 fc660000 fffe2002
ffffebef
 0x40: fffe0000 ffff03ff ffffffff fffe0000 000001c8 ffffef05 ffffff3f
ffff0008
 Port selection is half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 000001c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.

--------------------------------------------------------------

2.4.5-pre4 this kernel doesn't work

tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000 ffffffff ffffffff 0129e000 0129e200 fc660000 fffe2202
ffffebef
 0x40: fffe0000 ffff03ff ffffffff fffe0000 000050c8 ffffef01 ffffffff
ffff0008
 Port selection is full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 000050c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.

--------------------------------------------------------------

2.4.4-ac9 with tulip 1.1.7 driver (from sf.net/projects/tulip)

tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DC21041 Tulip adapter at 0xd800.
Digital DC21041 Tulip chip registers at 0xd800:
 0x00: ffe08000 ffffffff ffffffff 0129f000 0129f200 fc660000 fffe2202
ffffebef
 0x40: fffe0000 ffff03ff ffffffff fffe0000 000050c8 ffffef01 ffffffff
ffff0008
 Port selection is full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 000050c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.


 Let me know if I can provide any more useful information about the
driver problem.

    John
----------------
jbk@postmark.net


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: tulip driver BROKEN in 2.4.5-pre4
  2001-05-21  1:37 J Brook
@ 2001-05-23 21:39 ` Lukasz Trabinski
  0 siblings, 0 replies; 5+ messages in thread
From: Lukasz Trabinski @ 2001-05-23 21:39 UTC (permalink / raw)
  To: linux-kernel

In article <20010521013705.4079.qmail@venus.postmark.net> you wrote:
> Okay, so Jeff Garzik already knows about this - I told him last week -
> but seeing as how the code has made it to a Linus pre-release without
> a fix I thought I'd better post the breakage description to l-k!


Try drivers from http://sourceforge.net/projects/tulip/
1.1.6 drivers + 2.4.5-pre1 works OK on high load router ( one four-ports
card and one two-ports carts).
Tulip drivers from 2.4.5-pre1 are realy borken. :(

-- 
*[ Łukasz Trąbiński ]*
SysAdmin @wsisiz.edu.pl

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: tulip driver BROKEN in 2.4.5-pre4
  2001-05-21  9:54 tulip driver BROKEN in 2.4.5-pre4 Studierende der Universitaet des Saarlandes
@ 2001-05-24  2:24 ` Johan Kullstam
  0 siblings, 0 replies; 5+ messages in thread
From: Johan Kullstam @ 2001-05-24  2:24 UTC (permalink / raw)
  To: linux-kernel

Studierende der Universitaet des Saarlandes  <masp0008@stud.uni-sb.de> writes:

> Could you post the output of
> 
> #tulip-diag -mm -aa -f
> 
> with the broken driver?
> Some code that's required for Linksys Tulip clones was moved from pnic
> specific part into the generic part, perhaps that causes problems.

i have a 21041 dec tulip which has failed to work with
linux-2.4.5-pre[3-5] kernel drivers.  (it also fails with the
sourceforge devel version tulip-1.1.7)

it appears that the card gets lodged in full duplex mode.  however,
this could just be a superficial syndrome.

anyhow, here is the output of tulip-diag -mm -aa -f from the *broken*
driver

tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21140 Tulip adapter at 0xfc00.
Digital DS21140 Tulip chip registers at 0xfc00:
 0x00: fff88000 ffffffff ffffffff 03421000 03421200 fc000102 e3840000 fffe0000
 0x40: fffe0000 ffffdff0 ffffffff fffe0000 ffffff59 ffffffff 1c09fdc0 fffffec8
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
   No MII transceivers found!
Index #2: Found a Digital DC21041 Tulip adapter at 0xf080.
Digital DC21041 Tulip chip registers at 0xf080:
 0x00: ffe08000 ffffffff ffffffff 0ee4e000 0ee4e200 fc000112 fffe0200 fffe0000
 0x40: fffe0000 ffff4bf8 ffffffff fffe0000 000050c8 ffffef01 ffffffff ffff0008
 Port selection is full-duplex.
 Transmit stopped, Receive stopped, full-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 000050c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.



and here is one working dump for comparison (driver 0.9.14 from
sourceforge)

tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21140 Tulip adapter at 0xfc00.
Digital DS21140 Tulip chip registers at 0xfc00:
 0x00: fff88000 ffffffff ffffffff 03421000 03421200 fc000102 e3840000 fffe0000
 0x40: fffe0000 fff597ff ffffffff fffe0000 ffffff59 ffffffff 1c09fdc0 fffffec8
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
   No MII transceivers found!
Index #2: Found a Digital DC21041 Tulip adapter at 0xf080.
Digital DC21041 Tulip chip registers at 0xf080:
 0x00: ffe08000 ffffffff ffffffff 0ee4e000 0ee4e200 fc660000 fffe2002 ffffebef
 0x40: fffe0000 ffff03ff ffffffff fffe0000 000001c8 ffffef05 ffffff3f ffff0008
 Port selection is half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit unit is set to store-and-forward.
  The NWay status register is 000001c8.
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.


-- 
J o h a n  K u l l s t a m
[kullstam@ne.mediaone.net]
Don't Fear the Penguin!

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2001-05-24  2:25 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-05-21  9:54 tulip driver BROKEN in 2.4.5-pre4 Studierende der Universitaet des Saarlandes
2001-05-24  2:24 ` Johan Kullstam
  -- strict thread matches above, loose matches on Subject: below --
2001-05-21 11:50 J Brook
2001-05-21  1:37 J Brook
2001-05-23 21:39 ` Lukasz Trabinski

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox