aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/scsi_devinfo.c
diff options
context:
space:
mode:
authorKurt Garloff <garloff@suse.de>2006-04-03 15:18:35 +0200
committerJames Bottomley <jejb@mulgrave.il.steeleye.com>2006-04-14 13:56:03 -0500
commit6c7154c97e20c0ea28547240dc86731c0cee1b2f (patch)
tree9960dbadf3f685e70c03f0551f0bb890a68b94b7 /drivers/scsi/scsi_devinfo.c
parent4186ab1973758190916703eb8889ebe8002c5c8f (diff)
downloadkernel_samsung_espresso10-6c7154c97e20c0ea28547240dc86731c0cee1b2f.zip
kernel_samsung_espresso10-6c7154c97e20c0ea28547240dc86731c0cee1b2f.tar.gz
kernel_samsung_espresso10-6c7154c97e20c0ea28547240dc86731c0cee1b2f.tar.bz2
[SCSI] Better log messages for PQ3 devs
Some devices report a peripheral qualifier of 3 for LUN 0; with the original code, we would still try a REPORT_LUNS scan (if SCSI level is >= 3 or if we have the BLIST_REPORTLUNS2 passed in), but NOT any sequential scan. Also, the device at LUN 0 (which is not connected according to the PQ) is not registered with the OS. Unfortunately, SANs exist that are SCSI-2 and do NOT support REPORT_LUNS, but report a unknown device with PQ 3 on LUN 0. We still need to scan them, and most probably we even need BLIST_SPARSELUN (and BLIST_LARGELUN). See the bug reference for an infamous example. This patch 2/3: If a PQ3 device is found, log a message that describes the device (INQUIRY DATA and C:B:T:U tuple) and make a suggestion for blacklisting it. Signed-off-by: Kurt Garloff <garloff@suse.de> Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'drivers/scsi/scsi_devinfo.c')
0 files changed, 0 insertions, 0 deletions