On Tue, 4 Oct 2005, Yedidyah Bar-David wrote:

> On Mon, Oct 03, 2005 at 05:00:23PM -0400, Alan Stern wrote:
> > Okay.  Maybe there was a simple change that you'll be able to find.
> 
> Well, I took the patch between 2.6.8-rc1 and -rc2, took from it only the
> changes to the files drivers/usb/*/* and include/linux/usb*, and did two
> things: I applied this patch to 2.6.8-rc1 and reverse-applied it to
> -rc2. The results - rc1 with the patch still works, rc2 without it
> still does not work. This probably means the change that caused the
> regression is elsewhere.

It could be that the regression was caused not by a single change, but by 
a large collection of changes that, taken together, altered the timing of 
the computer.

> What should be my next step?

I don't know.  You could try binary dissection on the individual patches 
between -rc1 and -rc2.  Here's a URL that has a list of all of them (plus 
a lot more, if you let the transfer go all the way):

http://linux.bkbits.net:8080/linux-2.6/[EMAIL PROTECTED]|tags

It would be a lot of work, though.  I don't know any way to get a simple 
file containing all those patches.  It might be possible using git.

Also, you should post debugging logs showing the difference between -rc1 
and -rc2.

> logs:
> As mentioned, all of them done with 2.6.14-rc3, config at
> <http://www.cs.tau.ac.il/~didi/usb/config-2.6.14-rc3>
> 
> All created by doing 'dmesg -c >> log' once a second, from before
> plugging in to after plugging out.
> 
> dmesg of the working machine, while plugging in and out the card reader:
> <http://www.cs.tau.ac.il/~didi/usb/wcr>
> working machine, plugin/out the pen:
> <http://www.cs.tau.ac.il/~didi/usb/wpen>
> 
> non-working, card reader:
> <http://www.cs.tau.ac.il/~didi/usb/nwcr>
> The card reader does work - that is, I can mount it and copy from it.
> But unlike in the working machine, the kernel continues to try doing
> something and outputs lots of stuff during that.
> 
> non-working, pen:
> <http://www.cs.tau.ac.il/~didi/usb/nwpen>
> I noticed (by doing cat /proc/partitions) that it does manage to see the
> device for a few seconds (probably at the time it says in the logs 'sda1
> sda3'), then looses the connection.

I can't access any of these logs: Error 403.

Alan Stern



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to