Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*8390\.c\s+workaround\s+for\s+interrupt\s+storm\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*8390\.c\s+workaround\s+for\s+interrupt\s+storm\s*$/: 6 ]

Total 6 documents matching your query.

1. 8390.c workaround for interrupt storm (score: 1): Author: en Hemminger <shemminger@xxxxxxxx>; Date: Fri, 13 Aug 2004 12:30:47 -0300; /archives/netdev/2004-08/msg00323.html (8,518 bytes)
2. Re: 8390.c workaround for interrupt storm (score: 1): Author: xxxx>; Date: Fri, 13 Aug 2004 16:17:34 -0400; /archives/netdev/2004-08/msg00328.html (9,120 bytes)
3. Re: 8390.c workaround for interrupt storm (score: 1): Author: x>; Date: Fri, 13 Aug 2004 17:07:37 -0300; /archives/netdev/2004-08/msg00330.html (9,852 bytes)
4. 8390.c workaround for interrupt storm (score: 1): Author: Marcelo Tosatti <marcelo.tosatti@xxxxxxxxxxxx>; Date: Fri, 13 Aug 2004 12:30:47 -0300; Hi netdev, We've been seeing an interrupt storm on our embedded PowerPC systems with Linksys PCMLM56 (network+modem) PCMCIA cards (network part of it driven by pcnet_cs.c) as soon as the network cabl; /archives/netdev/2004-08/msg01214.html (8,516 bytes)
5. Re: 8390.c workaround for interrupt storm (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Fri, 13 Aug 2004 16:17:34 -0400; We've been seeing an interrupt storm on our embedded PowerPC systems with Linksys PCMLM56 (network+modem) PCMCIA cards (network part of it driven by pcnet_cs.c) as soon as the network cable is pluged; /archives/netdev/2004-08/msg01219.html (9,167 bytes)
6. Re: 8390.c workaround for interrupt storm (score: 1): Author: Marcelo Tosatti <marcelo.tosatti@xxxxxxxxxxxx>; Date: Fri, 13 Aug 2004 17:07:37 -0300; Hi Jeff! I see. So, following your thoughts, what is causing the interrupt storm here is not the card itself, but the bus/platform/irq controller? That is, those interrupts are not coming from the ca; /archives/netdev/2004-08/msg01221.html (9,930 bytes)

Current List: 1 - 6
Page: [1]