On Mon, 28 Jan 2008, Gene Heskett wrote: > I believe at this point, its moot. I captured quite a few instances of that > error message while rebooting the last time, all of which occurred long > before I logged in and did a startx (I boot to runlevel 3 here), so the > kernel was NOT tainted at that point. That dmesg has been posted and some > questions asked. > > As this has gone on for a while, it seems to me that with 14,800 google hits > on this problem, Linus should call a halt until this is found and fixed. But > I'm not Linus. I'm also locking up for 30 at a time, & probably ready for > reboot #7 today. Can you switch back to old IDE to get your work done (and to make sure it's not a hardware issue that's developed recently)? I believe libata is just a whole lot pickier about behavior than the IDE subsystem was, so it's more likely to complain about stuff, both for good reasons and when it shouldn't, and there are a slew of potential "we have to accept that old PATA hardware does this" bugs that all have the same symptom of "we go into error handling when nothing is actually wrong", hence the vast quantity of hits. I think it's not exactly that it's a common problem as that it's a lot of problems that aren't very distinguishable. -Daniel *This .sig left intentionally blank* - 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
