3.19.15 crashes on MBP 8,1

[monochromec]

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. Fan spins up audibly after 30 seconds of login screen display.

Kernel versions 3.16.0-33 and 3.16.0-34 work out of the box.
---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: root 731 F.... pommed
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=b3b2afbf-edea-40c5-9506-44b7f0cbf4d2
InstallationDate: Installed on 2014-04-26 (364 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: Apple Inc. MacBookPro8,1
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: \boot\vmlinuz-3.16.0-34-generic ro root=UUID=6a0139c1-488b-49e1-adee-a520c44dd9ab quiet splash initrd=boot\initrd.img-3.16.0-34-generic
ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-34-generic N/A
 linux-backports-modules-3.16.0-34-generic N/A
 linux-firmware 1.143
Tags: vivid
Uname: Linux 3.16.0-34-generic x86_64
UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/24/12
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP81.88Z.0047.B27.1201241646
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-94245B3640C91C81
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-94245B3640C91C81
dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
dmi.product.name: MacBookPro8,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1448458

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

apport information

[monochromec (monochromec)]

As I had removed 4.0rc7 already when running apport, here's the kernel log as far as I could retrieve from journalctl.

[monochromec (monochromec)]

Running apport from 3.16.0-34.

[Alberto Salvia Novella (es20490446e)]

Please:
  1. Report to <https://bugzilla.kernel.org/>.
  2. Paste the new report URL here.
  3. Set this bug status back to "confirmed".

Thank you.

[monochromec (monochromec)]

Here's the kernel.org URL:

https://bugzilla.kernel.org/show_bug.cgi?id=97251

[Alberto Salvia Novella (es20490446e)]

Many thanks.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc1-vivid/

[monochromec (monochromec)]

Downloaded and installed 4.1 as suggested. Unfortunately not working with similar symptoms. I attach the kernel log for reference.

[monochromec (monochromec)]

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-installation of the relevant broadcom-sta packages from the Vivid repo fixed this problem and reintroduced stability for the kernel once again.

BTW: The DKMS version of the package broadcom-sta-dkms doesn't compile on the Vivid stock kernel (3.19.0-15), due to header incompatibilities, I'll open a new bug report for this. Let me know if I should do the same on kernel.org.

[dino99 (9d9)]

Closed as per comment #25