I am seeing this problem in one or another form since ~2006, and it
looks like it will be with us for a while.
My understanding is that there may be a *number* of issues with USB 2.0
+ that end with more or less similar symptoms, producing lots of
confusion.
A number of workarounds exist, the
ссылка на этот текст :
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.17/+bug/61235/comments/123
On Sun, Sep 7, 2014 at 4:16 PM, Q 61...@bugs.launchpad.net wrote:
I am seeing this problem in one or another form since ~2006, and it
looks like it will be with us for a while.
My
I know the last comment on this ticket was more than 3 years ago, but I
thought I would add a note that this *still* seems to apply to some
devices.
I'm running the 3.14 kernel, and hooked up my old Lacie USB 500 GB hard
disk. I got identical behavior to that described in this bug report:
things
I was having disconnects after kernel 2.6.26 with a usb harddrive on an
intel mac mini. No USB quirks, or max sector changes helped. in the end
I traced the issue to kernel commit
b963801164618e25fbdc0cd452ce49c3628b46c8
I reverted the commit (had to be done manually), and everything is rock
I’ve checked the mp3 player with all ubuntu versions since 8.04. Now I have
connected (to 10.10) and it works correctly. Seems that there is a problem with
firmweare of the device, unfortunately there isn’t new updates on entryx
support page so I’ve installed different firmwere created by TEAC.
** This bug has been flagged as a security vulnerability
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@ Peter Schaefer:
as this seems like a regression between releases ... is there on special place
to put a new bug on? e.g.
https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.tag=regression-potential
** Tags added: regression-potential
--
USB mass storage stops working after a while
Seeing this still on Karmic Beta:
Linux version 2.6.31-11-generic (bui...@yellow) (gcc version 4.4.1 (Ubuntu
4.4.1-4ubuntu4) ) #38-Ubuntu SMP Fri Oct 2 11:06:40 UTC 2009
It's a 1TB Toshiba USB drive and it also needs the afm. max_sectors
trick. However, i'm under the expression that the drive
Using Seagate FreeAgent Go 500Gb drive, unable to perform sustained data
transfer.
Can confirm this issue is still in Karmic:
Linux nigel-laptop 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:23 UTC 2009
i686 GNU/Linux
As mentioned above, this:
echo 1024 /sys/block/sdb/device/max_sectors
After almost 7 weeks with no response to comment
https://bugs.edge.launchpad.net/ubuntu/+bug/61235/comments/115 I'm
closing this bug. Please feel free to reopen (by setting the status
back to New) if this issue remains in the latest release. Thanks.
** Changed in: linux (Ubuntu)
Status:
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue
The 18 month support period for Feisty Fawn 7.04 has reached it's end of
life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result,
we are closing the linux-source-2.6.20 kernel task. However, I'm adding
a linux task so that this will remain open against the actively
developed
Hello (again),
i tryed the way of Jansen Sena and compiled my own kernel.
_Disabled features (Device Drivers -- USB Support):_
* FULL speed ISO transactions (USB_EHCI_SPLIT_ISO)
* Root Hub Transaction Translators (USB_EHCI_ROOT_HUB_IT)
* Improved Transaction Translator schedulling
I tested my external USB disk (Bus 001 Device 002: ID 05e3:0702 Genesys
Logic, Inc. USB 2.0 IDE Adapter), which have still the same problem,
with the new kernel 2.6.27.
I tested the problem with badblock and the bug is still present on
2.6.27.
Now i try with uhci_hcd and have a slow but working
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I already built the disk of one of my external USB drive directly into
my PC (connected via SATA now) and gave the enclosure to a friend. The
other USB disk I have is still external, but I had never problems with
it.
So could it be possible that the problem depends on the actual
I haven't noticed any problems since Hardy - but I've built a new system
so it could be a chipset related issue I guess - no idea what chipset
unfortunately
Martin Emrich [EMAIL PROTECTED] wrote: I already built the disk of one of my
external USB drive directly into
my PC (connected via
Hi Everyone,
Unfortunately it seems this bug did not get resolved in time for the
Hardy release. Developers are currently working on the upcoming
Intrepid Ibex 8.10 release. Would anyone care to confirm this issue
with the 2.6.26 based kernel provided with Intrepid. Information
regarding the
I can assure you the issue absolutely has nothing to do with NTFS.
Yes as I said in my previous post, fault ntfs-3g is not at fault in this
case.
I emailed the manufacturer of my drives and this was their response
(unfortunately):
Fw: GreenStarME-740PS linux support
fromTiffany [EMAIL
I would suspect ntfs to be contributing to the issue but the other identical
psc has the same issue though it doesnt not need to be power cycled as often.
I can assure you the issue absolutely has nothing to do with NTFS.
--
USB mass storage stops working after a while
Failure again, while copying from a welland psc (power saving caddy) to
a normal firewire caddy. 5gb into copy.
Here is the strange ls output:
[EMAIL PROTECTED]:/mnt# ls -la usb2/
total 4
drwxrwxrwx 1 mem root 4096 2008-05-03 14:02 .
drwxr-xr-x 8 root root 88 2008-05-01 21:08 ..
drwxrwxrwx 1
Thanks Jacob. You mentioned this is resolved for you in upstream
2.6.25. I'd like to also point people to test the personal package
archive of one of our kernel devs who is helping pull the next Intrepid
Ibex 8.10 kernel together which is currently rebased with upstream
2.6.25 -
I have had both welland power saving drives fail with the errors since the
140gb copy. Interestingly the failures only seem to happen after the drives
have been idle for a long time (~ 1 hour +). Seems doing a ls /mnt/usb3 will
fail or return a weird listing. The devices will resume working
Well after alot of searching via google I came across this thread, not
much in the way of answers but enough research done to dismiss the
faulty caddy/usb controller/ hardware excuse. Seems its just an issue
with ubuntu's current kernel. 2.6.25 does not have the issue. I have
created the needed
Files finished uploading, have at it.
kernel:
http://rapidshare.de/files/39283576/linux-headers-2.6.25-custom.tar.bz2.html
[EMAIL PROTECTED]:/usr/src# sha1 linux-headers-2.6.25-custom.tar.bz2
9c0e457675b326af59c615a6423682441bf366f4 linux-headers-2.6.25-custom.tar.bz2
[EMAIL
Transfer test worked excellent last night, I shifted 140gb from 1
welland caddy to the other welland caddy (Welland caddies are one of the
ones containing the chipset pre 2.6.25 has issues with). So solution can
be confirmed.
--
USB mass storage stops working after a while
I too have had a problem which sounds similar whereby my USB device
would spin down and wait 10 or so seconds before spinning back on every
segment of a large file copy and after more research came across a
thread for bug #88746 (https://bugs.launchpad.net/ubuntu/+source/linux-
Bug seems to have resurfaced for me after upgrading to Hardy. Listening
to MP3s stored on an Iomega 500 GB external usb HD and the drive
unmounts after maybe 10, 15 minutes. Can sometimes reconnected by
powering off the HD and switching it back on but not always.
--
USB mass storage stops
Bug also occurs in hardy with the following syslog:
Apr 11 12:01:10 ak2 kernel: [ 975.711507] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Apr 11 12:01:10 ak2 kernel: [ 975.711525] end_request: I/O error, dev sdb,
sector 4155884
** Also affects:
I'm also experiencing this on Gutsy (7.10) with the 2.6.22-14-generic
kernel
My system is a Dell Vostro 1400, and the USB devices in question are
connected via a Kensington hub.
The devices are an Apple iPod, and a USB IDE drive enclosure made by
Initio (It's a generic store brand one).
After a
I am running fine with
/etc/udev/rules.d/85-ext_hd.rules
write
SUBSYSTEMS==“scsi”,DRIVERS==“sd”,KERNEL==”[0-9]*”,ATTRS{model}==“FreeAgent Go
”,ATTRS{vendor}==“Seagate ”,RUN+=”/usr/local/bin/fixFreeAgent.sh %k”
and
#!/bin/sh
echo 1 /sys/class/scsi_disk/$1/allow_restart
in
I am running fine with
/etc/udev/rules.d/85-ext_hd.rules
write
SUBSYSTEMS==“scsi”,DRIVERS==“sd”,KERNEL==”[0-9]*”,ATTRS{model}==“FreeAgent Go
”,ATTRS{vendor}==“Seagate ”,RUN+=”/usr/local/bin/fixFreeAgent.sh %k”
and
#!/bin/sh
echo 1 /sys/class/scsi_disk/$1/allow_restart
in
sudo modprobe -r ehci_hcd also worked for me, I am using ubuntu 7.10
with a Asus M2V motherboard.
My dmesg gives:
[ 5638.148000] usb 5-1: new high speed USB device using ehci_hcd and address 2
[ 5643.148000] ehci_hcd :00:10.4: Unlink after no-IRQ? Controller is
probably using the wrong IRQ.
I would like to add that I had similar problem with USB HD through
kernels 2.6.18-2.6.22 using the combination of Lacie USB 500 GB HD and
VIA VT6212L USB chip in an old PIII 500 Mhz machine using debian 4.0
(also tried ubuntu live CDs for gutsy and hardy to no avail)
USB 2.0 Device: Lacie black
After fixing the problem with some of the advice here, I started having
the problem again after I upgraded to Gutsy. I solved the problem the
same way that I did last time: modprobe -r ehci_hcd , restart.
-David
--
USB mass storage stops working after a while
modprobe -r ehci_hcd doesn't work for me :-(
--
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 mailing list
I am still being affected by this bug, in this kernel version (gutsy
amd64):
2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
--
USB mass storage stops working after a while
https://bugs.launchpad.net/bugs/61235
You received this bug notification because you are a member
can one explain me how to use the script KEYofR (
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/61235/comments/71 ) did.
where do I have to place the UDEV thing...
I figured out to place the script file in /usr/sbin
I am keen on learning but this is to much at a time for
** Attachment added: lshal.txt as per DebuggingRemovableDevices
http://launchpadlibrarian.net/10512296/lshal.txt
--
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
** Attachment added: as per DebuggingRemovableDevices
http://launchpadlibrarian.net/10512293/gvm.log
--
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
hi all,
I added a truecrypt ext3 partition to my recently-purchased Seagate FreeAgent
Go 160GB external disk. The driver was ntfs pre-formatted and auto mount worked
with no probs. unmounting was not really possible as the drive was remounted a
few seconds after unmounting (klick, no console).
Hi, my problem is not a hard disk but my nokia n73, when I plugged the
usb cable and select mass-storage mode in the phone, the phone does not
get mounted, I put at the end of this comment the relevant dmesg output.
I can't set allow_restart or max_sectors because it says permission
denied but I
I forgot to say I'm on ubuntu gutsy.
--
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 mailing list
ubuntu-bugs@lists.ubuntu.com
The most discussion here is changing the interfacing between hdd and the os.
What for me worked was simpel; Changing the jumpers.
Use the manufactuars website to be sure youve got the jumpers is the wright
settings. The jumpers (in case of connecting hdd through usb) must be set to
master.
I had problems with my WD MyBook 250Gig. Actually, I had two separate
and distinct issues. I was running the latest Ubuntu Feisty Fawn and
had the USB drive disconnecting with similar messages, and also had some
difficulties if the drive was plugged in at startup (would work fine if
it was
Look at this example
~$ cat /sys/block/sdb/device/max_sectors
240
[ Hmm. probably this is the problem. More info:
http://eliduc.berlios.de/index.php/Grabar_datos_en_un_pendrive
http://eliduc.berlios.de/index.php/Grabar_datos_en_un_pendrive#Caso_especial_-_Soluci.C3.B3n
]
~$ mount
[...]
/dev/sdb
I have an identical issue. Seagate FreeAgent 320GB.
Can confirm that the commands
echo 1024 /sys/block/sdb/device/max_sectors
echo 1 /sys/class/scsi_disk/X:0:0:0/allow_restart
work for me. (replacing X with 6 in my case).
Thanks for the temp fix. Let's hope that the kernel team fixes this.
FWIW: I was having the same problem and I appear to have come across a
solution (derived from this thread) for my particular setup at least:
Dell Latitude D620;
lsusb:
Bus 005 Device 008: ID 0b97:7762 O2 Micro, Inc. Oz776 SmartCard Reader
Bus 005 Device 006: ID 046d:c043 Logitech, Inc.
Bus 005
Follow-up on my earlier post regarding the 2.6.22 kernel from gutsy. Bad
news, it still fails in similar fashion :( It just seems that it's more
robust on 2.6.22 and does not fail as easy as on earlier kernel.
--
USB mass storage stops working after a while
https://bugs.launchpad.net/bugs/61235
I don't mean to clutter this thread with novice garble, but I was having
the same problem with my iRiver H10 mp3 player; that is, transfers would
lock up when I tried to transfer too many (or maybe too large of) files.
My /var/log/messages would show the same IO errors that everyone else
has been
Had the same problem with 2.6.20-16 using the onboard nforce2 usb
controller and a pair of Lacie 500Gb USB2.0 drives. I'm using software
raid1 on these drives.
...
Sep 4 22:50:01 dita kernel: [211049.946541] usb 3-1: reset high speed USB
device using ehci_hcd and address 4
Sep 4 22:50:31 dita
Hi,
I've experienced the same problems with my brand new ;) Entryx MP4-Player.
It didn't work as it should. Data was not written...
So I googled around and I've found some information about firmware upgrade in
german:
http://www.discountfan.de/forumneu/read.php?8,161599,162341
BUT: I've
Windows does many things in brute force inelegant ways in order to attain that
superiority.
I would rather my software be efficient and I would rather know when my
hardware (or network, or any number of configurations) has a problem and get it
fixed. It's a somewhat religeous or philosophical
For me, it finally appeared that this was a symptom of dying hardware.
After servicing the enclosure works well. The interesting fact is,
however. that even with unstable i.e. faulty hardware, Windoze was still
much less error prone than Linux. So there is room for improvement in
the driver
Well I've been poking at this a bit and have learned a few things.
I don't think the code in the fix_usb_hd.sh above is quite right. using expr to
get character 3 out of argv1 which was supplied via the udev rule code %k and
then using that value as part of the path to a spot under /sys for
I think I found another possible fix, Totally simple and userspace too.
I have a Seagate FreeAgent 500gb and I beleive I am having the drive
turns off problem and not the can't handle much traffic problem. BTW
it seems to be common to all linux not just ubuntu. I have this problem
on suse 10.2.
KEYofR wrote:
Also a question about the udev rules [...] if you detect a device by vendor
foo on scsi
You're right -- some of the udev rules posted above are overly general.
You can make them more specific by specifying the model of drive, or
even the drive serial number if you want to be that
Awsome thanks for the more specific udev rule. That's ideal since it
would apply to any FreeAgentDesktop, which obviously they all have the
same problem.
Also, by now I think I can say the sdparm fix works.
Without rebooting I did the disconnect/reconnect I mentioned, then
manually did the
Alberto,
the problem I have is that when I copy inside the external USB2 HD a large
file or
I do many access to it, through for example rsync, the HD goes in hang and
I have to restart it to make it works again.
The /var/log/messages shows me traces like:
Aug 2 12:22:23 Lucia kernel:
Hi all
I have a Freecom USB2 external HD and I have the same problem.
Basically if I copy on it a large file or I do many access to it,
through for example rsync, the HD goes in hang and I have to restart it
to make it work again.
The problem is so reproducible that I can't use the HD.
I
Sirs:
In spite of the fact I am new to this problem, I am seeing something
that may help us. My drive is working perfectly with just the addition
below:
echo 1 /sys/class/scsi_disk/X\:0\:0\:0/allow_restart
I did not use the other command that changes the max_sectors to 1024
because I think it
I had a Seagate 3.5-inch Pushbutton Backup External Hard Drive (750 GB)
connected to my server that had always worked perfectly. Then I connect
a Seagate FreeAgent Pro (750 GB) to the same server and I started seeing
the bugs described here. The bugs occur just on the new connected drive
(the
Alberto,
Try this on your FreeAgent. It solved the issue for me with spinning
down.
echo 1 /sys/class/scsi_disk/X\:0\:0\:0/allow_restart
This solved the IO/error but apparently it doesn't work for everyone.
echo 1024 /sys/block/sdX/device/max_sectors
--
USB mass storage stops working
I agree with Alberto's description of the issue -- I've seen the same behavior
with my 500G FreeAgent.
i.e., the issue happens after the drive shuts off, and then at that point, any
access seems to cause problems.
Also, JrFrost's solution has still been working for me. (although I need
to
Daniel,
The udev rules posted earlier were so you do not have to keep applying
the settings, it does it for you.
Mark
On 7/30/07, Daniel Holbert [EMAIL PROTECTED] wrote:
I agree with Alberto's description of the issue -- I've seen the same
behavior with my 500G FreeAgent.
i.e., the issue
I noticed that this bug says:
Affects Status
linux-source-2.6.17 (Ubuntu)Fix Released
at the very top. Does that mean that the bug would be fixed if I rolled back
to kernel 2.6.17?
(not sure if this is possible in Feisty -- at
I just had the same problem and haven't ever had this problem! It occured when
attaching a USB to SD card adapter (with a 1gb CD card made by Lexar) and also
a Internal HDD that's connected to a IDE-USB adapter (a Seagate 500gb
ST3500830A). This is what the error is in the syslog:
Looks like JrFrost's solution did not pass the test of time. I have
just experienced the USB disk error even after doing the /proc
configuration :-( Now I have to reboot to get it back :-/
--
USB mass storage stops working after a while
https://bugs.launchpad.net/bugs/61235
You received this
Suggested solution proven not to work in gutsy
** Changed in: udev (Ubuntu)
Status: Incomplete = Invalid
--
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
Sorry, this patch is already included in Feisty. No previous suggetion helped
me. I built some kernels, sooner or later dmesg will complain about lost pages.
We can however add this controller (it's very popular in empty enclosures from
Spire, Welland and the like) to unusual_devs.h to minimize
Has anybody tried compiling a kernel completely without any of the
experimental usb features?
--
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.
--
Yes. With or without. This doesn't seem to have any impact at all. You
may go to very, very low speed to be sure all data is written, but then
probably your broadband will be faster...
--
USB mass storage stops working after a while
https://bugs.launchpad.net/bugs/61235
You received this bug
My enclosure seems to work stable with 2.6.21.5
For the time being I didn't try Ubuntu with this kernel, but all the distros
seem to carry this bug. Then recent SLAX 6 works fine with the default
max_sectors.
It may have to do with the following change in kernel:
* Add stable release 2.6.21.5:
When upgraded to Feisty with Cypress AT2+ ATA to USB controller,
changing sectors does no longer fix the bug as if using Edgy kernel.
Lowering max_sectors does, generally, improve stability, but is no
longer an ultimate solution. For my enclosure, setting 1024 would mean
fs kernel panics and
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed = Fix Released
--
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.
--
Working usbhdfix:
#!/bin/bash
echo 1024 /sys/block/$1/device/max_sectors
echo 1 /sys/block/$1/device/scsi_disk:*/allow_restart
--
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,
Hi all,
JrFrost's solution fixes my 500G FreeAgent drive!
(his solution being:
echo 1024 /sys/block/sdX/device/max_sectors ;
echo 1 /sys/class/scsi_disk/X\:0\:0\:0/allow_restart
)
However, this setting doesn't persist after I've disconnected the drive
-- I need to run those commands every
I do not have an allow_restart setting for my external apparently. But all this
can be automated:
Udev Rule:
BUS==scsi, SYSFS{vendor}==WD, RUN+=/usr/bin/usbhdfix %k
usbhdfix:
#!/bin/bash
echo 1024 /sys/block/$1/device/max_sectors
temp=expr substr $1 3 1
echo 1
Hi people,
I don't want to say to much now because I've been disappointed before ..
But I've got my FreeAgent to work for quite some time now by doing the
following.
echo 1024 /sys/block/sdX/device/max_sectors
solved the I/O errors
echo 1 /sys/class/scsi_disk/X\:0\:0\:0/allow_restart
solved
Hey everybody, I had the same issues with a My Book 500gb. It would get
disconnected and go to sleep after a while/transferring a lot of files.
My theory of it going to sleep/disconnecting was because it was not
getting written to fast enough so I set max_sectors to 1024 (would not
go higher).
djhuang:
The errors you mention are the effect of filesystem corruption. Dirty
FAT is mounted ro, as any damaged filesystem (though different than
ext2/3 you will not see it's mounted ro). To repair it unmount the fs
first using sudo umount /dev/sda1 (assuming it's /dev/sda1) and do not
use eject
jonie,
Thanks for noticing. But I have the same error message posted above and the
target file system is ext3 formatted.
On the other hand, I did follow the work around changing the max_sector to
128, the error message disappeared
in the dmesg. So I believe the situation is much like and
I can confirm a couple of things.
1. Problem is related to some external controller / USB chip combinations.
2. AFAIK, this happens due to emulated SCSI bus being stalled by too many
sectors being transmitted in a turn.
My setup is an AT2+ (68030) enclosure by Cypress with an old 20 GB
I do have the same issue when boot from i386 desktop CD and try to install
Feisty into a SanDisk Cruzer Crossfire 4GB flash disk.
During the installation, there would be some writing errors and rejecting I/O
to dead device
message in dmesg. The first boot of this flash disk would end up
Not working after all.
[ 4661.576000] usb 5-7: reset high speed USB device using ehci_hcd and address 2
[ 4661.828000] usb 5-7: reset high speed USB device using ehci_hcd and address 2
[ 4662.08] usb 5-7: reset high speed USB device using ehci_hcd and address 2
[ 4874.296000] usb 5-7: USB
Andrew,
I changed to 0 in drivers/usb/host/ehci-hcd.c and built my kernel,
2.6.20.3.
Haven't had time to do a lot of testing yet. However it was working the few
hours I tested it. I moved a lot of data back and forth and also let it rest
for +30 min before going again.
The sessions
I believe we have found a real solution to this problem. Please try it
out and post your results so we can verify how well it works. We found
two issues which seem to contribute to this problem:
1) The EHCI controller has a setting for number of retries (1, 2, 3, or
endless). The kernel sets
Chiming in on this...
Feisty on kernel 2.6.20-16-generic #2
System is a Dell Inspiron 600m
lspci -v says the USB interface is thus:
USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI
Controller
Device is a low-profile laptop HD USB adapter.
lsusb -v says:
Bus 002 Device
Ubuntu Edgy kernel 2.6.17-11-generic
I'm pretty much having the same problem. At first I thought modprobe -r
ehci_hcd solved the issue (of course with lower speed).
But after plugging my Seagate FreeAgent 320GB in and trying to transfer a
dvd-image I get the following error.
Does anyone have an
Bad news: Jansen's solution seems to delay the problem, but not fix it
for me.
I got a new 500GB drive which dies when I try this:
# mke2fs -c /dev/sda1
The block at which it dies depends on whether I run a kernel with Jansen's
suggestion or not.
With USB_EHCI_SPLIT_ISO, USB_EHCI_ROOT_HUB_IT
Hi friends,
I was having the same problem. My external hard drive stopped work after
try to copy a lot of file to it. I got this message in dmesg:
rejecting I/O to dead device
I am able to copy a couple of large files (like DVD images) without
problems. The problem just happens when I try to
Then, I loaded the ehci_module again and tried to change the value
included in the max_sectors from 240 (default) to 128, 64 and 32. In my
desktop (a IBM Think Centre with Ubuntu Fesity Fawn) this solution
worked perfectly! But, in my laptop the problem stays happening. Then, I
tried to change
I have experienced the same problem with a TEAC external HDD usb 2.0. It
took me quite a while finding this thread as the problem is rather
difficult to describe in abstract terms.
The teac usb controller is only supported from 2.6.20, I'm running
2.6.20-16-generic
00:10.3 USB Controller: VIA
Hi pnd,
did you see my post showed two before yours?
Maybe, the steps I described there can help you to solve the problem.
Best regards,
Jansen
--
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
Boa tarde Jansen!
Thanks very much for your quick response.
modprobe -r ehci_hcd
I have tried this, and although it makes transfers unbearably slow, it
seems to stop the usbdisk from hanging up.
recompiling kernel looks a bit scary..
are there any ideas for a solution through userspace
Hi pnd,
Ok... you don't need to recompile your kernel.. I did this job for you!
:-D I recompiled the kernel just adjusting the features to make my
external HDD works fine. The other features are default in Ubuntu.
Because of that, just send an email to me and I can send to you my
.deb kernel
email sent- thanks very much!!
--
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 mailing list
ubuntu-bugs@lists.ubuntu.com
Hi friends,
there is a little mistake in my post about how I solved the problem. The
followed command:
# cd /usr/src/linux-source-2.6.20/.config
is wrong because .config is a file. The right thing to do is:
# cd /usr/src/linux-source-2.6.20
It was a kind of copy-and-paste problem! ;-)
Best
Same here.
I'm running a vmware-player session from a Iomega USB Harddisk.
Upon connect:
[ 2475.208541] usb 4-4: new high speed USB device using ehci_hcd and address 37
[ 2475.434483] usb 4-4: configuration #1 chosen from 1 choice
[ 2475.434732] scsi6 : SCSI emulation for USB Mass Storage
Having the same problem:
dmesg output:
[ 69.464000] EXT3 FS on sdc5, internal journal
[ 69.468000] EXT3-fs: mounted filesystem with ordered data mode.
[ 172.012000] sdc: Current: sense key: No Sense
[ 172.012000] Additional sense: No additional sense information
[ 202.124000] usb 4-1:
1 - 100 of 127 matches
Mail list logo
