On 8/3/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Fri, 3 Aug 2007, Oliver Neukum wrote:
>
> > Well, I've thought a bit about this. I know a hub is to blame. Even if I did
> > learn what causes this specific error, it wouldn't help in the other cases.
>
> These sorts of problems tend to be _very
On Fri, 3 Aug 2007, Oliver Neukum wrote:
> Well, I've thought a bit about this. I know a hub is to blame. Even if I did
> learn what causes this specific error, it wouldn't help in the other cases.
These sorts of problems tend to be _very_ hardware dependent. That
very same hub might work perfe
On Friday 03 August 2007, Oliver Neukum wrote:
> Well, I've thought a bit about this. I know a hub is to blame. Even if I did
> learn what causes this specific error, it wouldn't help in the other cases.
> IMHO improving error handling is better than avoiding this fault.
But do you know *how* a hu
Am Freitag 03 August 2007 schrieb Greg KH:
> On Mon, Jul 30, 2007 at 11:11:54AM -0700, David Brownell wrote:
> > On Monday 30 July 2007, Oliver Neukum wrote:
> > >
> > > > But -- never actually having had both a highspeed USB sniffer *AND*
> > > > hardware exhibiting this problem in the same place
On Mon, Jul 30, 2007 at 11:11:54AM -0700, David Brownell wrote:
> On Monday 30 July 2007, Oliver Neukum wrote:
> >
> > > But -- never actually having had both a highspeed USB sniffer *AND*
> > > hardware exhibiting this problem in the same place -- I've not been
> > > able to test that theory.
> >
On Monday 30 July 2007, Oliver Neukum wrote:
>
> > But -- never actually having had both a highspeed USB sniffer *AND*
> > hardware exhibiting this problem in the same place -- I've not been
> > able to test that theory.
>
> The hub in question is light and small. Give me your address and I'll
>
Am Samstag 28 Juli 2007 schrieb David Brownell:
> On Friday 27 July 2007, Alan Stern wrote:
> > In my experience this sort of thing tends to be caused by low-level
> > hardware communications errors. Noise in the USB data lines or a
> > missing handshake packet, stuff like that. Not much extra d
On Sat, 28 Jul 2007, David Brownell wrote:
> On Friday 27 July 2007, Alan Stern wrote:
> > > stressing a flash disk I rapidly get this error:
> >
> > > Jul 27 12:35:00 oenone kernel: ehci_hcd :00:02.2: devpath 3.4 ep1in
> > > 3strikes
> > > Jul 27 12:35:00 oenone kernel: usb-storage: Status
On Friday 27 July 2007, Alan Stern wrote:
> > stressing a flash disk I rapidly get this error:
>
> > Jul 27 12:35:00 oenone kernel: ehci_hcd :00:02.2: devpath 3.4 ep1in
> > 3strikes
> > Jul 27 12:35:00 oenone kernel: usb-storage: Status code -71; transferred
> > 8192/122880
>
> > Is there a
On Fri, 27 Jul 2007, Oliver Neukum wrote:
> Hi,
>
> stressing a flash disk I rapidly get this error:
> Jul 27 12:35:00 oenone kernel: ehci_hcd :00:02.2: devpath 3.4 ep1in
> 3strikes
> Jul 27 12:35:00 oenone kernel: usb-storage: Status code -71; transferred
> 8192/122880
> Is there a way I
Hi,
stressing a flash disk I rapidly get this error:
Jul 27 12:35:00 oenone kernel: usb-storage: *** thread awakened.
Jul 27 12:35:00 oenone kernel: usb-storage: Command READ_10 (10 bytes)
Jul 27 12:35:00 oenone kernel: usb-storage: 28 00 00 00 25 f8 00 00 3c 00
Jul 27 12:35:00 oenone kernel: us
11 matches
Mail list logo
