Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Ethernet\s+lockup\s+$Linksys\,\s+Tulip$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Ethernet\s+lockup\s+$Linksys\,\s+Tulip$\s*$/: 8 ]

Total 8 documents matching your query.

1. Ethernet lockup (Linksys, Tulip) (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Thu, 01 Jun 2000 22:02:31 -0700; This happened after I pulled the ethernet link (and re-inserted). The other end of the cable went into a no-name 10/100 Etherswitch. The card is a LinkSys (part# LNE100Tx), here's part of the kernel; /archives/netdev/2000-06/msg00006.html (8,615 bytes)
2. Re: Ethernet lockup (Linksys, Tulip) (score: 1): Author: "Anders K. Pedersen" <akp@xxxxxx>; Date: Fri, 02 Jun 2000 13:43:55 +0200; ... This looks like a problem I had with a 3c590 card recently. When tulip_tx_timeout() is called from tulip_start_xmit(), dev->tbusy is never cleared, and whenever tulip_start_xmit() is called after; /archives/netdev/2000-06/msg00007.html (8,397 bytes)
3. Re: Ethernet lockup (Linksys, Tulip) (score: 1): Author: Bogdan Costescu <Bogdan.Costescu@xxxxxxxxxxxxxxxxxxxxx>; Date: Fri, 2 Jun 2000 16:16:34 +0200 (CEST); By doing this you break the whole logic of setting and clearing handle another packet which is your case - the Tx ring is still full. When you reconnect the cable, the card could start sending packet; /archives/netdev/2000-06/msg00012.html (9,607 bytes)
4. Re: Ethernet lockup (Linksys, Tulip) (score: 1): Author: "Anders K. Pedersen" <akp@xxxxxx>; Date: Fri, 02 Jun 2000 16:39:37 +0200; One of the last things done in the tx_timeout() is to reset the card - I guess that this might cause the card not to generate the interrupt, that will clear dev->tbusy. Well, in our case, the driver; /archives/netdev/2000-06/msg00013.html (9,939 bytes)
5. Ethernet lockup (Linksys, Tulip) (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Thu, 01 Jun 2000 22:02:31 -0700; This happened after I pulled the ethernet link (and re-inserted). The other end of the cable went into a no-name 10/100 Etherswitch. The card is a LinkSys (part# LNE100Tx), here's part of the kernel; /archives/netdev/2000-06/msg00305.html (8,675 bytes)
6. Re: Ethernet lockup (Linksys, Tulip) (score: 1): Author: "Anders K. Pedersen" <akp@xxxxxx>; Date: Fri, 02 Jun 2000 13:43:55 +0200; ... This looks like a problem I had with a 3c590 card recently. When tulip_tx_timeout() is called from tulip_start_xmit(), dev->tbusy is never cleared, and whenever tulip_start_xmit() is called after; /archives/netdev/2000-06/msg00306.html (8,422 bytes)
7. Re: Ethernet lockup (Linksys, Tulip) (score: 1): Author: Bogdan Costescu <Bogdan.Costescu@xxxxxxxxxxxxxxxxxxxxx>; Date: Fri, 2 Jun 2000 16:16:34 +0200 (CEST); By doing this you break the whole logic of setting and clearing handle another packet which is your case - the Tx ring is still full. When you reconnect the cable, the card could start sending packet; /archives/netdev/2000-06/msg00311.html (9,632 bytes)
8. Re: Ethernet lockup (Linksys, Tulip) (score: 1): Author: "Anders K. Pedersen" <akp@xxxxxx>; Date: Fri, 02 Jun 2000 16:39:37 +0200; One of the last things done in the tx_timeout() is to reset the card - I guess that this might cause the card not to generate the interrupt, that will clear dev->tbusy. Well, in our case, the driver; /archives/netdev/2000-06/msg00312.html (10,027 bytes)

Current List: 1 - 8
Page: [1]