public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Steudten <alpha@steudten.com>
To: Norbert Preining <preining@logic.at>, linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org, mingo@redhat.com, neilb@cse.unsw.edu.au
Subject: Re: md raid oops on 2.4.25/alpha
Date: Mon, 29 Mar 2004 12:41:06 +0200	[thread overview]
Message-ID: <4067FD42.9030206@steudten.com> (raw)
In-Reply-To: <20040328223013.A15859@jurassic.park.msu.ru>

I know from my own system, that the oops in the raid1 sources, are
not the only point, where gcc generates wrong assembler code.
So it't better not to workaround just this single point, but
use the fixed gcc instead.

Ivan Kokshaysky wrote:

> Also, here is a hack (originally from Jay Estabrook) which
> should work around a bug in older compilers.


  reply	other threads:[~2004-03-29 10:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 14:13 Transmit timeout with 3c395, 2.4.19, 2.4.22 Norbert Preining
2003-10-27 19:18 ` Andrew Morton
2003-10-28  6:49   ` Norbert Preining
2003-10-30 17:50   ` Stian Jordet
2004-03-27 16:41 ` Oops with md/ext3 on 2.4.25 on alpha architecture Norbert Preining
2004-03-28 16:02   ` md raid oops on 2.4.25/alpha Norbert Preining
2004-03-28 17:30     ` Thomas Steudten
2004-03-28 16:45       ` Ross Dickson
2004-03-28 20:32         ` Norbert Preining
2004-03-28 18:30       ` Ivan Kokshaysky
2004-03-29 10:41         ` Thomas Steudten [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-02  6:53 Lewis Shobbrook
2004-04-02 12:03 ` Marcelo Tosatti

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=4067FD42.9030206@steudten.com \
    --to=alpha@steudten.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=preining@logic.at \
    /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