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

Message-ID: <4F8479CD.5030907@suse.cz>
Date:	Tue, 10 Apr 2012 20:19:57 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	Toralf Förster <toralf.foerster@....de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: /proc/interrupts has non-printable chars in kernel 3.3.1

On 04/10/2012 07:34 PM, Toralf Förster wrote:
> The interrrupt 47 shows (with powertop) a curious "Description" :
> 
> [@^EM-W] <interrupt>
> 
> under a stable Gentoo Linux at a Thinkpad T400  - the BIOS is the latest 
> available. FWIW I attached the output of the command  $>cat /proc/interrupts
...
>  47:     289270     468524   PCI-MSI-edge      @.��

It would be great if you could dig out of dmesg, who is bound to the
interrupt.

regards,
-- 
js
suse labs

--
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/