Re: Deadlock/crash with Quad tulip card in 2.4
Le 10 May 2001 12:08:08 -0400, Jeff Garzik a écrit : > Yann Dupont wrote: > I'm working on fixing this right now; until then, the "de4x5" driver > should work for you. > Yes that's true, it's working like a charm now. I didn't know the de4x5 driver was working on 4 port Ethernet 21140... Thanks for the quick answer. -- \|/ \|/ Fac. des sciences de Nantes-Linux-Python-IPv6-ATM-BONOM "@'/ ,. \@" Tel :(+33) [0]251125865(AM)[0]251125857(PM)[0]251125868(Fax) /_| \__/ |_\ [EMAIL PROTECTED] \__U_/http://www.unantes.univ-nantes.fr/~dupont - 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: Deadlock/crash with Quad tulip card in 2.4
Yann Dupont wrote: > Hello. I'm having problem with Quad eth100 tulip (digital 21140) cards. Unfortuantely a recent merge of the latest Becker code fixed these chips (and 2104[01]), and promptly broke support for other, more popular chips. :( I'm working on fixing this right now; until then, the "de4x5" driver should 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/
Deadlock/crash with Quad tulip card in 2.4
Hello. I'm having problem with Quad eth100 tulip (digital 21140) cards. The machine was acting as a bridge with kernel 2.2 very reliably. Now, when I boot 2.4.4-ac6, the machine hangs - no oops, nothing. Just hang. even CTRL-Scroll lock does nothing. I supected a bridge problem (I know 2.2 & 2.4 bridge are different) But it's not the case as I reproduce the bug on another machine (with another motherboard. kernel 2.4.4-ac6 where the bridge is not configured.) single boot is OK, ifconfig eth0 up is ok (MII negotiation is OK) ifconfig eth1 up crash the machine - on another boot i tried this : ifconfig eth0 up ifconfig eth0 down ifconfig eth1 up is OK ifconfig eth1 down ... etc etc This works as long as only one interface is up. If only 1 interface is up, the machine works reliably. just putting 2 interfaces up hang the machine. Can this be an IRQ sharing / bridge problem ??? (all interface shares the same IRQ and are after a bridge) I don't know if this is ac-series specific. I'll try tomorrow. Any Idea how I can test further ? Without oops it's not easy... Yann Dupont. -- \|/ \|/ Fac. des sciences de Nantes-Linux-Python-IPv6-ATM-BONOM "@'/ ,. \@" Tel :(+33) [0]251125865(AM)[0]251125857(PM)[0]251125868(Fax) /_| \__/ |_\ [EMAIL PROTECTED] \__U_/http://www.unantes.univ-nantes.fr/~dupont - 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/
