From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008042803 Red Hat/3.0b5-0.beta5.6.el5 Firefox/3.0b5 Description of problem: I have a Lenovo ThinkPad T61 with Intel Wireless card Intel Pro/Wireless 4965 abgn. This hardware causes the module iwl4965 and mac80211 to be loaded, along with a module called "compat". This "compat" module causes the following message in dmesg: kernel: compat: module license 'unspecified' taints kernel. If I disable the wireless card in the BIOS, this message goes away, and the kernel is not tainted. I found this while running hts for certification. Version-Release number of selected component (if applicable): kernel-2.6.18-92.el5 How reproducible: Always Steps to Reproduce: 1. Load the 5.2 GMC code. Deselect Virtualization. Take default options. 2. Boot system. 3. Loot at dmesg | grep taint -- the module compat taints the kernel. Actual Results: Kernel is tainted. Expected Results: Kernel should not be tainted by this module. Additional info:
Created attachment 305143 [details] /var/log/messages file My /var/log/messages file -- note that on the last boot, the kernel tainted message goes away -- this is because I prevented the iwlwifi module from loading by disabling it in the BIOS.
Created attachment 305407 [details] jwltest-mac80211-compat-module-license.patch
Above patch is in the test kernels here: http://people.redhat.com/linville/kernels/rhel5/ Do they resolve the issue?
John, howdy, Would this patch be possible to be added into the RHEL5.2 GA? This bug would affect our hardware certification process on RHEL5.2 GA. Thanks, /Xu
I think it is too late for 5.2 -- maybe Don will contradict me.
It is too late for 5.2. You will have to go through SEG to get this into 5.2.z
New test kernels with an alternative fix are here: http://people.redhat.com/linville/kernels/rhel5/ Please give them a try and verify that the problem disappears...thanks!
in kernel-2.6.18-107.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
Partners, this bug should be fixed in the latest RHEL 5.3 Snapshot. We believe that you have some interest in its correct functionality, so we're making a friendly request to send us some testing feedback. If you have a chance to test it, please share with us your findings. If you have successfully VERIFIED the fix, please add PartnerVerified to the Bugzilla keywords, along with a description of the results. Thanks!
~~ Snapshot 6 is out ~~ Partners, please test and let us know if this bug has been fixed. Add PartnerVerified keyword if everything works as expected. For any new issues encountered, CLONE this bug and report the issues in the new bug.
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. http://rhn.redhat.com/errata/RHSA-2009-0225.html