* Dale Blount <[EMAIL PROTECTED]>: > 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
Could be. > My system is also a dual Xeon using SMP and Hyperthreading > (/proc/cpuinfo shows 4 cpus). Same system here. > Mine, like Ralf's, is also a mail server running postfix using ext3 for > the spool directory. Same here. > 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. Me too -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - 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/