public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Chris Friesen <chris_friesen@sympatico.ca>
Cc: dgilbert@interlog.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: BUG REPORT: terminal hangs when I load the sd_mod module
Date: Tue, 21 Oct 2003 11:20:57 -0700	[thread overview]
Message-ID: <20031021112057.A5014@beaverton.ibm.com> (raw)
In-Reply-To: <3F94A869.9070607@sympatico.ca>; from chris_friesen@sympatico.ca on Mon, Oct 20, 2003 at 11:30:49PM -0400

On Mon, Oct 20, 2003 at 11:30:49PM -0400, Chris Friesen wrote:

> When I try and load the sd_mod module, that terminal just simply freezes
> and I can't break out.  Similarly, if I compile scsi disk support right
> into the kernel, it sits forever at boot time.  I have the following
> options set in my .config.

> This problem has been present since at least -test6.  Any ideas what's 
> going on?

Maybe the MODE SENSE page cache is causing problems (known problem with
some USB storage devices), triggering the error (i.e. timeout) handler to
run, leading to the command being retried forever.

Turn on all scsi logging (you must be logging and booting over IDE, so
the following won't cause infinite logging):

sysctl -w dev.scsi.logging_level=0xffffffff

Also get a trace of the hung process via sysrq.

After you get that data, try removing sd_do_mode_sense() calls in sd.c to
see if MODE SENSE commands are causing problems.

You could also try using sg (sg_utils) to send a MODE SENSE page 8, and
see what happens.

-- Patrick Mansfield

      reply	other threads:[~2003-10-21 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  3:30 BUG REPORT: terminal hangs when I load the sd_mod module Chris Friesen
2003-10-21 18:20 ` 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=20031021112057.A5014@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=chris_friesen@sympatico.ca \
    --cc=dgilbert@interlog.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox