linux-backports-modules-2.6.27 (2.6.27-14.16) intrepid-proposed; urgency=low
.
[Upstream Kernel Changes]
.
* wiphy_update_regulatory: avoid beacons and notifiers if no
regulatory_domain
- LP: #337929
** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Status: Fix Comm
** Description changed:
+ SRU justification:
+
+ Impact: Oops in cf80211 when specifying ieee80211_regdom=EU. A pointer
+ is used before valid, leading to NULL pointer dereference.
+
+ Fix: Backport of relevant changes from recent compat-wireless packages.
+
+ Testcase: see below
+
+ ---
+
Committed for Andy after user feedback
** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Status: Incomplete => Fix Committed
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member o
Tested, it works. :-)
(My AAO is currently dual-booting Jaunty and Intrepid - if you need
further testing done, let me know.)
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bu
Has anyone be able to test the intrepid versions of this fix? If you
could and report back here that would help.
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok for Intrepid it is going to be safer to fix the issue in the version
we already have in LBM for Intrepid. I believe we have identified the
issue there and produced a patch for that release. I have applied this
patch to the latest version of LBM and produced some test packages. If
those of you
** Changed in: linux-backports-modules-2.6.28 (Ubuntu)
Status: Fix Committed => Fix Released
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package linux-backports-modules-2.6.28 -
2.6.28-11.12
---
linux-backports-modules-2.6.28 (2.6.28-11.12) jaunty; urgency=low
[Tim Gardner]
* Update wireless-testing/compat-wireless to master-2009-03-24
-LP: #329975
-- Tim Gardner Tue, 24 Mar 2009 1
CRDA issue reported as bug 349001.
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Status: Incomplete => In Progress
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
@maxb -- agree completly, the fact that the main kernel is using CRDA
and the LBM is not should be the subject of a separate bug. Will close
off the Jaunty task on this one as you suggest, and get the Intrepid one
sorted out.
** Changed in: linux-backports-modules-2.6.28 (Ubuntu)
Status: I
OK, running Andy's deb, I see his printk, and things work (no oops).
Running lbm updated to master-2009-03-24 from ubuntu-jaunty-lbm.git
without Andy's patch, things *also* work.
Regarding the comments on the the CRDA framework, I've now shifted my
home AP to channel 13.
Using the master-2009-03
Ok, linux-backports-modules-2.6.28 packages with the patch alluded to in
my previous posting are now available at the URL below. If those of you
who can reproduce this could test this out and report back that would
help a lot. Packages are here:
http://people.ubuntu.com/~apw/lp337929-jaunty/
We are seeing panics coming out of wiphy_update_regulatory() from LBM on
both Jaunty and Intrepid. These two carry the same basic code for the
wireless stack. Sample stack trace as here:
[ 398.693189] BUG: unable to handle kernel NULL pointer dereference at
0004
[ 398.693206] IP:
@maxb -- you may get some messages about which frequencies are being
allowed i believe, in dmesg. But the only concrete way to check is to
find an AP on those channels and test there.
Should you still not be able to connect then there is a new way to
specifiy where you are:
iw reg
iw re
How do I test? Do I have to reconfigure my AP to channel 12/13 or is
there an easier way?
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I suspect very much that this is related to the removal of this option
as a result of moving to the new CRDA framework. This variable should
not be required on Jaunty. Could you test to confirm you do not require
it? I will investigate why it causes an ooops.
--
ieee80211_regdom=EU now causes
** Changed in: linux-backports-modules-2.6.28 (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft
(apw)
Status: Triaged => In Progress
** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) =>
Confirmed still a problem with -11.11.
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
** Tags added: regression-potential
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Hi Max,
Care to just confirm this remains with the 2.6.28-11.11 version of
linux-backports-modules. The reason I ask is I see 2.6.28-11.11 was
most recently updated to the 2009-03-17 compat-wireless stack -
https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.28
. I'll bring thi
** Changed in: linux-backports-modules-2.6.28 (Ubuntu)
Status: New => Triaged
** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Status: New => Triaged
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notifi
** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux-backports-modules-2.6.28 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Canonical
Interestingly (?) on Intrepid the issue prevents the system from booting
- I didn't notice this on Jaunty. Specifically, udev runs modprobe,
which exits abnormally, which causes udev to get stuck / halt.
I blacklisted atk5k to allow the system to boot, then manually modprobed
it. modprobe died wit
Bugtask added for intrepid's lbm, problem observed with lbm 2.6.27-14
(intrepid-proposed) too. Does not occur with 2.6.27-11 though. Therefore
tagging regression-proposed.
** Also affects: linux-backports-modules-2.6.27 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: regressio
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/23440773/Dependencies.txt
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attaching dmesg - BUG occurs at line 647
** Attachment added: "dmesg.0"
http://launchpadlibrarian.net/23440809/dmesg.0
--
ieee80211_regdom=EU now causes oops after latest update
https://bugs.launchpad.net/bugs/337929
You received this bug notification because you are a member of Ubuntu
Bugs,
27 matches
Mail list logo
