From: Chuck Ebbert <cebbert@redhat.com>
To: Dale Blount <linux-kernel@dale.us>
Cc: linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: PROBLEM: null pointer dereference in cfq_dispatch_requests (2.6.21-rc2 and 2.6.20)
Date: Wed, 21 Mar 2007 14:25:31 -0400 [thread overview]
Message-ID: <4601789B.8040403@redhat.com> (raw)
In-Reply-To: <1174501407.14261.34.camel@dale.velocity.net>
Dale Blount wrote:
> On Wed, 2007-03-21 at 14:09 -0400, Chuck Ebbert wrote:
>> Dale Blount wrote:
>>>> I'm puzzled why this is hitting Dan, but no one else has reported
>>>> anything. Dan, did 2.6.19 work for you?
>>> Actually, I believe it is happening to me too. This is on a 4-disk raid5 with
>>> one failed disk on two 2-port sata_sil pci controller cards.
>>>
>>> The BUG below is from 2.6.20.3, but I will try 2.6.21-rc4 tonight.
>>> The disk didn't fail until 2.6.20, so I don't know if 2.6.19 would have worked
>>> or not.
>>>
>>>
>> Just to be clear: you have a RAID array (what level?) with a failed disk
>> and it's giving you the same error that Dan gets?
>
>
> Yes, the BUG looks to be pretty similar to me. It's a 4 disk raid5 with
> one disk missing (dead and sent in for RMA).
>
OK, I'm add NeilB to the cc:
(Dan has a RAID6 array with two failed disks.)
next prev parent reply other threads:[~2007-03-21 18:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 18:02 PROBLEM: null pointer dereference in cfq_dispatch_requests (2.6.21-rc2 and 2.6.20) Dan Williams
2007-02-28 18:18 ` Dan Williams
2007-02-28 18:49 ` Chuck Ebbert
2007-02-28 19:21 ` Chuck Ebbert
2007-03-01 12:08 ` Frank Seidel
2007-03-01 12:30 ` Jens Axboe
2007-03-01 19:50 ` Dan Williams
2007-03-21 13:07 ` Dale Blount
2007-03-21 18:09 ` Chuck Ebbert
2007-03-21 18:23 ` Dale Blount
2007-03-21 18:25 ` Chuck Ebbert [this message]
2007-03-21 19:59 ` Jens Axboe
2007-03-22 12:54 ` Dale Blount
2007-03-21 19:04 ` Johannes Weiner
2007-03-22 17:29 ` Johannes Weiner
2007-03-22 18:42 ` Jens Axboe
2007-03-22 19:22 ` Johannes Weiner
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=4601789B.8040403@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@dale.us \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox