Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Once FCoE target got client/initiator conencted, the console will flooded with
===
ft_dump_cmd 2700002a 00009aba 000000bc 00000000
===
Quick guess, these debug log is from "tcm_fc" kernel module.
Please disabled it or use debugfs
Version-Release number of selected component (if applicable):
kernel -265
How reproducible:
100%
Steps to Reproduce:
1. Setup FCoE target:
===
yum install -y fcoe-taget-utils
service fcoe-target start
dd if=/dev/zero of=/tmp/fcoe-lun1 count=0 seek=10240 bs=1M
targetcli
/backstores/fileio create disk1 /tmp/fcoe-lun1 10240M
/tcm_fc/ create 20:00:00:1b:21:59:12:37
/tcm_fc/ create 20:00:00:1b:21:59:12:36
/tcm_fc/20:00:00:1b:21:59:12:37/luns/ create /backstores/fileio/disk1
/tcm_fc/20:00:00:1b:21:59:12:37/acls/ create 10:00:00:05:1e:8f:fa:da
/tcm_fc/20:00:00:1b:21:59:12:37/acls/ create 10:00:00:05:1e:8f:fa:db
/tcm_fc/20:00:00:1b:21:59:12:36/luns/ create /backstores/fileio/disk1
/tcm_fc/20:00:00:1b:21:59:12:36/acls/ create 10:00:00:05:1e:8f:fa:da
/tcm_fc/20:00:00:1b:21:59:12:36/acls/ create 10:00:00:05:1e:8f:fa:db
===
2. Connect FCoE initiator to this target.
3.
Actual results:
FCoE target Linux console flooded with "ft_dump_cmd 2700002a 00009aba 000000bc 00000000"
Expected results:
No debug output.
Additional info:
As fcoe target will get fully support in RHEL 6.3, requesting blocker for this bug.
ft_dump_cmd only uses pr_debug to dump commands out. Do you have dynamic debug enabled for this module, or do you have your console set to output debug level and high messages?
You shouldn't be getting these messages unless you've enabled dynamic debug or upped the console log level.
Yes, please setup the reproducer and send me the login info so that I can poke about with it.
Loaned two servers to you in beaker and they are well setuped, just take it and power it up.
* storageqe-13
FCoE target.
Intel ixgbe soft FCoE card.
Please use the command in comment #0 to setup FCoE target.
(I cannot save config)
* storageqe-14
FCoE initiator.
Brodcade bfa FCoE HBA. No software need. Just bfa kernel module.
Please execute these commands to rediscovery FCoE:
====
multipath -F
modprobe -r bfa
modprobe bfa
sleep 30
====
sorry, that commit should have been 35b2cdc4fea1f0d13e1602c07e62c797c9fe5ed4
Comment 10RHEL Program Management
2012-04-27 14:30:05 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2012-0862.html