linux-kernel - Re: iwl3945 didn't survive after s2ram failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120103122311.GC3391@redhat.com>
Date:	Tue, 3 Jan 2012 13:23:12 +0100
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Michal Hocko <mhocko@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-wireless@...r.kernel.org
Subject: Re: iwl3945 didn't survive after s2ram failure

On Tue, Jan 03, 2012 at 11:34:58AM +0100, Stanislaw Gruszka wrote:
> 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/
Actually I do not think we overwrite eeprom, seems problem is at pci-e
bus level. Simply we can not communicate with device through pci-e bus.
That is kind a silly, but you can check if removing cart from slot
and put it back again (assuring it correctly connected) helps.
 
Stanislaw 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/