Hi. I think git bisect is a tedious way (but simple) for detect a problem in the kernel. First, I recommend you install kernel 2.6.31-rc7 (it works for me) and 2.6.31-rc8 (it doesn't work for me). This is easy. Only download deb packages from here,
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc7/ http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc8/ and install the three packages for your architecture, linux-image...i386 or 64, linux-headers...all.deb and linux-headers...386 or 64. Test if the problem is present in those kernels. If rc7 works fine and rc8 doesn't work, you probably have the same problem that me. Next step is detect bad commit with git bisect, but this is hard work, you have to recompile entire kernel from git 5 or 6 times. Process is easy, but it requires time. You first have to clone the Linux kernel git repository. This is the same concept checking out a repository from CVS. $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git $ cd linux-git $ git bisect start Next, tell git which kernel was the last known-working kernel, and which kernel is known to be not working. For example: $ git bisect bad v2.6.31-rc8 $ git bisect good v2.6.31-rc7 Now, you have to compile kernel. Then, install it and check if problem are present. If so, $ git bisect bad You have more information here, http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to- find-buggy-kernel-patches/ Probably, you have the same problem than me. If you have any question, write. Greetings Eduardo -- network (eth0) doesn't work after suspend to ram (Marvell 88E8036) https://bugs.launchpad.net/bugs/509239 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
