Several USB port resets when attaching USB hard drive

Bug #545588 reported by Cristian Aravena Romero
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: gvfs

Not mount, message:
[ 101.900056] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 102.033190] usb 1-1: configuration #1 chosen from 1 choice
[ 102.111106] Initializing USB Mass Storage driver...
[ 102.111236] scsi6 : SCSI emulation for USB Mass Storage devices
[ 102.111438] usbcore: registered new interface driver usb-storage
[ 102.111441] USB Mass Storage support registered.
[ 102.119474] usb-storage: device found at 3
[ 102.119478] usb-storage: waiting for device to settle before scanning
[ 107.116241] usb-storage: device scan complete
[ 107.116717] scsi 6:0:0:0: Direct-Access Samsung S2 Portable PQ: 0 ANSI: 2 CCS
[ 107.121766] sd 6:0:0:0: Attached scsi generic sg4 type 0
[ 107.123325] sd 6:0:0:0: [sdd] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 107.124434] sd 6:0:0:0: [sdd] Write Protect is off
[ 107.124442] sd 6:0:0:0: [sdd] Mode Sense: 34 00 00 00
[ 107.124447] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 107.125954] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 107.125961] sdd: sdd1
[ 107.157210] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 107.157221] sd 6:0:0:0: [sdd] Attached SCSI disk
[ 114.928046] usb 1-1: reset high speed USB device using ehci_hcd and address 3
[ 123.928064] usb 1-1: reset high speed USB device using ehci_hcd and address 3
[ 154.928053] usb 1-1: reset high speed USB device using ehci_hcd and address 3

ProblemType: Bug
Architecture: i386
Date: Tue Mar 23 20:27:39 2010
DistroRelease: Ubuntu 10.04
HotplugNewDevices: /dev/sdd /dev/sdd1
HotplugNewMounts:

InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
Package: gvfs 1.5.5-0ubuntu1
ProcEnviron:
 LANG=es_CL.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: gvfs
Symptom: storage
Title: Does not detect hotplugged storage device
Uname: Linux 2.6.32-17-generic i686

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

(sorry "pitt" you have been subscribed by error instead of "pitti" there)

Changed in gvfs (Ubuntu):
importance: Undecided → Low
affects: gvfs (Ubuntu) → udisks (Ubuntu)
Revision history for this message
Martin Pitt (pitti) wrote :

Thanks for your report. I assume mounting the drive works just fine when you manually click on it in nautilus or the Places menu?

The problem here is

  Volume added: 'SAMSUNG'
  should_automount=0

There are some cases for which should_automount is false (0). The one that sticks out is that gvfs has this logic:

          /* If a volume (partition) appear _much later_ than when media was inserted it
           * can only be because the media was repartitioned. We don't want to automount
           * such volumes.
           */
          now = time (NULL);
          if (now - g_gdu_drive_get_time_of_last_media_insertion (volume->drive) > 5)
            volume->should_automount = FALSE;

and indeed:

Showing information for /org/freedesktop/UDisks/devices/sdd
  detected at: mar 23 mar 2010 20:28:34 CLST

Showing information for /org/freedesktop/UDisks/devices/sdd1
  detected at: mar 23 mar 2010 20:29:06 CLST

This delay is caused by the large number of USB resets. I think not automounting here is a cautious approach, since doing so while the drive is being reset can actually lead to data corruption.

So I assign that to linux, for the USB resets.

affects: udisks (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Triaged
summary: - Does not detect hotplugged storage device
+ Several USB port resets when attaching USB hard drive
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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