On Wed, Oct 05, 2005 at 01:29:28AM +0300, didi wrote: > On Wed, Oct 05, 2005 at 12:52:47AM +0300, didi wrote: > > On Tue, Oct 04, 2005 at 02:52:29PM -0400, Alan Stern wrote: > > > > > > > > I am a complete ignorant regarding bitkeeper. Are they ordered in the > > > > order they were applied? > > > > > > Yes. Or rather, the reverse order -- from latest to earliest. > > > > Are you sure about that? I downloaded all (using wget), and when I > > apply, sometimes patch says the patch seems to have already been > > applied. > > Specifically, I now tried applying the first 66 patches (from > 1.1784.29.71 to 1.1784.39.1, in that order). I chose this cut point as > according to the timestamps in the patches it seemed to be the last > patch applied on some day, so I guessed it should have been some stable > point - I did not want to pick randomnly a point in the middle of the > work. And it didn't help. Besides the problem above (mainly about the > one before the last - 1.1784.38.27, most of it was rejected, and seemed > rather important to me), the kernel compiled ok, booted ok, but had no > network :-(
Well, I rebooted to other kernels and still no network. I powered off the machine, booted it, and it had network also in this rc1+66patches kernel. But I decided to create clear logs for rc1 vs rc2, and found out the regression isn't in a single point. This currently makes me thinking of quitting this whole thing. In 2.6.7, everything works, both with and without hald. And there are no recurring messages (apparently triggered by hald). In 2.6.8-rc1, with hald running, when I plug in the pen, I do get the devices in /proc/partitions, but mount fails, and the devices disappear from /proc/partitions. If I kill hald, mount/cp/umount succeed. In 2.6.8-rc2, when hald is running, either I do not get devices at all in /proc/partitions, or they disappear after a few seconds, even when I do nothing, and there are recurring messages from the kernel. When I kill hald, mount/cp/umount all work. Detaild logs are in <http://www.cs.tau.ac.il/~didi/usb/logs-usbstorage.tar.gz>. It's a 300KB file, when opened it's 15MB. These are three syslog-generated files - syslog, kern.log, and debug. In debug you can see messages I inserted with logger - search for 'root:' - telling what I was doing. They have large duplicates - basically all the kernel debug messages appear in all 3. Use diff or something to see only the changes. I am now leaving until Friday morning (IDT). Unless someone gives me some interesting pointer, I think I'll stay for now with 2.6.7. I know it's an old kernel, but it does work for me, for now. I think. I did not yet try to see if hald works etc., but I hope it will. In any case, thanks a lot for all your work, -- Didi ------------------------------------------------------- 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
