Now that I took a closer look... > I've tried .31-rc1 on my HP 2510p notebook and noticed a problem when > using the hardware rf kill switch. > But with 2.6.31 I get this: > [disable] > wlan0: deauthenticating by local choice (reason=3) > iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 > mac80211-phy0: failed to remove key (0, 00:14:c1:38:e5:15) from hardware (-5) > iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 > mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5) > usb 3-1: USB disconnect, address 2 These errors are a driver problem. > [enable] > usb 3-1: new full speed USB device using uhci_hcd and address 3 > usb 3-1: configuration #1 chosen from 1 choice That is completely unrelated. You plugged in a USB device too :) > A lot uglier with those errors. And after that I have to run ifdown/ifup > before networking is up again (ifup only does not work as it will complain > "interface already configured"): And that's actually expected, and/or a bug in the debian networking scripts. (You can trigger the same problem by doing ifup wlan0 ip link set wlan0 down ifup wlan0 -> error) To get your network connection back automatically we will require changes to userland tools to listen to rfkill events. > BTW, would it make sense to bring back the first two lines shown with .30 > (or at least the first one): > iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On: > Kill switch must be turned off for wireless networking to work. > IMHO it's good to register the reason for the disconnect. I guess something like that could be added to cfg80211: phy0: taking interfaces down due to rfkill johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
