linux-kernel - Re: ksoftirqd/n permanently eating 60% of a CPU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Sep 2010 09:52:37 +0200
From:	Louis-David Mitterrand <vindex+lists-linux-kernel@...rtia.org>
To:	linux-kernel@...r.kernel.org
Subject: Re: ksoftirqd/n permanently eating 60% of a CPU

On Sun, Sep 12, 2010 at 08:57:15PM +0200, Andreas Mohr wrote:
> > Examining /proc/interrupts shows that "Local timer interrupts" are
> > mainly firing.
> 
> > Strangely enough, the interrupt storm starts only 5 minutes or so after
> > bootup.
> 
> And have you tried running powertop or manually (perhaps via
> sophisticated shell script) keeping a watch on
> /proc/timer[list|stats]?

Hi,

powertop seems to give a strong hint:

	54.5% (250.2)   [kernel core] dsp_cmx_send (dsp_cmx_send)
	25.8% (118.6)   usbhid-ups
	5.8% ( 26.7)   [ahci] <interrupt>
	2.6% ( 12.0)   [kernel core] usb_hcd_poll_rh_status (rh_timer_func)

Apparently dsp_cmx_send is in the mISDN stack which, in my kernel, is
compiled statically. This happens regardless of the box having isdn
hardware.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/