From: Matthias Juchem <lists@konfido.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.25: kernel BUG at inode.c:334
Date: Mon, 5 Apr 2004 10:55:04 +0200 [thread overview]
Message-ID: <200404051055.18712.lists@konfido.de> (raw)
In-Reply-To: <20040405001942.GA1879@logos.cnet>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 338 bytes --]
Hi Marcelo.
On Monday 05 April 2004 02:19, you wrote:
> This bug should be fixed in 2.4.26-rc1. Please try it.
Yes, Marc-Christian told me this, too.
I'm currently installing a patched kernel (2.4.25 + ChangeSet 1.1330). If this
one runs one month without problems, the problem should be fixed :)
Best regards,
Matthias
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-04-05 8:55 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
[not found] ` <20040405001942.GA1879@logos.cnet>
2004-04-05 8:55 ` Matthias Juchem [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=200404051055.18712.lists@konfido.de \
--to=lists@konfido.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