(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Sun, 15 Feb 2009 05:15:25 -0800 (PST) bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=12709 > > Summary: 2.6.28 is killing USBest 165 firmware (Corsair Flash > Voyager & A-DATA flash drives) > Product: Drivers > Version: 2.5 > KernelVersion: 2.6.28 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: blocking > Priority: P1 > Component: Flash/Memory Technology Devices This is now USB > AssignedTo: dwmw2@xxxxxxxxxxxxx This is now Greg > ReportedBy: harvie@xxxxxxxx > > > Latest working kernel version: unsure? > Earliest failing kernel version: 2.6.28 > Distribution: Arch Linux > Hardware Environment: Acer Aspire 3000 + Corsair Flash Voyager > Software Environment: > Problem Description: > > Flash Voyagers and A-Data are very popular usb thumbdrives, but their firmware > is killed after inserting&removing it in usb port on linux box few times (1 or > more) and it needs to be reflashed using windows! > > Additional info: > theres no special info in dmesg or kernel.log (its looks like everything works > OK), but device /dev/sdX is inaccessible, fdisk -l shows anything, cfdisk is > not working and you can't see partitions (/dev/sdXY)... > > These thumbdrives works well on windows systems until they are not inserted > into the Linux box. > > Steps to reproduce: > Create partition and format it to any type of FS using linux or windows. > Try to connect and disconnect it (i tried Corsair Flash Voyager 32 GB - version > with neckband - i heard it have different chipset than version without > neckband... - the USBest 165) few times to linux box. (I have hal+gnome > automount enabled, but removing mounted flashdrive still shouldn't brick the > thumbdrive - should it? and it was killed when removed after unmounting also) > > kernel.log (dmesg) output: > > *** CONNECTED > Feb 15 14:06:15 harvie-ntb usb 1-6: new high speed USB device using ehci_hcd > and address 3 > Feb 15 14:06:15 harvie-ntb usb 1-6: configuration #1 chosen from 1 choice > Feb 15 14:06:17 harvie-ntb Initializing USB Mass Storage driver... > Feb 15 14:06:17 harvie-ntb scsi2 : SCSI emulation for USB Mass Storage devices > Feb 15 14:06:17 harvie-ntb usbcore: registered new interface driver usb-storage > Feb 15 14:06:17 harvie-ntb USB Mass Storage support registered. > Feb 15 14:06:17 harvie-ntb usb-storage: device found at 3 > Feb 15 14:06:17 harvie-ntb usb-storage: waiting for device to settle before > scanning > Feb 15 14:06:22 harvie-ntb scsi 2:0:0:0: Direct-Access USBest > USB2FlashStorage 0.00 PQ: 0 ANSI: 2 > Feb 15 14:06:22 harvie-ntb sd 2:0:0:0: [sdb] Attached SCSI removable disk > Feb 15 14:06:22 harvie-ntb sd 2:0:0:0: Attached scsi generic sg2 type 0 > Feb 15 14:06:22 harvie-ntb usb-storage: device scan complete > > *** DISCONNECTED > Feb 15 14:06:30 harvie-ntb usb 1-6: USB disconnect, address 3 > > > ^^^^ so it looks like before firmware was crippled, but block device can't be > mounted or acessed by fdisk, dd and other similar tools. all data are probably > lost. but you can still repair drive using windows and firmware from this site: > > http://209.85.171.104/translate_c?hl=en&sl=ru&tl=en&u=http://flashboot.ru/index.php%3Fname%3DFiles%26op%3Dcat%26id%3D11&usg=ALkJrhjRTNKzyhieqp13n6fv_85u3v5yCA > > > This bug is NOT related to another corsair voyager bug: > http://bugzilla.kernel.org/show_bug.cgi?id=12188 > > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
