iwlagn crashes kernel with NetworkManager after resuming from Suspend to RAM

[Muelli]

My Ubuntu with kernel-2.6.27-7 crashes with an enabled NetworkManager after Resuming from Suspend To RAM.

To be clear: It doesn't crash immediatly, but it shows Oopses in dmesg and the system behaves strangely: Processes can't be started or terminated, shutdown doesn't work, ...

I don't experience this everytime, but roughly every second attempt to resume fails.

I'll attach two dmesg output from different suspend-resume cycles.

Please let me know if I can provide any information.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
Package: linux-image 2.6.27.7.11
SourcePackage: linux-meta
Uname: Linux 2.6.27-7-generic x86_64

[Micha Moskovic (micha-mosk)]

Same here, using an intel 4965 wireless card on an amd64 distro.
I tested it with the linux-2.6.27-10-generic kernel from intrepid-proposed, and the driver still crashes randomly after resuming from suspend to RAM.

[Leann Ogasawara (leannogasawara)]

Hi Muelli,

Can you try a few things first. . . Can you install the "linux-backports-modules-intrepid" package to see if it helps. It contains an updated compat-wireless stack. If that still doesn't help, would you be willing to test the latest pre-release of Jaunty 9.04 (currently Alpha4). It contains an updated 2.6.28 based kernel. It would be good to know if this issue remains there as well. You should be able to test suspend via a LiveCD. Please let us know your results. Also, I'm going to go ahead and close the "linux-meta (Ubuntu)" task of this bug report as the "linxu (Ubuntu)" task is the correct one and sufficient for tracking this issue. Thanks.

[kernel-janitor (kernel-janitor)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]