From: Joshua Kwan <jkwan@rackable.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [HELP] Tracking down a MD bug
Date: Fri, 25 Jun 2004 11:02:44 -0700 [thread overview]
Message-ID: <20040625180244.GA8009@mx.rackable.com> (raw)
In-Reply-To: <16603.19400.833911.26478@cse.unsw.edu.au>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
On Fri, Jun 25, 2004 at 07:46:48AM +1000, Neil Brown wrote:
> > Are there any MD code changes that could have caused this so I can point
> > SuSE somewhere? (Well, then again, many SuSE folks are on this list
> > anyway...)
>
> This is definitely a bug in the Suse 2.6.4-52 kernels, and I'm pretty
> sure they have fixed it.
Thanks, I upgraded the box to 2.6.5-7.75-smp and the bug has vanished.
--
Joshua Kwan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2004-06-25 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 17:24 [HELP] Tracking down a MD bug Joshua Kwan
2004-06-24 21:46 ` Neil Brown
2004-06-25 18:02 ` Joshua Kwan [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=20040625180244.GA8009@mx.rackable.com \
--to=jkwan@rackable.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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