From: Pavel Vasilyev <pavel@pavlinux.ru>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: RT <linux-rt-users@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.12.5 CRASH/FREEZE
Date: Fri, 20 Dec 2013 18:57:47 +0400 [thread overview]
Message-ID: <52B45AEB.2060508@pavlinux.ru> (raw)
In-Reply-To: <20131220141008.GE10249@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
20.12.2013 18:10, Sebastian Andrzej Siewior пишет:
> * Pavel Vasilyev | 2013-12-13 00:29:52 [+0400]:
>
>> On startup, if USB webcam (uvcvideo) attached in usb-hole
>>
>> NMI backtrace for cpu 0
>> CPU: 0 PID: 35 Comm: irq/43-xhci_hcd Not tainted 3.12.5-plx #6
>
>> [<c13aa59c>] xhci_queue_isoc_tx_prepare+0x39c/0x950
>> [<c139d35f>] xhci_urb_enqueue+0x22f/0x540
>> [<c1375745>] usb_hcd_submit_urb+0x65/0x280
>> [<c13777a0>] usb_submit_urb+0x170/0x3a0
>> [<c13e1ee8>] uvc_video_complete+0xb8/0xd0
>> [<c1374625>] __usb_hcd_giveback_urb+0x45/0xa0
>> [<c1374bd8>] usb_hcd_giveback_urb+0x38/0xf0
>> [<c13a84cf>] handle_tx_event+0x3af/0xda0
>> [<c13a9082>] xhci_irq+0x1a2/0x6c0
>> [<c13a95aa>] xhci_msi_irq+0xa/0x10
>> [<c1084c31>] irq_forced_thread_fn+0x21/0x70
>> [<c1085046>] irq_thread+0x106/0x220
>> [<c1057110>] kthread+0xd0/0xe0
>> [<c15083b7>] ret_from_kernel_thread+0x1b/0x28
>
> This looks like uvc is resubmitting the URB on completion. Nothing
> unusual. Howver it seems that then CPU gets stuck in
> xhci_queue_isoc_tx_prepare() for some reason. Could you try map c13aa59c
Same bug if attach to ehci hub.
ksoftird/0 process of loading the CPU upto 100%
Sometimes process irq17/0 - ehci_hcd or xhci_hcd.
After taking the camera out of the socket, the load does not fall,
keyboard and console blocked
> to the source line? Something like
> addr2lin -e xhci-hcd.ko -i c13aa59c
>
> should do the trick but of the module of this trace.
> What does the -plx stand for in localversion? Do you have any custom
> patches on your kernel?
No patches, just local flag.
--
Pavel.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-20 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 14:47 [PATCH] rt-tests: hackbench: fix for uninitialized start time Ciprian Barbu
2013-12-12 15:14 ` Clark Williams
2013-12-12 20:29 ` 3.12.5 CRASH/FREEZE Pavel Vasilyev
2013-12-20 14:10 ` Sebastian Andrzej Siewior
2013-12-20 14:57 ` Pavel Vasilyev [this message]
2013-12-20 15:05 ` Sebastian Andrzej Siewior
2013-12-22 22:19 ` Pavel Vasilyev
2013-12-22 22:33 ` Pavel Vasilyev
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=52B45AEB.2060508@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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).