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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*acenic\s+lockup\s*$/: 20 ]

Total 20 documents matching your query.

1. acenic lockup (score: 1): Author: Anton Blanchard <anton@xxxxxxxxx>; Date: Wed, 7 May 2003 17:06:57 +1000; Ive got a bucketload of acenic adapters in a ppc64 box. I get random tx timeouts, I suspect there is a missing memory barrier (power4 is good at catching those). Still looking. I did manage to lock; /archives/netdev/2003-05/msg00054.html (8,725 bytes)
2. Re: acenic lockup (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Tue, 06 May 2003 23:43:16 -0700 (PDT); It is well understood failure of this driver, actually. If Acenic hangs in any way at all, driver hangs in this loop.; /archives/netdev/2003-05/msg00055.html (8,038 bytes)
3. Re: acenic lockup (score: 1): Author: xxxx>; Date: Wed, 7 May 2003 21:06:32 +0400 (MSD); Yes, I did. I am not sure about barriers, I stopped attempts to understand this long ago. Anyway, intel does not have anything to put here, mb() at side updating pointer looks enough. There is a rea; /archives/netdev/2003-05/msg00063.html (8,472 bytes)
4. Re: acenic lockup (score: 1): Author: xxxx>; Date: Wed, 07 May 2003 12:34:21 -0700 (PDT); From: Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx> Date: Wed, 7 May 2003 21:06:32 +0400 (MSD) I remember we discussed this with Dave and he was very angry about this flaw shared by most of drivers and, se; /archives/netdev/2003-05/msg00066.html (8,399 bytes)
5. Re: acenic lockup (score: 1): Author: xxxx>; Date: Thu, 8 May 2003 02:21:11 +0400 (MSD); Usually it is a link problem and device will recover after link is restored. This happens here. If it is some PCI failure or something went wrong in hardware, the device will stop forever, I guess.; /archives/netdev/2003-05/msg00070.html (8,525 bytes)
6. Re: acenic lockup (score: 1): Author: xxxx>; Date: Thu, 08 May 2003 09:00:49 -0700 (PDT); Usually it is a link problem and device will recover after link is restored. This happens here. I fully recognize this. If it is some PCI failure or something went wrong in hardware, the device will; /archives/netdev/2003-05/msg00077.html (9,637 bytes)
7. Re: acenic lockup (score: 1): Author: xxxx>; Date: Thu, 8 May 2003 13:11:35 -0400; Agreed. Alexey has pointed out netif_wake_queue stupidities in drivers before, and he's absolutely right. Jeff P.S. Can you please email @pobox.com for stuff that is not Red Hat specific? I am trying; /archives/netdev/2003-05/msg00078.html (9,029 bytes)
8. Re: acenic lockup (score: 1): Author: xxxx>; Date: Thu, 08 May 2003 09:09:54 -0700 (PDT); From: Jeff Garzik <jgarzik@xxxxxxxxxx> Date: Thu, 8 May 2003 13:11:35 -0400 P.S. Can you please email @pobox.com for stuff that is not Red Hat specific? My apologies, I will do this in the future. Ho; /archives/netdev/2003-05/msg00079.html (8,323 bytes)
9. Re: acenic lockup (score: 1): Author: xxxx>; Date: Thu, 8 May 2003 13:27:35 -0400; Should improve it :) I didn't check my redhat.com email all weekend this past weekend, for example. Jeff; /archives/netdev/2003-05/msg00080.html (8,972 bytes)
10. Re: acenic lockup (score: 1): Author: xxxxxxxxxxxx>; Date: Wed, 14 May 2003 07:40:16 -0400 (EDT); Dont forget that nice looking fixed tulip which gets rid of the nonsense tx_timeout;-> http://www.cyberus.ca/~hadi/patches/tulip-sym-fixed-20030103.tgz cheers, jamal; /archives/netdev/2003-05/msg00125.html (8,784 bytes)
11. acenic lockup (score: 1): Author: Anton Blanchard <anton@xxxxxxxxx>; Date: Wed, 7 May 2003 17:06:57 +1000; Hi, Ive got a bucketload of acenic adapters in a ppc64 box. I get random tx timeouts, I suspect there is a missing memory barrier (power4 is good at catching those). Still looking. I did manage to lo; /archives/netdev/2003-05/msg00456.html (8,725 bytes)
12. Re: acenic lockup (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Tue, 06 May 2003 23:43:16 -0700 (PDT); It is well understood failure of this driver, actually. If Acenic hangs in any way at all, driver hangs in this loop.; /archives/netdev/2003-05/msg00457.html (8,154 bytes)
13. Re: acenic lockup (score: 1): Author: Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx>; Date: Wed, 7 May 2003 21:06:32 +0400 (MSD); Hello! Yes, I did. I am not sure about barriers, I stopped attempts to understand this long ago. Anyway, intel does not have anything to put here, mb() at side updating pointer looks enough. There is; /archives/netdev/2003-05/msg00465.html (8,510 bytes)
14. Re: acenic lockup (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Wed, 07 May 2003 12:34:21 -0700 (PDT); From: Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx> Date: Wed, 7 May 2003 21:06:32 +0400 (MSD) I remember we discussed this with Dave and he was very angry about this flaw shared by most of drivers and, se; /archives/netdev/2003-05/msg00468.html (8,495 bytes)
15. Re: acenic lockup (score: 1): Author: Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx>; Date: Thu, 8 May 2003 02:21:11 +0400 (MSD); Hello! Usually it is a link problem and device will recover after link is restored. This happens here. If it is some PCI failure or something went wrong in hardware, the device will stop forever, I g; /archives/netdev/2003-05/msg00472.html (8,564 bytes)
16. Re: acenic lockup (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Thu, 08 May 2003 09:00:49 -0700 (PDT); Usually it is a link problem and device will recover after link is restored. This happens here. I fully recognize this. If it is some PCI failure or something went wrong in hardware, the device will; /archives/netdev/2003-05/msg00479.html (9,734 bytes)
17. Re: acenic lockup (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxxx>; Date: Thu, 8 May 2003 13:11:35 -0400; Agreed. Alexey has pointed out netif_wake_queue stupidities in drivers before, and he's absolutely right. Jeff P.S. Can you please email @pobox.com for stuff that is not Red Hat specific? I am trying; /archives/netdev/2003-05/msg00480.html (9,214 bytes)
18. Re: acenic lockup (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Thu, 08 May 2003 09:09:54 -0700 (PDT); From: Jeff Garzik <jgarzik@xxxxxxxxxx> Date: Thu, 8 May 2003 13:11:35 -0400 P.S. Can you please email @pobox.com for stuff that is not Red Hat specific? My apologies, I will do this in the future. Ho; /archives/netdev/2003-05/msg00481.html (8,448 bytes)
19. Re: acenic lockup (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxxx>; Date: Thu, 8 May 2003 13:27:35 -0400; Should improve it :) I didn't check my redhat.com email all weekend this past weekend, for example. Jeff; /archives/netdev/2003-05/msg00482.html (9,185 bytes)
20. Re: acenic lockup (score: 1): Author: Jamal Hadi <hadi@xxxxxxxxxxxxxxxx>; Date: Wed, 14 May 2003 07:40:16 -0400 (EDT); Jeff, Dont forget that nice looking fixed tulip which gets rid of the nonsense tx_timeout;-> http://www.cyberus.ca/~hadi/patches/tulip-sym-fixed-20030103.tgz cheers, jamal; /archives/netdev/2003-05/msg00527.html (8,991 bytes)

Current List: 1 - 20
Page: [1]