From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
tiwai@suse.de
Subject: Re: irq 16: nobody cared
Date: Sun, 21 Apr 2013 11:47:49 -0700 [thread overview]
Message-ID: <20130421184749.GC3509@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130421165653.GA4623@pd.tnic>
On Sun, Apr 21, 2013 at 06:56:54PM +0200, Borislav Petkov wrote:
> On Sun, Apr 21, 2013 at 09:30:02AM -0700, Paul E. McKenney wrote:
> > 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.
>
> Onboard sound chip so only BIOS disable should help, if present. Let me
> check. Oh, I can take out the laser and cut it out of the silicon. :-)
>
> What about not enabling any sound support and thus not using this IRQ
> handler? Would that tell us something?
Using a laser to cut out the silicon would be more entertaining, but
either BIOS disable or compiling out sound support should work. ;-)
> > 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.
>
> Well, the "Disabling IRQ..." line comes from note_interrupt() down the
> do_IRQ() path. It looks like
>
> if (unlikely(desc->irqs_unhandled > 99900)) {
>
> we hit some high number of unhandled interrupts, issue the message about
> the bad IRQ and then disable it by dumping the handlers beforehand.
It would also be interesting to print out desc->irqs_unhandled at some
point during suspend to get a feel for the magnitude of the difference.
After all, 99900 is an interesting choice of number!
> > Hmmm... Do you have either CONFIG_PM_SLEEP, SUPPORT_VGA_SWITCHEROO,
> > or CONFIG_PM_RUNTIME set for these runs?
>
> CONFIG_PM_SLEEP=y
> # CONFIG_VGA_SWITCHEROO is not set
> # CONFIG_PM_RUNTIME is not set
>
> You meant CONFIG_VGA_SWITCHEROO and not SUPPORT_VGA_SWITCHEROO, right?
You are quite correct.
Thanx, Paul
> Ok, let me try to disable the soundcard in the BIOS.
>
> --
> Regards/Gruss,
> Boris.
>
> Sent from a fat crate under my desk. Formatting is fine.
> --
>
next prev parent reply other threads:[~2013-04-21 18:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 18:53 irq 16: nobody cared Borislav Petkov
2013-04-20 23:52 ` Paul E. McKenney
2013-04-21 10:34 ` Borislav Petkov
2013-04-21 16:30 ` Paul E. McKenney
2013-04-21 16:56 ` Borislav Petkov
2013-04-21 18:10 ` Borislav Petkov
2013-04-21 18:56 ` Paul E. McKenney
2013-04-21 19:06 ` Borislav Petkov
2013-04-21 20:34 ` Paul E. McKenney
2013-04-21 20:51 ` Borislav Petkov
2013-04-21 21:42 ` Borislav Petkov
2013-04-21 22:00 ` Paul E. McKenney
2013-04-21 22:12 ` Borislav Petkov
2013-04-22 8:01 ` Ingo Molnar
2013-04-22 9:18 ` Borislav Petkov
2013-04-22 13:16 ` Paul E. McKenney
2013-04-21 18:47 ` Paul E. McKenney [this message]
2013-04-22 8:32 ` Takashi Iwai
2013-04-22 9:13 ` Borislav Petkov
2013-04-22 9:19 ` Takashi Iwai
2013-04-22 10:06 ` Borislav Petkov
2013-04-22 11:33 ` Takashi Iwai
2013-04-22 13:56 ` Borislav Petkov
2013-04-22 12:56 ` Thomas Gleixner
2013-04-22 14:23 ` Borislav Petkov
2013-04-22 14:44 ` Paul E. McKenney
2013-04-22 21:33 ` Borislav Petkov
2013-04-22 22:07 ` Paul E. McKenney
2013-04-23 14:10 ` Thomas Gleixner
2013-04-23 14:34 ` Borislav Petkov
2013-04-23 15:01 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130421184749.GC3509@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox