#4013 BLOC Update.: sd goes unusable after a suspend cycle

[Zarro Boogs per Child]

#4013: sd goes unusable after a suspend cycle
---------------------------+------------------------------------------------
  Reporter:  PierreOssman  |       Owner:  dwmw2                            
      Type:  defect        |      Status:  new                              
  Priority:  blocker       |   Milestone:  Update.1                         
 Component:  kernel        |     Version:  Development build as of this date
Resolution:                |    Keywords:  killjoy?                         
  Verified:  0             |    Blocking:                                   
 Blockedby:                |  
---------------------------+------------------------------------------------

Comment(by eeksock):

 My steps:

 1. Restart machine.[[BR]]
 2. Start Terminal Activity, enter df to verify that "/mount/CRUCIAL2G" (my
 SD card) appears.[[BR]]
 3. Open Journal, Click on a PDF to launch the Read activity.[[BR]]
 4. Move to a page in the middle, Zoom to Width, and wait until machine
 Suspends (the power light blinks green).[[BR]]
 5. Alt-Tab to Terminal Activity, entered df multiple times to verify that
 "/mount/CRUCIAL2G" is gone and doesn't reappear.  I did this for several
 minutes to make sure.  I also went to Journal and waited a few minutes, to
 also make sure it doesn't appear there.  In my past experience with
 Update.1-690, I have waited for up to an hour and the card never
 reappears.  Only if I manually re-mount it does it appear.[[BR]]

 I see errors in the Journal log file that look like this:

 {{{
 Traceback (most recent call last):
   File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 214, in
 maybe_handle_message
     self._handler(*args, **kwargs)
   File "/usr/share/activities/Journal.activity/volumesmanager.py", line
 90, in _hal_device_added_cb
     self._add_hal_device(udi)
   File "/usr/share/activities/Journal.activity/volumesmanager.py", line
 159, in _add_hal_device
     volume.Mount(mount_point, fs_type, options)
   File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 136, in
 __call__
     **keywords)
   File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 607, in
 call_blocking
     message, timeout)
 DBusException: org.freedesktop.Hal.Device.Volume.MountPointNotAvailable:
 The mount point '/media/CRUCIAL2G' is already occupied
 1201460296.917376 ERROR dbus.proxies: Introspect error on
 :1.5:/org/freedesktop/Hal/devices/volume_uuid_3E30_F2D0:
 dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No device
 with id /org/freedesktop/Hal/devices/volume_uuid_3E30_F2D0

 }}}

 Seems related to the problem?

-- 
Ticket URL: <http://dev.laptop.org/ticket/4013#comment:24>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system