Using Atto Celerity Fiber Card with ESOS 4

[Okita240]

Hello All,

We are trying to use Atto Celerity FC cards with ESOS 4.X.X, but Atto fiber ports does not show in the TUI. The scst driver and the celerity driver have been added during the configure process with the following command, using Centos 7.9:

./configure --with-celerity_16_32=/home/build/esos/atto/lnx_drv_celerity16-32_2060f1.tgz --with-atto_scst=/home/build/esos/atto/lnx_drv_attoscst_2.06.0f1.tgz

make image completes with no error, and I am able to boot up the ESOS with a USB stick. The Atto FC also shows when running lspci.

I see the following in /var/log/message

atto_scst(1): ATTO-SCST support driver, version 2.06.0f1

atto_scst(1): No ATTO target mode adapters found

atto_scst(1): FC TMD INITIALIZE Failed; FcTmIoct1.Status = 2

Any help in getting the Atto FC HBA to work with the ESOS 4 would be greatly appreciated. Please let me know if I should add any more information.

Thank you!

[Marc Smith]

Is the Celerity driver loaded (eg, check 'lsmod | grep celerity' and
see)? If not, find out why the driver didn't load, or why it doesn't
bind to your FC HBA PCIe EP's (check 'dmesg' output for lines
containing "celerity").

--Marc


>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/b6da9d9c-ecff-45f8-87f1-657fdffe761dn%40googlegroups.com.

[Okita240]

Hello Marc,

Thank you for the response. Running lsmod shows the following:

celerity16fc          491520  0
celerity16fc_cfg       16384  1 celerity16fc
nvme_fc                32768  1 celerity16fc_cfg
nvmet_fc               28672  1 celerity16fc_cfg

so it seems like the driver is loading, but it does not seem to be binding to the FC HBA.

Here is the dmesg output with Celerity.

