From: Andrew Morton <akpm@linux-foundation.org>
To: linux-wireless@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>,
m.s.tsirkin@gmail.com
Subject: Re: [Bugme-new] [Bug 11476] New: failure to associate after resume from suspend to ram
Date: Mon, 1 Sep 2008 17:18:17 -0700 [thread overview]
Message-ID: <20080901171817.48743179.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-11476-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 1 Sep 2008 13:33:47 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=11476
>
> Summary: failure to associate after resume from suspend to ram
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.25-rc5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Wireless
> AssignedTo: networking_wireless@kernel-bugs.osdl.org
> ReportedBy: m.s.tsirkin@gmail.com
>
>
> Latest working kernel version: 2.6.25-rc4
> Earliest failing kernel version: 2.6.25-rc5
A very recent regression.
> Distribution: ubuntu gutsy
> Hardware Environment: T60p
> Software Environment: self-built kernel, .config attached
> Problem Description:
>
> Starting with 2.6.27-rc5, my T60p sometimes fails to associate
> with an access point after suspend to ram/resume.
>
> This does not seem to happen on 2.6.27-rc4.
>
> Steps to reproduce:
> suspend and resume several times.
> At some point the card fails to associate with
> the AP.
Which device driver is that machine using?
next parent reply other threads:[~2008-09-02 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11476-10286@http.bugzilla.kernel.org/>
2008-09-02 0:18 ` Andrew Morton [this message]
2008-09-02 12:59 ` [Bugme-new] [Bug 11476] New: failure to associate after resume from suspend to ram Michael S. Tsirkin
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=20080901171817.48743179.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.s.tsirkin@gmail.com \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.