Re: [Bisected] 3.7-rc1 can't resume

From: H. Peter Anvin
Date: Sat Feb 23 2013 - 16:55:58 EST

On 02/23/2013 05:18 AM, Jonas Heinrich wrote:
thank you for your replay and the effort you invest in helping me out
with this problem.
Today, I further debuged the problem and reverted this part of your commit
(without understanding the actual code):

Hi, that commit is indeed buggy, but it has already been fixed; commit
1396adc3c2bdc556d4cdd1cf107aa0b6d59fbb1e contains the fix.

So to bisect anything between 73201dbec64aebf6b0dca855b523f437972dc7bb and 1396adc3c2bdc556d4cdd1cf107aa0b6d59fbb1e in a meaningful way you will have to apply 1396adc3c2bdc556d4cdd1cf107aa0b6d59fbb1e on top.

If 73201dbec64aebf6b0dca855b523f437972dc7b with 1396adc3c2bdc556d4cdd1cf107aa0b6d59fbb1e on top fails whereas the previous one does, then that is very interesting and something we can work with.


H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at