On Wed, 2005-02-16 at 21:04 +0100, Ralf Hildebrandt wrote: > * Jan Kara <[EMAIL PROTECTED]>: > > > I guess the system is SMP... > > Indeed it is. Dual Xeon with SMP. >
This looks very similar (at least to me) to an OOPS I posted with 2.6.9 on 12/03/2004. http://marc.theaimsgroup.com/?l=linux-kernel&m=110210705504716&w=2 My system is also a dual Xeon using SMP and Hyperthreading (/proc/cpuinfo shows 4 cpus). Mine, like Ralf's, is also a mail server running postfix using ext3 for the spool directory. > > but it seems similar like a several other oopses I've seen reported > > recently. Is this the first time you hit this bug? > > It's actually the second time. The first time it hit the SAME box but > with kernel-2.6.10 (vanilla) after 30 days of uptime. Nobody had a > camera at hand, so I couldn't take a photo. > I've actually hit this bug (assuming it's the same) with 2.6.10 also. I had to power cycle remotely and unfortunately didn't have the serial console logging enabled when it happened with 2.6.10. I upgraded from 2.4.23 to 2.6.8.1 and crashed within a week, and continued to crash at least monthly after that. It had been running 2.4.23 for 200+ days with no problems. Hope this helps trace it back. Dale - 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/
