This bug was fixed in the package linux - 2.6.26-5.14
---
linux (2.6.26-5.14) intrepid; urgency=low
[ Ben Collins ]
* SAUCE: applesmc: Add MacBookAir
* build: Do not build ddeb unless we are on the buildd
* build: control: Consistency in arch fields.
* SAUCE: Update
Update:
It seems there is no bug at all.
I just downloaded the latest daily live CD (Kernel 2.6.26-5) and retested my
WLAN adapter on the PC of my house-mate. Well, i couldn't reproduce the error
on his PC.
Out of curiosity, i booted my pc with the live CD. Again, no OOPS occurred.
So my
The bug occurs when the driver tries to allocated some memory and fails
to do so, causing the oops. Maybe your system hit this error, which
generally 99.999% of the time does not happen.
I will put a fix in to catch this corner case anyway to make the driver
more robust.
Colin
--
rt2x00 oopses
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
rt2x00 oopses in 2.6.26-4, regression against 2.6.24-3
https://bugs.launchpad.net/bugs/249242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Colin King
(colin-king)
Status: Triaged = In Progress
--
rt2x00 oopses in 2.6.26-4, regression against 2.6.24-3
https://bugs.launchpad.net/bugs/249242
You received this bug notification because you are
Hi,
I've examined the OOPS and it occurs when the driver attempts to create
a workqueue and this fails - causing the code to free the workqueue,
which causes the OOPS.
I was wondering if this problem occurs every time, or was just a
transient problem caused by a lack of resources for just the
** Description changed:
I have an Edimax EW-7318UG wlan usb stick which works fine with
linux-2.6.26-3 and older.
Under 2.6.26-4 the kernel oopses after plugging in the stick
uname -r: 2.6.26-4-generic
Oops log:
[ 1144.232094] usb 3-5: new high speed USB device using ehci_hcd and
Hi Colin,
Yes, the bug is reproducible. (That's why i wrote this bug report in the first
place :) )
The new 2.6.26-5-generic kernel oopses as well. The new oops message doesn't
really differ from the original except for some different memory addresses.
(Well, at least i think those are memory
** Attachment added: lsmod 2.6.26-3
http://launchpadlibrarian.net/16457020/lsmod%202.6.26-3
--
rt2x00 oopses in 2.6.26-4, regression against 2.6.24-3
https://bugs.launchpad.net/bugs/249242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: lsmod 2.6.26-5 without blacklisting oops.txt
http://launchpadlibrarian.net/16457027/lsmod%202.6.26-5%20without%20blacklisting%20oops.txt
--
rt2x00 oopses in 2.6.26-4, regression against 2.6.24-3
https://bugs.launchpad.net/bugs/249242
You received this bug notification
** Changed in: linux (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
--
rt2x00 oopses in 2.6.26-4, regression against 2.6.24-3
https://bugs.launchpad.net/bugs/249242
You received this bug notification
** Tags added: 2.6.26-4
--
rt2x00 oopses in 2.6.26-4, regression against 2.6.24-3
https://bugs.launchpad.net/bugs/249242
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.com
12 matches
Mail list logo
