From: Adam Kropelin <akropel1@rochester.rr.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpqarray broken since 2.5.19
Date: Wed, 24 Jul 2002 20:32:35 -0400 [thread overview]
Message-ID: <20020725003235.GA5345@www.kroptech.com> (raw)
In-Reply-To: <20020724133959.GD5159@suse.de>
> On Sun, Jul 21 2002, Adam Kropelin wrote:
> > The cpqarray driver seems to have been broken around 2.5.19 with the
> > blk_start_queue/blk_stop_queue changes. As-is, cpqarray deadlocks the entire
On Wed, Jul 24, 2002 at 03:39:59PM +0200, Jens Axboe wrote:
> Thanks for the report. Could you just kill the spin_lock/unlock in
> blk_stop_queue() in drivers/block/ll_rw_blk.c and see if it works?
Hi, Jens,
I killed the spin_lock/unlock as you directed (and made no other changes
to the tree). Result is the same as before: hard lock on partition detect.
The first time I tried it I got an oops but didn't have the serial console
up so it didn't get captured. (Stupid, stupid) Subsequent attempts have just
the hard lock with no oops.
--Adam
next prev parent reply other threads:[~2002-07-25 0:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 15:28 cpqarray broken since 2.5.19 Adam Kropelin
2002-07-24 13:39 ` Jens Axboe
2002-07-24 14:07 ` Bartlomiej Zolnierkiewicz
2002-07-24 14:09 ` Jens Axboe
2002-07-24 14:11 ` Marcin Dalecki
2002-07-24 14:19 ` Jens Axboe
2002-07-24 14:41 ` Bartlomiej Zolnierkiewicz
2002-07-24 14:44 ` Jens Axboe
2002-07-24 14:46 ` Marcin Dalecki
2002-07-24 15:15 ` Bartlomiej Zolnierkiewicz
2002-07-24 14:21 ` Bartlomiej Zolnierkiewicz
2002-07-24 14:27 ` Marcin Dalecki
2002-07-24 14:45 ` Bartlomiej Zolnierkiewicz
2002-07-25 0:32 ` Adam Kropelin [this message]
2002-07-25 10:39 ` Jens Axboe
2002-07-26 0:30 ` Adam Kropelin
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=20020725003235.GA5345@www.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=axboe@suse.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