https://bugzilla.kernel.org/show_bug.cgi?id=14994 --- Comment #23 from Marc H. Thoben <kernelbug@xxxxxxxxxx> 2010-04-16 17:19:08 --- Hello Borislav, Thank you for that hint to finally start figuring out how to switch from IDE to LIBATA. It took me a while but it was worth it. No kernel panics anymore using libata & pata_it8213 & sr_mod! :) > No, tainted kernel doesn't help. The only info I get from this is that > it might be that the proprietary crap interferes with the cdrom. How do > I know it doesn't? > > Well, I don't because I can't look at the source code. So the reason > I'm asking you to retry without the nvidia driver is so that we can be > really sure whether there's a bug. Well, I would have thought that showing the same kernel panic with the call traces showing the oops in the same functions over and over again, no matter whether the kernel is tainted or not, had made it obvious that the tainted status doesn't matter. Pity I couldn't get Nouveau working with 2.6.34. But running a single monitor setup for days just to wait for the randomly occurring crash wasn't an option. But yeah - I wish I didn't have to use the closed-source nvidia driver either. Anyways.. Thank you very much again for taking time to look into this. I hope you'll find the cause. Let me know if anything comes up that you would like me to test or try out. Cheers, Marc -- 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-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
