if i remove device after it hangs something is printed on stdout
see attachment
** Attachment added: stdout errors
http://librarian.launchpad.net/7337346/stdout.txt
--
USB mass storage stops working after a while
https://bugs.launchpad.net/bugs/61235
You received this bug notification
** Changed in: udev (Ubuntu)
Assignee: Scott James Remnant = (unassigned)
--
USB mass storage stops working after a while
https://bugs.launchpad.net/bugs/61235
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team
Status: Needs Info = Confirmed
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have this issue not only with a USB mass storage device but also with
an Artec T14 DVB stick. I'm using the newest kernel from feisty repos.
My issue is different from the description. My devices aren't recognized
at all.
--
USB mass storage stops working after a while
** Changed in: linux-source-2.6.19 (Ubuntu)
Status: Unconfirmed = Rejected
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I've been experiancing these problems, added the rule..
BUS==scsi, SYSFS{vendor}==RockChip, RUN+=/bin/sh -c '/bin/echo 128
/sys/block/%k/device/max_sectors'
and it seems to be working fine (copied a 117mb file onto the disk, and
read a 96mb file from the disk.
--
USB mass storage stops
I already tried that in the past and it made no difference.
I think I must be stress-testing the USB disk a lot more than anyone
else here. Try backing up your home directory to an USB disk using
rdiff-backup! :)
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
No, I don't think it's just stress; I regularly run an entire Ubuntu OS
off my external 160GB for days and days of usage, including backports
work, video encoding/copying/transcoding, backing up, you name it
On Fri, 2007-01-05 at 22:24 +, Gustavo Carneiro wrote:
I already tried that in
Tested against 2.6.20-3; problem remains.
:-(
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Please retest against 2.6.20-2 when it is available in the feisty
archive.
** Changed in: linux-source-2.6.19 (Ubuntu)
Sourcepackagename: linux-source-2.6.19 = linux-source-2.6.20
Status: Confirmed = Needs Info
--
USB mass storage stops working after a while
Could people running feisty try this rule instead:
SUBSYSTEM==block, SUBSYSTEMS==scsi, ATTRS{vendor}==RockChip,
ATTR{max_sectors}=128
(Note that the use of plural vs singular and == vs = is deliberate)
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
A few days back I did a test for the external USB disk, which failed in
the middle of a backup as usual. Without rebooting, today I inserted a
simple USB flash disk, and it doesn't work:
[172878.782917] usb 3-5: new high speed USB device using ehci_hcd and address 7
[172885.168523] usb 3-5:
What does this sysfs attribute do? limit the size of the disk?
** Changed in: udev (Ubuntu)
Importance: Undecided = Wishlist
Assignee: (unassigned) = Scott James Remnant
Status: Unconfirmed = Needs Info
--
USB mass storage stops working after a while
I should point out that max_sectors = 128 doesn't solve my problem at
all, so it is certainly not the solution to _this_ bug; maybe it fixes
the other bug which was marked as dup of this one, maybe they're not the
same bug after all...
--
USB mass storage stops working after a while
http://www.linux-usb.org/FAQ.html#i5
For USB Mass Storage devices (that is, devices which use the usb-
storage driver) max_sectors controls the maximum amount of data that
will be transferred to or from the device in a single command.
--
USB mass storage stops working after a while
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed = Fix Committed
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Unfortunately, GO_SLOW does not fix it. It needs max_sectors to be set
to 128. This should either be done in the kernel or userspace. I
understand that one class of USB mass storage controllers (the genesis
series?) get max_sectors=64 set automagically.
This device needs the same workaround
The following udev rule fixes the bug for me. It's currently the best
way I've found to set max_sectors from udev (for some reason
SYSFS{max_sectors}=128 does nothing)
BUS==scsi, SYSFS{vendor}==RockChip, RUN+=/bin/sh -c '/bin/echo 128
/sys/block/%k/device/max_sectors'
--
USB mass storage stops
Your trick of setting max_sectors to 128 didn't work for me; same
problem as before..
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
dmesg output again:
[42466.244022] EXT3 FS on sda2, internal journal
[42466.244085] EXT3-fs: mounted filesystem with ordered data mode.
[42861.724469] usb 3-3: reset high speed USB device using ehci_hcd and address 2
[42867.492402] usb 3-3: device not accepting address 2, error -110
I did some more testing on this last night, and it seems like
max_sectors is OK up to 128, but going any higher causes the device to
disconnect. after some more investigation, it appears like 128 matches
Windows XP's behavior, which explains why Windows doesn't bork on
transfers.
The kernel
Ben, here's the lsusb output for my device. It's the Domain
Technologies one.
As far as the original bug reporter, I'm guessing he'll need to provide his
lsusb, too.
** Attachment added: lsusb output
http://librarian.launchpad.net/4439277/lsusb.out
--
USB mass storage stops working after
http://paste.ubuntu-nl.org/24737
A pastebin of what I see... The connection was stable until I tried to
copy a 5MB file into the MP3 player.
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
UPDATE:
Setting max_sectors in /sys/block/sdb/device to 32 (default 240), in an
attempt to throttle speed, fixes this issue... So it must be that the
problem is triggered by writing to the USB device too fast?
Maybe the kernel should have some sort of throttling mechanism.
--
USB mass storage
** Attachment added: output of lspci (-n, -t, and plain)
http://librarian.launchpad.net/4311201/lspci.out
--
USB mass storage stops working after a while
https://launchpad.net/bugs/61235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
About this part:
[37974.978380] 0:0:0:0: rejecting I/O to dead device
[37974.978383] Buffer I/O error on device sda2, logical block 0
[37974.978385] lost page write due to I/O error on sda2
[38055.734000] usb 3-3: new high speed USB device using ehci_hcd and address 7
[38061.499838] usb 3-3:
I can confirm this happening on two Centrino Duo laptops. The problem is
quite fascinating in my testing: (fascinating meaning that the ubuntu
kernel team should probably reach for aspirin before reading on)
(1) It happens only when certain USB mass storage devices AND certain
USB controllers are
101 - 127 of 127 matches
Mail list logo
