I have reported before a kernel oops. I now oberserved the same oops, with the same stack trace, and a Dell Poweredge 1550 with dual CPU, 1 gb RAM, only one disk and with little disk usage (most file activity via NFS, where this system is a client). The kernel is identical to the one reported before, and the stack trace is identical too. The oops occurred with the process 'top' I have not yet found a way to reproduce the crash in a systematic way, I am running the kernel now on 4 different machines under heavy load, and will try to reproduce. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
