From: J Sloan <jjs@pobox.com>
To: Linux Kernel Developer <linux_developer@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPQARRAY driver horribly broken in 2.4.14
Date: Thu, 08 Nov 2001 19:45:13 -0800 [thread overview]
Message-ID: <3BEB5149.B0B7990F@pobox.com> (raw)
In-Reply-To: <F5uLCTaogxLDp7mvjkO00000742@hotmail.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Linux Kernel Developer wrote:
> Hi all,
>
> I'm using the cpqarray driver for a Compaq Smart Arrat 3100ES
> controller on a Compaq Proliant 7000. Today I tried upgrading the kernel to
> 2.4.14. Soon after the upgrade I though about making a small change in the
> kernel however as soon as I tried doing a "make dep" the system oopsed and
> froze.
Been there, done that, bought the t-shirt.
The attached patch courtesy of Jens Axboe
fixed my Compaq 6500 which was giving me
fits - basically in 2.4.14 it had a nasty habit of
scribbling on the disk and then locking up,
requiring a power cycle, manual fsck and
file restoration to get it running again.
With this patch 2.4.14 has been solid.
cu
jjs
[-- Attachment #2: cciss-dequeue-1 --]
[-- Type: text/plain, Size: 625 bytes --]
--- linux/drivers/block/cciss.c~ Thu Nov 8 11:36:24 2001
+++ linux/drivers/block/cciss.c Thu Nov 8 11:37:03 2001
@@ -1307,6 +1307,8 @@
if (( c = cmd_alloc(h, 1)) == NULL)
goto startio;
+ blkdev_dequeue_request(creq);
+
spin_unlock_irq(&io_request_lock);
c->cmd_type = CMD_RWREQ;
@@ -1386,12 +1388,6 @@
spin_lock_irq(&io_request_lock);
- blkdev_dequeue_request(creq);
-
- /*
- * ehh, we can't really end the request here since it's not
- * even started yet. for now it shouldn't hurt though
- */
addQ(&(h->reqQ),c);
h->Qdepth++;
if(h->Qdepth > h->maxQsinceinit)
next prev parent reply other threads:[~2001-11-09 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 3:04 CPQARRAY driver horribly broken in 2.4.14 Linux Kernel Developer
2001-11-09 3:45 ` J Sloan [this message]
2001-11-09 21:51 ` Linux Kernel Developer
2001-11-10 13:37 ` Jens Axboe
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=3BEB5149.B0B7990F@pobox.com \
--to=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_developer@hotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.