public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Alberto Cammozzo <mmzz@stat.unipd.it>,
	linux-scsi@vger.kernel.org
Subject: Re: lp8000 and 2.6.18-rc6
Date: Wed, 13 Sep 2006 08:33:35 -0700	[thread overview]
Message-ID: <20060913153335.GA21698@us.ibm.com> (raw)
In-Reply-To: <45081936.4040209@torque.net>

On Wed, Sep 13, 2006 at 10:44:06AM -0400, Douglas Gilbert wrote:
> James Bottomley wrote:

> No lun 0 either hence the PQual=1 for the inquiry
> response for /dev/sg6 ('sg_inq /dev/sg6'). I suspect
> 'sg_inq /dev/sg7', sg8 and sg9 also have PQual=1.
> There may be a similar pattern to 'sg_luns /dev/sg7',
> sg8 and sg9 as was reported for 'sg_luns /dev/sg6'.
> 
> > So something really strange is going on here ... The linux code should
> > have executed a probe and add luns for the contents of report lun, which
> > should have found the correct set, unless something went wrong during
> > the reporting.
> > 
> > Can you post the full dmesg from the time the Emulex is detected to the
> > time sg attaches?  report luns is supposed to issue a failure message if
> > something goes wrong (additionally, using the latest -mm would be
> > helpful since that prints enhanced inquiry information from scsi-misc).
> 
> Yes dmesg would be useful. Is there something stopping
> the mid level scanning luns where lun>0 (perhaps something
> in the black list)?

Also set scsi log scan before scanning and include that output, so if the
device isn't added because of PQ it should print a message, use:

	sysctl -w dev.scsi.logging_level=0x01c0

-- Patrick Mansfield

  parent reply	other threads:[~2006-09-13 15:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 21:08 lp8000 and 2.6.18-rc6 Alberto Cammozzo
2006-09-10 13:56 ` Matthew Wilcox
2006-09-10 21:04   ` Alberto Cammozzo
2006-09-11  1:06     ` Douglas Gilbert
2006-09-11  2:17       ` James Bottomley
2006-09-11  9:51         ` Alberto Cammozzo
2006-09-11 12:21           ` James Smart
2006-09-11 16:29             ` Alberto Cammozzo
2006-09-11  6:40       ` Alberto Cammozzo
2006-09-11 17:00         ` James Bottomley
2006-09-12  6:45           ` Alberto Cammozzo
2006-09-13 14:11             ` James Bottomley
2006-09-13 14:44               ` Douglas Gilbert
2006-09-13 15:20                 ` James Bottomley
2006-09-13 15:33                 ` Patrick Mansfield [this message]
2006-09-13 15:37                 ` Alberto Cammozzo
  -- strict thread matches above, loose matches on Subject: below --
2006-09-09 21:03 Alberto Cammozzo
2006-09-09 21:01 Alberto Cammozzo
2006-09-10 14:03 ` James Smart
2006-09-10 20:43   ` Alberto Cammozzo

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=20060913153335.GA21698@us.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mmzz@stat.unipd.it \
    /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