Ian Kumlien schrieb: > On Sun, 2006-02-26 at 23:38 +0100, Carl-Daniel Hailfinger wrote: > >>Ian Kumlien schrieb: >> >>>I also saw some oddities... portage stopped working, i dunno if this can >>>be MSI related or so, else something is trashing memory in a very >>>special way =P >> >>Yes, 0.15 causes memory corruption even if MSI is disabled. > > > So if i run with iommu=forced or what the hell the option is called i > should be able to catch these trashings? > > I also found it odd that it was only python that suffered... Starting > large and long running C apps worked just fine.
For me, it was usually timer list corruption during boot (50% probability) or unidentified lockups (probably also timer list corruption) after a few minutes of operation (40% probability). Sample Oops message: Unable to handle kernel NULL pointer dereference at 00000008 rip: run_timer_softirq+322 process udev Call trace: __do_softirq+68 call_softirq+30 do_softirq+46 do_IRQ+61 ret_from_intr+0 EOI Regards, Carl-Daniel - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
