From: Clemens Ladisch <clemens@ladisch.de>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Jiri Slaby <jslaby@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: /proc/interrupts has non-printable chars in kernel 3.3.1
Date: Wed, 11 Apr 2012 11:32:16 +0200 [thread overview]
Message-ID: <4F854FA0.2000809@ladisch.de> (raw)
In-Reply-To: <201204102023.07775.toralf.foerster@gmx.de>
Toralf Förster wrote:
> Jiri Slaby wrote at 20:19:57
>> On 04/10/2012 07:34 PM, Toralf Förster wrote:
>>> 47: 289270 468524 PCI-MSI-edge @\x05��
>>> 48: 297 413 PCI-MSI-edge snd_hda_intel
>>
>> It would be great if you could dig out of dmesg, who is bound to the
>> interrupt.
>
> snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
Two HDA controllers are typically for the on-board codec and for the
GPU's HDMI outputs.
snd-hda-intel uses KBUILD_MODNAME for this string, so in theory, it
should not be possible for garbage to appear if the same string for
irq 48 is OK.
Which device is 0:1b.0 (see lspci)? And does the high number of
interrupts indicate that you did play sounds through it?
Regards,
Clemens
prev parent reply other threads:[~2012-04-11 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 17:34 /proc/interrupts has non-printable chars in kernel 3.3.1 Toralf Förster
2012-04-10 18:19 ` Jiri Slaby
2012-04-10 18:23 ` Toralf Förster
2012-04-11 9:32 ` Clemens Ladisch [this message]
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=4F854FA0.2000809@ladisch.de \
--to=clemens@ladisch.de \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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