Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*via\-rhine\s+\"reset\s+did\s+not\s+complete\"\s+errors\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*via\-rhine\s+\"reset\s+did\s+not\s+complete\"\s+errors\s*$/: 12 ]

Total 12 documents matching your query.

1. IpInDelivers, IpInDiscards (score: 1): Author: <acme@xxxxxxxxxxxxxxxx>; Date: Mon, 28 Oct 2002 10:45:08 -0500; re in the code I'm really spending the time. Rig; /archives/netdev/2002-10/msg00536.html (9,292 bytes)
2. ete" errors (score: 1): Author: xxxxxxxxxx>; Date: Mon, 28 Oct 2002 14:38:18 -0500 (EST); D and Intel three times or more. Roy, do you like; /archives/netdev/2002-10/msg00539.html (9,252 bytes)
3. h netlink (score: 1): Author: vem@xxxxxxxxxx>; Date: Mon, 28 Oct 2002 16:03:25 -0500; l Mensajero Millonario para comprar tus tiquetes!; /archives/netdev/2002-10/msg00540.html (10,149 bytes)
4. eset did not complete" errors (score: 1): Author: @xxxxxxxxxx>; Date: Mon, 28 Oct 2002 16:20:19 -0500; K cache, 2G SDRAM (133Mhz, ECC) The only change; /archives/netdev/2002-10/msg00542.html (10,915 bytes)
5. support for IPv6, updated to 2.5.44 (score: 1): Author: xxxxxxxx>; Date: Mon, 28 Oct 2002 17:38:34 -0500; ead of L0. You need to be more clever than that; /archives/netdev/2002-10/msg00543.html (11,647 bytes)
6. (score: 1): Author: unce@xxxxxxxxxxx; Date: Tue, 29 Oct 2002 17:35:16 +0100; ssue a stop cmd, the "bad" status of CR0 is 0xc (not 0xE as my mind read it). The "start" bit is not on after the; /archives/netdev/2002-10/msg00567.html (8,842 bytes)
7. via-rhine "reset did not complete" errors (score: 1): Author: "Larry Sendlosky" <Larry.Sendlosky@xxxxxxxxxxxx>; Date: Mon, 28 Oct 2002 10:45:08 -0500; Hi, We're using VIA EPIA mini-ITX with 800Mhz C3 and the VT6103 PHY. (via-rhine driver says VT6102). We have made sure power supply is "big enough". Our kernel is 2.4.18 with via-rhine.c patches to f; /archives/netdev/2002-10/msg01147.html (9,292 bytes)
8. Re: via-rhine "reset did not complete" errors (score: 1): Author: Donald Becker <becker@xxxxxxxxx>; Date: Mon, 28 Oct 2002 14:38:18 -0500 (EST); Those are evil patches... A driver _really_, _really_ shouldn't be busy-waiting for link negotiation to complete. That happened a lot with MS-DOS drivers, but it wasn't even reasonable there. Yet it'; /archives/netdev/2002-10/msg01150.html (9,313 bytes)
9. RE: via-rhine "reset did not complete" errors (score: 1): Author: "Larry Sendlosky" <Larry.Sendlosky@xxxxxxxxxxxx>; Date: Mon, 28 Oct 2002 16:03:25 -0500; Hi Donald, Thanks for the reply. The "reset timeout" happens on the initial reset in the 'open' routine. The reset bit (bit 7 of CR1) is not clearing after being written. This usually happens after t; /archives/netdev/2002-10/msg01151.html (10,179 bytes)
10. RE: via-rhine "reset did not complete" errors (score: 1): Author: "Larry Sendlosky" <Larry.Sendlosky@xxxxxxxxxxxx>; Date: Mon, 28 Oct 2002 16:20:19 -0500; Oop, litte red-faced here....basically, I can't count. When the 'stop' routine does issue a stop cmd, the "bad" status of CR0 is 0xc (not 0xE as my mind read it). The "start" bit is not on after the; /archives/netdev/2002-10/msg01153.html (10,945 bytes)
11. RE: via-rhine "reset did not complete" errors (score: 1): Author: "Larry Sendlosky" <Larry.Sendlosky@xxxxxxxxxxxx>; Date: Mon, 28 Oct 2002 17:38:34 -0500; More info/possible solution: I remembered the Via linuxfet driver and dug it up. The linuxfet close routine does acknowledge some problems and does some special casing and action when the recvr does; /archives/netdev/2002-10/msg01154.html (11,677 bytes)
12. Re: via-rhine "reset did not complete" errors (score: 1): Author: Roger Luethi <rl@xxxxxxxxxxx>; Date: Tue, 29 Oct 2002 17:35:16 +0100; Care to elaborate? Since I wrote the patch to fix the Tx timeout issue, I'd be very interested to learn how exactly it is evil. Roger; /archives/netdev/2002-10/msg01178.html (8,982 bytes)

Current List: 1 - 12
Page: [1]