linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	James.Bottomley@SteelEye.com
Subject: Re: [patch] 2.6 -- add IOI Media Bay to SCSI quirk list
Date: Thu, 12 Aug 2004 19:00:53 -0400	[thread overview]
Message-ID: <411BF6A5.2030306@tuxdriver.com> (raw)
In-Reply-To: <20040812225118.GA20904@beaverton.ibm.com>

Patrick Mansfield wrote:

>We seem to be getting quite a few of these. In theory we could add a line
>like this for every multi-lun SCSI device.
>  
>

Isn't that what the quirk list is for?

>Can you instead try booting with scsi_mod.max_luns=8 (or such) or build
>with SCSI_MULTI_LUN enabled?
>  
>

That works for my box, but what about for others?  Like those who may 
have both a multi-lun device and a single-lun device that hangs on a 
non-zero lun?  What about the average luser who can't be bothered to 
hack-up his startup scripts or *gasp* rebuild his kernel?

It seems like the quirk list is there for a reason.  If we start 
rejecting certain devices, then what is the criteria for a device to 
actually make it on the list?

John

  reply	other threads:[~2004-08-12 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 21:37 [patch] 2.6 -- add IOI Media Bay to SCSI quirk list John W. Linville
2004-08-12 22:51 ` Patrick Mansfield
2004-08-12 23:00   ` John W. Linville [this message]
2004-08-12 23:39     ` Dave Jones
2004-08-13  0:27     ` Patrick Mansfield
2004-08-13  1:21       ` John W. Linville
2004-08-13 21:32         ` Marcelo Tosatti

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=411BF6A5.2030306@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@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;
as well as URLs for NNTP newsgroup(s).