From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755973AbYIITIj (ORCPT ); Tue, 9 Sep 2008 15:08:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753409AbYIITIb (ORCPT ); Tue, 9 Sep 2008 15:08:31 -0400 Received: from qw-out-2122.google.com ([74.125.92.25]:47635 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751731AbYIITIa (ORCPT ); Tue, 9 Sep 2008 15:08:30 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=V97tCzbphA/KxP/H7RQiYsbZ1kwBLtN7WvoJ4601fgyuuNlSa/bGGS0/Pe/8JrKbbE Hz5QS9iMS69Tjd6j7vAAsVYayxnMyUMP0S8nec9vYWpzf75GR5TxV5GLEtpEUyy3ydXt DBLnJumP8L58EijlghHTWK6/Hp+deTR/npW0w= Message-ID: Date: Tue, 9 Sep 2008 12:08:28 -0700 From: "Justin Mattock" To: "Linux Kernel Mailing List" Subject: [19.666764] Disabling IRQ #23 Cc: "April Tsui" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I've been noticing this message appear every "X" amount of boot's(maybe ten or so); [19.656768] irq 23: nobody cared (try booting with the "irqpoll" option) [19.666039] Pid: 0, comm: swapper Tainted: P 2.6.27-rc5-00363-ga002d93 [19.666764] [] __report_bad_irq+0x2e/0x6f [19.666764] [] note_interrupt+0x1e6/0x217 [19.666764] [] ? handle_IRQ_event+0x2a/0x5a [19.666764] [] handle_fastoei_irq+0x91/0xb6 [19.666764] [] do_IRQ+ox6c/0x86 [19.666764] [] common_interrupt+0x23/0x28 [19.666764] [] ? acpi_idle_enter_simple+0x19c/0x20e [processor] [19.666764] [] cpuidle_idle_call+ox5e/0x8b [19.666764] [] cpu_idle+0xda/0xfa [19.666764] [] rest_init+0x4e/0x50 [19.666764] ======================= [19.666764] handlers: [19.666764] [] (usb_hcd_irq+0x0/0x79) [19.666764] [] (usb_hcd_irq+0x0/0x79) [19.666764] Disabling IRQ #23 normally upon booting leaving me unable to login. -- Justin P. Mattock