[   63.917223] celerity16fc: module license 'Proprietary' taints kernel.
[   63.917225] Disabling lock debugging due to kernel taint
[   67.326672] scsi host13: ATTO Celerity FC-164P, PCI address 101:0:0, Driver 2.06.0f1
[   70.734642] scsi host14: ATTO Celerity FC-164P, PCI address 101:0:1, Driver 2.06.0f1
[   74.142636] scsi host15: ATTO Celerity FC-164P, PCI address 101:0:2, Driver 2.06.0f1
[   77.550642] scsi host16: ATTO Celerity FC-164P, PCI address 101:0:3, Driver 2.06.0f1
[   79.895073] [1152]: scst: User interface thread started
[   79.896872] [1148]: scst: Attached to scsi0, channel 2, id 0, lun 0, type 0
[   79.896904] [1148]: scst: Attached to scsi0, channel 2, id 1, lun 0, type 0
[   79.896935] [1148]: scst: Attached to scsi1, channel 2, id 0, lun 0, type 0
[   79.896966] [1148]: scst: Attached to scsi1, channel 2, id 1, lun 0, type 0
[   79.896998] [1148]: scst: Attached to scsi12, channel 0, id 0, lun 0, type 0
[   79.897298] [1162]: scst: Init thread started
[   79.897328] [1163]: scst: Task management thread started
[   79.897349] [1164]: scst: Management thread started
[   79.897357] [1148]: scst: Target template copy_manager registered successfully
[   79.897400] [1148]: scst: Target copy_manager_tgt for template copy_manager registered successfully
[   79.897408] [1148]: scst: Using security group "copy_manager_tgt" for initiator "copy_manager_sess" (target copy_manager_tgt)
[   79.897475] [1148]: scst: SCST version 3.7.0 loaded successfully (global max mem for commands ignored, per device 1496MB)
[   79.897478] [1148]: scst: Enabled features: TRACING
[   79.947480] [1165]: iscsi-scst: iSCSI SCST Target - version 3.7.0
[   79.947482] [1165]: iscsi-scst: Registered iSCSI transport: iSCSI-TCP
[   79.947967] [1165]: scst: Target template iscsi registered successfully
[   79.948004] [1166]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948029] [1167]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948057] [1168]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948078] [1169]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948103] [1170]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948123] [1171]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948151] [1172]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948173] [1173]: iscsi-scst: Read thread for pool 0000000013ea0e5d started
[   79.948194] [1174]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.948214] [1175]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.948234] [1176]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.948259] [1177]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.948280] [1178]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.948301] [1179]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.948327] [1180]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.948346] [1181]: iscsi-scst: Write thread for pool 0000000013ea0e5d started
[   79.987401] [1182]: iscsi-scst: Registered iSCSI transport: iSER
[   80.004090] [1184]: scst: Target template ib_srpt registered successfully
[   80.007229] [1185]: scst: Device handler "dev_disk" for type 0 registered successfully
[   80.007236] [1185]: scst: Device handler "dev_disk_perf" for type 0 registered successfully
[   80.011943] [1186]: scst: Virtual device handler vdisk_fileio for type 0 registered successfully
[   80.011950] [1186]: scst: Virtual device handler vdisk_blockio for type 0 registered successfully
[   80.011956] [1186]: scst: Virtual device handler vdisk_nullio for type 0 registered successfully
[   80.011965] [1186]: scst: Virtual device handler vcdrom for type 5 registered successfully
[   80.014963] [1187]: scst: Device handler "dev_tape" for type 1 registered successfully
[   80.014972] [1187]: scst: Device handler "dev_tape_perf" for type 1 registered successfully
[   80.017906] [1188]: scst: Device handler "dev_changer" for type 8 registered successfully
[   80.037869] [1189]: scst: Target template fcst registered successfully
[   80.050811] [1190]: qla2x00t: Initializing QLogic Fibre Channel HBA Driver target mode addon version 3.7.0
[   80.050841] [1190]: qla2x00t: Target mode driver for QLogic 2x00 controller registered successfully
[   80.050848] [1190]: scst: Target template qla2x00t registered successfully
[   80.061651] atto_scst: ATTO SCST support driver, version 2.06.0f1
[   80.061665] [1191]: scst: Target template atto_scst registered successfully
[   80.061823] atto_scst(1): FC TMD INITIALIZE Failed;  FcTmIoctl.Status = 2
[   80.061828] atto_scst(1): FC TMD INITIALIZE Failed;  FcTmIoctl.Status = 2
[   80.061832] atto_scst(1): FC TMD INITIALIZE Failed;  FcTmIoctl.Status = 2
[   80.061836] atto_scst(1): FC TMD INITIALIZE Failed;  FcTmIoctl.Status = 2
[   80.062423] atto_scst(1): No ATTO target mode adapters found
[   80.089485] atto_scst: ATTO SCST support driver, version 2.06.0f1
[   80.089497] BUG: unable to handle page fault for address: ffffffffa095b140
[   80.089638] #PF: supervisor read access in kernel mode
[   80.089769] #PF: error_code(0x0000) - not-present page
[   80.089901] PGD 2814067 P4D 2814067 PUD 2815063 PMD 3cd128067 PTE 0
[   80.090040] Oops: 0000 [#1] SMP PTI
[   80.090167] CPU: 5 PID: 1191 Comm: modprobe Kdump: loaded Tainted: P           OE     5.4.229-esos.prod #1
[   80.090341] Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.6 01/03/2022

[   80.090514] RIP: 0010:strcmp+0x2/0x1a

Is this showing that there is a conflict with teh Qlogic driver? If so, it there a way to not include the QLogic driver during the build process?

Also, looking at /proc/scsi/celerity16fc/13 shows that the SCSI Target Mode is enabled, which I would think is a good sign?

ATTO Celerity FC-164P
Driver version: 2.06.0f1 (09:30:49 Jun 17 2022)
Copyright 2011-2022
http://www.atto.com
SCSI host: 13
Flash version: 5/31/2022
Firmware version: 14.0.597.0
WWNN: 20000010:86050424
WWPN: 10000010:86050424
SCSI Initiator Mode is disabled
SCSI Target Mode is enabled/disconnected
NVMe Initiator Mode is disabled
NVMe Target Mode is disabled/disconnected

Driver Parameters:
------------------
max_logins=512                        multi_tgt_queue=2
reg_sgl_percent=0                     npiv_enable=0
max_npiv_vports=0                     max_npiv_logins=0
target_mode=1                         target_mode_link_delay=1
multimode_ports=0                     target_mode_mask=0xffffffff
initiator_mode_mask=0x0               target_link_delay_mask=0xffffffff
num_xcb=1024                          num_scb=1024
change_notification=1                 use_transport_layer=1
rport_timeout=30                      atto_log_mask=0x0
cpu_affinity=1                        log_level=7
quick_init=0                          cmd_per_lun=1024
can_queue=1024                        num_sg_lists=512
sg_tablesize=128                      sgl_page_size=127
max_xfer_size=524288                 

Thank you,