kernel-packages team mailing list archive

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

slumbergod, 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? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, 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

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

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.

** 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/493720

Title:
  Can't reconnect to wireless network after upgrade to 1.25 unless I
  reboot

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: linux-firmware

  With linux-firmware 1.24, I can reconnect to a wireless network by reloading the following wireless kernel modules:
  iwl3945, iwlcore, and mac80211. It isn't possible for me to reconnect unless I reload these modules with modprobe (though even having to do this is inconvenient).

  Following an upgrade to linux-firmware 1.25, a reboot becomes
  mandatory for reconnection i.e. reloading the above drivers no longer
  works.

  As soon as I downgrade to 1.24 I can reconnect again after manually
  reloading the drivers. This weekend I wondered why it stopped working
  again and it turned out I had forgot to lock the version at 1.24 and
  it had been automatically upgrades back to 1.25 in a subsequent system
  update. Back at 1.24 again and it works again.

  (No idea why I have to keep reloading kernel drivers to refresh the
  wireless stack though. It is frustrating but it is certainly better
  than rebooting everytime.)

  Intel 3945 wireless chipset.
  Xubuntu Karmic

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