usb storage devices are no longer recognised by the kernel

Bug #1563491 reported by Andrei Dobrea
8
This bug affects 1 person
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=/vmlinuz-3.13.0-83-generic root=UUID=49bf7b42-01d5-4ba6-9049-c495c5a6e20e ro rootflags=subvol=@ quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware 1.127.20
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.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA50_HB
dmi.board.vendor: Acer
dmi.board.version: V1.26
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnExtensa2510:pvrV1.26:rvnAcer:rnBA50_HB:rvrV1.26:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Extensa 2510
dmi.product.version: V1.26
dmi.sys.vendor: Acer

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote :
affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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/KernelMainlineBuilds . 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/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1563491

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : BootDmesg.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : CRDA.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : IwConfig.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : Lspci.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : Lsusb.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : ProcEnviron.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : ProcModules.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : RfKill.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : UdevDb.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : UdevLog.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote : WifiSyslog.txt

apport information

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote :

I am happy to report that I now no longer reproduce the problem; it may be that the RO update server is faulty though.
---

I had to install some dependencies for running apport-collect and, in the process I switched from Romania updates server to the Main updates server (the Romanian one gave me some errors). After that I received some new updates (which the RO did not seem to have) and I rebooted. It is now working fine.

I then had to install PyQt4, but pip3 always reported that it cannot find a source, so I ended up removing apport-kde (and it resorted to apport-cli I guess, which worked).

@Joseph
I am sure I was able to access the external HDD on this Ubuntu OS in the past, but I cannot pinpoint the exact moment in time, nor the kernel version; since changing the apt sources/update server seems to have fixed the problem, it doesn't matter any more.

If you need anything on my part, please don't hesitate to ask, but I think that this can be closed (maybe try to investigate more regarding the mirror servers in RO ?).

Thank you, guys, for the your time.

Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote :

I am not sure what state to choose now (invalid?).

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Andrei Dobrea (andrei-dobrea) wrote :

Hello.
Please apologise the "noise" information above...
I have managed to reproduce it again, but now at least I have the root cause. It goes like this:

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.

So it has nothing to do with updates, please ignore my babbling on the matter.
If you cannot reproduce this issue or you need more information on my part, please let me know.

Regards,
Andrei.

description: updated
Revision history for this message
penalvch (penalvch) wrote :

Andrei Dobrea, as per http://www.acer.com/ac/en/US/content/drivers an update to your computer's buggy, insecure, and outdated BIOS is available (1.32). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

description: updated
tags: added: bios-outdated-1.32
removed: dist-upgrade
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.