lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 20 Dec 2013 15:10:08 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Pavel Vasilyev <pavel@...linux.ru>
Cc:	RT <linux-rt-users@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 3.12.5 CRASH/FREEZE

* 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
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?

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