> > > Marc wrote: > > > >> scsi 0:0:0:49488: scsi_add_lun: correcting incorrect peripheral device type > 0x0 for W-LUN 0x c150hN > > > > ^^^^^ Where do these crazy LUN numbers come from? That > > looks like something which needs fixing... > > sdev_printk(KERN_WARNING, sdev, "%s: correcting incorrect > peripheral device type 0x%x for W-LUN 0x%16xhN\n", > __func__, sdev->type, (unsigned int)sdev->lun); > > What does the "hN" suffix stand for? It seems redundant with the "0x" > prefix... > (Looks like hN might be "hexadecimal Number") > > > scsi 0:0:0:49488 -> 0xc150 > scsi 0:0:0:49476 -> 0xc144 > scsi 0:0:0:49456 -> 0xc130 Those are coming from ufshcd_scsi_add_wlus(), In which we call __scsi_add_device() for each one of the 3 w-luns: UFS Device - 0x50, Boot - 0x30, RPMB - 0x44. Everything seems in order. Thanks, Avri
