On Tue, May 10, 2011 at 11:36 AM, Colin Guthrie <mageia@xxxxxxxxxxxxxx> wrote: > 'Twas brillig, and Matthew Garrett at 09/05/11 18:11 did gyre and gimble: >> On Mon, May 09, 2011 at 06:09:27PM +0100, Colin Guthrie wrote: >> >>> Just a quick (non-compile) followup from my last email... blacklisting >>> the dell-laptop module works around the issue, so I think the commit >>> previously mentioned is indeed the culprit (as it's the only recent >>> commit and does fiddle with the rfkill stuff). >>> >>> Not sure what the best track forward is, but it's certainly a >>> regression, so should probably be fixed or reverted until a more >>> complete fix is found. >> >> If you can confirm that with a build then I'll do that. > > ACK. Reverting that commit and unblacklisting the dell_laptop module > restores the previous, working functionality. I've flipped rfkill a few > times and it's always worked fine. > May I have the model of your Dell laptop? dell_latop has a debugfs node in /sys/kernel/debug/dell_latop/rfkill, can you attach the logs at both the moment when the radio devices are enabled and disabled? the output of the command `rfkill list` at both moments will helpful too. In my experience that different models of Dell laptop may have different reaction/behaviour on the rfkill handling. Reverting the patch may make your laptop working, but can cause others non-working. It should make sense and be appreciated that you attach more debug information for investigation on the bug. Thanks, -kengyu -- 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
