Clone of https://bugzilla.redhat.com/show_bug.cgi?id=466441
While running MRG Realtime kernel 18.104.22.168-149.el5rt on a Dell PowerEdge 2950 system, customer see the following messages in dmesg:
mptctldrivers/message/fusion/mptctl.c::mptctl_ioctl() @596 - ioc0 not found!
mptctldrivers/message/fusion/mptctl.c::mptctl_ioctl() @596 - ioc1 not found!
mptctldrivers/message/fusion/mptctl.c::mptctl_ioctl() @596 - ioc30 not found!
mptctldrivers/message/fusion/mptctl.c::mptctl_ioctl() @596 - ioc31 not found!
If he runs RHEL 5.5 kernel 2.6.18-194.3.1.el5, no such messages are seen.
* How reproducible: Run MRG Realtime kernel 22.214.171.124-149.el5rt on a Dell PowerEdge 2950 system and check the dmesg.
* Steps to Reproduce: As above.
* Actual results: The above "iocX not found" messages are seen.
* Expected results: No such message should be seen.
* Additional info:
- mptbase module version with RHEL 5.5 (2.6.18-194.el5): 3.04.13rh
As per https://bugzilla.redhat.com/show_bug.cgi?id=466441, the messages seems to be due to verbose debug information and seems to have been fixed on RHEL 5.4. The mptctl.c of kernel 2.6.18-164.el5 shows the following:
595 printk(KERN_DEBUG MYNAM "%s::mptctl_ioctl() @%d - ioc%d not found!\n",
596 __FILE__, __LINE__, iocnumX);
- mptbase module version with RHEL 5.4 (2.6.18-164.el5): 3.04.07rh
- mptbase module version with RHEL MRG-R (126.96.36.199-149.el5rt): 3.04.06
Patch bz601210-Fusion-MPT-misc-dev-driver-too-verbose.patch added to kernel -159 patch queue.
Verified by code review. Found bz601210-Fusion-MPT-misc-dev-driver-too-verbose.patch implemented in kernel-rt-188.8.131.52-160.src.rpm. Double checked that DMPT_DEBUG_IOCTL was not #define'd in the source code or enabled via other debug flags in the kernel config.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
surrounded a printk in the fusion mpt driver with debugging ifdefs to reduce irritating console output
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.