Sharp
On Wed, Aug 08, 2012 at 12:44:39PM -0700, Matthew Hall wrote:
Hi Sarah,
If I am reading right, this patch is not any different from the one we
were
trying to get my card reader to work on USB 3.0.
I did some further testing last with the same card, reader
Hi Sarah,
I'm wondering what to try next on the issue with my card reader running over
this controller? Should I try a fresher kernel or anything?
Regards,
Matthew.
On Wed, Aug 08, 2012 at 02:37:36PM -0700, Matthew Hall wrote:
I understand if it takes a while as it's a complex one off problem
On Sun, Sep 02, 2012 at 10:43:25PM -0400, Alan Stern wrote:
On Sun, 2 Sep 2012, Matthew Hall wrote:
I can't see any reasonable way of fixing this problem. Even if Linux
did settle for the READ CAPACITY(10) value, it would then think that
the drive was only 2 TB
Hi Sarah,
If I am reading right, this patch is not any different from the one we were
trying to get my card reader to work on USB 3.0.
I did some further testing last with the same card, reader, and exfat driver
on a USB 2.0 port on the same machine and everything worked with no errors in
. I'll be back Sept 4th.
Sarah Sharp
On Wed, Aug 08, 2012 at 12:44:39PM -0700, Matthew Hall wrote:
Hi Sarah,
If I am reading right, this patch is not any different from the one we were
trying to get my card reader to work on USB 3.0.
I did some further testing last
On Thu, Jul 26, 2012 at 11:36:44PM -0700, Matthew Hall wrote:
On Thu, Jul 26, 2012 at 11:27:47PM -0700, Sarah Sharp wrote:
Man, I hope my code hasn't eaten your disk. Is there any chance you
could replace the drive in the enclosure and create a new file system to
test?
This part
Argh! Forgot to remember to include the kern log again:
http://www.mhcomputing.net/tmp/xhci-bug/dmesg-usb-3-port-memory-patch-plugin.txt.gz
Regards,
Matthew.
On Thu, Jul 26, 2012 at 11:09:13PM -0700, Matthew Hall wrote:
On Thu, Jul 26, 2012 at 01:22:15PM -0700, Sarah Sharp wrote:
Ok, I think
On Thu, Jul 26, 2012 at 11:27:47PM -0700, Sarah Sharp wrote:
Yeah, I was kind of banging my head on the desk as well. I'm really not
sure why it wasn't causing a general protection fault, so it's possible
I could be wrong in my analysis of what the bug might do.
;-)
I did test this latest
