>-----Original Message----- >From: ipw3945-devel-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:ipw3945-devel- >bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of drago01 >Sent: Tuesday, January 22, 2008 10:05 PM >To: ipw3945-devel >Cc: Cahill, Ben M; Zhu, Yi; linux-wireless >Subject: [ipw3945-devel] iwl3945 rfkill regression > >Hi, >Hi recent updates to wireless-2.6 / iwlwifi (1.2.22->1.2.23) broke >rfkill in a weird way for me. >What happens: >When I switch off the card using the hw rfkill switch (while >acciotated) I get this in dmesg: >iwl3945: Radio Frequency Kill Switch is On: >Kill switch must be turned off for wireless networking to work. >wlan0: disassociate(reason=3) >wlan0: disassociate(reason=3) >iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC >iwl3945: MAC is in deep sleep! >iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC >iwl3945: MAC is in deep sleep! >iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC >iwl3945: MAC is in deep sleep! >iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC >ACPI: PCI interrupt for device 0000:07:00.0 disabled > >Notice the last line (interupt gets disabled). When this happens there >is no way to get the card back up other then reloading the module. >Earlier version (1.2.22) was working fine I could switch the switch >on/off without having an suchs kind of issues. >I have not tryed to find out which patch broke it yet, but I suspect >the suspend / resume rfkill fix mighr be the culprit. > >If any more tests / information is needed feel free to ask. > I believe it's delaying uCode load to mac_start - still need to be polished. Tomas --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. - 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
