2008/12/11 Troy James Sobotka <email address hidden>:
> I'd compile a list of the suspect boards if we can separate the bug into
> those that are actually mounting but failing. For example, mine look
> like this after an 'lsusb':
>
> ID 058f:6366 Alcor Micro Corp.
> ID 058f:6254 Alcor Micro Corp.
>
> The above fix will work that is noted in the bug report. Locate your
> drive location path and perform the 'echo "128" >' etc. line.
Everybody seems to be assuming lately that this bug only affects USB
storage devices. However, I was getting these errors with a USB
wireless adapter and I'm sure other people on this buglist are not
only having trouble with storage devices. I say this because the focus
of comments recently seems to be shifting towards the assumption that
only drives are affected and how to mask/avoid that problem.
2008/12/11 Troy James Sobotka <email address hidden>:
> I'd compile a list of the suspect boards if we can separate the bug into
> those that are actually mounting but failing. For example, mine look
> like this after an 'lsusb':
>
> ID 058f:6366 Alcor Micro Corp.
> ID 058f:6254 Alcor Micro Corp.
>
> The above fix will work that is noted in the bug report. Locate your
> drive location path and perform the 'echo "128" >' etc. line.
Everybody seems to be assuming lately that this bug only affects USB
storage devices. However, I was getting these errors with a USB
wireless adapter and I'm sure other people on this buglist are not
only having trouble with storage devices. I say this because the focus
of comments recently seems to be shifting towards the assumption that
only drives are affected and how to mask/avoid that problem.
Oisín