[lkml]   [2001]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: USB broken in 2.4.0
There's a flurry of emails I haven't read yet.
I wanted to answer the direction question first

test9 OK
test10 OK
test11 BROKEN

so that's where the break occurred.

I've gotta admit I was scared running the older
test kernels because somewhere in the series
the filesystem could be damaged and it bit me
bad on the first pass a couple of months ago.
I compiled the kernels under current full 2.4.0
and when rebooting to the test kernels tried
to get in, do the test, and get out as fast
as possible.


-----Original Message-----
From: Greg KH []
Sent: Friday, January 05, 2001 1:01 PM
To: Heitzso
Cc: ''; ''; 'Johannes
Subject: Re: USB broken in 2.4.0

On Fri, Jan 05, 2001 at 12:38:25PM -0500, Heitzso wrote:
> I just tested with fresh-out-of-the-box
> 2.4.0 and using the newer libusb 0.1.2
> as suggested by antirez (see email chain
> below for more info). I compiled libusb
> and s10sh code this AM under 2.4.0.
> It blows up BAD by finding increasingly
> larger photo images in the camera over
> the usb link and extracting them to disk.
> So by the third file you're trying to
> extract gig sized files. Obviously the
> filesystem files up, the sytem chokes, etc.
> This is the same code that works fine
> under 2.2.18 kernel (I use it all of the
> time there).

I made the same request to Jordan Mendelson yesterday, who has the same
problem. Could you be so kind as to try to narrow down which kernel
version this broke on? I have reports that it used to work on -test9
but doesn't now. Could you try -test10, etc and let me know?


greg k-h

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.042 / U:2.664 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site