linux-kernel - Re: /proc/interrupts has non-printable chars in kernel 3.3.1

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] [day] [month] [year] [list]

Message-ID: <4F854FA0.2000809@ladisch.de>
Date:	Wed, 11 Apr 2012 11:32:16 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Toralf Förster <toralf.foerster@....de>
CC:	Jiri Slaby <jslaby@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: /proc/interrupts has non-printable chars in kernel 3.3.1

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      @.��
>>>  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
--
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/