From: Patrick Mansfield <patmans@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
mikeand@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Broken SCSI code in the BK tree (was: 2.5.59-mm8)
Date: Thu, 6 Feb 2003 18:25:02 -0800 [thread overview]
Message-ID: <20030206182502.A16364@beaverton.ibm.com> (raw)
In-Reply-To: <293060000.1044583265@[10.10.2.4]>; from mbligh@aracnet.com on Thu, Feb 06, 2003 at 06:01:06PM -0800
On Thu, Feb 06, 2003 at 06:01:06PM -0800, Martin J. Bligh wrote:
>
> Curious. I've no idea why the changes brought this out then ... I've done
> hundreds and hundreds of reboots on 2.5 on all sorts of different kernels,
> and never, ever seen this. Yet in 2.5.59-bk I see it every single time.
> Very odd.
>
> M.
Okay:
There were some bk scsi changes that ignored the queue depth (qlogicisp
sets them all to one).
Current bk (I just pulled and checked) has a fix, the cleaner shinier
better scsi_lib.c scsi_request_fn now has this code:
if (sdev->device_busy >= sdev->queue_depth)
break;
So the oops has to do with the isp handling multiple requests in a row or
in quick succession.
Hopefully going to the latest bk will fix your oops.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-02-07 2:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 7:31 2.5.59-mm8 Andrew Morton
2003-02-04 8:02 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:05 ` 2.5.59-mm8 Andrew Morton
2003-02-04 8:08 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:09 ` 2.5.59-mm8 Martin J. Bligh
2003-02-04 8:17 ` 2.5.59-mm8 Andrew Morton
2003-02-04 22:15 ` Broken SCSI code in the BK tree (was: 2.5.59-mm8) Martin J. Bligh
2003-02-06 5:13 ` Martin J. Bligh
2003-02-06 20:50 ` Martin J. Bligh
2003-02-06 22:30 ` Martin J. Bligh
2003-02-06 23:25 ` James Bottomley
2003-02-07 1:24 ` Patrick Mansfield
2003-02-07 2:01 ` Martin J. Bligh
2003-02-07 2:25 ` Patrick Mansfield [this message]
2003-02-07 4:05 ` Doug Ledford
2003-02-07 4:19 ` Anton Blanchard
2003-02-07 8:50 ` Mike Anderson
2003-02-07 4:19 ` Andrew Morton
2003-02-07 4:24 ` Doug Ledford
2003-02-07 4:35 ` William Lee Irwin III
2003-02-07 4:53 ` Matthew Jacob
2003-02-07 4:50 ` Matthew Jacob
2003-02-07 4:28 ` Martin J. Bligh
2003-02-04 9:07 ` 2.5.59-mm8 Dave Hansen
2003-02-04 9:18 ` 2.5.59-mm8 compile error in tcp_ipv6.c Helge Hafting
2003-02-04 9:21 ` Andrew Morton
2003-02-04 9:29 ` David S. Miller
2003-02-04 9:33 ` 2.5.59-mm8 Arjan van de Ven
2003-02-05 8:08 ` 2.5.59-mm8 Mike Galbraith
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=20030206182502.A16364@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=mikeand@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®