Bug #10850

Some USB devices only work after being unplugged/re-plugged

Added by emmapeel 2016-01-04 14:35:11 . Updated 2016-01-27 13:33:41 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Tails_2.0
Start date:
2016-01-04
Due date:
% Done:

100%

Feature Branch:
bugfix/10850-no-lmt-autosuspend
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

  • Seen with a Logitech USB mouse (on a laptop that also has a touchpad).
  • User claims his USB multiplier is not working from startup in Tails Jessie. Works ok on Tails 1.8.1 and previous. After boot the adaptor needs to be unplugged/plugged to work.

Subtasks

History

#1 Updated by intrigeri 2016-01-05 13:10:44

  • Assignee set to emmapeel
  • QA Check changed from Dev Needed to Info Needed

OK, I’ve had a good look at the logs, and see:

  • a few USB hubs (not sure which ones are external);
  • no trace of unplugging/re-plugging a USB hub, so I can’t tell which one would be problematic;
  • a “USB disconnect” event for a mouse, that reappaers 13 seconds later.

So I need:

  • the output of lsusb -v
  • logs from a session during which the USB hub that doesn’t work correctly is unplugged/re-plugged at least once (ideally, the exact time when it was unplugged/re-plugged)

Given we ship the same kernel than in 1.8.1, the only possible root causes I can think of are: removed udev rules (I think a bunch of quirks were dropped), or on the contrary laptop-mode going mad.

#2 Updated by emmapeel 2016-01-05 14:10:17

  • Status changed from Confirmed to Rejected

We cannot follow up with the user because of anonymous report…

So I close it and will reopen if we get more information.

#3 Updated by intrigeri 2016-01-16 12:30:44

  • Subject changed from Tails 2.0 beta: USB adaptor does not work at startup to Some USB devices only work after being unplugged/re-plugged
  • Description updated
  • Status changed from Rejected to Confirmed
  • Assignee deleted (emmapeel)
  • QA Check deleted (Info Needed)
  • Type of work changed from Code to Research

#4 Updated by intrigeri 2016-01-16 13:33:40

  • Status changed from Confirmed to In Progress
  • Assignee set to intrigeri
  • Target version set to Tails_2.0

I got another set of logs. Sadly, there’s little to be learned from it. I’ll try one or two possible fixes, and will ask the reporter for feedback on them. It might be that it’s enough to fix this in time for 2.0, or not, but putting it on my radar, still.

#5 Updated by intrigeri 2016-01-16 13:43:17

  • Feature Branch set to bugfix/10850-no-lmt-autosuspend

#6 Updated by intrigeri 2016-01-16 15:55:44

  • % Done changed from 0 to 10

Asked the reporter to try and reproduce on a nightly build from bugfix/10850-no-lmt-autosuspend.

#7 Updated by emmapeel 2016-01-17 10:14:42

Yes!

User has reported that her mouse worked on
http://nightly.tails.boum.org/build_Tails_ISO_bugfix-10850-no-lmt-autosuspend/lastSuccessful/archive/latest.iso

without any intervention

#8 Updated by intrigeri 2016-01-17 13:34:24

  • Assignee changed from intrigeri to anonym
  • QA Check set to Ready for QA

#9 Updated by anonym 2016-01-22 14:54:06

  • Status changed from In Progress to Fix committed
  • % Done changed from 10 to 100

Applied in changeset commit:76390c2e60ff43f8cef7e08f15f41d5255547f48.

#10 Updated by anonym 2016-01-22 14:55:52

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

I pushed a small fix in commit commit:76390c2. I agree that this makes sense even if it doesn’t fix the problem => merged. I’ve optimistically closed the ticket, but we’ll reopen it if the we get reports that it’s still a problem.

#11 Updated by anonym 2016-01-27 13:33:41

  • Status changed from Fix committed to Resolved