Main
Pruning the forum database.
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 761/M761 Host (rev 02)00:01.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS965 [MuTIOL Media IO] (rev 48)00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01)00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller00:06.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge00:07.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge00:08.0 IDE interface: Silicon Integrated Systems [SiS] Device 0183 (rev 01)00:09.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d0)00:0a.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control01:00.0 VGA compatible controller: ATI Technologies Inc RV610 video device [Radeon HD 2400 PRO]01:00.1 Audio device: ATI Technologies Inc RV610 audio device [Radeon HD 2400 PRO]
Your computer communicates with the devices attached to it through IRQs (interrupt requests). When an interrupt comes from a device, the operating system pauses what it was doing and starts addressing that interrupt.In some situations IRQs come very very fast one after the other and the operating system cannot finish servicing one before another one arrives. This can happen when a high speed network card receives a very large number of packets in a short time frame.Because the operating system cannot handle IRQs as they arrive (because they arrive too fast one after the other), the operating system queues them for later processing by a special internal process named ksoftirqd.If ksoftirqd is taking more than a tiny percentage of CPU time, this indicates the machine is under heavy interrupt load.
Sounds like you have some bad hardware that is generating interrupts non stop. Take a look at /proc/interrupts and see if you can spot the one that is going nuts. –
QuoteSounds like you have some bad hardware that is generating interrupts non stop. Take a look at /proc/interrupts and see if you can spot the one that is going nuts. –
Makes me wonder if it is connected to the SIS hardware .......
I doubt that as pclinuxos is the only os that has done this - more likely pclinuxos bug.
QuoteI doubt that as pclinuxos is the only os that has done this - more likely pclinuxos bug.From the web searches I quickly did it seems the ksoftirqd/0 is not restricted to PCLinuxsOS and in fact it seems fairly widespread.