Bug 4590
| Summary: | usb external enclosure box failure | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Imre Péntek (pentek.imre) |
| Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | bunk, heitzso, stern |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.9 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 5089 | ||
| Attachments: | unusual_devs entry | ||
|
Description
Imre Péntek
2005-05-06 14:30:12 UTC
I replaced my previous kernel with 2.6.11.8, and tried the same using perfectly the same hardware... The result is very similar. the error is similar using Ubuntu Linux 5.04 too. just one remark for my note at 2005-05-08 10:07 At this time I used this unpatched kernel source: http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.8.tar.bz2 Your dmesg output does not include the USB Mass Storage verbose debugging output. Maybe you didn't install the version with debugging enabled. Can you do this again and capture all the debugging information? okay, I'll do it next week. I used this script to initialize a minimal Linux (now 2.6.11.9) (init=/bin/bash, without initrd): #!/bin/bash export PATH=/bin:/sbin:/usr/bin:/usr/sbin mount / -o remount,rw mount -t proc proc /proc mount -t sysfs sysfs /sys modprobe scsi_mod modprobe scsi_debug modprobe usbcore modprobe usb-storage loadkeys hu udev udevd udevinit udevstart syslogd klogd dbus-daemon-1 --system hald ########## But maybe I was wrong, and it can't notice if this usb device is attached. Where's your USB Mass Storage debugging output? In this configuration there aren't any usb messages, seems like kernel can't notice if I plug this device. Maybe I shouldn't use modules? Now I recompiled the kernel, I used somewhere <Y> instead of <M> and worked properly. Here is the full dmesg output, this was after I unplugged the usb device: http://people.inf.elte.hu/pentek_i/dmesg/dmesg_2.6.11.9.txt I don't have any (other) scsi devices, but somehow this usb device was sdb (not a big bug, but be aware) I hope this one will be helpful. Created attachment 5066 [details]
unusual_devs entry
This patch may help. It's meant for 2.6.12-rc4; it won't work with 2.6.11.
If you don't feel like upgrading just now, you could instead try doing
rmmod ehci-hcd
and running at full speed instead of high speed. Probably your drive will work
okay at the lower speed.
My device works well when ehci_hcd unloaded. thanks for your kind help. But anyways I want to try this patch just for fun :) As I suppose I will need this: http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.12-rc4.bz2 And the patch posted by you. But what kernel source to use? That's right. The patch-2.6.12-rc4 file applies to the 2.6.11 kernel source. Is this bug related to the USB2 storage bug flagged in kernel bug report 4057 http://bugme.osdl.org/show_bug.cgi?id=4057 And, if so, does .12-rc5 include the patch flagged on this page? I've got to get my 3 USB2 300G drives working (ubuntu) to backup 10G and 12G DV files and am getting beaten to a pulp by filesystem corruption problems due to USB2 problems when moving these big files back and forth. (3 expensive silverriver usb2 enclosures, 3 brand new WD 300G caviar drives). Thanks. Entry 4057 actually contains about 5 different bug reports, and for all I know they are all caused by different bugs. There's no way to tell if any of them is the same as this one. The patch on this page is _not_ included in 2.6.12-rc5 because it has never been tested. Even if it was tested and did work correctly, it won't help fix any of the problems listed for that other bug report. As it looks like this is completed, I'm closing this bug. |