Results 1 to 2 of 2

Thread: Wake from suspend issues with 2016 MacBookPro

  1. #1
    Join Date
    Nov 2023

    Wake from suspend issues with 2016 MacBookPro

    I've been trying to install / debug making a 2016 MBP dual-boot with Ubuntu 22.04.03. Before I go into any details, I just want to check if there are some basic steps for this laptop that I missed upon installation. Here's the info.

    Basic guidelines I followed for install here:

    The machine itself:

    • MacBook Pro 13" (late 2016, MacBookPro13,1)
    • 2.4 GHz Dual-Core Intel Core i7
    • 16 GB 1867 MHz LPDDR3
    • Intel Iris Graphics 540 1536 MB
    • 13.3-inch Built-in Retina Display
    • 1TB Flash Storage
    • WiFi Broadcom BCM4350 1.0

    The issue: Upon waking from sleep, the root filesystem becomes read-only. Looking at dmesg output, there are a number of error messages concerning changing the states of various bits of hardware. Eventually there are disk system errors ending with an error writing the superblock, which causes the filesystem to be remounted read-only.

    I have the dmesg output but will hold off on that until it's clear that it's helpful (it's big). I think I have to be missing something from the start (perhaps drivers) given that other users have been successful with MacBooks. FWIW, everything works OK if I don't suspend. The only add I had to do was to get the sound working (solution that worked:

    Thanks in advance.

    Edit: I was able to install on a MacBook Air 13" (Mid 2012, MacBookAir5,2) with no other problems than wifi (Broadcom), so it is definitely something to do with this particular Pro's hardware and/or drivers.
    Last edited by jjkraw; November 12th, 2023 at 03:07 PM. Reason: Report success with different MacBook model.

  2. #2
    Join Date
    Nov 2023

    Re: Wake from suspend issues with 2016 MacBookPro


    I was able to get rid of the read-only file system problem by based on info I found here:

    Scroll down to "Suspend & Hibernation".

    I found that I also needed to disable "d3cold" for a PCI bridge to get it to work consistently. I created an /etc/rc.local file with the following contents:

    echo 0 > /sys/bus/pci/devices/0000\:01\:00.0/d3cold_allowed
    echo 0 > /sys/bus/pci/devices/0000\:04\:00.0/d3cold_allowed
    So now I can suspend, for some definition of suspend, because I'm still seeing via dmesg what is described in this bug report here:

    This is a bug that was fixed and the patch has been included for 2+ years, but apparently the fix doesn't work/apply to a MacBookPro13,1.

    I'll keep poking away at this, but if anyone has ideas let me know!


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts