From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-usb@vger.kernel.org
Cc: Alan Stern <stern@rowland.harvard.edu>,
Jan Ceuleers <jan.ceuleers@computer.org>,
Clemens Ladisch <clemens@ladisch.de>,
Simon Jones <sijones2010@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: 3.4.4: disabling irq
Date: Mon, 19 Nov 2012 17:47:06 +0100 [thread overview]
Message-ID: <50AA628A.1090405@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1211191139140.1598-100000@iolanthe.rowland.org>
On 2012-11-19 17:41, Alan Stern wrote:
>> How to proceed next?
>
> Firstly, what does /proc/interrupts say?
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 39 0 0 0 IO-APIC-edge timer
1: 716 721 730 687 IO-APIC-edge i8042
4: 1631 1603 1713 1914 IO-APIC-edge serial
9: 0 0 0 0 IO-APIC-fasteoi acpi
16: 427 437 443 447 IO-APIC-fasteoi
snd_hda_intel
17: 0 0 3 1 IO-APIC-fasteoi
ehci_hcd:usb4, ehci_hcd:usb5
18: 100443 100710 103881 116011 IO-APIC-fasteoi
ohci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
20: 8049 8235 8456 9657 IO-APIC-fasteoi serial
40: 0 0 0 0 PCI-MSI-edge AMD-Vi
43: 47534 47847 49501 52187 PCI-MSI-edge ahci
44: 118811 119571 123111 134412 PCI-MSI-edge eth0
45: 0 0 0 0 PCI-MSI-edge
xhci_hcd
46: 0 0 0 0 PCI-MSI-edge
xhci_hcd
47: 0 0 0 0 PCI-MSI-edge
xhci_hcd
48: 0 0 0 0 PCI-MSI-edge
xhci_hcd
49: 0 0 0 0 PCI-MSI-edge
xhci_hcd
50: 0 0 0 0 PCI-MSI-edge
xhci_hcd
51: 0 0 0 0 PCI-MSI-edge
xhci_hcd
52: 0 0 0 0 PCI-MSI-edge
xhci_hcd
53: 0 0 0 0 PCI-MSI-edge
xhci_hcd
54: 0 0 0 0 PCI-MSI-edge
xhci_hcd
55: 0 0 0 0 PCI-MSI-edge
xhci_hcd
56: 33 28 36 28 PCI-MSI-edge
snd_hda_intel
57: 52846 53825 56666 64450 PCI-MSI-edge radeon
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 381988 405614 348070 323872 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 Performance
monitoring interrupts
IWI: 0 0 0 0 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 1166893 1184781 1089048 1016935 Rescheduling interrupts
CAL: 34472 32009 62610 50241 Function call interrupts
TLB: 0 0 0 0 TLB shootdowns
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 8 8 8 8 Machine check polls
ERR: 4
MIS: 0
> Secondly, try building a kernel with the patch below and
> CONFIG_USB_DEBUG enabled. Let's see what the dmesg log says when the
> problem occurs.
Will do!
Udo
next prev parent reply other threads:[~2012-11-19 16:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 7:53 3.4.4: disabling irq Udo van den Heuvel
2012-07-09 13:54 ` Clemens Ladisch
2012-07-09 16:05 ` Udo van den Heuvel
2012-07-09 18:58 ` Alan Stern
2012-07-11 14:50 ` Udo van den Heuvel
2012-07-11 15:15 ` Alan Stern
2012-07-12 13:23 ` Udo van den Heuvel
2012-07-12 13:43 ` Jan Ceuleers
2012-07-12 14:02 ` Udo van den Heuvel
2012-07-12 14:54 ` Alan Stern
2012-07-15 14:28 ` Udo van den Heuvel
2012-07-15 14:36 ` Udo van den Heuvel
2012-07-15 15:35 ` Alan Stern
2012-07-15 15:55 ` Udo van den Heuvel
2012-07-15 15:57 ` Udo van den Heuvel
2012-07-15 18:28 ` Alan Stern
2012-11-04 10:31 ` Udo van den Heuvel
2012-11-17 12:35 ` Udo van den Heuvel
2012-11-19 16:41 ` Alan Stern
2012-11-19 16:47 ` Udo van den Heuvel [this message]
2012-11-20 14:41 ` Udo van den Heuvel
2012-11-20 16:14 ` Alan Stern
2012-12-01 8:52 ` Udo van den Heuvel
2012-12-01 16:54 ` Alan Stern
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=50AA628A.1090405@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=clemens@ladisch.de \
--cc=jan.ceuleers@computer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sijones2010@gmail.com \
--cc=stern@rowland.harvard.edu \
/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.