USB 3.0 automount after "Power off driver/safely remove"

Bug #1432459 reported by 公输目
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Ubuntu 14.04 amd64
I can not eject my USB 3.0 driver at USB 3.0 interface, but at USB 2.0 interface it's ok;

&& USB 2.0 driver at USB 3.0 interface is ok too.
&& USB 2.0 driver at USB 2.0 interface is ok too.

it's may likt this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/626874
---
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: gshmu 2237 F.... pulseaudio
 /dev/snd/controlC0: gshmu 2237 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=f4dc984b-1147-4bcc-a88a-10bbb417d88b
InstallationDate: Installed on 2015-02-25 (18 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: ASUS All Series
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=35caf531-0fd6-49e9-a463-86849f353125 ro quiet splash
ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-31-generic N/A
 linux-backports-modules-3.16.0-31-generic N/A
 linux-firmware 1.127.11
RfKill:

Tags: trusty
Uname: Linux 3.16.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85-PLUS R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd10/27/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85-PLUSR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

公输目 (yue937)
description: updated
description: updated
description: updated
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 1432459

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
公输目 (yue937) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
公输目 (yue937) wrote : BootDmesg.txt

apport information

Revision history for this message
公输目 (yue937) wrote : CRDA.txt

apport information

Revision history for this message
公输目 (yue937) wrote : CurrentDmesg.txt

apport information

Revision history for this message
公输目 (yue937) wrote : Lspci.txt

apport information

Revision history for this message
公输目 (yue937) wrote : Lsusb.txt

apport information

Revision history for this message
公输目 (yue937) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
公输目 (yue937) wrote : ProcEnviron.txt

apport information

Revision history for this message
公输目 (yue937) wrote : ProcInterrupts.txt

apport information

Revision history for this message
公输目 (yue937) wrote : ProcModules.txt

apport information

Revision history for this message
公输目 (yue937) wrote : PulseList.txt

apport information

Revision history for this message
公输目 (yue937) wrote : UdevDb.txt

apport information

Revision history for this message
公输目 (yue937) wrote : UdevLog.txt

apport information

Revision history for this message
公输目 (yue937) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated
penalvch (penalvch)
tags: added: bios-outdated-0501
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
公输目 (yue937) wrote :

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for root:
0501
03/04/2015

after update BIOS, the eject will not automount (it's ok), but using Disks click the "Power off the driver", the driver will auto-mount.

summary: - USB 3.0 automount after eject
+ USB 3.0 automount after "Power off driver"
summary: - USB 3.0 automount after "Power off driver"
+ USB 3.0 automount after "Power off driver/safely remove"
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

公输目, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: latest-bios-0501
removed: bios-outdated-0501
Revision history for this message
公输目 (yue937) wrote :

Christopher M. Penalver (penalvch), I'm sorry.
I can't login in using the new kernel. after type in password at the login screen, it will Stuck!
How can i get the package: linux-image-extra-x.xx-generic, I think it's will useful.

and when I install the new kernel, some problem raise: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1424238 and "nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build" (this is the Graphics Driver)
$ sudo dpkg -i linux-headers-4.0.0-040000rc4_4.0.0-040000rc4.201503152135_all.deb linux-headers-4.0.0-040000rc4-generic_4.0.0-040000rc4.201503152135_amd64.deb linux-image-4.0.0-040000rc4-generic_4.0.0-040000rc4.201503152135_amd64.deb

Thank you for your understanding.

Revision history for this message
penalvch (penalvch) wrote :

公输目, as per the previously provided support article, you need to uninstall the proprietary nvidia drivers first before installing the mainline kernel.

Revision history for this message
公输目 (yue937) wrote :

Christopher M. Penalver (penalvch), uninstall nvidia drivers && install kernel && install nvidia drivers && reboot
But can't login in... Stuck after type in password && Enter

tty1 login it's ok, restart lightdm can't login in tty7 too.

Revision history for this message
penalvch (penalvch) wrote :

公输目, I never said to reinstall the nvidia drivers.

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.