public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris_friesen@sympatico.ca>
To: dgilbert@interlog.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: BUG REPORT: terminal hangs when I load the sd_mod module
Date: Mon, 20 Oct 2003 23:30:49 -0400	[thread overview]
Message-ID: <3F94A869.9070607@sympatico.ca> (raw)

I have a 2.6.0-test8 kernel with the jumpshot card reader.  I can
compile the generic scsi driver no problem, and when I insert the flash
card I get the following log entry:

Oct 20 23:23:02 doug kernel: hub 2-1:1.0: new USB device on port 2, 
assigned address 4
Oct 20 23:23:02 doug kernel: scsi1 : SCSI emulation for USB Mass Storage 
devices
Oct 20 23:23:02 doug kernel:   Vendor: Lexar     Model: Jumpshot USB CF 
   Rev: 0001
Oct 20 23:23:02 doug kernel:   Type:   Direct-Access 
   ANSI SCSI revision: 02

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.

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y



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

Thanks,
Chris


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  3:30 Chris Friesen [this message]
2003-10-21 18:20 ` BUG REPORT: terminal hangs when I load the sd_mod module Patrick Mansfield

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=3F94A869.9070607@sympatico.ca \
    --to=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