As already suspected, a kernel upgrade as suggested by Joseph didn't
change anything wrt to the issue. It would be great if we can give more
specific advice rather than suggesting a vanilla kernel upgrade as a
"one cure for all".
@Joseph: When can the community expect an increase in severity as
re
This issue has been around my stock Ubuntu installation at least since
15.04 and continues to persist after the upgrade to 16.10. I have tried
all the workarounds of #1464917 without success.
I have my doubts that the kernel upgrade as suggested by Joseph will
remedy the situation but will give it
Hi Karen,
The location of the patch directory is as outlined above on 16.04. Please
double-check that you have installed the correct version of the package (this
should
be 6.30.223.248+bdcom). Otherwise, please post the contents of your /usr/src
directory to progress
this further.
--
You recei
Sorry, wrong kernel version. The correct version is 4.4.0-22-generic
which came as part of a normal update from the repo.
--
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/1585765
Title:
GP
Issue disappeared with latest 4.4.2 kernel update.
--
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/1585765
Title:
GPU driver problem with i915 driver
Status in linux package in Ubuntu:
Public bug reported:
First observed on freedesktop.org:
https://bugs.freedesktop.org/show_bug.cgi?id=94002
Steps to reproduce:
1) Suspend machine
2) Wake it back up
3) X11 crashes and takes E17 with it.
Environment:
- Kernel: 4.4.0-22-generic (stock)
- E17
- Otherwise: stock 16.04
ProblemType
In case you are running on problems with the NetworkManager (version
1.0.4-ubuntu5) after the official upgrade to Wily (messages "[platform
/nm-linux-platform.c:2782] do_change_link(): platform-linux: do-change-
link: failure changing link 4: No such device (31)" or similar) after
wakeup from a sus
Please note that the null pointer crash is only required for kernels >=
3.18. I can confirm that the patch is working on both unicorn and vivid
releases.
@Hugo: Just follow the instructions at the beginning of the bug report A
somewhat different approach using dkms is described in a duplicate bug
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 modul
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
#file-broadcom-sta-6-30-223-248
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
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 imm
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 co
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 Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1451789
Title:
bcmwl causes system freeze
Status in b
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 Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https
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 /etc/mo
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 15.04
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 Kernel
Packages, 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 Kernel
Packages, which is subscribed
Public bug reported:
I'll file a bugzilla port on kernel.org with the kernel logs and post
the reference here asap.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 [modified:
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
ProcVersionSignature: U
Duplicate of # 1424676
(https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1424676). See
other bug report for issue resolution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1447788
Tit
Got to the bottom of this: root cause was a heavily hacked version of
BCMWL (6.20) which I manually introduced in Trusty due to the severe
shortcomings / instability of both the FOSS b43 driver and the repo
version of Broadcoms hybrid driver (which I think was version 6.30 at
the time). A re-insta
Downloaded and installed 4.1 as suggested. Unfortunately not working
with similar symptoms. I attach the kernel log for reference.
** Attachment added: "boot.4.1.dmp"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448458/+attachment/4385911/+files/boot.4.1.dmp
--
You received this bug
Here's the kernel.org URL:
https://bugzilla.kernel.org/show_bug.cgi?id=97251
** Bug watch added: Linux Kernel Bug Tracker #97251
http://bugzilla.kernel.org/show_bug.cgi?id=97251
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification becau
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384014/+files/CRDA.txt
--
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/1448458
Ti
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384018/+files/Lspci.txt
--
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/1448458
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384025/+files/UdevDb.txt
--
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/1448458
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384023/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
As I had removed 4.0rc7 already when running apport, here's the kernel
log as far as I could retrieve from journalctl.
** Attachment added: "4.0rc kernel log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448458/+attachment/4384028/+files/4.0rc7
** Changed in: linux (Ubuntu)
St
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384015/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384017/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384020/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384016/+files/IwConfig.txt
--
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/14
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384019/+files/Lsusb.txt
--
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/1448458
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384026/+files/UdevLog.txt
--
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/1448
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384022/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384021/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384024/+files/RfKill.txt
--
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/1448458
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1448458/+attachment/4384027/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Running apport from 3.16.0-34.
--
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/1448458
Title:
3.19.15 crashes on MBP 8,1
Status in linux package in Ubuntu:
Confirmed
Bug description:
apport information
** Tags added: apport-collected vivid
** Description changed:
Installation of 3.19.15 as part of Vivid upgrade causes machine to
freeze after Lightdm has displayed login screen. Trackpad / keyboard /
USB mouse don't work, machine isn't visible on network. Same happens
Public bug reported:
Installation of 3.19.15 as part of Vivid upgrade causes machine to
freeze after Lightdm has displayed login screen. Trackpad / keyboard /
USB mouse don't work, machine isn't visible on network. Same happens
with kernel versions 4.0, 4.0rc7 from the Ubuntu mainline kernel repo.
Public bug reported:
Automatically generated BR
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 [modified:
usr/src/bcmwl-6.30.223.141+bdcom/Makefile
usr/src/bcmwl-6.30.223.141+bdcom/src/wl/sys/wl_dbg.h]
Uname: Linux 3.14.1-031401-generic
After giving 3.13.0-031300rc3-generic a spin for the last few days I
haven't been able to reproduce the problem. As this seems to be fixed
upstream, I'm tagging this bug "kernel-fixed-upstream" as requested.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you a
Also occurs in 3.11.0-13.
I will give 3.13 and 3.12 a spin as soon as I get around to doing it and
report result back and tag this bug accordingly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
First observed on a Macbook Pro 8,1 running Saucy.
Steps to reproduce:
1. Close laptop lid
2. Open laptop lid -> blank screen -> frozen OS.
3. Only alternative: hard reboot via power button.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-13-generic
Problem is gone after a complete fresh install of Saucy Salamander on
the same machine.
I suspect a problem between the b43 kernel driver and the proprietary
firmware as I noticed a different URL when running
firmware-b43-installer as part of the wireless installation. The
previous installation of
PS: Tagging this as requested.
--
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/1236937
Title:
wifi connection drop (b43 eapol timeout)
Status in “linux” package in Ubuntu:
Incomplete
Took Saucy 3.12 RC4 for a spin. Unfortunately, the symptoms remain the
same. Seems to be a B43 issue as all devices (a few Droids (Gingerbread
+ ICS), Window machines and even the OSX driver on the same machine)
handled a second re-keying request the way it is supposed to be: when
getting a second
PS: same dependency issue surfaced with the Saucy RC4 kernel you
mentioned in your post.
--
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/1236937
Title:
wifi connection drop (b43 eapol tim
Hi Joseph,
Thanks for the quick reply!
Strange error: Just tried to install a nightly DRM build (image +
headers) and encountered an odd dependency when I tried to install the
header:
dpkg -I linux-
headers-3.12.0-994-generic_3.12.0-994.201310080405_amd64.deb
produces the following output:
ne
Public bug reported:
Experiencing problems with a BMC4331 wlan chip controlled by the b43
kernel driver with the following environment:
- Stock raring with b43 wifi driver on a 3.0.8-31 generic kernel on a Macbook
Pro 8,1 (although this problem has been around since kernel version 3.2),
- Route
52 matches
Mail list logo
