Re: non-printable characters in /proc/interrupts

[Clemens Ladisch]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/