usb storage devices are no longer recognised by the kernel
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
Bug Description
1. Normal boot up (either from the internal HDD or from the usb stick Kubuntu Live Session)
2. Mount the usb stick and then unmount (get the "Safely remove" message, but do NOT remove the stick from the usb)
3. Restart the laptop (let it boot-up using the internal HDD)
Expected: next session should recognize USB devices (even if it won't "see" the device I left in the USB, it should at least detect its removal or other new devices)
Actual: rebooting with the USB device still plugged in (after the "safely remove" message) somehow disables all the USB ports of the laptop; no matter if I remove the device afterwards, the USB ports activity no longer gets detected until another reboot.
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: zmb 2352 F.... pulseaudio /dev/snd/controlC0: zmb 2352 F.... pulseaudio
DistroRelease: Ubuntu 14.04
MachineType: Acer Extensa 2510
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
Tags: trusty
Uname: Linux 3.13.0-83-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 12/18/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.26
dmi.board.
dmi.board.name: BA50_HB
dmi.board.vendor: Acer
dmi.board.version: V1.26
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.name: Extensa 2510
dmi.product.
dmi.sys.vendor: Acer
| affects: | ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu) |
| description: | updated |

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the latest v4.6 kernel[0].
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
[0] http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v4.6-rc1- wily/