Parent hub missing LPM exit latency info

2014-05-17 Thread Heinz Diehl
Hi, first: keep me posted, I'm not subscribed to this list. When I connect an external USB 3.0 HDD, I see the following in my logs: [ 24.616996] usb 9-2: new SuperSpeed USB device number 2 using xhci_hcd [ 24.629627] usb 9-2: Parent hub missing LPM exit latency info. Power management will b

Re: Parent hub missing LPM exit latency info

2014-05-17 Thread Heinz Diehl
On 17.05.2014, Heinz Diehl wrote: Sorry, this block here is a copy & paste error, it's not from the mentioned external HDD. The problem, however, remains the same. > [ 424.790287] sd 6:0:0:0: [sdb] Device not ready > [ 424.790292] sd 6:0:0:0: [sdb] > [ 424.790293] Result: hostbyte=DID_OK dr

Re: [PATCH v2] separate usb_address0 mutexes for each bus

2014-05-17 Thread Alan Stern
On Fri, 16 May 2014, Todd E Brandt wrote: > This patch creates a separate instance of the usb_address0 mutex for each USB > bus, and attaches it to the usb_bus device struct. This allows devices on > separate buses to be enumerated in parallel; saving time. > > In the current code, there is a sin

bugzilla.kernel.org/show_bug.cgi?id=76291: system doesn't power off, just reboots

2014-05-17 Thread Wulf Richartz
Hi, I was asked to send this to you. Nice weekend kind regards Wulf Bug 76291 Summary: system doesn't power off, just reboots Product: Drivers Reporter: Wulf Component: USB Assignee: Greg Kroah-Hartman Status: NEW --- Severity: normal CC:

xhci dmesg flood on short packet

2014-05-17 Thread Parag Warudkar
I see a continuous flood of below messages on plugging in/using my USB token. (The comp code wasn't in the original message - I added it.) From what I can tell the device continues to work as expected. Should the warning be disabled for COMP_SHORT_TX like it is for COMP_STOP and COMP_STOP_INVAL

Re: [PATCH net-next v2 00/12] cdc_ncm: add buffer tuning and stats using ethtool

2014-05-17 Thread Peter Stuge
Bjørn Mork wrote: > > Just make doubly sure that you will be ok, for a long time, with using > > the ethtool coalescing interface for configuring this because you'll > > really be stuck with this forever. > > Yes, I am painfull aware of that. So I was hoping someone would jump at > this and say s