DebuggingRemovableDevices

Differences between revisions 1 and 20 (spanning 19 versions)
⇤ ← Revision 1 as of 2005-05-28 20:58:45 →
Size: 1247
Editor: adsl-213-190-44-43
Comment: imported from the old wiki
← Revision 20 as of 2007-03-25 18:12:33 → ⇥
Size: 2854
Editor: 127
Comment: merging lists
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= DebuggingRemovableDevices = ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]||

= Introduction =

Help on debugging removable device issues.

= How to report =
Line 7: Line 13:
 0. `gnome-volume-manager 2>&1 | tee gvm.log`  0. In Ubuntu 5.10 (Breezy Badger) and older
  `gnome-volume-manager 2>&1 | tee gvm.log`
 In Ubuntu 6.06 (Dapper Drake) :
  `gnome-volume-manager -n 2>&1 | tee gvm.log`[[BR]]
 and in another terminal
  `sudo udevmonitor -e | tee udev.log`
Line 11: Line 22:
 0. In Dapper press Control-C to stop the udevmonitor
Line 13: Line 25:
 0. attach `gvm.log`, `lshal.txt`, and `dmesg.txt` to the bug report
 0. restart your Gnome session to get a proper background g-v-m back		  0. `ls -l /dev/sd* > devices.txt`
 0. attach `gvm.log`, `lshal.txt`, `devices.txt`, `dmesg.txt` and `udev.log` (dapper only) to the bug report
 0. Press Alt-F2 and type `gnome-volume-manager` to get your background g-v-m back (or just log out and back in again)
Line 16: Line 29:
 0. paste the output of `id hal` into the bug report
 0. paste the output of `id haldaemon` into the bug report
 0. paste the output of `uname -a` into the bug report
Line 21: Line 37:
 0. `sudo hald --drop-privileges --daemon=no --verbose=yes 2>&1 | tee hal.log`  0. In Warty and Hoary:
  `sudo hald --drop-privileges --daemon=no --verbose=yes 2>&1 | tee hal.log`
 In Breezy and Dapper:
  `sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log`
Line 26: Line 45:
 0. `sudo /etc/init.d/dbus-1 restart` to properly restore the background hal  0. Restore the background hal:
  * `sudo /etc/init.d/dbus-1 restart` (in Warty and Hoary)
  * `sudo /etc/dbus-1/event.d/20hal start` (in Breezy and Dapper)
Line 28: Line 49:
 0. Restart your desktop session

= Debugging procedure =
TBD.

= Known bugs =

Description of known issues, how to recognise them and stock responses/actions.

'''Open'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

= Non-bugs =

TBD.

------
'''Also see:'''

 * DebuggingProcedures


----
CategoryBugSquad

Introduction

Help on debugging removable device issues.

How to report

When reporting a problem with removable devices, such as USB storage devices ("keys", hard drives, card readers, music players, digital cameras, etc.), please do the following steps:

  1. disconnect the device

  2. killall gnome-volume-manager

  3. In Ubuntu 5.10 (Breezy Badger) and older

    • gnome-volume-manager 2>&1 | tee gvm.log

    In Ubuntu 6.06 (Dapper Drake) :

    • gnome-volume-manager -n 2>&1 | tee gvm.logBR

    and in another terminal

    • sudo udevmonitor -e | tee udev.log

  4. connect the device
  5. wait a few seconds
  6. Press Control-C to stop the foreground gnome-volume-manager
  7. In Dapper press Control-C to stop the udevmonitor

  8. lshal > lshal.txt

  9. dmesg > dmesg.txt

  10. ls -l /dev/sd* > devices.txt

  11. attach gvm.log, lshal.txt, devices.txt, dmesg.txt and udev.log (dapper only) to the bug report

  12. Press Alt-F2 and type gnome-volume-manager to get your background g-v-m back (or just log out and back in again)

  13. paste the output of id into the bug report

  14. paste the output of id hal into the bug report

  15. paste the output of id haldaemon into the bug report

  16. paste the output of uname -a into the bug report

In easy cases this is everything that is needed. However, you might be asked for a "hal debug output"; please do the following steps to get it:

  1. disconnect the device

  2. sudo killall hald

  3. In Warty and Hoary:

    • sudo hald --drop-privileges --daemon=no --verbose=yes 2>&1 | tee hal.log

    In Breezy and Dapper:

    • sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log

  4. wait until the flood of messages settled
  5. connect the device
  6. wait again until no messages appear any more
  7. press Control-C to stop the foreground hal
  8. Restore the background hal:

    • sudo /etc/init.d/dbus-1 restart (in Warty and Hoary)

    • sudo /etc/dbus-1/event.d/20hal start (in Breezy and Dapper)

  9. attach hal.log to the bug report
  10. Restart your desktop session

Debugging procedure

TBD.

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

TBD.

TBD.

TBD.

Closed

Bug#

Description

Action

TBD.

TBD.

TBD.

Non-bugs

TBD.

Also see:

CategoryBugSquad

DebuggingRemovableDevices (last edited 2011-01-07 14:06:15 by 67-42-160-182)