Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ksoftirqd\s+uses\s+99\%\s+CPU\s+triggered\s+by\s+network\s+traffic\s+$maybe\s+RLT\-8139\s+related$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ksoftirqd\s+uses\s+99\%\s+CPU\s+triggered\s+by\s+network\s+traffic\s+$maybe\s+RLT\-8139\s+related$\s*$/: 64 ]

Total 64 documents matching your query.

1. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: Pasi Sjoholm <ptsjohol@xxxxxxxxx>; Date: Mon, 2 Aug 2004 12:57:41 +0300 (EEST); Yep, I tried that one also, didn't help a thing. We are making some sort of a progress but not enough. Patch r8139-20.patch didn't help. I made some printk(...)-debug messages and that part of a code; /archives/netdev/2004-08/msg00019.html (13,796 bytes)
2. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: Pasi Sjoholm <ptsjohol@xxxxxxxxx>; Date: Mon, 2 Aug 2004 13:03:15 +0300 (EEST); I forgot to mention that it was quite hard to crash the driver with that /* Clear out errors and receive interrupts */-patch. Took about 15minutes everytime, when normally it takes about 2mins.; /archives/netdev/2004-08/msg00020.html (11,873 bytes)
3. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: xxxxxx>; Date: Tue, 3 Aug 2004 00:35:15 +0200; Pasi Sjoholm <ptsjohol@xxxxxxxxx> : I have made a few changes. Please enable the DEBUG option and set msglvl to its maximal value via ethtool. You may test the patches separately if you find some tim; /archives/netdev/2004-08/msg00038.html (11,223 bytes)
4. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: u <herbert@xxxxxxxxxxxxxxxxxxx>; Date: Tue, 3 Aug 2004 15:32:15 +0300 (EEST); /archives/netdev/2004-08/msg00058.html (11,079 bytes)
5. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: trick McHardy <kaber@xxxxxxxxx>; Date: Tue, 3 Aug 2004 18:50:26 +0200; /archives/netdev/2004-08/msg00068.html (10,832 bytes)
6. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: Hemminger <shemminger@xxxxxxxx>; Date: Tue, 3 Aug 2004 23:19:33 +0300 (EEST); /archives/netdev/2004-08/msg00077.html (10,949 bytes)
7. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: ki <tomasz.paszkowski@xxxxxxxx>; Date: Wed, 4 Aug 2004 19:26:03 +0300 (EEST); /archives/netdev/2004-08/msg00107.html (11,110 bytes)
8. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: ene Surovegin <ebs@xxxxxxxxxxx>; Date: Thu, 05 Aug 2004 12:14:26 +0200; /archives/netdev/2004-08/msg00130.html (11,376 bytes)
9. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: Martin <hector@xxxxxxxxxxxxxx>; Date: Thu, 05 Aug 2004 12:55:51 +0200; /archives/netdev/2004-08/msg00131.html (12,552 bytes)
10. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: Martin <hector@xxxxxxxxxxxxxx>; Date: Thu, 5 Aug 2004 13:22:33 +0200; /archives/netdev/2004-08/msg00132.html (10,602 bytes)
11. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: xxxx>; Date: Fri, 06 Aug 2004 00:28:40 +0900; /archives/netdev/2004-08/msg00135.html (11,781 bytes)
12. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: T Kerrisk" <mtk-lists@xxxxxxx>; Date: Thu, 5 Aug 2004 19:21:59 +0200; /archives/netdev/2004-08/msg00138.html (10,724 bytes)
13. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: ard <jameshubbard@xxxxxxxxx>; Date: Mon, 26 Jul 2004 18:15:34 +0300 (EEST); After 24 hours of hard working I can answer yes to this question. Now I can reproduce this from 2 to 15 minutes with 2 cp-processes from some mp3 via nfs to notice when kernel goes down.. =) and so o; /archives/netdev/2004-07/msg00594.html (17,171 bytes)
14. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: e, Dan" <DanE@xxxxxxxxxx>; Date: Mon, 26 Jul 2004 18:37:26 +0200; Hello! This looks very much like the problem we see when doing route DoS testing with Alexey. In summary: High softirq loads can totally kill userland. The reason is that do_softirq() is run from man; /archives/netdev/2004-07/msg00596.html (11,526 bytes)
15. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: n <pp@xxxxxxxxxx>; Date: Mon, 26 Jul 2004 09:55:05 -0700; Is network traffic still coming in? or perhaps there is a network packet that causes some soft irq to go into an infinite loop. The recent iptables bug with ip options would be an example.; /archives/netdev/2004-07/msg00597.html (11,305 bytes)
16. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: ger <shemminger@xxxxxxxx>; Date: Tue, 27 Jul 2004 00:28:04 +0300 (EEST); At least tcpdump doesn't say anything, I can only see only arp-packets which my computer (not other computer's arp-packets) has made but no response to those. That would make sense but Robert Olsson; /archives/netdev/2004-07/msg00601.html (10,922 bytes)
17. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: Hemminger <shemminger@xxxxxxxx>; Date: Tue, 27 Jul 2004 00:46:54 +0300 (EEST); Hur är läget Robert?-) Hmm, at least it sounds like same problem and in both situations network interface is kept busy. Ok, this explanation makes sense and my point of view I think this is quite cri; /archives/netdev/2004-07/msg00602.html (12,084 bytes)
18. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: lm <ptsjohol@xxxxxxxxx>; Date: Tue, 27 Jul 2004 00:38:12 +0200; Tack bra! Well the packets also has to create hard softirq loads in practice this means route lookup or something else for normal traffic the RX_SOFIRQ is very well behaved and schedules itself to gi; /archives/netdev/2004-07/msg00605.html (12,628 bytes)
19. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: xxxx>; Date: Tue, 27 Jul 2004 03:16:50 +0300 (EEST); The system will be more responsive but won't ever come back to normal operation and if I use my computer just for some chatting/writing/browsing the ksoftirqd-problem won't ever happen. It is also ve; /archives/netdev/2004-07/msg00608.html (13,256 bytes)
20. Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related) (score: 1): Author: @xxxxxxxxxxx>; Date: Tue, 27 Jul 2004 13:10:37 +0200; Yes you starved your user apps for ~5 sec. Any idea where your load comes from? Pure NFS network load cannot be hard. Cheers. --ro; /archives/netdev/2004-07/msg00609.html (10,875 bytes)

Current List: 1 - 20
Page: [1] [2] [3] [4]