[lkml]   [2005]   [Feb]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
On Wed, 2005-02-16 at 21:04 +0100, Ralf Hildebrandt wrote:
> * Jan Kara <>:
> > 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.

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 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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:10    [W:0.075 / U:8.244 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site