> - I haven't seen those oopses again either; they may have been caused
> by i810_configure_clocking being called twice during the
> initialization due to a merging goof on my part...
Ok, I spoke too soon. That piece of code couldn't cause the problem,
because of the surrounding if (clocking==...
So there may be some VM/buffer related problem lurking under the covers
still. Originally the oops popped up in kswapd, for me, but I can't
trigger it again.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/