http://bugzilla.kernel.org/show_bug.cgi?id=13886 --- Comment #5 from Rafael J. Wysocki <rjw@xxxxxxx> 2009-08-01 19:12:54 --- (In reply to comment #4) > The fix mentioned above (commit 2ea5521022ac8f4f528dcbae02668e02a3501a5a) does > not address the problem I am encountering (which is present in 2.6.30.2). > Bart's point is that the problem introduced by commit 295f00042aaf6b553b5f37348f89bab463d4a469 was fixed by commit 2ea5521022ac8f4f528dcbae02668e02a3501a5a, so if you have a bisection point between the two commits, the bisection may lead to commit 295f00042aaf6b553b5f37348f89bab463d4a469 instead of the real culprit. > There is no e100 hardware present here. How is e100 relevant here? > I am more than willing to help with the debugging process from this end. > > Might we test by reverting his commit on 2.6.30.2? That might be difficult, because I guess commit 295f00042aaf6b553b5f37348f89bab463d4a469 doesn't revert cleanly. Could you instead test the kernel where commit 2ea5521022ac8f4f528dcbae02668e02a3501a5a is the head and see if the problem is present there? [Bart, I know you're not maintaining IDE any more, but your commit was pointed out by the bisection. Thanks for the information that it was a false positive.] First-Bad-Commit: unknown -- Configure bugmail: http://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-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
