This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Apr 26 02:54:04 2024 Delivery-date: Tue, 10 Apr 2012 20:20:17 +0200 Received: from mail-wg0-f42.google.com ([74.125.82.42]:40376 "EHLO mail-wg0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755521Ab2DJSUB (ORCPT ); Tue, 10 Apr 2012 14:20:01 -0400 Received: by wgbds11 with SMTP id ds11so3325369wgb.1 for ; Tue, 10 Apr 2012 11:20:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh Received: by 10.180.81.135 with SMTP id a7mr9328972wiy.16.1334082000736; Tue, 10 Apr 2012 11:20:00 -0700 (PDT) Received: from [192.168.2.129] ([178.22.113.142]) by mx.google.com with ESMTPS id l5sm39255017wia.11.2012.04.10.11.19.58 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 Apr 2012 11:19:59 -0700 (PDT) Message-Id: <4F8479CD.5030907@suse.cz> Date: Tue, 10 Apr 2012 20:19:57 +0200 From: Jiri Slaby User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120404 Thunderbird/13.0a2 Mime-Version: 1.0 To: =?UTF-8?B?VG9yYWxmIEbDtnJzdGVy?= Cc: linux-kernel@vger.kernel.org Subject: Re: /proc/interrupts has non-printable chars in kernel 3.3.1 References: <201204101934.34046.toralf.foerster@gmx.de> In-Reply-To: <201204101934.34046.toralf.foerster@gmx.de> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org On 04/10/2012 07:34 PM, Toralf F=C3=B6rster wrote: > The interrrupt 47 shows (with powertop) a curious "Description" : >=20 > [@^EM-W] >=20 > under a stable Gentoo Linux at a Thinkpad T400 - the BIOS is the lat= est=20 > available. FWIW I attached the output of the command $>cat /proc/int= errupts =2E.. > 47: 289270 468524 PCI-MSI-edge @=05=EF=BF=BD=EF=BF=BD It would be great if you could dig out of dmesg, who is bound to the interrupt. regards, --=20 js suse labs -- 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/