Hi Yi, > > It should be triggered by the BUG_ON() in the function. Are you able to > > confirm it with netconsole or maybe even a frame buffer enabled console > > (it just shows more lines)? If this is the culprit, Tomas has been > > already working on it. But your BT coexist finding should help us > > reproducing the bug. > > http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703 > > so I was looking through the bug and switched some options around based > on wild assumptions made in that bug. The current settings are this: > > CONFIG_IWLWIFI=m > CONFIG_IWLCORE=m > # CONFIG_IWLWIFI_LEDS is not set > CONFIG_IWLWIFI_RFKILL=y > # CONFIG_IWLWIFI_DEBUG is not set > CONFIG_IWLAGN=m > # CONFIG_IWLAGN_SPECTRUM_MEASUREMENT is not set > # CONFIG_IWLAGN_LEDS is not set > CONFIG_IWL4965=y > # CONFIG_IWL5000 is not set > # CONFIG_IWL3945 is not set > > these seem to be stable and have no problems. I tried to crash the > kernel, but didn't manage it. > > Previously I had IWLWIFI_RFKILL off (wich was an oversight) and > IWLAGN_LEDS on. > > So my guess is either disabling RFKILL or enabling LEDS makes the > difference. This is another reason to not have all these config options, > because nobody find any bugs :( I take this back. It took a couple of hours, but it crashed again. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
