kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Pascal Desroches, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal (Applications->Accessories->Terminal), as it will
automatically gather and attach updated debug information to this
report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** This bug is no longer a duplicate of bug 1021904
   8086:4222 Sometimes Wi-Fi does not work after resume from suspend -- Intel PRO/Wireless 3945ABG iwl3945

** Tags added: karmic lucid needs-kernel-logs needs-upstream-testing
regression-potential

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/702344

Title:
  Network disconnected after "suspend" (Intel 3945ABG), reboot only way
  to get it back on

Status in “linux” package in Ubuntu:
  Incomplete
Status in Fedora:
  Invalid

Bug description:
  Happens about 50 % of the time when resuming from "suspend" (or
  "hibernate" but I don't use this). Unable to restart wireless, the
  only option is to reboot. Resuming from "suspend" might work perfectly
  3 times in a row, only then to get the next 4 with network
  disconnected...

  Other users have had similar problems, but that was regarding power
  management (the problem didn't occur when plugged in, only when on
  battery). My problem occurs when plugged in.

  I used "Aport" (or something) but I did this after a suspend session,
  so I wasn't connected to the internet and therefore I was unable to
  send it. I also tried to copy the huge amount of information it gave
  but that didn't seem to be possible. However, I did create the 4
  documents listed on this page. I'll try to find a way to attach them
  to this text.

  Same problem with 10.04. As far as I can remember, it also occurred
  with 9.10. Also, I've tried the last 2 or 3 versions of Xubuntu and
  Linux Mint, and the latest version of Fedora, and the same happens. It
  happens with 32- and 64-bit versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/702344/+subscriptions