public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: "Vladimir G. Ivanovic" <vladimir@acm.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: sym53c8xx: 'echo "scsi dump 1" > /proc/scsi/scsi' generates an oops
Date: Wed, 29 May 2002 10:44:51 -0700	[thread overview]
Message-ID: <20020529104451.A5229@eng2.beaverton.ibm.com> (raw)
In-Reply-To: <200205272332.g4RNWgi22980@bach.leonora.org>; from vladimir@acm.org on Mon, May 27, 2002 at 04:32:42PM -0700

On Mon, May 27, 2002 at 04:32:42PM -0700, Vladimir G. Ivanovic wrote:
> The command 
> 
>     echo "scsi dump 1" > /proc/scsi/scsi
> 
> generated an oops (syslog entries appended) on my SMP machine running a
> 2.4.18 custom kernel derived from Red Hat's 2.4.18-4 kernel. My SCSI
> controller is an sym53c1010-33, and its driver is
> sym53c8xx-1.7.3c-20010512. 
> 
> Is this (1) operator error, (2) a high/mid/low-level SCSI problem, or
> (3) some other kind of kernel problem that should be reported on the
> linux-kernel list?
> 
> If some more information is needed, please let me know.
> 
> Thanks. 
> 
> --- Vladimir
> 
> P.S. I know, if it hurts, don't do that. ;-)

It's a mid layer SCSI bug, it improperly references the queue:

	queue_head = &blk_dev[i].request_queue.queue_head;

It should really be something like:

	queue_head = SDpnt->request_queue;

Better yet the code should be deleted, as it is also dumping all queues for
each Scsi_Device. The code is gone in the current 2.5.x.

-- Patrick Mansfield

      reply	other threads:[~2002-05-29 17:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 23:32 sym53c8xx: 'echo "scsi dump 1" > /proc/scsi/scsi' generates an oops Vladimir G. Ivanovic
2002-05-29 17:44 ` Patrick Mansfield [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=20020529104451.A5229@eng2.beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=vladimir@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox