From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Ladisch Subject: Re: non-printable characters in /proc/interrupts Date: Fri, 17 Jun 2011 15:35:42 +0200 Message-ID: <4DFB582E.7070909@ladisch.de> References: <201106101040.20282.toralf.foerster@gmx.de> <20110610091132.90531e0e.randy.dunlap@oracle.com> <201106110038.43139.toralf.foerster@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <201106110038.43139.toralf.foerster@gmx.de> Sender: linux-kernel-owner@vger.kernel.org To: =?UTF-8?B?VG9yYWxmIEbDtnJzdGVy?= Cc: Randy Dunlap , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org List-Id: dri-devel@lists.freedesktop.org Toralf F=C3=B6rster wrote: > Randy Dunlap wrote at 18:11:32 > > On Fri, 10 Jun 2011 10:40:19 +0200 Toralf F=C3=B6rster wrote: > > > I've wondering about this entry at my ThinkPad T400 (kernel 2.6.3= 9.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=E2=96=92=EF=BF=BD= =EF=BF=BD@=EF=BF=BDE=EF=BF=BD > > > 48: 71969 102457 PCI-MSI-edge iwlagn > >=20 > > Is there any other info (like dmesg or boot log) that tells what > > device/driver uses interrupt 47 ? >=20 > 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