After resume, wireless connection is not restored with kernel 2.6.31-17-generic

[Robert Moerland]

Binary package hint: linux-image-2.6.31-17-generic

After the update of (X)ubuntu karmic to kernel 2.6.31-17-generic, my wireless connection is not restored anymore after a suspend/resume cycle. My wireless card is of the PCMCIA type, and when I pop it out and push it back into its slot, the wireless connection is restored. It's like this 10/10 times.

With kernel 2.6.31-16-generic, the wireless connection is restored automatically.

I've seen similar bug reports associated with Network Manager, but since it depends (in my case) on the kernel version, I don't suspect that Network Manager is the culprit.

BTW, I've tried ubuntu-bug, apport-bug, and apport-cli to get this bug reported, but all of them resulted in a Launchpad Oops. I don't know why. I'm gonna try to update this bug report with apport-collect and add some more info here. If it fails, I'll add my machine's specifications by hand.

Thanks for reading

[Robert Moerland (veel-mail)]

Blech, apport-collect crashes. Anyway, here's the output of lspci -vv

[Robert Moerland (veel-mail)]

This copy of syslog contains all the information of a (re)boot, suspend, resume, wireless card ejection (becaus of no connection) and reinsertion (connection is reestablished).

[Robert Moerland (veel-mail)]

Unfortunately, the issue still exists with with a kernel updated to 2.6.31-19.

[Jeremy Foshee (jeremyfoshee)]

Hi Robert,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 514675

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[Robert Moerland (veel-mail)]

It was an issue on my Karmic laptop, until I updated it to an alpha version of Lucid back in february. The issue seems to be resolved in that version. For me personally it's not an issue anymore.