From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
Date: Wed, 16 Feb 2005 23:00:07 +0100 [thread overview]
Message-ID: <20050216220007.GQ19871@charite.de> (raw)
In-Reply-To: <1108590885.17089.17.camel@dale.velocity.net>
* Dale Blount <linux-kernel@dale.us>:
> 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) Ralf.Hildebrandt@charite.de
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 spamtrap@charite.de
next prev parent reply other threads:[~2005-02-16 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 14:56 Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction) Ralf Hildebrandt
2005-02-16 15:33 ` Jan Kara
2005-02-16 20:04 ` Ralf Hildebrandt
2005-02-16 21:54 ` Dale Blount
2005-02-16 22:00 ` Ralf Hildebrandt [this message]
2005-02-16 22:55 ` Andrew Morton
2005-02-17 10:58 ` Ralf Hildebrandt
2005-02-17 13:21 ` Ralf Hildebrandt
2005-02-17 15:51 ` Randy.Dunlap
2005-02-17 16:00 ` Ralf Hildebrandt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050216220007.GQ19871@charite.de \
--to=ralf.hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox