Svante Signell wrote: > ON, now I have made the bisection: > > 2.6.33-1~experimental.5 works OK, however with the address space > collision warning reported earlier. > > 2.6.34-1~experimental.1 shows the same problems ar later kernels. > > Do you need dmesg output or anything else to make progress?
Would it be possible to bisect between those versions, to find the exact change that introduced this problem? It works like this: $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git $ cd linux-2.6 $ git bisect start v2.6.34 v2.6.33 Git checks out a version half-way between. So: $ make localmodconfig; # minimal configuration $ make deb-pkg; # builds a .deb # dpkg -i ../<whatever>.deb; reboot $ git bisect good; # if it works $ git bisect bad; # if it shows the same problem $ git bisect skip; # if another problem makes it impossible to test Then: $ make silentoldconfig; # reuse configuration $ make deb-pkg; # build a .deb # dpkg -i ../<whatever>.deb; reboot $ git bisect good / bad / skip ... rinse and repeat until it shows the "first bad commit" ... If the gitk package is installed, you can use "git bisect visualize" at any point to see the regression range narrowing. The point of this exercise is to find out what subsystem in particular broke. For more information on "git bisect", see [1] if interested. Thanks for reporting, and sorry for the trouble. Jonathan [1] http://www.kernel.org/pub/software/scm/git/docs/git-bisect-lk2009.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org