3.19.15 crashes on MBP 8,1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Unknown
|
Unknown
|
|||
linux (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Vivid |
Invalid
|
High
|
Unassigned | ||
Wily |
Invalid
|
High
|
Unassigned |
Bug Description
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/
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=
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
NonfreeKernelMo
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: \boot\vmlinuz-
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
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.
dmi.board.
dmi.board.name: Mac-94245B3640C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBookPro8,1
dmi.product.
dmi.sys.vendor: Apple Inc.
description: | updated |
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.