On 13.02.2013 09:28, Holger Hoffstätte wrote: > On 12.02.2013 21:42, Sarah Sharp wrote: > > [..] > > I think I see the issue. Your host controller reports the Inactive > > state after a USB disconnect. My host controllers go to the RxDetect > > state on a disconnect. > > > > The patches that went into 3.8 and the stable kernels to better handle > > the Inactive state were not designed to handle a connected device going > > to the Inactive state. I thought that would be a rare case, but > > apparently it's not. > > > > There was a further set of patches queued for 3.9 to deal with connected > > devices going to the Inactive state, but they looked like they were too > > big for stable: > > > > d3b9d7a USB: Fix connected device switch to Inactive state. > > a24a607 USB: Rip out recursive call on warm port reset. > > 2d4fa94 USB: Prepare for refactoring by adding extra udev checks. > > 0fe51aa USB: Don't use EHCI port sempahore for USB 3.0 hubs. > > > > Can you retry with Greg's usb-next branch? > > > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git -b usb-next > > > > If that fixes your problem, we should either get those additional > > patches into 3.8 and the stable trees, or do a revert of the whole > > series and just let 3.9 carry the full patchset. > > Good news! This one does indeed work as expected - the device can be > removed and is gone for good. Upstream & Stable plz :) That kernel fixes the problem for me too. -- Matthias -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
