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  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:	Sun, 21 Apr 2013 09:30:02 -0700
From:	"Paul E. McKenney" <>
To:	Borislav Petkov <>
Cc:	x86-ml <>, lkml <>,
Subject: Re: irq 16: nobody cared

On Sun, Apr 21, 2013 at 12:34:03PM +0200, Borislav Petkov wrote:
> On Sat, Apr 20, 2013 at 04:52:07PM -0700, Paul E. McKenney wrote:
> > Hmmm... Does this problem occur only with CONFIG_RCU_FAST_NO_HZ=y, or
> > does it occur unconditionally? (My guess is the former, but figured I
> > should check.)
> Your guess is correct, sir.
> >From quickly grepping in /boot/, I have CONFIG_RCU_FAST_NO_HZ=y in all
> my 3.9 configs. So I went and turned it off and the issue doesn't appear
> anymore.

Thank you for the info!  Now to figure out what the heck is causing this.

I am also guessing that your system does have hardware that could do an
irq 16.  Of course, if removing or disabing this hardware is an option,
it would be interesting to see what happens.  Especially given that at the
very bottom of the .jpg, there is a chopped-off line that appears to read
"Disabling IRQ #16".  Which of course leads me to wonder whether we hit
a race between the last interrupt arriving and the device being disabled.

or CONFIG_PM_RUNTIME set for these runs?

Adding Takashi Iwai on CC in case he has any insight.

							Thanx, Paul

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists