Hide Forgot
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?
Neil, I use the default configuration of kernel and console for RHEL 6.3. If you need a setuped server for investigation, let me know. Thanks.
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 ====
thank you, I'll look at this in the morning.
ah, ok I see the problem, we need to backport (at least a few chunks of) 6708bb27bb2703da238f21f516034263348af5be. I'll have a build for test shortly
sorry, that commit should have been 35b2cdc4fea1f0d13e1602c07e62c797c9fe5ed4
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.
Patch(es) available on kernel-2.6.32-269.el6
no debug console log found on kernel -272. VERIFY.
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