From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Yinghai Lu <yinghai@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: iwl3945 didn't survive after s2ram failure
Date: Thu, 5 Jan 2012 16:00:41 +0100 [thread overview]
Message-ID: <20120105150040.GE2222@redhat.com> (raw)
In-Reply-To: <20120105141913.GA3937@tiehlicka.suse.cz>
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
next prev parent reply other threads:[~2012-01-05 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 10:53 iwl3945 didn't survive after s2ram failure Michal Hocko
2012-01-03 10:34 ` Stanislaw Gruszka
2012-01-03 12:23 ` Stanislaw Gruszka
2012-01-03 13:07 ` Michal Hocko
2012-01-05 11:26 ` Stanislaw Gruszka
2012-01-05 12:20 ` Michal Hocko
2012-01-03 13:03 ` Michal Hocko
2012-01-05 11:07 ` Stanislaw Gruszka
2012-01-05 14:19 ` Michal Hocko
2012-01-05 14:34 ` Michal Hocko
2012-01-05 15:00 ` Stanislaw Gruszka [this message]
2012-01-05 16:25 ` Michal Hocko
2012-01-05 19:44 ` Yinghai Lu
2012-01-06 8:49 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120105150040.GE2222@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).