From: Clemens Ladisch <clemens@ladisch.de>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: non-printable characters in /proc/interrupts
Date: Fri, 17 Jun 2011 15:35:42 +0200 [thread overview]
Message-ID: <4DFB582E.7070909@ladisch.de> (raw)
In-Reply-To: <201106110038.43139.toralf.foerster@gmx.de>
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
prev parent reply other threads:[~2011-06-17 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 8:40 non-printable characters in /proc/interrupts Toralf Förster
2011-06-10 16:11 ` Randy Dunlap
2011-06-10 22:38 ` Toralf Förster
2011-06-10 23:05 ` Randy Dunlap
2011-06-17 13:35 ` 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=4DFB582E.7070909@ladisch.de \
--to=clemens@ladisch.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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