Not all Fiber Channel Tape devices are visible when using Qlogic Host Bus Adapters

This document (7013001) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 2

Situation

When booting the server the not all Fiber Channel Tape Devices are visible, the /var/log/boot.msg file shows only one tape device being detected. Depending on the amount of Tape Devices available, sometimes two may also be detected, the rest of the devices are not shown / visible.

Resolution

Reported to engineering, please open a Service Request to obtain a PTF (Public Test File) kernel that resolves the problem.

Cause

The tape devices are not detected due to Async-adisc requests failing. When enabling extended error logging for the qla2xxx driver the below is an excerpt of the related messages that can be seen in /var/log/boot.msg repeating multiple times;

kernel: [  870.470890] qla2xxx [0000:03:0b.0]-5046:3:
Async-adisc failed - portid=c909e1 status=30 mb0=4005 mb1=4 mb2=6 mb6=0 mb7=0.
kernel: [  870.470923] qla2xxx [0000:03:0b.0]-4801:3: DPC
handler waking up.
kernel: [  870.470929] qla2xxx [0000:03:0b.0]-4802:3:
dpc_flags=0x0.
kernel: [  870.470934] qla2xxx [0000:03:0b.0]-480d:3:
Relogin scheduled.
kernel: [  870.470939] qla2xxx [0000:03:0b.0]-1873:3:
Entered qla2x00_fabric_logout.
kernel: [  870.470943] qla2xxx [0000:03:0b.0]-1800:3:
Entered qla2x00_mailbox_command.
kernel: [  870.470948] qla2xxx [0000:03:0b.0]-1806:3:
Prepare to issue mbox cmd=0x71.
kernel: [  870.471074] qla2xxx [0000:03:0b.0]-180f:3:
Going to unlock irq & waiting for interrupts. jiffies=100022d19.
kernel: [  870.472008] qla2xxx [0000:03:0b.0]-5800:3: Got
mbx completion. cmd=71.
kernel: [  870.472035] qla2xxx [0000:03:0b.0]-1814:3:
Cmd=71 completed.
kernel: [  870.472042] qla2xxx [0000:03:0b.0]-1821:3: Done
qla2x00_mailbox_command.
kernel: [  870.472074] qla2xxx [0000:03:0b.0]-1875:3: Done
qla2x00_fabric_logout.
kernel: [  870.472113] qla2xxx [0000:03:0b.0]-480e:3:
Relogin end.
kernel: [  870.472143] qla2xxx [0000:03:0b.0]-4800:3: DPC
handler sleeping.
kernel: [  870.500018] qla2xxx [0000:03:0b.0]-680b:3:
isp_abort_needed=0 loop_resync_needed=0 fcport_update_needed=0 start_dpc=1
reset_marker_needed=0
kernel: [  870.500026] qla2xxx [0000:03:0b.0]-680c:3:
beacon_blink_needed=0 isp_unrecoverable=0 fcoe_ctx_reset_needed=0
vp_dpc_needed=0 relogin_needed=0, host_ramp_down_needed=0
host_ramp_up_needed=0.
kernel: [  870.500038] qla2xxx [0000:03:0b.0]-4801:3: DPC
handler waking up.
kernel: [  870.500043] qla2xxx [0000:03:0b.0]-4802:3:
dpc_flags=0x0.
kernel: [  870.500054] qla2xxx [0000:03:0b.0]-2872:3:
Async-login - loopid=86 portid=c909e1 retries=139.
kernel: [  870.500059] qla2xxx [0000:03:0b.0]-4800:3: DPC
handler sleeping.
kernel: [  870.506268] qla2xxx [0000:03:0b.0]-5845:3:
Async-login complete - portid=c909e1 mbx1=6.

Additional Information

To enable full extended error logging for the qla2xxx driver take the following steps;

1. In "/etc/moprobe.conf.local" add the following line:

options qla2xxx ql2xextended_error_logging=0x7fffffff

2. If the driver is included in the initrd it is alse needed to run mkinitrd to have the changes included in the initrd before rebooting the server.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7013001
  • Creation Date: 07-Aug-2013
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center