[intrepid] iwl3945 not working after resume from hibernation

Bug #250667 reported by Martin Pool
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

On a current installation of Intrepid on a thinkpad x61s, the iwl3945 wireless device works well, except that after resuming from hibernation it can see networks but not associate to them (as shown in the gnome nm applet). Removing and reinstall the module does not help, neither does restarting nm or toggling the radio enable switch.

Linux lithe 2.6.26-4-generic #1 SMP Mon Jul 14 18:39:53 UTC 2008 i686 GNU/Linux

Tags: cft-2.6.27
Revision history for this message
Martin Pool (mbp) wrote :
Revision history for this message
Martin Pool (mbp) wrote :

This might be a dupe of bug 25614?

Revision history for this message
Martin Pool (mbp) wrote :

Or possibly bug 162654.

Restarting init.d/networking does not fix it as was suggested there.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 250667] Re: [intrepid] iwl3945 not working after resume from hibernation

On Wed, Jul 23, 2008 at 3:02 AM, Brian Murray <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This bug did not have a package associated with it, which
> is important for ensuring that it gets looked at by the proper
> developers. You can learn more about finding the right package at
> https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this
> bug as a bug in linux.
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux

I did try to complete the package field by choosing
linux-image-2.6.24-4 from the search window. However, when I tried to
submit the bug it said "no such package". Is this a Launchpad bug?

--
Martin <http://launchpad.net/~mbp/>

Revision history for this message
Brian Murray (brian-murray) wrote :

Perhaps, the package name in Launchpad has changed from linux-source-2.6.24 to just linux. This will be true for the kernel going forward. Maybe there should be aliases for the package names that direct you to linux.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
dwp0980 (dwp0980) wrote :

Happy to report that (so far) my iwl3945 ABG in Sony Vaio laptop does not have any problems. I was experiencing similar problems to the original bug reporter when laptop was put in sleep mode (with the lip shut). This doesn't seem to happen. I have installed intrepid Alpha5 and after some initial problems with nm-applet everything seems to be fine now.

Revision history for this message
Martin Pool (mbp) wrote :

I can't suspend or hibernate my X61s with current Intrepid therefore
can't test this.

Revision history for this message
Martin Pool (mbp) wrote :

Actually, I can hibernate and resume from the applet, but not from the hotkey. Wireless networking is working after I come back, so this does seem to be fixed. Well done.

Revision history for this message
hendrikwout (hendrikwout) wrote :

Most of the time, wireless works when resuming from suspend mode. But in some case it doesn't (i don't see any acces point and can't connect to it). Reloading the iwl3945-module doesn't get the wireless up again.

I haven't tested resuming from hibernation.

Revision history for this message
Lincoln Stein (lstein) wrote :

I recently installed linux-image-2.6.27-5-generic on top of my Hardy system to see if it would solve problems I have been having with kernel panics when rmmod-ing iwl3945. Sorry to say that 2.6.27 causes a different sort of crash on suspend/resume cycles. The system wakes up from sleep, but as soon as it associates with the access point, the keyboard becomes unresponsive and other aspects of the UI (such as launching new applications) hang - perhaps because the hard disk in inaccessible?

The same behavior can be reproduced by rmmoding and modprobing iwl3945 a couple of times -- the freeze occurs on the association after the SECOND rmmod/modprobe cycle.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Martin,

Thanks for testing and the feedback. Since you are the original bug reporter I'm going to mark this bug as "Fix Released". Regarding the hotkey issue, it sounds like you'll want to take a look at bug 267682 which was also recently fixed.

@hendrikwout and @Lincoln Stein - it seems you both are experiencing slightly different bugs than what Martin originally reported. It is helpful to the kernel team if bug reports target one specific issue against a specific set of hardware. If you could please open a new bug report regarding the issue you are still seeing that would be great. Thanks.

Changed in linux:
status: Triaged → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.