public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.org>
To: rwhron@earthlink.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.2-pre1 dbench 32 hangs in vmstat "b" state
Date: Fri, 21 Dec 2001 23:19:51 +0100	[thread overview]
Message-ID: <20011221231951.F2929@suse.de> (raw)
In-Reply-To: <20011221091104.A120@earthlink.net> <20011221154654.E811@suse.de> <20011221114352.A8661@earthlink.net> <20011221180156.C2929@suse.de> <20011221134709.A128@earthlink.net>
In-Reply-To: <20011221134709.A128@earthlink.net>

On Fri, Dec 21 2001, rwhron@earthlink.net wrote:
> On Fri, Dec 21, 2001 at 06:01:56PM +0100, Jens Axboe wrote:
> > Thanks -- could you also try and do sysrq-t back traces when it seems
> > stuck?
> > 
> > Does a non-highmem kernel run ok?
> > 
> > -- 
> > Jens Axboe
> 
> I recompiled with highmem turned off.  
> # CONFIG_HIGHMEM4G is not set
> # CONFIG_HIGHMEM64G is not set
> 
> I run a scripty that executes dbench 32, then dbench 128.

Ok, please try something for me. In drivers/block/elevator.c, comment
out this block:

	if (q->last_merge) {
		__rq = list_entry_rq(q->last_merge);
		BUG_ON(__rq->flags & REQ_STARTED);

		if ((ret = elv_try_merge(__rq, bio))) {
			*req = __rq;
			return ret;
		}
	}

(just #if 0 the entire thing) -- the one inside elevator_linus_merge()

Loop back highmem issue is different, I'll take a look at that later.
I'll be pretty unresponsive over christmas, though.

-- 
Jens Axboe


  reply	other threads:[~2001-12-21 22:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21 14:11 2.5.2-pre1 dbench 32 hangs in vmstat "b" state rwhron
2001-12-21 14:46 ` Jens Axboe
2001-12-21 16:43   ` rwhron
2001-12-21 17:01     ` Jens Axboe
2001-12-21 18:47       ` rwhron
2001-12-21 22:19         ` Jens Axboe [this message]
2001-12-21 23:55   ` rwhron
2001-12-24 14:03     ` Jens Axboe
2001-12-24 16:59       ` rwhron
2001-12-24 17:02         ` Jens Axboe
2001-12-24 22:14           ` rwhron
2001-12-27 19:07           ` rwhron
2001-12-28 11:40             ` Jens Axboe
2001-12-28 14:14               ` rwhron
2001-12-28 14:30                 ` Jens Axboe
2001-12-28 17:49                   ` rwhron
2001-12-28 19:29                   ` rwhron
2001-12-29  6:42                   ` rwhron
2001-12-29 17:33                     ` Jens Axboe
2001-12-29 17:48                       ` Jens Axboe
2001-12-29 19:43                         ` rwhron

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=20011221231951.F2929@suse.de \
    --to=axboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhron@earthlink.net \
    /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