All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Uwe Langenkamp <ul@uwe-langenkamp.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: System crashed (kernel bug report)
Date: Wed, 13 Nov 2002 00:03:15 -0800	[thread overview]
Message-ID: <3DD20743.48DE596F@digeo.com> (raw)
In-Reply-To: JLECLKCMILLGAJOCDMKEOEDMCEAA.ul@uwe-langenkamp.de

Uwe Langenkamp wrote:
> 
> Hello,
> 
> after running 8 weeks without problems, our server had a system crash, I
> found the following bug message in /var/log/messages:
> 
> An additional information: Since 19th of October, the system is shut down by
> a SmartUPS over night (to save energy, from 11pm to 7am).
> 
> Nov 12 16:16:30 serv1 kernel: Assertion failure in
> journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)"
> ...
> Linux version 2.4.18-3smp (bhcompile@daffy.perf.redhat.com) (gcc version

Red Hat fixed this in 2.4.18-4.  See http://rhn.redhat.com/errata/RHBA-2002-085.html

Suggest you grab their latest kernel.

      reply	other threads:[~2002-11-13  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13  7:43 PROBLEM: System crashed (kernel bug report) Uwe Langenkamp
2002-11-13  8:03 ` Andrew Morton [this message]

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=3DD20743.48DE596F@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ul@uwe-langenkamp.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.