From: FUJITA Tomonori <tomof@acm.org>
To: akpm@linux-foundation.org
Cc: just.for.lkml@googlemail.com, apw@shadowen.org,
linux-kernel@vger.kernel.org, mel@csn.ul.ie,
jens.axboe@oracle.com, linux-scsi@vger.kernel.org,
linux-ide@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: 2.6.23-rc4-mm1
Date: Tue, 11 Sep 2007 04:42:53 +0900 [thread overview]
Message-ID: <20070910045503O.tomof@acm.org> (raw)
In-Reply-To: <20070910122038.1f1bb006.akpm@linux-foundation.org>
On Mon, 10 Sep 2007 12:20:38 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 10 Sep 2007 20:59:49 +0200 "Torsten Kaiser" <just.for.lkml@googlemail.com> wrote:
>
> > On 9/10/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> > > On Mon, 10 Sep 2007 18:49:26 +0100 Andy Whitcroft <apw@shadowen.org> wrote:
> > >
> > > > I have a couple of old NUMA-Q systems which are unable to read their
> > > > boot disks with 2.6.23-rc4-mm1. The disks appear to be recognised and
> > > > even the partition tables read correctly, and then they go pop:
> >
> > I reported a similar problem on Sep 1, but until now got no response.
>
> You still haven't had a response ;) Let's add a cc.
>
> Oh, you reported it against 2.6.23-rc4-mm1
> (http://lkml.org/lkml/2007/9/1/92) and I did cc linux-ide in my response.
>
> I'll continue to point out where this sort of thing occurs because last
> week I was told that a reson why so many bug reports are ignored is because
> "linux-kernel has too much traffic".
many SCSI people don't subscribe to linux-kernel, I think.
> > The system boots, reads the partition tables, starts the RAID and then
> > kicks one drive out because of errors.
>
> Andy is using qla1280. You're using sata. So it's probably a different
> bug, with the same symptoms.
This might be a sg chaining bug too (probabaly sg chaining libata
patch).
Can you try the following patch that I've just sent:
http://lkml.org/lkml/2007/9/10/251
The patch also disables chaining sg list for libata.
next prev parent reply other threads:[~2007-09-10 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070831215822.26e1432b.akpm@linux-foundation.org>
[not found] ` <64bb37e0709010907x5a73f9dbof8e5b2c92425452e@mail.gmail.com>
2007-09-01 16:16 ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-09 20:24 ` [-mm patch] remove ide_get_error_location() Adrian Bunk
2007-09-11 21:27 ` Bartlomiej Zolnierkiewicz
2007-09-12 5:54 ` Jens Axboe
[not found] ` <20070910174926.GC30335@shadowen.org>
[not found] ` <20070910111926.9c942358.akpm@linux-foundation.org>
[not found] ` <64bb37e0709101159v47f586aby7f078ef1db5cbc39@mail.gmail.com>
2007-09-10 19:20 ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-10 19:38 ` 2.6.23-rc4-mm1 Torsten Kaiser
2007-09-10 19:42 ` FUJITA Tomonori [this message]
2007-09-10 20:43 ` 2.6.23-rc4-mm1 Torsten Kaiser
2007-09-11 8:32 ` 2.6.23-rc4-mm1 Jens Axboe
[not found] ` <20070910044323T.tomof@acm.org>
[not found] ` <20070914081018.GA20042@shadowen.org>
[not found] ` <64bb37e0709140601te21f5d0l9871ea03dbf4b135@mail.gmail.com>
2007-09-14 20:15 ` 2.6.23-rc4-mm1 Andrew Morton
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=20070910045503O.tomof@acm.org \
--to=tomof@acm.org \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=just.for.lkml@googlemail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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;
as well as URLs for NNTP newsgroup(s).