Andres Cimmarusti wrote: > I found the patch that brings about the problem. It turns out it > happened quite early in the 3.1 kernel merge window. This the commit > that changes things: > > [...]76531d4166fb620375ff3c1ac24753265216d579
To be clear, are you saying "git bisect" told you that 76531d4166 was the first bad commit? If so, that means that _both_ its parents (7d339ae and a353fbb) tested fine and that the merge tested as broken. Which would mean that either we have a heisenbug and all information so far is suspect, or their interaction produced the bug. If you have been using "git bisect", could you attach the output of "git bisect log"? Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120219141912.GA3657@burratino
