Here the driver is trying to remove the keys from the device but withrfkill enabled it is not able to do so.

> usb 3-1: USB disconnect, address 2> [enable]> usb 3-1: new full speed USB device using uhci_hcd and address 3> usb 3-1: configuration #1 chosen from 1 choice> > 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"):

yes, as Johannes mentioned this is a new required step to get networkingback up after rfkill state changes.

> 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.

It would be nice to get this from the upper layers, but the device cando it also as it is getting the interrupt.

Could you please try the patch below? It will not send command to devicewhen rfkill is enabled and it will also print messages indicating thatrfkill state changed.