From: Oliver Neukum <oneukum-l3A5Bk7waGM@public.gmane.org>
To: Martin Mokrejs
<mmokrejs-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
Cc: "linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 3.4-rc5: usbserial pl2303 attached via Texas Instruments USB3.0 chip Oopses
Date: Wed, 2 May 2012 12:22:30 +0200 [thread overview]
Message-ID: <201205021222.30133.oneukum@suse.de> (raw)
In-Reply-To: <4FA10AC6.8030809-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
Am Mittwoch, 2. Mai 2012, 12:21:58 schrieb Martin Mokrejs:
>
> Oliver Neukum wrote:
> > interesting. There's no good reason scheduling a work should fail
> > depending on the hardware at this point. What does /proc/interrupts say?
>
> When the dongle is connected via the EHCI controller, it says:
>
> # cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3
> 0: 25 0 0 0 IR-IO-APIC-edge timer
> 1: 682 0 0 0 IR-IO-APIC-edge i8042
> 8: 50 0 0 0 IR-IO-APIC-edge rtc0
> 9: 0 0 0 0 IR-IO-APIC-fasteoi acpi
> 12: 241 0 0 0 IR-IO-APIC-edge i8042
> 16: 42804 0 0 0 IR-IO-APIC-fasteoi ehci_hcd:usb1
> 23: 367 0 0 0 IR-IO-APIC-fasteoi ehci_hcd:usb2
> 40: 0 0 0 0 DMAR_MSI-edge dmar0
> 41: 0 0 0 0 DMAR_MSI-edge dmar1
> 42: 0 0 0 0 IR-PCI-MSI-edge pciehp
> 43: 192073 0 0 0 IR-PCI-MSI-edge i915
> 44: 19744 0 0 0 IR-PCI-MSI-edge ahci
> 45: 21862 0 0 0 IR-PCI-MSI-edge eth0
> 46: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
> 47: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
> 48: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
> 49: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
> 50: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
> 51: 14 0 0 0 IR-PCI-MSI-edge mei
> 52: 889 0 0 0 IR-PCI-MSI-edge snd_hda_intel
> 53: 6 0 0 0 IR-PCI-MSI-edge iwlwifi
> NMI: 104 65 62 87 Non-maskable interrupts
> LOC: 43763 22386 26368 21843 Local timer interrupts
> SPU: 0 0 0 0 Spurious interrupts
> PMI: 104 65 62 87 Performance monitoring interrupts
> IWI: 0 0 0 0 IRQ work interrupts
> RTR: 0 0 0 0 APIC ICR read retries
> RES: 9763 5079 863 510 Rescheduling interrupts
> CAL: 106 136 130 116 Function call interrupts
> TLB: 1246 770 2069 2017 TLB shootdowns
> TRM: 0 0 0 0 Thermal event interrupts
> THR: 0 0 0 0 Threshold APIC interrupts
> MCE: 0 0 0 0 Machine check exceptions
> MCP: 13 13 13 13 Machine check polls
> ERR: 0
> MIS: 0
> #
>
> If you wanted me to reboot without the dongle inserted and plug it into the USB3.0
> socket after bootup and provide lsusb -vvxx and /proc/interrupts, please let me know. ;-)
There's on obvious difference that might be worth checking out.
Does it work if you boot with nomsi?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-05-02 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 9:57 3.4-rc5: usbserial pl2303 attached via Texas Instruments USB3.0 chip Oopses Martin Mokrejs
2012-05-02 10:08 ` Oliver Neukum
2012-05-02 10:21 ` Martin Mokrejs
[not found] ` <4FA10AC6.8030809-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
2012-05-02 10:22 ` Oliver Neukum [this message]
[not found] ` <201205021222.30133.oneukum-l3A5Bk7waGM@public.gmane.org>
2012-05-02 10:48 ` Martin Mokrejs
2012-05-02 12:44 ` Oliver Neukum
2012-05-02 23:46 ` Sarah Sharp
2012-05-03 9:14 ` Martin Mokrejs
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=201205021222.30133.oneukum@suse.de \
--to=oneukum-l3a5bk7wagm@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mmokrejs-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).