From: Jiri Kosina <jkosina@suse.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Thomas Meyer <thomas@m3y3r.de>,
Shawn Starr <shawn.starr@rogers.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
linux-acpi@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)
Date: Thu, 14 Mar 2013 16:39:19 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1303141634440.30118@pobox.suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1303141111350.1983-100000@iolanthe.rowland.org>
On Thu, 14 Mar 2013, Alan Stern wrote:
> > > 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?
> >
> > That was my first thought, but unfortunately I am afraid there will be
> > point at which I will easily make a bisection mistake, as the
> > responsiveness of the system varies over time, so it's not really a
> > 100% objective measure.
>
> All right.
>
> There have been only three significant changes to uhci-hcd since last
> summer, and two of them appear to be completely unrelated to this
> issue. The three commits are
>
> 3171fcabb169 USB: uhci: beautify source code
> 13996ca7afd5 USB: uhci: check buffer length to avoid memory
> overflow
> 0f815a0a700b USB: UHCI: fix IRQ race during initialization
>
> Reverting the first two almost certainly will not have any effect, but
> you may as well try it anyway. The third commit may be relevant.
I have reverted all three commits, and the "nobody cared" is still there.
> If you revert all three and still see the problem then it must be
> caused by changes outside of the USB stack. Differences in interrupt
> routing could be a result of changes to PCI or ACPI. Have you compared
> the current /proc/interrupts with versions from earlier kernels without
> this problem?
The diff of stripped-down (without CPU statistics) /proc/interrupts from
some oldish working 3.1 and the current tree:
--- /tmp/interrupts-old.txt 2013-03-14 16:30:46.938710286 +0100
+++ /tmp/interrupts-new.txt 2013-03-14 16:30:18.954571413 +0100
@@ -3,27 +3,28 @@
8:IO-APIC-edge rtc0
9:IO-APIC-fasteoi acpi
12:IO-APIC-edge i8042
- 16:IO-APIC-fasteoi uhci_hcd:usb6
- 17:IO-APIC-fasteoi uhci_hcd:usb7
- 18:IO-APIC-fasteoi ata_generic, uhci_hcd:usb8
- 19:IO-APIC-fasteoi ehci_hcd:usb2
- 20:IO-APIC-fasteoi uhci_hcd:usb3
- 21:IO-APIC-fasteoi uhci_hcd:usb4
- 22:IO-APIC-fasteoi uhci_hcd:usb5
- 23:IO-APIC-fasteoi ehci_hcd:usb1
+ 16:IO-APIC-fasteoi uhci_hcd:usb4
+ 17:IO-APIC-fasteoi uhci_hcd:usb5
+ 18:IO-APIC-fasteoi ata_generic, uhci_hcd:usb6
+ 19:IO-APIC-fasteoi ehci_hcd:usb8
+ 20:IO-APIC-fasteoi uhci_hcd:usb1
+ 21:IO-APIC-fasteoi uhci_hcd:usb2
+ 22:IO-APIC-fasteoi uhci_hcd:usb3
+ 23:IO-APIC-fasteoi ehci_hcd:usb7, i801_smbus
40:PCI-MSI-edge PCIe PME
41:PCI-MSI-edge PCIe PME
42:PCI-MSI-edge PCIe PME
43:PCI-MSI-edge ahci
44:PCI-MSI-edge i915
45:PCI-MSI-edge eth0
- 46:PCI-MSI-edge iwlagn
+ 46:PCI-MSI-edge iwlwifi
47:PCI-MSI-edge snd_hda_intel
NMI:Non-maskable interrupts
LOC:Local timer interrupts
SPU:Spurious interrupts
PMI:Performance monitoring interrupts
IWI:IRQ work interrupts
+RTR:APIC ICR read retries
RES:Rescheduling interrupts
CAL:Function call interrupts
TLB:TLB shootdowns
IRQ16 is routed differently (usb4 vs usb6), so that might be relevant.
> Is occurrence of the "nobody cared" connected with any particular
> device? Somebody reported a similar problem not long ago (although IIRC
> it was for OHCI rather than UHCI) which appeared to be related to
> activity on the built-in webcam.
Will check this. No external devices are plugged in, I think the only
internal one it has is bluetooth chip. I'll try turning it off.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2013-03-14 15:39 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 19:12 [3.9-rc1] very poor interrupt responses Shawn Starr
2013-03-08 21:33 ` [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) Peter Hurley
2013-03-09 2:19 ` Alan Stern
2013-03-09 8:53 ` Thomas Meyer
2013-03-09 13:07 ` Peter Hurley
2013-03-13 21:35 ` Jiri Kosina
2013-03-14 14:51 ` Alan Stern
2013-03-14 14:51 ` Alan Stern
2013-03-14 14:56 ` Jiri Kosina
2013-03-14 15:18 ` Alan Stern
2013-03-14 15:18 ` Alan Stern
2013-03-14 15:39 ` Jiri Kosina [this message]
2013-03-14 15:47 ` Jiri Kosina
2013-03-14 16:10 ` Alan Stern
2013-03-14 16:10 ` Alan Stern
2013-03-14 16:13 ` Alan Stern
2013-03-14 16:13 ` Alan Stern
2013-03-14 16:09 ` Jiri Kosina
2013-03-14 16:42 ` Peter Hurley
2013-03-14 16:46 ` Rafael J. Wysocki
2013-03-14 17:06 ` Peter Hurley
2013-03-14 17:22 ` Rafael J. Wysocki
2013-03-14 17:26 ` Peter Hurley
2013-03-15 7:59 ` Jiri Kosina
2013-03-15 9:20 ` Harald Arnesen
2013-03-15 13:33 ` Jiri Kosina
2013-03-15 13:33 ` Jiri Kosina
2013-03-15 15:14 ` Jiri Kosina
2013-03-15 19:14 ` Yinghai Lu
2013-03-18 2:41 ` Shawn Starr
2013-03-18 9:12 ` Jiri Kosina
2013-03-18 18:57 ` Yinghai Lu
2013-03-18 22:05 ` Jiri Kosina
2013-03-18 22:50 ` Yinghai Lu
[not found] ` <alpine.LNX.2.00.1303181010080.9529-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2013-03-18 19:19 ` Daniel Vetter
2013-03-18 19:19 ` Daniel Vetter
2013-03-18 19:57 ` Chris Wilson
2013-03-18 22:04 ` Jiri Kosina
2013-03-15 15:32 ` Greg KH
2013-03-15 15:37 ` Jiri Kosina
2013-03-15 15:47 ` Greg KH
2013-03-15 16:21 ` Jiri Kosina
2013-03-18 8:21 ` Daniel Vetter
2013-03-18 15:56 ` [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)) Jiri Kosina
2013-03-18 17:04 ` Chris Wilson
2013-03-19 8:56 ` Jiri Kosina
2013-03-19 9:03 ` Chris Wilson
2013-03-18 19:21 ` Daniel Vetter
2013-03-18 11:13 ` [PATCH] drm/i915: Flush writes to GMBUS registers Chris Wilson
2013-03-18 11:51 ` Jiri Kosina
2013-03-18 12:48 ` Chris Wilson
2013-03-14 18:48 ` [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) Yinghai Lu
2013-03-11 3:38 ` [3.9-rc1] very poor interrupt responses Rafael J. Wysocki
2013-03-11 10:09 ` Harald Arnesen
2013-03-11 14:55 ` Rafael J. Wysocki
2013-03-18 7:14 [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) Thomas Meyer
2013-03-18 7:14 ` Thomas Meyer
2013-03-18 7:14 ` Thomas Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1303141634440.30118@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=rjw@sisk.pl \
--cc=shawn.starr@rogers.com \
--cc=stern@rowland.harvard.edu \
--cc=thomas@m3y3r.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.