Hi David, > When a bisect identifies a commit in between a known-broken patch and fix > for that broken patch, you need to revert your tree back to the fix > (b52723c5) and retest. If the problem persists, then 696d3cd5 is the bad > commit. Otherwise, you need to bisect between the fix (by labeling it > with "git bisect good") and HEAD. It turned out that this bug is not always reproducible after your fix. Sorry for the false alarm. CAI Qian -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>