Bug 46291
Summary: | (NET TULIP) 2.4.3-12 kills my network | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michal Jaegermann <michal> |
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | len, patricio_zuniga, peterm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Michal Jaegermann
2001-06-27 17:37:12 UTC
Created attachment 21967 [details]
tulip-diag output - de4x5 loaded and working card
Created attachment 21968 [details]
tulip-diag output - tulip reloaded after de4x5 and network dead
Created attachment 21969 [details]
tulip-diag output - tulip loaded after boot, network dead
The interesting bit is that 2.4.3-12 has the exact same tulip version as before, eg 0.9.14....... so why it stopped working is beyond me My VALinux Varstation 27 has a Digital 21143-chipset 10/100 fast ethernet card. It worked fine under RedHat 7.1 with the 2.4.2-2 kernel. I upgraded the kernel to 2.4.3-12, and it stopped working. I'm not sure at this point about the details. If I go back to the previous kernel it works again. I compared the tulip.o module for the two kernels and they are exactly the same. In my case there is an added complication. With the 2.4.2 kernel, the USB controller and the network card share irq 9, apparently happily. I don't know if this is the problem under 2.4.3. I will try the d4x5 module to see if that works. > The interesting bit is that 2.4.3-12 has the exact same tulip version as
> before ...
Before of what? I was reporting on previous occasions that a new tulip
driver is broken (see, for example, #44158 and also some postings on
linux-kernel list, and some other occasions as well). This does not
seem to generate too much of interest.
Once again - so far among variants for 2.4 kernels (this includes stuff
from sourceforge) I found only a version 0.9.14d which is usable _for me_.
I have seen more, independent, reports of that kind so I am far from beeing
unique.
I think the comment "same as before" probably meant that the files tulip.o in the /lib/modules/2.4.2-2 and /lib/modules/2.4.3-12 are exactly the same. I used cmp and found they are the same. So whatever the problem is, it appears not to be the module itself, but of course its interaction with other parts of the kernel could cause the problem. I tried using the de4x5 module instead, and it appears to work. On further checking I find my current ethernet card is a DE500 PCI 10/100 fast ethernet, so that is not surprising. However, the tulip module is supposed to work with this card and it is what was chosen automatically by kudzu under the 2.4.2 kernel when I put that ethernet card in (replacing a 3Com card I had there before). I think there is something definitely wrong here. Here are some additional facts I left out previously. My machine has a DEC DE500 10/100 fast ethernet card, and it is connected to a Linksys DSL/Cable router. It worked fine under RH7.1 with the kernel 2.4.2-2. The DSL/Cable router acts as a DHCP server. With eth0 aliased to tulip, under 2.4.3-12, /var/log/messages shows the same messages as under 2.4.2, but apparently ifup fails. During this process the lights on the DSL/Cable router blink on and off, and that continues even after the attempt to start eth0 times out. Because of that, I conjecture that with the 2.4.3 kernel, the tulip module is not making an adequate connection to the DSL/Cable router, so ifup naturally fails. Also, /proc/interrupts shows no IRQ assigned to the network card, whereas before it always has shown it sharing IRQ 9 with the usb controller. If I alias eth0 to de4x5 instead, everything works properly, except that according to the lights on the DSL/Cable router, it is only in half duplex. Of course the problem could instead be some problem with pump or the network startup scripts. Are you sure that 'ifconfig' fails for you? In all cases which I have seen so for 'ifconfig' succeeds and a card is up but left in a "Transmitter stopped" state. You can collect more information about your card status with 'tulip-diag' which you can find on http://sourceforge.net/projects/tulip/ in tulip driver sources or on http://www.scyld.com (slightly different version). I got tulip-diag and ran it, but I'm not sure what it is telling me. Here is part of it when run under 2.4.2 with network down since it never started. Index #1: Found a Digital DS21143 Tulip adapter at 0x1400. Port selection is 10mpbs-serial, full-duplex. Transmit stopped, Receive stopped, full-duplex. The Rx process state is 'Stopped'. The Tx process state is 'Stopped'. The transmit threshold is 72. The NWay status register is 45e192ce. . . . Internal autonegotiation state is 'Transmit disabled'. When run under 2.4.2, here is what I get Index #1: Found a Digital DS21143 Tulip adapter at 0x1400. Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex. Transmit started, Receive started, full-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 128. The NWay status register is 45e1d2cc. Internal autonegotiation state is 'Negotiation complete'. It should be noted that under 2.4.3, the full duplex and 100 MHz light on the dsl/cable router keep blinking on and off in unison, but according to tulip-diag, the ethernet card is set at 10 MHz. What do I make of all this, and is there anything else to try to get it to work? > Transmit stopped, Receive stopped, full-duplex.
Yes, this is the same failure I see on other occasions and no Linksys in sight.
An output from tulip-diag does not tell you very much but, hopefully, is
more meaningfull to somebody else with a knowledge of tulip internals.
You can get more with extra flags to tulip-diag but likely this will be
similar to what I already filed in attachements.
The problem is still the same for 2.4.7-6 kernel and betas for an upcoming 7.2 distribution. To make it even more exciting after replacing broken tulip with an "alternative" (not quite, but say...) de4x5 driver one sees the following: # ifup eth0 RTNETLINK answers: Illegal seek but a network seems to be operational regardless. Just a reminder that 'tulip' did work for a long time until it got "improved". 2.4.7-6 has the original 7.1 tulip driver available as tulip_old.o Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |