Bug 11476
Summary: | failure to associate after resume from suspend to ram | ||
---|---|---|---|
Product: | Networking | Reporter: | Michael S. Tsirkin (m.s.tsirkin) |
Component: | Wireless | Assignee: | Zhu Yi (yi.zhu) |
Status: | CLOSED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.25-rc5 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 7216, 11167 | ||
Attachments: |
my kernel .config
wpa_supplicant conf wpa_supplicant -dd log dmesg output (debug enabled) |
Description
Michael S. Tsirkin
2008-09-01 13:33:47 UTC
Created attachment 17565 [details]
my kernel .config
Created attachment 17566 [details]
wpa_supplicant conf
Reply-To: akpm@linux-foundation.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? Created attachment 17574 [details]
wpa_supplicant -dd log
Created attachment 17575 [details]
dmesg output (debug enabled)
On Mon, Sep 01, 2008 at 05:18:17PM -0700, Andrew Morton wrote: > > (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. Seems so. > > 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? iwl3945 Handled-By : Zhu Yi <yi.zhu@intel.com> Handled-By : Dan Williams <dcbw@redhat.com> Handled-By : Jouni Malinen <j@w1.fi> References : http://marc.info/?l=linux-kernel&m=122028529415108&w=4 Do you use hwcrypto? Can you try the other way around? > ------- Comment #8 from yi.zhu@intel.com 2008-09-07 23:30 ------- > Do you use hwcrypto? No > Can you try the other way around? just set hwcrypto=1, right? (In reply to comment #9) > just set hwcrypto=1, right? Yes. It looks like wpa_supplicant authentication timeouts 10 seconds after association. So the STA decides to disassociate itself. I'm not 100% sure it is wpa_supplicant authentication related. Could you configure the AP to open mode (and also change your wpa_supplicant.conf setting to reflect that) and retest? The reporter has not responded for almost two months. Closing. |