Date: Thu, 18 Sep 2003 13:44:22 +0200
From: Olivier Galibert <galibert@limsi.fr>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: AIC7xxx LUN enumeration failure and DV config failure
Message-ID: <20030918114422.GA82516@dspnet.fr.eu.org>
Mail-Followup-To: Olivier Galibert <galibert@limsi.fr>,
	Patrick Mansfield <patmans@us.ibm.com>, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
References: <20030917130656.GA2948@m23.limsi.fr> <20030917082359.A23802@beaverton.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030917082359.A23802@beaverton.ibm.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1008
Lines: 29

On Wed, Sep 17, 2003 at 08:23:59AM -0700, Patrick Mansfield wrote:
> The following looks like 2.6.x output, since 2.4.x does not have REPORT
> LUN support.

And it is.  I had a blonde moment I guess and booted with the wrong
kernel.  2.4.23p4 works perfectly well.


> My guess is that something is totally screwed up with the arrays REPORT
> LUN results.
> 
> Does it work OK if you turn off CONFIG_SCSI_REPORT_LUNS?

I'll see when I can try that.


> If you could dump the result of sending a REPORT LUN to the device, that
> would be useful. You could use the sg interface on a system (modify one of
> the sg utils programs, like sg_inq.c) that found the LUNs OK, or hack the
> kernel to dump the REPORT LUN output, or get a trace.

I'll try to do that.

  OG.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/