Andy Walls wrote: > 1. Find that latest kernel that still works and the earliest kernel that > does not. > > A binary search will terminate in a few trials, e.g. .30, .26, .24, .23. > (I suspect this could be painful on a Gentoo system, if you have to > rebuild each kernel.) I have done this in the past, unfortunately not down to patchlevel, but I have found that linux-2.6.22-gentoo-r8 works and linux-2.6.23-gentoo-r3 not. I have just booted from the first and did not have the reboot issue there. Unfortunately I no longer have a compiled version of the .23 release, and I cannot compile them anymore since they cannot be compiled with gcc 4.3
> 2. Diff the source tree of the two kernels. video src # diff -r linux-2.6.22-gentoo-r9 linux-2.6.23-gentoo-r3 | wc -l 472301 ....mmmmm little bit too much > > 3. Analyze the diff for the change that may have caused the problem. > > That will narrow the cause down from "anything" to "one of these > changes". That changeset still could be rather large. Indeed, but if I just check the ivtv part, it goes down: video ~ # cd /usr/src/linux-2.6.22-gentoo-r9/drivers/media/video/ video video # diff -r ivtv /usr/src/linux-2.6.23-gentoo-r3/drivers/media/video/ivtv | wc -l 556 Also, a reasonable part of that is changes in comments and printed text. I think it's a bit too big to include in or attach to the mail, but for anyone interested, there's a unified diff (diff -uN) at http://thuis.tuxinet.nl/ivtv.patch. Jeroen _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
