Thanks for the git crash course. I did not look at 'git-bisect' too much. It is more systematic, but how to test each commit confused me some.
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: http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=76531d4166fb620375ff3c1ac24753265216d579 Which is more elaborate in the alsa-git repo: http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=76531d4166fb620375ff3c1ac24753265216d579 Unfortunately this commit is rather extensive and includes many changes. I believe alsa-git has the detailed commits leading to this merge here: http://git.alsa-project.org/?p=alsa-kernel.git;a=shortlog;h=76531d4166fb620375ff3c1ac24753265216d579 Particularly, I found this commit rather suspicious: http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=4c11398edc19fdd9c651f3ff287cd628fecaf574 I'm not sure how to test each alsa commit individually. I guess I have to build alsa externally... Perhaps it's time to send this upstream? Cheers, Andres -- 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/CAH=dYrE1xYkLJmQ5N_h_u=ectsh9inoyjdcoq4wxfrgqcqv...@mail.gmail.com
