On Mon, 29 Jan 2007, Mike Galbraith wrote: > > The extremely unlikely winner is: > > 29b08d2bae854f66d3cfd5f57aaf2e7c2c7fce32 is first bad commit Yeah, that's not going to be it. You probably had a bad kernel there somewhere that you called "good". Git bisect is wonderful for figuring out (reasonably quickly) where problems are, but exactly because it zeroes in on the bug so quickly, if you give it faulty data, it zeroes in on something *else* very quickly and without any kind of sense. There's just no redundancy there, so one small bit error in the input, and you get a totally wrong end result ;) I'm trying to narrow it down myself. It all *seemed* to work with the commit I suspected initially (the "support larger block pc requests" one). But yes, I haven't actually tried to burn anything either. I also just started up "nero" and looked whether I'd get the error messages in dmesg. Linus - 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
