From: Jens Axboe <axboe@suse.de>
To: markw@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 oops w/ reiserfs + deadline elevator
Date: Thu, 15 Jan 2004 10:36:36 +0100 [thread overview]
Message-ID: <20040115093636.GJ5507@suse.de> (raw)
In-Reply-To: <200401142115.i0ELFDo23784@mail.osdl.org>
On Wed, Jan 14 2004, markw@osdl.org wrote:
> I'm getting the following oops with our DBT-2 workload. It appears that
> I can only reproduce the problem with a combination of an aacraid
> controller, reiserfs, and the deadline elevator. I'm also using lvm2
> but I can't really try to do the same test without lvm2 though. I have
> seen everything behave properly with the AS elevator or without an
> aacraid controller.
I don't believe this has anything to do with the io scheduler, it looks
clearly like a problem deep inside the aac driver (and thus completely
io scheduler independent). The fact that it triggers with deadline is
likely completely coincidental.
Looks like scsicmd->scsi_done == NULL which is very odd. You may want to
try and add some debug prints checking that (and dumping scsicmd state)
fact.
--
Jens Axboe
prev parent reply other threads:[~2004-01-15 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 21:15 2.6.1 oops w/ reiserfs + deadline elevator markw
2004-01-15 9:36 ` Jens Axboe [this message]
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=20040115093636.GJ5507@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.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.