linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@wdc.com>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>,
	Martin Petersen <martin.petersen@oracle.com>,
	Alim Akhtar <alim.akhtar@samsung.com>
Cc: SCSI <linux-scsi@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: RE: correcting incorrect peripheral device type 0x0
Date: Tue, 2 Apr 2019 15:40:34 +0000	[thread overview]
Message-ID: <SN6PR04MB4925C5CD48062BA0DE8DEFF3FC560@SN6PR04MB4925.namprd04.prod.outlook.com> (raw)
In-Reply-To: <ab8d589f-db76-9a95-1b55-3e906ad89487@free.fr>

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@free.fr>
> Sent: Tuesday, April 02, 2019 6:05 PM
> To: Martin Petersen <martin.petersen@oracle.com>; Avri Altman
> <Avri.Altman@wdc.com>; Alim Akhtar <alim.akhtar@samsung.com>
> Cc: SCSI <linux-scsi@vger.kernel.org>; LKML <linux-kernel@vger.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.

  reply	other threads:[~2019-04-02 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 15:05 correcting incorrect peripheral device type 0x0 Marc Gonzalez
2019-04-02 15:40 ` Avri Altman [this message]
2019-04-04  3:34 ` Martin K. Petersen
2019-04-04  4:04   ` Douglas Gilbert
2019-04-04 12:02   ` Marc Gonzalez
2019-04-04 13:02     ` Avri Altman

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=SN6PR04MB4925C5CD48062BA0DE8DEFF3FC560@SN6PR04MB4925.namprd04.prod.outlook.com \
    --to=avri.altman@wdc.com \
    --cc=alim.akhtar@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=martin.petersen@oracle.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).