← Back to team overview

kernel-packages team mailing list archive

Re: [Bug 1497716] Re: MacBookPro12, 1 Unable to suspend


Hi, Christopher.

I tested the bug with:
kernel linux 4.3.0-040300rc1-generic and it has the problem.
kernel linux 3.19.8-031908 doesn't have the problem.

Ram on

On Sun, Sep 20, 2015 at 5:49 PM, Christopher M. Penalver <
christopher.m.penalver@xxxxxxxxx> wrote:

> ramon, unfortunately bugzilla is the wrong venue for this issue. Also,
> as this report doesn't have enough information yet, it's not yet ready
> to upstream at this point.
> Despite this, the next step is to fully commit bisect from kernel 4.1 to
> 4.2 in order to identify the last good kernel commit, followed
> immediately by the first bad one. This will allow for a more expedited
> analysis of the root cause of your issue. Could you please do this
> following https://wiki.ubuntu.com/Kernel/KernelBisection ?
> Please note, finding adjacent kernel versions is not fully commit
> bisecting.
> Thank you for your understanding.
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
> ** Tags added: needs-bisect
> ** No longer affects: linux (Ubuntu)
> ** Project changed: linux => linux (Ubuntu)
> ** Changed in: linux (Ubuntu)
>        Status: New => Incomplete
> ** Changed in: linux (Ubuntu)
>    Importance: Undecided => Medium
> ** Tags removed: asked-to-upstream
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1497716
> Title:
>   MacBookPro12,1 Unable to suspend
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497716/+subscriptions

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  MacBookPro12,1 Unable to suspend

Status in linux package in Ubuntu:

Bug description:

  Ubuntu 1510 + kubuntu 
  Linux 4.2.0-10-generic #12-Ubuntu SMP Tue Sep 15 19:43:01 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  System can't get into standby mode. Screen flickered, shut down for a few seconds and then go on.
  After failed standby attempt  no network until restart
  Display is not clear when using compositing.

  Everthing is working good under vmlinuz-4.1.0-3-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-10-generic 4.2.0-10.12
  ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
   /dev/snd/controlC0:  ram        1855 F.... pulseaudio
   /dev/snd/controlC1:  ram        1855 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Sun Sep 20 13:48:14 2015
  HibernationDevice: RESUME=UUID=52f0fdb1-338f-44a5-a25f-b57d104f33ea
  InstallationDate: Installed on 2015-08-25 (25 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic root=UUID=90c123a3-e234-4509-b857-14ba43c70955 ro vga=0x0364
   linux-restricted-modules-4.2.0-10-generic N/A
   linux-backports-modules-4.2.0-10-generic  N/A
   linux-firmware                            1.148
   0: phy0: Wireless LAN
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-08-27 (23 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to: