[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SN6PR04MB4925C5CD48062BA0DE8DEFF3FC560@SN6PR04MB4925.namprd04.prod.outlook.com>
Date: Tue, 2 Apr 2019 15:40:34 +0000
From: Avri Altman <Avri.Altman@....com>
To: Marc Gonzalez <marc.w.gonzalez@...e.fr>,
Martin Petersen <martin.petersen@...cle.com>,
Alim Akhtar <alim.akhtar@...sung.com>
CC: SCSI <linux-scsi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: RE: correcting incorrect peripheral device type 0x0
Hi,
Looking where this warning is coming from,
Scsi is just forcing sdev->type = TYPE_WLUN for wluns.
As no other driver sets it by itself - I wouldn't lose sleep over it.
Thanks,
Avri
> -----Original Message-----
> From: Marc Gonzalez <marc.w.gonzalez@...e.fr>
> Sent: Tuesday, April 02, 2019 6:05 PM
> To: Martin Petersen <martin.petersen@...cle.com>; Avri Altman
> <Avri.Altman@....com>; Alim Akhtar <alim.akhtar@...sung.com>
> Cc: SCSI <linux-scsi@...r.kernel.org>; LKML <linux-kernel@...r.kernel.org>
> Subject: correcting incorrect peripheral device type 0x0
>
> Hello,
>
> In my boot log, when UFS is enabled, I get the following warnings:
>
> scsi 0:0:0:49488: scsi_add_lun: correcting incorrect peripheral device type
> 0x0 for W-LUN 0x c150hN
> scsi 0:0:0:49488: Well-known LUN SAMSUNG KLUCG4J1EB-B0B1 0200 PQ:
> 0 ANSI: 6
> scsi 0:0:0:49476: scsi_add_lun: correcting incorrect peripheral device type
> 0x0 for W-LUN 0x c144hN
> scsi 0:0:0:49476: Well-known LUN SAMSUNG KLUCG4J1EB-B0B1 0200 PQ:
> 0 ANSI: 6
> scsi 0:0:0:49456: scsi_add_lun: correcting incorrect peripheral device type
> 0x0 for W-LUN 0x c130hN
> scsi 0:0:0:49456: Well-known LUN SAMSUNG KLUCG4J1EB-B0B1 0200 PQ:
> 0 ANSI: 6
>
> Is there something I can/should do to fix these issues?
> Or may they be safely ignored?
>
> Regards.
Powered by blists - more mailing lists