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 for Android: free password hash cracker in your pocket

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

Message-ID: <20120105150040.GE2222@redhat.com>
Date:	Thu, 5 Jan 2012 16:00:41 +0100
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Michal Hocko <mhocko@...e.cz>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-wireless@...r.kernel.org
Subject: Re: iwl3945 didn't survive after s2ram failure

On Thu, Jan 05, 2012 at 03:19:13PM +0100, Michal Hocko wrote:
> 
> OK, so I have tried to boot with pcie_aspm=off and the wireless
> resurrect. The I found out that I booted into 3.2 rather than 3.2-rc6 so
> I retested with the original kernel and guess what, yes it reported the
> same problem as before (with or without parameter). 
> So I have tried to retest with few kernels (3.2.0-rc5,
> 3.2.0-rc6-00005-ga36bfdd, 3.2.0-rc7-00083-g115e8e7 and 3.2.0) that I
> still had on my machine and 3.2.0-rc6-00005-ga36bfdd seems to be the
> only affected one.
> There doesn't seem to be any obvious difference wrt. the driver in the
> logs (attached).
> 
> Looking in the history it seems that 497f16f2 [pci: Fix hotplug of
> Express Module with pci bridges] might be related.

>From the changelog of that commit: "I noticed that the bridges get
assigned but do not get enabled", that looks like the problem we had
seen.

Anyway there is noting to do here, we have bug in 3.2-rc6 fixed in
3.2-rc7.

Thanks
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/