Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
Sarah Sharp writes: > > > But with RDF8 reader I just got write errors pretty quickly after starting > > writing to the Transcend SDHC. With Sandisk card it works OK just like > > with older kernels. (Also, my Nikon D60 has no trouble accessing any > > of the cards.) > > My problems with Transcend TS-RDF8W card reader are gone after TS-RDF8 firmware upgrade (from original TS08 firmware version to TS17); Also, I have upgraded firmware for NEC Corporation uPD720200 USB3 controller on my ASUS Crosshair-IV Formula mainboard to version 303408 - look for Renesas firmware); The TS17 firmware for Transcend RDF-8 is from manufacturer site (there is a version for MAC and for Windows, which I used (on another computer - laptop with Win7 installed, over USB2)). Now I have read and written data with TS-RDF8 connected to USB3 port with no problem so far. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Sun, 16 Sep 2012, Sami Farin wrote: > On Fri, Sep 14, 2012 at 12:01:36 -0700, Sarah Sharp wrote: > > some logs with the 0x4000 quirk enabled.. I tried to write to a file > on VFAT fs—the Transcend SDHC again—I got only IO error and > when mounted on USB2 port, filesystem had 0-byte file. > > sarah-quirk-dmesg.txt > (action starts at 180 seconds) > https://docs.google.com/file/d/0B_EMXtsx7o56UDUyVzlBVUpnbzg/edit > > sarah-quirk-usbmon.txt > https://docs.google.com/file/d/0B_EMXtsx7o56LXZwc19mUU1pWk0/edit For whatever help it's worth, the usbmon log shows that the second WRITE command got an error. The command attempted to write 240 blocks starting at block 4129904, which is well below the end of the disk. The error code was Aborted Command with some sort of low-level hardware error (possibly a parity error or possibly not; my outdated copy of the SCSI spec doesn't include this particular code). Incidentally, the first WRITE command, which did succeed, was for 240 blocks starting at block 4129664. There's no way to tell exactly what went wrong with the second WRITE. I suspect it is a bug in the Genesys Logic GL3220 interface. There does not appear to be any problem with the xHCI driver or hardware, as far as I can tell. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Fri, Sep 14, 2012 at 12:01:36 -0700, Sarah Sharp wrote: some logs with the 0x4000 quirk enabled.. I tried to write to a file on VFAT fs—the Transcend SDHC again—I got only IO error and when mounted on USB2 port, filesystem had 0-byte file. sarah-quirk-dmesg.txt (action starts at 180 seconds) https://docs.google.com/file/d/0B_EMXtsx7o56UDUyVzlBVUpnbzg/edit sarah-quirk-usbmon.txt https://docs.google.com/file/d/0B_EMXtsx7o56LXZwc19mUU1pWk0/edit -- Do what you love because life is too short for anything else. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Fri, 14 Sep 2012, Sami Farin wrote: > I forgot to tell this quirk was not enabled in usb-next > [4.299978] usb-storage 2-1.5.3:1.0: Quirks match for vid 8564 pid 4000: > 4000 > (US_FL_BULK_IGNORE_TAG) > > Maybe it would have been happier with the RDF8.. Yes, that definitely is part of the story. But even if that quirk had been present, something would have gone wrong. A write command failed. Maybe with the quirk we would know why it failed. Try again with the quirk enabled and see what happens. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Fri, Sep 14, 2012 at 12:01:36 -0700, Sarah Sharp wrote: > On Fri, Sep 14, 2012 at 12:49:59PM +0300, Sami Farin wrote: > > Hello, > > > > thanks for analyzing my logs =) > > I tried usb-next kernel. It works much better with sanXi reader > > (<20120824111628.usmh54g2iv2yx...@m.safari.iki.fi> for more info), > > though not very fast read/write speeds (can xhci debug slow it down?). I forgot to tell this quirk was not enabled in usb-next [4.299978] usb-storage 2-1.5.3:1.0: Quirks match for vid 8564 pid 4000: 4000 (US_FL_BULK_IGNORE_TAG) Maybe it would have been happier with the RDF8.. > Yes, xHCI debug can slow it down. The logs show it is running at USB > 3.0 speeds, so if turning off debugging doesn't help, it may be the > device is just not very fast. Or maybe the xHCI driver needs more > performance tuning (although I have seen at least 200 MB/s with a 512KB > block size with O_DIRECT to /dev/null). usbmon slowed by a factor of 2.6, so I started thinking.. Do you have ASMedia ASM1042 in some of your test machines? > > But with RDF8 reader I just got write errors pretty quickly after starting > > writing to the Transcend SDHC. With Sandisk card it works OK just like > > with older kernels. (Also, my Nikon D60 has no trouble accessing any > > of the cards.) > > > > dmesg-xhci.txt > > https://docs.google.com/file/d/0B_EMXtsx7o56Z2dFYnpUM05iNFk/edit > > The RDF8 reader just happened to successfully respond to the Set Address > Device, and it looks like there's no xHCI errors, so I think the issue > must be with the SCSI command responses. I'm not a SCSI expert, so > maybe Alan has the time to take a look at them? > > > usbmon-rdf8-usb3.txt > > https://docs.google.com/file/d/0B_EMXtsx7o56OWNSTEVkX2xkRnc/edit > > > > usbmon-rdf8-usb2.txt > > https://docs.google.com/file/d/0B_EMXtsx7o56ZUd1Tk9DR2xlTGM/edit > > Sarah Sharp -- Do what you love because life is too short for anything else. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Fri, Sep 14, 2012 at 12:49:59PM +0300, Sami Farin wrote: > Hello, > > thanks for analyzing my logs =) > I tried usb-next kernel. It works much better with sanXi reader > (<20120824111628.usmh54g2iv2yx...@m.safari.iki.fi> for more info), > though not very fast read/write speeds (can xhci debug slow it down?). Yes, xHCI debug can slow it down. The logs show it is running at USB 3.0 speeds, so if turning off debugging doesn't help, it may be the device is just not very fast. Or maybe the xHCI driver needs more performance tuning (although I have seen at least 200 MB/s with a 512KB block size with O_DIRECT to /dev/null). > But with RDF8 reader I just got write errors pretty quickly after starting > writing to the Transcend SDHC. With Sandisk card it works OK just like > with older kernels. (Also, my Nikon D60 has no trouble accessing any > of the cards.) > > dmesg-xhci.txt > https://docs.google.com/file/d/0B_EMXtsx7o56Z2dFYnpUM05iNFk/edit The RDF8 reader just happened to successfully respond to the Set Address Device, and it looks like there's no xHCI errors, so I think the issue must be with the SCSI command responses. I'm not a SCSI expert, so maybe Alan has the time to take a look at them? > usbmon-rdf8-usb3.txt > https://docs.google.com/file/d/0B_EMXtsx7o56OWNSTEVkX2xkRnc/edit > > usbmon-rdf8-usb2.txt > https://docs.google.com/file/d/0B_EMXtsx7o56ZUd1Tk9DR2xlTGM/edit Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Thu, Sep 13, 2012 at 14:57:20 -0700, Sarah Sharp wrote: > On Sat, Aug 25, 2012 at 12:31:46PM +0300, Sami Farin wrote: ... > > I plugged rdf8 reader into usb3 port, mounted it (vfat), > > cat garbage > out.bin , at the end ls showed a bit over 25200 byte file, > > then empty dir listing (df showed input/output error). When mounted > > with rdf8 reader plugged into usb2 port the dir listing was intact, > > like it did not manage to write anything when in usb3.. > > Hi Sami, > > I'm back from vacation and I took a look at your log. It seems like > your device works fine for a while, and then it doesn't respond to a > transfer. The usb-storage driver attempts to reset it, and the Set > Address command times out, which causes issues in the xHCI driver. Hello, thanks for analyzing my logs =) I tried usb-next kernel. It works much better with sanXi reader (<20120824111628.usmh54g2iv2yx...@m.safari.iki.fi> for more info), though not very fast read/write speeds (can xhci debug slow it down?). But with RDF8 reader I just got write errors pretty quickly after starting writing to the Transcend SDHC. With Sandisk card it works OK just like with older kernels. (Also, my Nikon D60 has no trouble accessing any of the cards.) dmesg-xhci.txt https://docs.google.com/file/d/0B_EMXtsx7o56Z2dFYnpUM05iNFk/edit usbmon-rdf8-usb3.txt https://docs.google.com/file/d/0B_EMXtsx7o56OWNSTEVkX2xkRnc/edit usbmon-rdf8-usb2.txt https://docs.google.com/file/d/0B_EMXtsx7o56ZUd1Tk9DR2xlTGM/edit -- Do what you love because life is too short for anything else. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Thu, 13 Sep 2012, Sarah Sharp wrote: > > I plugged rdf8 reader into usb3 port, mounted it (vfat), > > cat garbage > out.bin , at the end ls showed a bit over 25200 byte file, > > then empty dir listing (df showed input/output error). When mounted > > with rdf8 reader plugged into usb2 port the dir listing was intact, > > like it did not manage to write anything when in usb3.. > > Hi Sami, > > I'm back from vacation and I took a look at your log. It seems like > your device works fine for a while, and then it doesn't respond to a > transfer. The usb-storage driver attempts to reset it, and the Set > Address command times out, which causes issues in the xHCI driver. It would be interesting to know why the device failed to respond to the transfer. Presumably the same sequence of commands would be sent for USB-2 and USB-3 connections (unless the drive uses UAS). Why would a command work at high speed but crash the device at SuperSpeed? And what was the offending command? A usbmon trace would help answer these questions. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Sat, Aug 25, 2012 at 12:31:46PM +0300, Sami Farin wrote: > On Sat, Aug 25, 2012 at 15:10:13 +0800, Andiry Xu wrote: > ... > > > > > > 3.6.0-rc2-g6dab7ede has some funny printk's , but it panics on network use > > > so I am back to 3.5.0-rc7-g84a1caf: > > > > > > <5>[5.163846] scsi 10:0:0:0: bad extra_isize (%u != %u)Direct-Access > > >Generic STORAGE DEVICE TS07 PQ: 0 ANSI: 0 > > > <3>[ 2277.412255] sd 10:0:0:1: 6mpf: %llx > > > > > > > > >> This would seem to indicate another type of bug in the host controller. > > >> Apparently it reported normal completion for a transfer that was > > >> cancelled. > > > > > > Can these be worked around in kernel, or is firmware update needed > > > for asmedia? I have latest BIOS from Asus... > > > > A dmesg with CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING would > > be helpful. > > these with git/torvalds/linux-2.6.git 2d809dcd88f590 > > I plugged rdf8 reader into usb3 port, mounted it (vfat), > cat garbage > out.bin , at the end ls showed a bit over 25200 byte file, > then empty dir listing (df showed input/output error). When mounted > with rdf8 reader plugged into usb2 port the dir listing was intact, > like it did not manage to write anything when in usb3.. Hi Sami, I'm back from vacation and I took a look at your log. It seems like your device works fine for a while, and then it doesn't respond to a transfer. The usb-storage driver attempts to reset it, and the Set Address command times out, which causes issues in the xHCI driver. > [ 323.724325] xhci_hcd :03:00.0: Cancel URB 8803e5bf8300, dev 1, ep > 0x2, starting at offset 0x364565f0 > [ 323.724329] xhci_hcd :03:00.0: // Ding dong! > [ 323.724364] xhci_hcd :03:00.0: Stopped on Transfer TRB > [ 323.724485] xhci_hcd :03:00.0: Removing canceled TD starting at > 0x364565f0 (dma). > [ 323.724486] xhci_hcd :03:00.0: Finding segment containing stopped TRB. > [ 323.724488] xhci_hcd :03:00.0: Finding endpoint context > [ 323.724489] xhci_hcd :03:00.0: Finding segment containing last TRB in > TD. > [ 323.724490] xhci_hcd :03:00.0: Cycle state = 0x1 > [ 323.724491] xhci_hcd :03:00.0: New dequeue segment = 880409d9c280 > (virtual) > [ 323.724492] xhci_hcd :03:00.0: New dequeue pointer = 0x36456680 (DMA) > [ 323.724494] xhci_hcd :03:00.0: Set TR Deq Ptr cmd, new deq seg = > 880409d9c280 (0x36456400 dma), new deq ptr = 880036456680 (0x36456680 > dma), new cycle = 1 > [ 323.724496] xhci_hcd :03:00.0: // Ding dong! Above, you can see that the USB core is attempting to cancel a transfer (probably because the device failed to respond to it). Then the usb-storage driver asks for a port reset: > [ 323.724524] xhci_hcd :03:00.0: set port reset, actual port 0 status = > 0x1311 > [ 323.724547] xhci_hcd :03:00.0: Port Status Change Event for port 1 > [ 323.724640] xhci_hcd :03:00.0: Successful Set TR Deq Ptr cmd, deq = > @36456681 > [ 323.775271] xhci_hcd :03:00.0: get port status, actual port 0 status > = 0x201203 The port status shows the device is still connected, and the port reset bit is set, meaning the reset is complete. > [ 323.775273] xhci_hcd :03:00.0: Get port status returned 0x100203 > [ 323.826221] xhci_hcd :03:00.0: Resetting device with slot ID 1 > [ 323.826223] xhci_hcd :03:00.0: // Ding dong! > [ 323.826814] xhci_hcd :03:00.0: Completed reset device command. > [ 323.826822] xhci_hcd :03:00.0: Successful reset device command. > [ 323.826823] xhci_hcd :03:00.0: Cached old ring, 1 ring cached > [ 323.826825] xhci_hcd :03:00.0: Cached old ring, 2 rings cached > [ 323.826826] xhci_hcd :03:00.0: Output context after successful reset > device cmd: > [ 323.826828] xhci_hcd :03:00.0: Slot Context: > [ 323.826829] xhci_hcd :03:00.0: @880036453000 (virt) @36453000 > (dma) 0x2040 - dev_info > [ 323.826831] xhci_hcd :03:00.0: @880036453004 (virt) @36453004 > (dma) 0x01 - dev_info2 > [ 323.826832] xhci_hcd :03:00.0: @880036453008 (virt) @36453008 > (dma) 0x00 - tt_info > [ 323.826833] xhci_hcd :03:00.0: @88003645300c (virt) @3645300c > (dma) 0x800 - dev_state > [ 323.826835] xhci_hcd :03:00.0: @880036453010 (virt) @36453010 > (dma) 0x00 - rsvd[0] > [ 323.826836] xhci_hcd :03:00.0: @880036453014 (virt) @36453014 > (dma) 0x00 - rsvd[1] > [ 323.826837] xhci_hcd :03:00.0: @880036453018 (virt) @36453018 > (dma) 0x00 - rsvd[2] > [ 323.826839] xhci_hcd :03:00.0: @88003645301c (virt) @3645301c > (dma) 0x00 - rsvd[3] > [ 323.826840] xhci_hcd :03:00.0: Endpoint 00 Context: > [ 323.826841] xhci_hcd :03:00.0: @880036453020 (virt) @36453020 > (dma) 0x01 - ep_info > [ 323.826843] xhci_hcd :03:00.0: @880036453024 (virt) @36453024 > (dma) 0x226 - ep_info2 > [ 323.826844] xhci_hcd :03:00.0: @880036453028 (virt)
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Sat, Aug 25, 2012 at 12:31:46 +0300, Sami Farin wrote: >... Did you get the email (360 kB), it did not show up at marc.info but I did not get delivery status notifications..? I uploaded the xhci debug log here: https://docs.google.com/open?id=0B_EMXtsx7o56eUw5dC10RDhTcmc these with git/torvalds/linux-2.6.git 2d809dcd88f590 I plugged rdf8 reader into usb3 port, mounted it (vfat), cat garbage > out.bin , at the end ls showed a bit over 25200 byte file, then empty dir listing (df showed input/output error). When mounted with rdf8 reader plugged into usb2 port the dir listing was intact, like it did not manage to write anything when in usb3.. -- Do what you love because life is too short for anything else. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Fri, Aug 24, 2012 at 7:16 PM, Sami Farin wrote: > On Sun, Jul 15, 2012 at 11:14:13 -0400, Alan Stern wrote: > ... >> In past years I have found that Genesys's devices tend to be rather >> buggy. This card reader continues the tradition. Basically, although >> the firmware works reasonably well at high speed, the SuperSpeed >> support is too buggy to be usable. >> >> My advice is to exchange the card reader for one of a different brand. > > I got £6 reader from eBay, sanXi usb3 sdcx reader.. > It reset itself to usb2 speed when I tried it in usb3 port > and in usb2 port it is quite slow (14 MB/s). > There are benchmarks done by other people with sanXi where they get good > speed (90 MB/s) but presumably they do not have any ASMedia near their > computers. > Also, (after first use) the usb3 port I used sanXi in was DEAD till I rebooted > the machine; also, other devices were not detected in the port, either. > >> Alan Stern >> >> P.S.: Sarah, the lspci information shows this xHCI controller to be an >> ASM1042 controller from ASMedia. Is this one of those known to have >> the short-packet bug? The usbmon trace shows a cancelled transfer, for >> which 0 bytes must have been received, but with actual_length equal to >> the transfer_buffer_length. > > 3.6.0-rc2-g6dab7ede has some funny printk's , but it panics on network use > so I am back to 3.5.0-rc7-g84a1caf: > > <5>[5.163846] scsi 10:0:0:0: bad extra_isize (%u != %u)Direct-Access > Generic STORAGE DEVICE TS07 PQ: 0 ANSI: 0 > <3>[ 2277.412255] sd 10:0:0:1: 6mpf: %llx > > >> This would seem to indicate another type of bug in the host controller. >> Apparently it reported normal completion for a transfer that was >> cancelled. > > Can these be worked around in kernel, or is firmware update needed > for asmedia? I have latest BIOS from Asus... A dmesg with CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING would be helpful. Thanks, Andiry > > -- > Do what you love because life is too short for anything else. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Fri, 24 Aug 2012, Sami Farin wrote: > On Sun, Jul 15, 2012 at 11:14:13 -0400, Alan Stern wrote: > ... > > In past years I have found that Genesys's devices tend to be rather > > buggy. This card reader continues the tradition. Basically, although > > the firmware works reasonably well at high speed, the SuperSpeed > > support is too buggy to be usable. > > > > My advice is to exchange the card reader for one of a different brand. > > I got �6 reader from eBay, sanXi usb3 sdcx reader.. > It reset itself to usb2 speed when I tried it in usb3 port > and in usb2 port it is quite slow (14 MB/s). > There are benchmarks done by other people with sanXi where they get good > speed (90 MB/s) but presumably they do not have any ASMedia near their > computers. > Also, (after first use) the usb3 port I used sanXi in was DEAD till I rebooted > the machine; also, other devices were not detected in the port, either. > > > Alan Stern > > > > P.S.: Sarah, the lspci information shows this xHCI controller to be an > > ASM1042 controller from ASMedia. Is this one of those known to have > > the short-packet bug? The usbmon trace shows a cancelled transfer, for > > which 0 bytes must have been received, but with actual_length equal to > > the transfer_buffer_length. > > 3.6.0-rc2-g6dab7ede has some funny printk's , but it panics on network use > so I am back to 3.5.0-rc7-g84a1caf: > > <5>[5.163846] scsi 10:0:0:0: bad extra_isize (%u != %u)Direct-Access > Generic STORAGE DEVICE TS07 PQ: 0 ANSI: 0 > <3>[ 2277.412255] sd 10:0:0:1: 6mpf: %llx > > > > This would seem to indicate another type of bug in the host controller. > > Apparently it reported normal completion for a transfer that was > > cancelled. > > Can these be worked around in kernel, or is firmware update needed > for asmedia? I have latest BIOS from Asus... I don't know the answers to all this. Sarah is the person to ask, but she will have a lot of other work to get through first when she returns from vacation. All I can tell you is that the ASM1042 controller appears to have a bug for which there is a workaround in the kernel. But that workaround may be targeted at other models, so the kernel may need a change in order to apply the workaround to the ASM1042 as well. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb3 writes fail with transcend rdf8 + ASMedia ASM1042 woes
On Sun, Jul 15, 2012 at 11:14:13 -0400, Alan Stern wrote: ... > In past years I have found that Genesys's devices tend to be rather > buggy. This card reader continues the tradition. Basically, although > the firmware works reasonably well at high speed, the SuperSpeed > support is too buggy to be usable. > > My advice is to exchange the card reader for one of a different brand. I got £6 reader from eBay, sanXi usb3 sdcx reader.. It reset itself to usb2 speed when I tried it in usb3 port and in usb2 port it is quite slow (14 MB/s). There are benchmarks done by other people with sanXi where they get good speed (90 MB/s) but presumably they do not have any ASMedia near their computers. Also, (after first use) the usb3 port I used sanXi in was DEAD till I rebooted the machine; also, other devices were not detected in the port, either. > Alan Stern > > P.S.: Sarah, the lspci information shows this xHCI controller to be an > ASM1042 controller from ASMedia. Is this one of those known to have > the short-packet bug? The usbmon trace shows a cancelled transfer, for > which 0 bytes must have been received, but with actual_length equal to > the transfer_buffer_length. 3.6.0-rc2-g6dab7ede has some funny printk's , but it panics on network use so I am back to 3.5.0-rc7-g84a1caf: <5>[5.163846] scsi 10:0:0:0: bad extra_isize (%u != %u)Direct-Access Generic STORAGE DEVICE TS07 PQ: 0 ANSI: 0 <3>[ 2277.412255] sd 10:0:0:1: 6mpf: %llx > This would seem to indicate another type of bug in the host controller. > Apparently it reported normal completion for a transfer that was > cancelled. Can these be worked around in kernel, or is firmware update needed for asmedia? I have latest BIOS from Asus... -- Do what you love because life is too short for anything else. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
