From: Alexander Perlis <aperlis@math.lsu.edu>
To: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Perlis <aperlis@math.lsu.edu>,
Nikkos Svoboda <nsvoboda@math.lsu.edu>
Subject: [PATCH] scsi: devinfo: Add BLIST_NO_RSOC for Promise VTrak E310f
Date: Tue, 12 May 2026 18:12:54 -0500 [thread overview]
Message-ID: <20260512231254.27530-1-aperlis@math.lsu.edu> (raw)
The extremely slow boots reported July 2014 in
[Bug 79901](https://bugzilla.kernel.org/show_bug.cgi?id=79901)
for Promise VTrak E610f 3U 16-bay FC RAID enclosure occur also with
the Promise VTrak E310f 2U 12-bay FC RAID enclosure. The 2014
[patch](https://bugzilla.kernel.org/attachment.cgi?id=144101&action=diff)
added support for the BLIST_NO_RSOC flag and specified that flag for the
Promise VTrak E610f. This current patch simply adds the E310f to that same
list. (My workaround has been to include
scsi_mod.dev_flags=Promise:\"VTrak E310f\":0x20000040
among my kernel boot parameters.)
One curiosity is the additional BLIST_SPARSELUN flag. This was also in
the 2014 patch for the E610f, and was already in place for *all* Promise
devices since 2007 due to commit
e0b2e597d5dd ("[SCSI] stex: fix id mapping issue")
which added the line
{"Promise", "", NULL, BLIST_SPARSELUN}
The 2007 commit message talks of issues with SuperTrak EX (stex) but
the added line did not limit itself to that particular device family.
The current patch for E310F, like the 2014 patch for E610f, adds
BLIST_NO_RSOC while preserving BLIST_SPARSELUN from 2007.
Signed-off-by: Alexander Perlis <aperlis@math.lsu.edu>
Suggested-by: Nikkos Svoboda <nsvoboda@math.lsu.edu>
---
drivers/scsi/scsi_devinfo.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/scsi_devinfo.c b/drivers/scsi/scsi_devinfo.c
index 68a992494b12..c6defe1c3152 100644
--- a/drivers/scsi/scsi_devinfo.c
+++ b/drivers/scsi/scsi_devinfo.c
@@ -218,6 +218,7 @@ static struct {
{"PIONEER", "CD-ROM DRM-602X", NULL, BLIST_FORCELUN | BLIST_SINGLELUN},
{"PIONEER", "CD-ROM DRM-604X", NULL, BLIST_FORCELUN | BLIST_SINGLELUN},
{"PIONEER", "CD-ROM DRM-624X", NULL, BLIST_FORCELUN | BLIST_SINGLELUN},
+ {"Promise", "VTrak E310f", NULL, BLIST_SPARSELUN | BLIST_NO_RSOC},
{"Promise", "VTrak E610f", NULL, BLIST_SPARSELUN | BLIST_NO_RSOC},
{"Promise", "", NULL, BLIST_SPARSELUN},
{"QEMU", "QEMU CD-ROM", NULL, BLIST_SKIP_VPD_PAGES},
--
2.43.0
next reply other threads:[~2026-05-12 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 23:12 Alexander Perlis [this message]
[not found] ` <f5f2c2d0-382e-4032-a5a4-c82aac3a4b80@gmail.com>
2026-05-13 11:54 ` [PATCH] scsi: devinfo: Add BLIST_NO_RSOC for Promise VTrak E310f Xose Vazquez Perez
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=20260512231254.27530-1-aperlis@math.lsu.edu \
--to=aperlis@math.lsu.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nsvoboda@math.lsu.edu \
/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