https://bugzilla.kernel.org/show_bug.cgi?id=17361 Christian Casteyde <casteyde.christian@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #20 from Christian Casteyde <casteyde.christian@xxxxxxx> 2010-10-20 20:10:37 --- Hello My bisection was obviously false, sorry. It took me some time, but I've finally understood why my bisection failed, and what was happening. The problem is that with kmemcheck, the kernel boots so slowly (except if there is a warning at boot in swapper, as it occured in several revision pre rc1), that the hard and soft lockup detection mechanism was triggering (often in udev or hal or ldconfig or other slow commands). Moreover, it triggered sometimes at a place the kernel cannot cope with it, and crashes. Before bisecting, I took a fresh 2.6.35 .config file and reactivated the debugging options, but I fogot the lockup detector. So I couldn't see the errors anymore. Nevertheless, I checked other warnings that used to occur before -rc1, and that were fixed later. As I was looking for a range between 2.6.35 and rc1, I got false results on already fixed bugs. Finally, I do not have any problem anymore with 2.6.36-rc8. Except that the lockup timeout is either too low for my computers, or crashes the kernel sometimes whent it triggers. But that's not critical. I'm closing the bug. -- 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
