From: Andrea Arcangeli <andrea@suse.de>
To: Jamie Clark <jamie@metaparadigm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23pre6aa3 scsi oops
Date: Tue, 4 Nov 2003 11:28:16 +0100 [thread overview]
Message-ID: <20031104102816.GB2984@x30.random> (raw)
In-Reply-To: <3FA713B9.3040405@metaparadigm.com>
On Tue, Nov 04, 2003 at 10:49:29AM +0800, Jamie Clark wrote:
> Hi,
>
> Consistent oops with 2.4.23pre6aa3 after 3-4 hours running bonnie on
> ext3 fs through qla2300 HBA. (w SMP, HIGHMEM) The test machine was
> completely wedged so I ended up transcribing the oops from the vga
> console. No typos I think.
I need to release an update that has a chance to fix it. Jens identified
problem in his last_merge scsi patch so I will back it out.
you can try to backout it by yourself in the meantime, it's called
\*elevator-merge-fast-path\* . or you can disable it with this patch:
--- xx/drivers/block/elevator.c.~1~ 2003-10-17 21:49:49.000000000 +0200
+++ xx/drivers/block/elevator.c 2003-11-04 11:27:13.000000000 +0100
@@ -77,6 +77,7 @@ inline int bh_rq_in_between(struct buffe
static int rq_mergeable(struct request *req, struct buffer_head *bh,
request_queue_t *q, int rw, int count, int max_sectors)
{
+ return 0;
if (q->head_active && !q->plugged) {
struct request *next;
next = blkdev_entry_next_request(&q->queue_head);
Hope this helps.
next prev parent reply other threads:[~2003-11-04 10:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 2:49 2.4.23pre6aa3 scsi oops Jamie Clark
2003-11-04 10:28 ` Andrea Arcangeli [this message]
2003-11-04 11:52 ` Jamie Clark
2003-11-04 12:48 ` Andrea Arcangeli
2003-11-27 3:21 ` 2.4.23pre6aa3 - possible ext3 deadlock Jamie Clark
2003-11-27 12:56 ` Jan Kara
2003-12-06 1:05 ` 2.4.23pre6aa3 scsi oops Andrea Arcangeli
2003-12-06 1:39 ` Jamie Clark
2003-12-11 2:33 ` 2.4.23aa1 ext3 oops Jamie Clark
2003-12-16 15:15 ` Marcelo Tosatti
2003-12-16 15:55 ` Jamie Clark
2003-12-17 11:42 ` David Woodhouse
2003-12-18 6:19 ` Jamie Clark
2003-12-18 6:25 ` David Woodhouse
2003-12-18 7:33 ` Jamie Clark
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=20031104102816.GB2984@x30.random \
--to=andrea@suse.de \
--cc=jamie@metaparadigm.com \
--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 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.