Date: Tue, 26 Nov 2002 14:24:35 -0800
From: Patrick Mansfield <patmans@us.ibm.com>
To: Rusty Lynch <rusty@stinkycat.com>
Cc: groudier@free.fr, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [BUG][2.5.49 SCSI]Duplicate Proc Entries for SCSI
Message-ID: <20021126142435.A1402@eng2.beaverton.ibm.com>
References: <200211250609.gAP69YS09374@stinkycat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <200211250609.gAP69YS09374@stinkycat.com>; from rusty@stinkycat.com on Sun, Nov 24, 2002 at 10:09:34PM -0800
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 3653
Lines: 80

Rusty -

On Sun, Nov 24, 2002 at 10:09:34PM -0800, Rusty Lynch wrote:
> On my 2.5.49 build, I am seeing duplicate entries in /proc/scsi/scsi. 
> On this system both scsi devices are both emulated (one is an Sony 
> IDE ReWritable CD drive and the other is PNY USB flash card reader using 
> the mass-storage driver.) 
> 
> Before plugging in the flash card reader, /proc/scsi/scsi looks like: 
> Attached devices: 
> Host: scsi0 Channel: 00 Id: 00 Lun: 00 
>   Vendor: SONY     Model: CD-RW CRX1611    Rev: TYS3 
>   Type:   CD-ROM                           ANSI SCSI revision: 02 
> Host: scsi0 Channel: 00 Id: 00 Lun: 01 
>   Vendor: SONY     Model: CD-RW CRX1611    Rev: TYS3 
>   Type:   CD-ROM                           ANSI SCSI revision: 02 
> 
> and after plugging in the flash card reader, /proc/scsi/scsi looks like: 
> Attached devices: 
> Host: scsi0 Channel: 00 Id: 00 Lun: 00 
>   Vendor: SONY     Model: CD-RW CRX1611    Rev: TYS3 
>   Type:   CD-ROM                           ANSI SCSI revision: 02 
> Host: scsi0 Channel: 00 Id: 00 Lun: 01 
>   Vendor: SONY     Model: CD-RW CRX1611    Rev: TYS3 
>   Type:   CD-ROM                           ANSI SCSI revision: 02 
> Host: scsi1 Channel: 00 Id: 00 Lun: 00 
>   Vendor: Datafab  Model: USB to CF + SM C Rev: 0017 
>   Type:   Direct-Access                    ANSI SCSI revision: 02 
> Host: scsi1 Channel: 00 Id: 00 Lun: 01 
>   Vendor: Datafab  Model: USB to CF + SM C Rev: 0017 
>   Type:   Direct-Access                    ANSI SCSI revision: 02 

Did you figure out anything? Was there anything of interest in your dmesg?

I tried out 2.5.49, and all scsi devices showed up just once, both for
the aic driver built into the kernel, and for qla driver built as a
module, with SCSI revision 2 and 3 devices attached to the qla.

Maybe it is specific to ide-scsi or the usb-scsi pseudo adapter drivers.

Try turning on scsi scan logging before inserting the flash card via:

echo scsi log scan 4  >/proc/scsi/scsi

And send the output.

My single lun scsi 2 disks display the following, showing that
lun 1 is (correctly) not configured off of id 1 and id 2:

[ junk deleted ]
scsi scan: INQUIRY to host 2 channel 0 id 1 lun 0
scsi scan: 1st INQUIRY successful with code 0x0
scsi scan: 2nd INQUIRY successful with code 0x0
  Vendor: SEAGATE   Model: ST39173F CLAR09   Rev: 351B
  Type:   Direct-Access                      ANSI SCSI revision: 02
scsi scan: host 2 channel 0 id 1 lun 0 name/id: '32000002037109657'
scsi scan: Sequential scan of host 2 channel 0 id 1
scsi scan: INQUIRY to host 2 channel 0 id 1 lun 1
scsi scan: 1st INQUIRY successful with code 0x0
scsi scan: 2nd INQUIRY successful with code 0x0
scsi scan: peripheral qualifier of 3, no device added
scsi scan: INQUIRY to host 2 channel 0 id 2 lun 0
scsi scan: 1st INQUIRY successful with code 0x0
scsi scan: 2nd INQUIRY successful with code 0x0
  Vendor: SEAGATE   Model: ST39173F CLAR09   Rev: 351B
  Type:   Direct-Access                      ANSI SCSI revision: 02
scsi scan: host 2 channel 0 id 2 lun 0 name/id: '32000002037109db0'
scsi scan: Sequential scan of host 2 channel 0 id 2
scsi scan: INQUIRY to host 2 channel 0 id 2 lun 1
scsi scan: 1st INQUIRY successful with code 0x0
scsi scan: 2nd INQUIRY successful with code 0x0
scsi scan: peripheral qualifier of 3, no device added
[ lots of stuff deleted, as this fcp adapter goes up to id 255 ]

-- Patrick Mansfield
-
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/