*** This bug is a duplicate of bug 1415880 ***
https://bugs.launchpad.net/bugs/1415880
** This bug has been marked a duplicate of bug 1415880
14e4:4365 bcmwl-kernel source: fix for null pointer crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could we please fast-track this solution? My laptop is crashing every
other hour because of it :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451789
Title:
bcmwl causes system freeze
To manage
Moritz,
Instead of waiting for the upstream packagers to fix this, try one of
the following:
- Use a pre-3.18 kernel. 3.16.33 and 3.16.34 are quite stable,
- Install the bmcwl package (version 6.30.233.248) and apply the patch manually
in the /usr/src hierarchy which dkms uses to build the
Thanks for your feedback, Ralph - much appreciated!
I've found a solution for this bug. When research recent changes to the
WL module source code, I came across a Fedora patch for kernel versions
3.18 and later (https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6
The attachment Patch for kernel versions 3.18 and later seems to be a
patch. If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user
Sure, happy to oblige:
- Kernel: 3.19.0-16-generic
- bcmwl-kernel-source: 6.30.223.248+bdcom-0ubuntu2
- TP-Link router:
+ Hardware Version: WR841N v8 000
+ Firmware Version: 3.13.33 Build 130506 Rel.48660n - no modifications
whatsoever
Hope that helps. (Note that in the meantime I
Hey Ralph,
Thanks for your feedback. While the issue is in the process of being
narrowed down - would it be possible for you to supply the following
information:
- Version of the kernel you're using alongside the distro version,
- Version of the wl module (you can get this with apt-cache showpkg
** Changed in: bcmwl (Ubuntu)
Importance: Undecided = High
** Changed in: bcmwl (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451789
Title:
bcmwl causes
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=97881
Importance: Unknown
Status: Unknown
** Changed in: bcmwl (Ubuntu)
Status: Confirmed = Triaged
** No longer affects: linux
--
You received this bug notification because you are a member of Ubuntu
I was able to reproduce the issue on a stock Jessie install on a Vostro
1320 (featuring a BCM 3412). Kernel versions after 3.17 (including
3.18.12, 3.19.0, 3.19.6 and 4.0.1, at least these are the ones I checked
myself) seem to have an issue which causes the kernel to lock up.
BCM4331 causes an
Some additional comments:
My machine is a Dell XPS 13 using the BCM 4360 chip. The driver works
perfectly fine with my Linksys wireless router (b/g mode). When I
connect to my TP-Link router, however, authentication works fine, but
sending and receiving additional packets nearly instantly
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451789
Title:
Kernel maintainer closed issue, referring back to Broadcom. I guess that
leaves the responsibility with the package maintainer. As b43 is still
showing the group temporal key issue rendering it essentially unusable
in the current kernel line (confirmed on 3.19 and 4.0.1), it would be
great if we
Driver bug confirmed.
I'll open bugzilla bug report on kernel.org with the details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451789
Title:
bcmwl causes system freeze
To manage notifications
Bugzilla bug: https://bugzilla.kernel.org/show_bug.cgi?id=97881
** Bug watch added: Linux Kernel Bug Tracker #97881
http://bugzilla.kernel.org/show_bug.cgi?id=97881
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As a kludge (I wouldn't go as far as calling it a proper workaround),
it's possible to substitute the wl LKM with the FOSS b43 LKM.
Assuming both b43-fwcutter and firmware-b43-installer (/ b43-legacy-
installer) are installed, you can use a slightly modified version of
boradcom-sta.conf in
When trying to reproduce the issue, I noticed that I could log into the
GUI as created by the session manager (lightdm) if I left the cable in
the onboard NIC. That means the system does go ahead when it can at
least create one network connection other than lo (which is the default
auto in my
Kernel log with cable attached to NIC.
** Attachment added: 3.19.0-15.nic.dmp
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1451789/+attachment/4391330/+files/3.19.0-15.nic.dmp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Needless to say, the above information doesn't reflect the system state
as I had to remove the wl kernel module in order to file this issue.
Watch out for the kernel logs on bugzilla.kernel.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
19 matches
Mail list logo
