Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932782Ab3CNOvh (ORCPT ); Thu, 14 Mar 2013 10:51:37 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:52421 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757315Ab3CNOve (ORCPT ); Thu, 14 Mar 2013 10:51:34 -0400 Date: Thu, 14 Mar 2013 10:51:33 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Jiri Kosina cc: Peter Hurley , Thomas Meyer , Shawn Starr , Kernel development list , USB list , , "Rafael J. Wysocki" , Bjorn Helgaas , Subject: Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3085 Lines: 60 On Wed, 13 Mar 2013, Jiri Kosina wrote: > OK, this is a "me too", on Thinkpad x200s. > > [ 4.116847] irq 16: nobody cared (try booting with the "irqpoll" option) > [ 4.116849] Pid: 1, comm: systemd Not tainted 3.9.0-rc2-00188-g6c23cbb #186 > [ 4.116850] Call Trace: > [ 4.116860] [] __report_bad_irq+0x38/0xf0 > [ 4.116862] [] note_interrupt+0x1f3/0x240 > [ 4.116865] [] handle_irq_event_percpu+0x147/0x230 > [ 4.116867] [] handle_irq_event+0x49/0x70 > [ 4.116869] [] handle_fasteoi_irq+0x61/0x100 > [ 4.116873] [] handle_irq+0x59/0x150 > [ 4.116877] [] ? irq_enter+0x16/0x80 > [ 4.116879] [] do_IRQ+0x5b/0xe0 > [ 4.116883] [] common_interrupt+0x6d/0x6d > [ 4.116888] [] ? cfb_imageblit+0x581/0x5b0 > [ 4.116891] [] bit_putcs+0x329/0x560 > [ 4.116893] [] ? bit_cursor+0x5cf/0x630 > [ 4.116896] [] fbcon_putcs+0xf8/0x130 > [ 4.116898] [] ? bit_cursor+0x630/0x630 > [ 4.116900] [] fbcon_redraw+0x16e/0x1e0 > [ 4.116902] [] fbcon_scroll+0x264/0xe40 > [ 4.116905] [] scrup+0x113/0x120 > [ 4.116907] [] lf+0x80/0x90 > [ 4.116910] [] do_con_trol+0xcd/0x1360 > [ 4.116912] [] do_con_write+0x2b5/0xa10 > [ 4.116915] [] ? __mutex_lock_slowpath+0x237/0x2e0 > [ 4.116917] [] con_write+0x19/0x30 > [ 4.116920] [] do_output_char+0x1eb/0x220 > [ 4.116922] [] process_output+0x46/0x70 > [ 4.116924] [] n_tty_write+0x13f/0x2f0 > [ 4.116928] [] ? try_to_wake_up+0x2b0/0x2b0 > [ 4.116930] [] tty_write+0x1cc/0x280 > [ 4.116932] [] ? n_tty_ioctl+0x110/0x110 > [ 4.116934] [] redirected_tty_write+0xad/0xc0 > [ 4.116937] [] vfs_write+0xcb/0x130 > [ 4.116939] [] sys_write+0x5c/0xa0 > [ 4.116943] [] system_call_fastpath+0x16/0x1b > [ 4.116943] handlers: > [ 4.116959] [] usb_hcd_irq [usbcore] > [ 4.116960] Disabling IRQ #16 > > I don't think I have seen this message on rc1+ (8343bce, to be precise), > but I have definitely seen sluggish system response on that kernel as > well. > > Attaching lspci, /proc/interrupts and dmesg. Can you try to do a git bisect for this? Is the sluggish system response clear enough that you can tell reliably when it is present and when it isn't? 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/