All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org
Cc: Matthias Juchem <lists@konfido.de>
Subject: Re: 2.4.25: kernel BUG at inode.c:334
Date: Sun, 4 Apr 2004 18:00:49 +0200	[thread overview]
Message-ID: <200404041800.49339@WOLK> (raw)
In-Reply-To: <200404041752.25721.lists@konfido.de>

On Sunday 04 April 2004 17:52, Matthias Juchem wrote:

Hi Matthias,

> I am using 2.4.25 and get the following bug approximately once a week:
> Apr  3 08:34:52 xxxxxx kernel: kernel BUG at inode.c:334!
> The server does not hang, but of course it has some serious problems.
> I do not know how the bug is triggered.
> The server is used for some network services which usually do not cause a
> heavy load.
> If you need further information, please ask.
> Please CC me on any replies as I'm not subscribed to LKML.

Please try 2.4.26-rc1. It has a fix for the bug.

ciao, Marc

  reply	other threads:[~2004-04-04 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04 15:52 2.4.25: kernel BUG at inode.c:334 Matthias Juchem
2004-04-04 16:00 ` Marc-Christian Petersen [this message]
     [not found] ` <20040405001942.GA1879@logos.cnet>
2004-04-05  8:55   ` Matthias Juchem

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=200404041800.49339@WOLK \
    --to=m.c.p@wolk-project.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@konfido.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.