For what it's worth - I've had a very similar oops ages ago. Back then it
was blamed on bad RAM, but ever since then I've run numerous memtest's
over it without finding anything and never had any problems later either.
See here:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0101.0/0303.html
Call Trace is very similar. Maybe it's just coincidence, but who knows.
Regards,
Udo.
-
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/