Re: tulip driver BROKEN in 2.4.5-pre4
Studierende der Universitaet des Saarlandes <[EMAIL PROTECTED]> 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 ([EMAIL PROTECTED]) 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 03421000 03421200 fc000102 e384 fffe 0x40: fffe dff0 fffe ff59 1c09fdc0 fec8 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 0ee4e000 0ee4e200 fc000112 fffe0200 fffe 0x40: fffe 4bf8 fffe 50c8 ef01 0008 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 50c8. 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 ([EMAIL PROTECTED]) 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 03421000 03421200 fc000102 e384 fffe 0x40: fffe fff597ff fffe ff59 1c09fdc0 fec8 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 0ee4e000 0ee4e200 fc66 fffe2002 ebef 0x40: fffe 03ff fffe 01c8 ef05 ff3f 0008 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 01c8. No MII transceivers found! Internal autonegotiation state is 'Autonegotiation disabled'. -- J o h a n K u l l s t a m [[EMAIL PROTECTED]] Don't Fear the Penguin! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver BROKEN in 2.4.5-pre4
In article <[EMAIL PROTECTED]> 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 Trbiski ]* SysAdmin @wsisiz.edu.pl - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver BROKEN in 2.4.5-pre4
In article [EMAIL PROTECTED] 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 Trbiski ]* SysAdmin @wsisiz.edu.pl - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver BROKEN in 2.4.5-pre4
Studierende der Universitaet des Saarlandes [EMAIL PROTECTED] 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 ([EMAIL PROTECTED]) 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 03421000 03421200 fc000102 e384 fffe 0x40: fffe dff0 fffe ff59 1c09fdc0 fec8 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 0ee4e000 0ee4e200 fc000112 fffe0200 fffe 0x40: fffe 4bf8 fffe 50c8 ef01 0008 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 50c8. 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 ([EMAIL PROTECTED]) 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 03421000 03421200 fc000102 e384 fffe 0x40: fffe fff597ff fffe ff59 1c09fdc0 fec8 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 0ee4e000 0ee4e200 fc66 fffe2002 ebef 0x40: fffe 03ff fffe 01c8 ef05 ff3f 0008 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 01c8. No MII transceivers found! Internal autonegotiation state is 'Autonegotiation disabled'. -- J o h a n K u l l s t a m [[EMAIL PROTECTED]] Don't Fear the Penguin! - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver BROKEN in 2.4.5-pre4
> 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 ([EMAIL PROTECTED]) 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 0129f000 0129f200 fc66 fffe2002 ebef 0x40: fffe 03ff fffe 01c8 ef05 ff3f 0008 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 01c8. 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 ([EMAIL PROTECTED]) 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 0129e000 0129e200 fc66 fffe2202 ebef 0x40: fffe 03ff fffe 50c8 ef01 0008 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 50c8. 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 ([EMAIL PROTECTED]) 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 0129f000 0129f200 fc66 fffe2202 ebef 0x40: fffe 03ff fffe 50c8 ef01 0008 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 50c8. 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 [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver BROKEN in 2.4.5-pre4
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver BROKEN in 2.4.5-pre4
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 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver BROKEN in 2.4.5-pre4
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 ([EMAIL PROTECTED]) 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 0129f000 0129f200 fc66 fffe2002 ebef 0x40: fffe 03ff fffe 01c8 ef05 ff3f 0008 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 01c8. 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 ([EMAIL PROTECTED]) 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 0129e000 0129e200 fc66 fffe2202 ebef 0x40: fffe 03ff fffe 50c8 ef01 0008 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 50c8. 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 ([EMAIL PROTECTED]) 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 0129f000 0129f200 fc66 fffe2202 ebef 0x40: fffe 03ff fffe 50c8 ef01 0008 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 50c8. 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 [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
tulip driver BROKEN in 2.4.5-pre4
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 [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
tulip driver BROKEN in 2.4.5-pre4
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 [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver broken in 2.4.4?
Well, I guess I should chip in here with the rather amusing fact that 2.4.4 is the first kernel *not* to do this to me... ;-) I am, of course, glad to help out testing stuff if needed. My card is also a LinkSys LNE100TX v4.1, which the tulip driver identifies as an ADMtek Comet rev 17 (although somebody told me it's really a Centaur). -Jacob On Tue, 1 May 2001, Ronny Haryanto wrote: > On 01-May-2001, Jeff Garzik wrote: > > Ronny Haryanto wrote: > > > > > > Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. > > > > Does 2.4.3 work for you? > > Yes. I just tried 2.4.3, and it works fine. So it looks like there's a bug > introduced between 2.4.3 and 2.4.4. Too bad I can't use 2.4.3; I need 2.4.4 > due to the VIA chipset bug. Is there any other info that I could provide > from here to help debugging? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver broken in 2.4.4?
On 01-May-2001, Jeff Garzik wrote: > Ronny Haryanto wrote: > > > > Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. > > Does 2.4.3 work for you? Yes. I just tried 2.4.3, and it works fine. So it looks like there's a bug introduced between 2.4.3 and 2.4.4. Too bad I can't use 2.4.3; I need 2.4.4 due to the VIA chipset bug. Is there any other info that I could provide from here to help debugging? Ronny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver broken in 2.4.4?
Ronny Haryanto wrote: > > Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. Does 2.4.3 work for you? -- Jeff Garzik | Game called on account of naked chick Building 1024| MandrakeSoft | - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
tulip driver broken in 2.4.4?
Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. The log says: Apr 30 10:30:59 fluke kernel: NETDEV WATCHDOG: eth1: transmit timed out Apr 30 10:30:59 fluke kernel: eth1: Transmit timed out, status fc664010, CSR12 , resetting... Apr 30 10:31:07 fluke kernel: NETDEV WATCHDOG: eth1: transmit timed out Apr 30 10:31:07 fluke kernel: eth1: Transmit timed out, status fc664010, CSR12 , resetting... ... and so on repeatedly ... I had to ifdown-ifup cycle to re-enable it but it's dead again after 5 minutes with the same problem. The card is LinkSys LNE100TX v4.1. It is currently working fine with 2.2.18. If there's any other info that is needed please let me know. Ronny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
tulip driver broken in 2.4.4?
Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. The log says: Apr 30 10:30:59 fluke kernel: NETDEV WATCHDOG: eth1: transmit timed out Apr 30 10:30:59 fluke kernel: eth1: Transmit timed out, status fc664010, CSR12 , resetting... Apr 30 10:31:07 fluke kernel: NETDEV WATCHDOG: eth1: transmit timed out Apr 30 10:31:07 fluke kernel: eth1: Transmit timed out, status fc664010, CSR12 , resetting... ... and so on repeatedly ... I had to ifdown-ifup cycle to re-enable it but it's dead again after 5 minutes with the same problem. The card is LinkSys LNE100TX v4.1. It is currently working fine with 2.2.18. If there's any other info that is needed please let me know. Ronny - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver broken in 2.4.4?
Ronny Haryanto wrote: Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. Does 2.4.3 work for you? -- Jeff Garzik | Game called on account of naked chick Building 1024| MandrakeSoft | - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver broken in 2.4.4?
On 01-May-2001, Jeff Garzik wrote: Ronny Haryanto wrote: Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. Does 2.4.3 work for you? Yes. I just tried 2.4.3, and it works fine. So it looks like there's a bug introduced between 2.4.3 and 2.4.4. Too bad I can't use 2.4.3; I need 2.4.4 due to the VIA chipset bug. Is there any other info that I could provide from here to help debugging? Ronny - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: tulip driver broken in 2.4.4?
Well, I guess I should chip in here with the rather amusing fact that 2.4.4 is the first kernel *not* to do this to me... ;-) I am, of course, glad to help out testing stuff if needed. My card is also a LinkSys LNE100TX v4.1, which the tulip driver identifies as an ADMtek Comet rev 17 (although somebody told me it's really a Centaur). -Jacob On Tue, 1 May 2001, Ronny Haryanto wrote: On 01-May-2001, Jeff Garzik wrote: Ronny Haryanto wrote: Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes. Does 2.4.3 work for you? Yes. I just tried 2.4.3, and it works fine. So it looks like there's a bug introduced between 2.4.3 and 2.4.4. Too bad I can't use 2.4.3; I need 2.4.4 due to the VIA chipset bug. Is there any other info that I could provide from here to help debugging? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
TULIP driver broken
Well it would appear the tulip driver regressed from 2.4.2-ac22 and 2.4.3. (2.4.3-ac12 isn't working either) Once again, my tulip card just spews carrier errors and doesn't even get a link light. If someone could point me to a patch I would appreciate it. I have attached any pretient information below. Thanks, Ian Zink Linux zforce 2.4.3-ac12 #5 Tue Apr 24 02:49:03 CDT 2001 i686 unknown Bus 0, device 11, function 0: Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 32). IRQ 10. Master Capable. Latency=32. Min Gnt=20.Max Lat=40. I/O at 0xb000 [0xb07f]. Non-prefetchable 32 bit memory at 0xe080 [0xe080007f]. eth0 Link encap:Ethernet HWaddr 00:00:C0:41:99:E9 inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:243 dropped:0 overruns:0 carrier:243 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xb000 Linux version 2.4.3-ac12 (root@zforce) (gcc version 2.95.4 20010319 (Debian prer elease)) #5 Tue Apr 24 02:49:03 CDT 2001 Linux Tulip driver version 0.9.14e (April 20, 2001) PCI: Found IRQ 10 for device 00:0b.0 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. 00:0b.0: MII transceiver #3 config 3100 status 7809 advertising 01e1. 00:0b.0: Advertising 0001 on PHY 3, previously advertising 01e1. 00:0b.0: Advertising 0001 (to advertise is 0001). eth0: Digital DS21140 Tulip rev 32 at 0xb000, 00:00:C0:41:99:E9, IRQ 10. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
