https://bugzilla.kernel.org/show_bug.cgi?id=25832 --- Comment #47 from Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> 2011-03-13 21:17:00 --- Okay, if you believe this, and if you can reliably detect the bug (which is often a difficult thing to be sure of), then you can try bisecting the kernel changes between 2.6.35 and 2.6.36-rc1. The thing is, the test really does have to be reliable. If you make a mistake (tell git that a kernel doesn't have the bug when it actually does) then you're very unlikely to track down the true cause. Still, it's worth a try -- especially since nothing else seems to help! The test you used in comment #31 would be a good approach. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
