On Thu, 9 Dec 2010, caiqian@xxxxxxxxxx wrote: > > > The version is 2010-11-23-16-12 which included b52723c5 you mentioned. > > > 2.6.37-rc5 had the same problem. > > > > > The problem with your bisect is that you're bisecting in between 696d3cd5 > > and b52723c5 and identifying a problem that has already been fixed. > Both 2010-11-23-16-12 and 2.6.37-rc5 have b52723c5 but still have the > problem with OOM testing. If went back one commit before 696d3cd5, it > had no problem. Might be b52723c5 did not fix the problem fully? > 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. -- 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>