On Tue, Dec 27, 2011 at 11:53:40AM +0100, Michal Hocko wrote: > my laptop died (due to drained batteries) while it was suspended to > RAM and the wireless didn't get back to life after I booted again. I wonder how we could kill hardware that way ... > Dmesg says: > cfg80211: Calling CRDA to update world regulatory domain > iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s > iwl3945: Copyright(c) 2003-2011 Intel Corporation > iwl3945 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 > iwl3945 0000:05:00.0: setting latency timer to 64 > iwl3945 0000:05:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF > iwl3945 0000:05:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF > iwl3945 0000:05:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF > iwl3945 0000:05:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF > iwl3945 0000:05:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF > iwl3945 0000:05:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF > iwl3945 0000:05:00.0: bad EEPROM signature,EEPROM_GP=0x00000007 > iwl3945 0000:05:00.0: EEPROM not found, EEPROM_GP=0xffffffff > iwl3945 0000:05:00.0: Unable to init EEPROM > iwl3945 0000:05:00.0: PCI INT A disabled > iwl3945: probe of 0000:05:00.0 failed with error -2 > > Is there anything I can do to resurrect it? No idea. Please provide logs with debug=0x47ffffff option. Did you try to totally power-off the laptop by removing battery (and power cable of course) ? If anything other will not help, is possible to rewrite eeprom, I don't know how to do this, but I know that tool for that exist: http://code.google.com/p/iwleeprom/ Stanislaw -- 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
