I have a problem with my realtek wifi driver (rtl8192se): I want to send a bug report and want to gather some debug info. So i load the module with: modprobe -v rtl8192se debug=2 But there is no differense in output in dmesg / rsyslog. Version-Release number of selected component (if applicable): kernel-3.6.8-2.fc17.x86_64 How reproducible: 100% Steps to Reproduce: 1. Unload realtek module (modprobe -r -v rtl8192se) 2. Load realtek module with debug=2 (modprobe -v rtl8192se debug=2) 3. Check logs if any debug info is written Actual results: No debug information is written to the logs Expected results: Debug information written to logs Additional info: After loading module i check parameters by catting .. cat /sys/module/rtl8192se/parameters/debug 2 So it looks like the module has picked up the debug option... #modinfo rtl8192se filename: /lib/modules/3.6.9-2.fc17.x86_64/kernel/drivers/net/wireless/rtlwifi/rtl8192se/rtl8192se.ko firmware: rtlwifi/rtl8192sefw.bin description: Realtek 8192S/8191S 802.11n PCI wireless license: GPL author: Larry Finger <Larry.Finger> author: Realtek WlanFAE <wlanfae> author: lizhaoming <chaoming_li.cn> alias: pci:v000010ECd00008174sv*sd*bc*sc*i* alias: pci:v000010ECd00008173sv*sd*bc*sc*i* alias: pci:v000010ECd00008172sv*sd*bc*sc*i* alias: pci:v000010ECd00008171sv*sd*bc*sc*i* alias: pci:v000010ECd00008192sv*sd*bc*sc*i* depends: rtlwifi,mac80211 intree: Y vermagic: 3.6.9-2.fc17.x86_64 SMP mod_unload
From what I can tell, the module debug options depend on CONFIG_RTLWIFI_DEBUG being set. We don't have that option set for release kernels. We could look at enabling it for debug kernels though.
Ahh, that explains alot. We'll i'd like to be able to debug modules for trying to assist in submitting bug reports. And i know i've done it before for on fedora 16 for example. I'm guessing for now i need to build my own kernel for debugging this? /J
Moving this to rawhide for now. Need to make sure enabling the debug option doesn't cripple the driver's performance before we turn it on.
That option will not harm the performance. With the normal debug level of 0, only the emergency messages will be output, and there is only a little code executed when the various trace macros do not result in output. The driver is larger with debugging enabled, but the main effect is that the debugging level can be changed when the module is loaded.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Finally done in rawhide.