Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751399Ab2JRG5e (ORCPT ); Thu, 18 Oct 2012 02:57:34 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:52691 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750793Ab2JRG5d (ORCPT ); Thu, 18 Oct 2012 02:57:33 -0400 Message-ID: <507FA858.6090109@baka.sk> Date: Thu, 18 Oct 2012 08:57:28 +0200 From: Martin Vysny User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Alan Stern CC: Kernel development list , USB list , 1062114@bugs.launchpad.net Subject: Re: usb issue on Intel chipset: abrupt mouse movements, usb keyboard loosing key events References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3296 Lines: 76 Good day, thank you for your response, please see the answers below. On 10/17/2012 08:05 PM, Alan Stern wrote: > On Wed, 17 Oct 2012, Martin Vysny wrote: > >> Good day, >> thank you for your mail. I was finally able to reproduce the issue. I >> am attaching a dmesg output of a correct boot (please note that there >> still are several unwanted IRQs), and a dmesg output of a reproduced error. > > Did you boot with the "irqpoll" option? Judging by the log, it looks > like you did. > Nope, I didn't boot with the irqpoll boot option enabled: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=02dfb985-99c1-431d-882f-87475db02062 ro crashkernel=384M-2G:64M,2G-:128M splash elevator=noop vt.handoff=7 >> [ 67.512014] ehci_hcd 0000:00:1d.0: >Unwanted IRQ: c000 0 >> [ 67.512021] ehci_hcd 0000:00:1d.0: >Unwanted IRQ: e000 0 >> [ 67.512023] irq 17: nobody cared (try booting with the "irqpoll" option) >> [ 67.512026] Pid: 0, comm: swapper/0 Tainted: G O 3.5.0-17-generic #28 >> [ 67.512027] Call Trace: >> [ 67.512034] [] __report_bad_irq+0x29/0xd0 >> [ 67.512037] [] note_interrupt+0x175/0x1c0 >> [ 67.512041] [] ? intel_idle+0xc3/0x120 >> [ 67.512045] [] handle_irq_event_percpu+0x9f/0x1d0 >> [ 67.512047] [] handle_irq_event+0x3b/0x60 >> [ 67.512050] [] ? unmask_irq+0x30/0x30 >> [ 67.512052] [] handle_fasteoi_irq+0x4e/0xd0 >> [ 67.512053] [] ? do_IRQ+0x42/0xc0 >> [ 67.512062] [] ? enqueue_hrtimer+0x1e/0x70 >> [ 67.512064] [] ? common_interrupt+0x30/0x38 >> [ 67.512069] [] ? in_gate_area+0x10/0x50 >> [ 67.512071] [] ? intel_idle+0xc3/0x120 >> [ 67.512076] [] ? cpuidle_enter+0x15/0x20 >> [ 67.512078] [] ? cpuidle_idle_call+0x88/0x220 >> [ 67.512081] [] ? cpu_idle+0xaa/0xe0 >> [ 67.512086] [] ? rest_init+0x5d/0x68 >> [ 67.512090] [] ? start_kernel+0x35d/0x363 >> [ 67.512092] [] ? do_early_param+0x80/0x80 >> [ 67.512094] [] ? i386_start_kernel+0xa6/0xad >> [ 67.512095] handlers: >> [ 67.512098] [] usb_hcd_irq >> [ 67.512099] Disabling IRQ #17 >> [ 69.507175] ehci_hcd 0000:00:1d.0: >Unwanted IRQ: c000 0 >> [ 69.607118] ehci_hcd 0000:00:1d.0: >Unwanted IRQ: c000 0 > > The debugging output show that the EHCI controller was not the source > of the unwanted IRQs. And /proc/interrupts shows that ehci-hcd is the > only driver using IRQ #17, for the 0000:00:1d.0 device. > > The most likely explanation is that there an interrupt-routing error > and some other device is causing these problems. I don't know of any > easy way to find out what the other device is, however. > Thanks for hinting at the probable source of the problem. I am new to these things, but the /proc/interrupts lists IO-APIC-fasteoi. Perhaps there may be some relation to some APIC issue? Kind regards, Martin Vysny > Alan Stern > -- 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/