lkml.org 
[lkml]   [2011]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: non-printable characters in /proc/interrupts
Toralf Förster wrote:
> Randy Dunlap wrote at 18:11:32
> > On Fri, 10 Jun 2011 10:40:19 +0200 Toralf Förster wrote:
> > > I've wondering about this entry at my ThinkPad T400 (kernel 2.6.39.1):
> > > ...
> > > 44: 484163 55698 PCI-MSI-edge ahci
> > > 45: 750 1809 PCI-MSI-edge eth0
> > > 46: 94 213 PCI-MSI-edge hda_intel
> > > 47: 44399 70713 PCI-MSI-edge l▒��@�E�
> > > 48: 71969 102457 PCI-MSI-edge iwlagn
> >
> > Is there any other info (like dmesg or boot log) that tells what
> > device/driver uses interrupt 47 ?
>
> I attached the dmesg output

> ahci 0000:00:1f.2: irq 44 for MSI/MSI-X
> e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> iwlagn 0000:03:00.0: irq 46 for MSI/MSI-X
> HDA Intel 0000:00:1b.0: irq 47 for MSI/MSI-X
> i915 0000:00:02.0: irq 48 for MSI/MSI-X

These interrupt numbers do not match; I'd guess that you rebooted and
that the drivers were initialized in a different order.

Anyway, it looks as if the i915 driver is the culprit.

A quick look into the DRM code shows that it uses dev->devname as
interrupt name, but that field might get freed by drm_setversion().
(Or I might be wrong; I don't have this hardware.)


Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2011-06-17 15:35    [W:0.047 / U:0.344 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site