On Wed, Feb 10, 2016 at 07:13:38PM +0200, Mathias Nyman wrote:
>
> Most likely xhci is messed up after two device slots are in default state at
> the same time.
> This happens when both threads are in hub_port_init() have called
> hub_port_reset()
>
> The issue becomes visible when the the
On Wed, Feb 10, 2016 at 07:13:38PM +0200, Mathias Nyman wrote:
>
> Most likely xhci is messed up after two device slots are in default state at
> the same time.
> This happens when both threads are in hub_port_init() have called
> hub_port_reset()
>
> The issue becomes visible when the the
On 08.02.2016 15:49, Chris Bainbridge wrote:
The XHCI controller presents two USB buses to the system - one for USB 2
and one for USB 3. When only one bus is locked there is a race condition
with two threads in hub_port_init:
[8.984500] Call Trace:
[8.985698] [] schedule+0x37/0x90
[
On 08.02.2016 15:49, Chris Bainbridge wrote:
The XHCI controller presents two USB buses to the system - one for USB 2
and one for USB 3. When only one bus is locked there is a race condition
with two threads in hub_port_init:
[8.984500] Call Trace:
[8.985698] [] schedule+0x37/0x90
[
The XHCI controller presents two USB buses to the system - one for USB 2
and one for USB 3. When only one bus is locked there is a race condition
with two threads in hub_port_init:
[8.984500] Call Trace:
[8.985698] [] schedule+0x37/0x90
[8.986918] [] usb_kill_urb+0x8d/0xd0
[
The XHCI controller presents two USB buses to the system - one for USB 2
and one for USB 3. When only one bus is locked there is a race condition
with two threads in hub_port_init:
[8.984500] Call Trace:
[8.985698] [] schedule+0x37/0x90
[8.986918] [] usb_kill_urb+0x8d/0xd0
[
6 matches
Mail list logo