FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 05-11-2011, 01:58 PM
 
Default USB data corruption except in single user mode

What does it mean here on sid, when plugging in memory cards works fine
in single user mode, with only
# pstree
init-+-init---bash---emacs-+-aspell
| `-bash---pstree
`-udevd---2*[udevd]
running, but then in multi user mode, with
# pstree
init-+-acpi_fakekeyd
|-acpid
|-atd
|-bash---xterm---su---bash
|-cron
|-2*[dbus-daemon]
|-dbus-launch
|-dictd
|-emacs-+-aspell
| `-pstree
|-exim4
|-fancontrol---sleep
|-2*[getty]
|-nodm---xinit-+-Xorg
| `-nodm---bash-+-icewm-session-+-icewm
| | |-icewmbg
| | `-icewmtray
| `-ssh-agent
|-pdnsd---3*[{pdnsd}]
|-rsyslogd---3*[{rsyslogd}]
|-scim-helper-man
|-scim-launcher
|-scim-panel-gtk---{scim-panel-gtk}
|-udevd---2*[udevd]
|-wwwoffled
`-xterm---bash
running, plugging in many of the same memory cards results in
device not accepting address
device descriptor read/64, error -71
etc. etc.
Even data corruption -- gee thanks.

What process is fighting for the USB connection. I use
# Change to zero to disable usbmount
ENABLED=0
so what others might be the culprit?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87boz9nxtm.fsf@jidanni.org">http://lists.debian.org/87boz9nxtm.fsf@jidanni.org
 
Old 05-12-2011, 08:42 PM
Arno Schuring
 
Default USB data corruption except in single user mode

jidanni@jidanni.org (jidanni@jidanni.org on 2011-05-11 21:58 +0800):
> What does it mean here on sid, when plugging in memory cards works
> fine in single user mode, with only
[..]
> running, but then in multi user mode, with
[..]
> running, plugging in many of the same memory cards results in
> device not accepting address
> device descriptor read/64, error -71
> etc. etc.
> Even data corruption -- gee thanks.
Just a wild guess - in single-user mode, USB power saving is not
enabled. do a
$ cat /sys/module/usbcore/parameters/autosuspend
to check. But this is really a stretch, autosuspend is controlled
through modprobe so should work the same in any boot mode.

You might also want to check if the same usb modules are loaded in both
modes. Use
$ lsmod |grep hci
to check.

> What process is fighting for the USB connection. I use
> # Change to zero to disable usbmount
> ENABLED=0
> so what others might be the culprit?
This sort of thing can drive you nuts. I've had this problem a few
years ago, and it's really hard to find out what's really wrong. Let's
just say that not all USB devices are created equal. See
http://www.spinics.net/lists/linux-usb/msg33539.html and its thread for
an example.

My problem eventually turned out to be an underpowered external USB
hub, even though the failing devices were not connected through that
hub, and the hub itself appeared to be working fine. Giving the hub its
own power supply resolved the issue.

If you can reliably reproduce this, you still might want to take it up
on the linux-usb mailing list.


Good luck,
Arno


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110512224232.3ef9bdd3@neminis.loos.site">http://lists.debian.org/20110512224232.3ef9bdd3@neminis.loos.site
 

Thread Tools




All times are GMT. The time now is 10:07 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org