Re: sysupgrade boot.bin apply m1 boot failure

[Bobby Johnson]

Found today that the current apple-boot-firmware installed with fw_update
works.

Built my own backing out the most recent changes, but then noticed that the
boot.bin
from current fw_update package was different than the boot.bin in my efi
partition.  File hashes
below if they're useful.  pkg_info showed v 1.3 installed with the
failing-boot.bin file.

SHA256 (failing-boot.bin) =
f78c547db8e9a5193c2f1c8d9c89b1f35f57e2a8c87fb67e2e83c3bae60c1e45
SHA256 (1.3-now-boot.bin) =
fa892b057949648dd7f562efeae7a46939f787b4b664a9e79bf2ea73fc3fbc33

sysupgrade boot.bin apply m1 boot failure

[bobby]

>Synopsis:  sysupgrade to latest snap results in bootloop, had to replace 
>boot.bin
>Category:  system aarch64
>Environment:
System  : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 
MDT 2024
 
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP

Architecture: OpenBSD.arm64
Machine : arm64
>Description:
Upgraded my m1 macbook air to the latest snapshot.
After the installation, reboot, I see the mac logo, asahi logo, no 
OpenBSD logo, then it reboots and repeats.
I copied /m1n1/boot.bin from another asahi efi partition to the OpenBSD 
m1n1 partition and it boots again. 
>How-To-Repeat:
Install a snapshot on a mac?
>Fix:
Use a boot.bin from asahi


dmesg:
OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 MDT 2024
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 16379801600 (15620MB)
avail mem = 15738245120 (15009MB)
random: good seed from bootblocks
mainbus0 at root: Apple MacBook Air (M1, 2020)
efi0 at mainbus0: UEFI 2.10
efi0: Das U-Boot rev 0x20230700
cpu0 at mainbus0 mpidr 0: Apple Icestorm r1p1
cpu0: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu0: 4096KB 128b/line 16-way L2 cache
cpu0: 
TLBIOS+IRANGE,TS+AXFLAG,FHM,DP,SHA3,RDM,Atomic,CRC32,SHA2+SHA512,SHA1,AES+PMULL,SPECRES,SB,FRINTTS,GPI,LRCPC+LDAPUR,FCMA,JSCVT,API+PAC,DPB,SpecSEI,PAN+ATS1E1,LO,HPDS,VH,CSV3,CSV2,DIT,SSBS+MSR
cpu1 at mainbus0 mpidr 1: Apple Icestorm r1p1
cpu1: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu1: 4096KB 128b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: Apple Icestorm r1p1
cpu2: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu2: 4096KB 128b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: Apple Icestorm r1p1
cpu3: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu3: 4096KB 128b/line 16-way L2 cache
cpu4 at mainbus0 mpidr 10100: Apple Firestorm r1p1
cpu4: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu4: 12288KB 128b/line 12-way L2 cache
cpu5 at mainbus0 mpidr 10101: Apple Firestorm r1p1
cpu5: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu5: 12288KB 128b/line 12-way L2 cache
cpu6 at mainbus0 mpidr 10102: Apple Firestorm r1p1
cpu6: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu6: 12288KB 128b/line 12-way L2 cache
cpu7 at mainbus0 mpidr 10103: Apple Firestorm r1p1
cpu7: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu7: 12288KB 128b/line 12-way L2 cache
"asc-firmware" at mainbus0 not configured
"asc-firmware" at mainbus0 not configured
"framebuffer" at mainbus0 not configured
"region95" at mainbus0 not configured
"region94" at mainbus0 not configured
"region57" at mainbus0 not configured
"dcp_data" at mainbus0 not configured
"uat-handoff" at mainbus0 not configured
"uat-pagetables" at mainbus0 not configured
"uat-ttbs" at mainbus0 not configured
"isp-heap" at mainbus0 not configured
apm0 at mainbus0
"opp-table-0" at mainbus0 not configured
"opp-table-1" at mainbus0 not configured
"opp-table-gpu" at mainbus0 not configured
agtimer0 at mainbus0: 24000 kHz
"pmu-e" at mainbus0 not configured
"pmu-p" at mainbus0 not configured
"clock-ref" at mainbus0 not configured
"clock-120m" at mainbus0 not configured
"clock-200m" at mainbus0 not configured
"clock-disp0" at mainbus0 not configured
"clock-dispext0" at mainbus0 not configured
"clock-ref-nco" at mainbus0 not configured
simplebus0 at mainbus0: "soc"
aplpmgr0 at simplebus0
aplpmgr1 at simplebus0
aplmbox0 at simplebus0
apldart0 at simplebus0: 32 bits
apldart1 at simplebus0: 32 bits, locked
apldart2 at simplebus0: 32 bits, locked
aplmbox1 at simplebus0
apldart3 at simplebus0: 32 bits, bypass
apldart4 at simplebus0: 32 bits
apldart5 at simplebus0: 32 bits
apldart6 at simplebus0: 32 bits, bypass
aplintc0 at simplebus0 nirq 896 ndie 1
aplpinctrl0 at simplebus0
aplpinctrl1 at simplebus0
apldog0 at simplebus0
aplmbox2 at simplebus0
aplpinctrl2 at simplebus0
aplpinctrl3 at simplebus0
aplmbox3 at simplebus0
aplefuse0 at simplebus0
apldart7 at simplebus0: 32 bits, bypass
apldart8 at simplebus0: 32 bits, bypass
apldart9 at simplebus0: 32 bits, bypass
apldart10 at simplebus0: 32 bits, bypass
apldart11 at simplebus0: 32 bits
"gpu" at simplebus0 not configured
aplcpu0 at simplebus0
aplcpu1 at simplebus0
apldcp0 at simplebus0
apldrm0 at simplebus0
drm0 at apldrm0
"isp" at simplebus0 not configured
apliic0 at simplebus0
iic0 at apliic0
tipd0 at iic0 addr 0x38
tipd1 at iic0 addr 0x3f
apliic1 at simplebus0
iic1 at apliic1
tascodec0 at iic1 addr 0x31
apliic2 at simplebus0
iic2 at apliic2
tascodec1 at iic2 addr 0x34
"cirrus,cs42l83" at iic2 addr 0x48 not configured
aplpwm0 at simplebus0
aplspi0 at simplebus0
aplspi1 at simplebus0
aplhidev0 at aplspi1
aplkbd0 at aplhidev0: 8 variable keys, 6 key 

Re: Lenovo C930 entry point reboot

[Bobby Johnson]

> On Dec 22, 2019, at 6:49 PM, YASUOKA Masahiko  wrote:
> 
> On Wed, 27 Nov 2019 15:59:10 -0700
> Bobby Johnson  wrote:
>> Attempting to install OpenBSD on the Lenovo C930, Kaby Lake laptop.
>> When booting I only see the entry point at line and then it restarts.
>> It does this with a very recent snapshot on bsd.rd and bsd, booting
>> from a usb drive.
> 
> No message from kernel.  
> 
> If the frame buffer is located high, there is an unfixed issue.
> 
> https://marc.info/?l=openbsd-tech=156890945

The patch you linked fixed it!

Thank you!

Re: Lenovo C930 entry point reboot

[Bobby Johnson]

On Sat, Dec 21, 2019 at 4:58 AM Alexander Bluhm  wrote:
>
> On Fri, Dec 20, 2019 at 10:33:02PM -0700, Bobby Johnson wrote:
> > Any clues how I could test further?
>
> The laptop I had hang after printing the enry point.  To debug
> I moved a reset function around to find the final line that is
> executed before the hang.
>
> #include 
> void
> cpu_reset(void)
> {
> outb(0x64, 0xfe);
> for (volatile long i = 0; i < 1; i++);
> outb(0x64, 0xfe);
> for (volatile long i = 0; i < 1; i++);
> for (;;)
> continue;
> }
>
> As your machine reboots for unknown reason, you have to do it the
> other way around.  Move an endless loop before the instruction that
> causes the reboot to identify the problematic code.
>
> void
> cpu_hang(void)
> {
> for (;;)
> continue;
> }
>
> The problem may be in the boot loader or after jumping into the
> kernel before printing anything.  The reset/hang debugging works
> for both.
>
> Good luck,
>
> bluhm

Thank you!

Earlier I was trying to use printf statements to determine where it
was failing.  With this cpu_hang function I've found that it's booting
further than I realized.  Still troubleshooting to determine where it
is failing.

Re: Lenovo C930 entry point reboot

[Bobby Johnson]

On Wed, Dec 4, 2019 at 11:45 AM Bobby Johnson  wrote:
>
>
>
> > On Nov 30, 2019, at 3:40 PM, Bobby Johnson  wrote:
> >
> > Thanks for the ideas.  This machine will do PXE but apparently only
> > with UEFI.  I tried releases back to 6.2 via a usb drive all with the
> > same result.
> >
> > One other thing I tried was dd-ing a current install image to a
> > partition on the onboard disk.  I get the bootloader, but then it
> > can't find /bsd and I can't ls the contents of the install from the
> > bootloader.
> >
> >> On Thu, Nov 28, 2019 at 3:59 AM Stuart Henderson  
> >> wrote:
> >>
> >>> On 2019/11/27 15:59, Bobby Johnson wrote:
> >>> Hello,
> >>>
> >>> Attempting to install OpenBSD on the Lenovo C930, Kaby Lake laptop.
> >>> When booting I only see the entry point at line and then it restarts.
> >>> It does this with a very recent snapshot on bsd.rd and bsd, booting
> >>> from a usb drive.
> >>
> >> As well as Stefan's suggestion of legacy PXE, maybe try 6.6 or 6.5 as well
> >> instead of the very recent snapshot?
> >>
> >>> I found the NVME wasn't in the pcidevs.  The vendor also wasn't
> >>> listed, HYNIX, 0x151c.  I added the vendor and and device id for the
> >>> card, regenerated the pcidevs.h and pcidevs_data.h and recompiled.
> >>> Is that all that's necessary to get a new nvme to attach?  Anything
> >>> else I could look into to get it booting?
> >>
> >> Kernel drivers attach much later than the "entry point", even if the
> >> NVME isn't being picked up, that wouldn't make it restart here.
> >>
> >>> Below is what I added to pcidevs
> >>>
> >>> vendor  HYNIX   0x1c5c  Hynix
> >>> product HYNIX NVME1 0x1527  NVMe
> >>>
> >>> Bobby
> >>>
> >>
> >> NVME normally attaches by device subclass/interface, this code in
> >> nvme_pci_match() in sys/dev/pci/nvme_pci.c:
> >>
> >>if (PCI_CLASS(pa->pa_class) == PCI_CLASS_MASS_STORAGE &&
> >>PCI_SUBCLASS(pa->pa_class) == PCI_SUBCLASS_MASS_STORAGE_NVM &&
> >>PCI_INTERFACE(pa->pa_class) == NVME_PCI_INTERFACE)
> >>return (1);
> >>
> >> If the class/subclass/interface match then there's no need to look at
> >> vendor/device id. Currently the driver has a special attachment for some
> >> Apple device ids. It's very unlikely that your device needs any change,
> >> but if it did then you'd add it alongside the Apple ones (as well as
> >> updating pcidevs).
> >>
> >> FWIW here's a pcidump -v example of a device which already matches:
> >>
> >> 5:0:0: Samsung SM961/PM961 NVMe
> >>0x: Vendor ID: 144d, Product ID: a804
> >>0x0004: Command: 0006, Status: 0010
> >>0x0008: Class: 01 Mass Storage, Subclass: 08 NVM,
> >>Interface: 02, Revision: 00
> >>
> >> or this in lspci -v
> >>
> >> 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe 
> >> SSD Controller SM961/PM961 (prog-if 02 [NVM Express])
> >>
> >> There's no dev/vendor match for this but still:
> >>
> >> nvme0 at pci5 dev 0 function 0 "Samsung SM961/PM961 NVMe" rev 0x00: msix, 
> >> NVMe 1.2
> >> nvme0: SAMSUNG MZVLW256HEHP-000L7, firmware 4L7QCXB7, serial S35ENX0J765205
> >> scsibus1 at nvme0: 2 targets, initiator 0
> >>
>
> Figured out how to do UEFI pxe. Same result though.


I found some recent commits by bluhm@ to get a laptop with maybe a
similar problem working.  His work didn't fix my problem, but the hex
dump command he added to the bootloader gives a possible clue.  When I
boot I get an entry point of 0x1001000.  From the bootloader when I do
a hex dump around that location I see some stuff.  On the VM I'm
testing on I just see everything set to ff at the same location.

I've tried to see if I could change the entry point by altering delta
in sys/arch/amd64/stand/efiboot/exec_i386.c.  But even with a small
change my test vm won't boot with it.

Any clues how I could test further?

Re: Lenovo C930 entry point reboot

[Bobby Johnson]

> On Nov 30, 2019, at 3:40 PM, Bobby Johnson  wrote:
> 
> Thanks for the ideas.  This machine will do PXE but apparently only
> with UEFI.  I tried releases back to 6.2 via a usb drive all with the
> same result.
> 
> One other thing I tried was dd-ing a current install image to a
> partition on the onboard disk.  I get the bootloader, but then it
> can't find /bsd and I can't ls the contents of the install from the
> bootloader.
> 
>> On Thu, Nov 28, 2019 at 3:59 AM Stuart Henderson  
>> wrote:
>> 
>>> On 2019/11/27 15:59, Bobby Johnson wrote:
>>> Hello,
>>> 
>>> Attempting to install OpenBSD on the Lenovo C930, Kaby Lake laptop.
>>> When booting I only see the entry point at line and then it restarts.
>>> It does this with a very recent snapshot on bsd.rd and bsd, booting
>>> from a usb drive.
>> 
>> As well as Stefan's suggestion of legacy PXE, maybe try 6.6 or 6.5 as well
>> instead of the very recent snapshot?
>> 
>>> I found the NVME wasn't in the pcidevs.  The vendor also wasn't
>>> listed, HYNIX, 0x151c.  I added the vendor and and device id for the
>>> card, regenerated the pcidevs.h and pcidevs_data.h and recompiled.
>>> Is that all that's necessary to get a new nvme to attach?  Anything
>>> else I could look into to get it booting?
>> 
>> Kernel drivers attach much later than the "entry point", even if the
>> NVME isn't being picked up, that wouldn't make it restart here.
>> 
>>> Below is what I added to pcidevs
>>> 
>>> vendor  HYNIX   0x1c5c  Hynix
>>> product HYNIX NVME1 0x1527  NVMe
>>> 
>>> Bobby
>>> 
>> 
>> NVME normally attaches by device subclass/interface, this code in
>> nvme_pci_match() in sys/dev/pci/nvme_pci.c:
>> 
>>if (PCI_CLASS(pa->pa_class) == PCI_CLASS_MASS_STORAGE &&
>>PCI_SUBCLASS(pa->pa_class) == PCI_SUBCLASS_MASS_STORAGE_NVM &&
>>PCI_INTERFACE(pa->pa_class) == NVME_PCI_INTERFACE)
>>return (1);
>> 
>> If the class/subclass/interface match then there's no need to look at
>> vendor/device id. Currently the driver has a special attachment for some
>> Apple device ids. It's very unlikely that your device needs any change,
>> but if it did then you'd add it alongside the Apple ones (as well as
>> updating pcidevs).
>> 
>> FWIW here's a pcidump -v example of a device which already matches:
>> 
>> 5:0:0: Samsung SM961/PM961 NVMe
>>0x: Vendor ID: 144d, Product ID: a804
>>0x0004: Command: 0006, Status: 0010
>>0x0008: Class: 01 Mass Storage, Subclass: 08 NVM,
>>Interface: 02, Revision: 00
>> 
>> or this in lspci -v
>> 
>> 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
>> Controller SM961/PM961 (prog-if 02 [NVM Express])
>> 
>> There's no dev/vendor match for this but still:
>> 
>> nvme0 at pci5 dev 0 function 0 "Samsung SM961/PM961 NVMe" rev 0x00: msix, 
>> NVMe 1.2
>> nvme0: SAMSUNG MZVLW256HEHP-000L7, firmware 4L7QCXB7, serial S35ENX0J765205
>> scsibus1 at nvme0: 2 targets, initiator 0
>> 

Figured out how to do UEFI pxe. Same result though. 

Re: Lenovo C930 entry point reboot

[Bobby Johnson]

Thanks for the ideas.  This machine will do PXE but apparently only
with UEFI.  I tried releases back to 6.2 via a usb drive all with the
same result.

One other thing I tried was dd-ing a current install image to a
partition on the onboard disk.  I get the bootloader, but then it
can't find /bsd and I can't ls the contents of the install from the
bootloader.

On Thu, Nov 28, 2019 at 3:59 AM Stuart Henderson  wrote:
>
> On 2019/11/27 15:59, Bobby Johnson wrote:
> > Hello,
> >
> > Attempting to install OpenBSD on the Lenovo C930, Kaby Lake laptop.
> > When booting I only see the entry point at line and then it restarts.
> > It does this with a very recent snapshot on bsd.rd and bsd, booting
> > from a usb drive.
>
> As well as Stefan's suggestion of legacy PXE, maybe try 6.6 or 6.5 as well
> instead of the very recent snapshot?
>
> > I found the NVME wasn't in the pcidevs.  The vendor also wasn't
> > listed, HYNIX, 0x151c.  I added the vendor and and device id for the
> > card, regenerated the pcidevs.h and pcidevs_data.h and recompiled.
> > Is that all that's necessary to get a new nvme to attach?  Anything
> > else I could look into to get it booting?
>
> Kernel drivers attach much later than the "entry point", even if the
> NVME isn't being picked up, that wouldn't make it restart here.
>
> > Below is what I added to pcidevs
> >
> > vendor  HYNIX   0x1c5c  Hynix
> > product HYNIX NVME1 0x1527  NVMe
> >
> > Bobby
> >
>
> NVME normally attaches by device subclass/interface, this code in
> nvme_pci_match() in sys/dev/pci/nvme_pci.c:
>
> if (PCI_CLASS(pa->pa_class) == PCI_CLASS_MASS_STORAGE &&
> PCI_SUBCLASS(pa->pa_class) == PCI_SUBCLASS_MASS_STORAGE_NVM &&
> PCI_INTERFACE(pa->pa_class) == NVME_PCI_INTERFACE)
> return (1);
>
> If the class/subclass/interface match then there's no need to look at
> vendor/device id. Currently the driver has a special attachment for some
> Apple device ids. It's very unlikely that your device needs any change,
> but if it did then you'd add it alongside the Apple ones (as well as
> updating pcidevs).
>
> FWIW here's a pcidump -v example of a device which already matches:
>
>  5:0:0: Samsung SM961/PM961 NVMe
> 0x: Vendor ID: 144d, Product ID: a804
> 0x0004: Command: 0006, Status: 0010
> 0x0008: Class: 01 Mass Storage, Subclass: 08 NVM,
> Interface: 02, Revision: 00
>
> or this in lspci -v
>
> 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
> Controller SM961/PM961 (prog-if 02 [NVM Express])
>
> There's no dev/vendor match for this but still:
>
> nvme0 at pci5 dev 0 function 0 "Samsung SM961/PM961 NVMe" rev 0x00: msix, 
> NVMe 1.2
> nvme0: SAMSUNG MZVLW256HEHP-000L7, firmware 4L7QCXB7, serial S35ENX0J765205
> scsibus1 at nvme0: 2 targets, initiator 0
>

Lenovo C930 entry point reboot

[Bobby Johnson]

Hello,

Attempting to install OpenBSD on the Lenovo C930, Kaby Lake laptop.
When booting I only see the entry point at line and then it restarts.
It does this with a very recent snapshot on bsd.rd and bsd, booting
from a usb drive.

I found the NVME wasn't in the pcidevs.  The vendor also wasn't
listed, HYNIX, 0x151c.  I added the vendor and and device id for the
card, regenerated the pcidevs.h and pcidevs_data.h and recompiled.
Is that all that's necessary to get a new nvme to attach?  Anything
else I could look into to get it booting?

Below is what I added to pcidevs

vendor  HYNIX   0x1c5c  Hynix
product HYNIX NVME1 0x1527  NVMe

Bobby

Re: xbacklight not working on Lenovo ideapad S210 Touch

[Bobby Johnson]

Thank you!  I had this same issue on another laptop and this fixed it.

On Tue, May 22, 2018 at 6:43 AM, Mark Kettenis  wrote:
>> Date: Tue, 22 May 2018 14:04:56 +0200 (CEST)
>> From: eda...@muj-disk.cz
>>
>> >Synopsis:xbacklight not working on Lenovo ideapad S210 Touch
>> >Category:system
>> >Environment:
>>   System  : OpenBSD 6.3
>>   Details : OpenBSD 6.3-current (GENERIC.MP) #38: Wed May  9 
>> 17:38:06 MDT 2018
>>
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>>
>>   Architecture: OpenBSD.amd64
>>   Machine : amd64
>> >Description:
>>
>>   xbacklight not working on Lenovo ideapad S210 Touch. Hotkeys (Fn 
>> F11/F12) not working.
>>   xbacklight -set also.
>>
>> >How-To-Repeat:
>>
>>   xbacklight -set 50 (0 to 100)
>>   or press hotkeys
>>
>>   always returns
>>
>>   $ xbacklight -get
>>   0.00
>>
>>   and brightness is always 100%
>> >Fix:
>>   I do not know
>
> Try disabling acpivideo and/or acpivout.
>

Re: Touchpad (iatp) error on resume on Chromebook Pixel 2015

[Bobby Johnson]

I tried reverting iatp.c to the previous revision. Didn’t make a difference. 
Any thoughts on where else to look?

> On Mar 1, 2018, at 10:14 AM, Bobby Johnson <bo...@plexuscomp.com> wrote:
> 
> It is a regression, it used to resume without issue. I’m not sure when it 
> started because I don’t use this laptop very often. 
> 
>> On Mar 1, 2018, at 1:37 AM, Anthony J. Bentley <anth...@anjbe.name> wrote:
>> 
>> bob writes:
>>> Hardware is the Chromebook pixel 2015.  No response from touchpad or 
>>> touchscr
>>> een on resume.  These errors pop up in the dmesg.  Full dmesg below.
>>> 
>>> iatp0: failed reading main memory map
>>> iatp1: failed reading main memory map
>>> iatp0: failed reading 540
>>> iatp1: failed reading 680
>> 
>> I get these as well with my 2015 Pixel, with or without your xorg.conf.
>> (I don't get the "iatp0: failed reading t44 and t5" message either way.)
>> 
>> I almost never suspend my laptops. Have you successfully suspended
>> this laptop before? Is this a regression?

Re: Touchpad (iatp) error on resume on Chromebook Pixel 2015

[Bobby Johnson]

It is a regression, it used to resume without issue. I’m not sure when it 
started because I don’t use this laptop very often. 

> On Mar 1, 2018, at 1:37 AM, Anthony J. Bentley  wrote:
> 
> bob writes:
>> Hardware is the Chromebook pixel 2015.  No response from touchpad or touchscr
>> een on resume.  These errors pop up in the dmesg.  Full dmesg below.
>> 
>> iatp0: failed reading main memory map
>> iatp1: failed reading main memory map
>> iatp0: failed reading 540
>> iatp1: failed reading 680
> 
> I get these as well with my 2015 Pixel, with or without your xorg.conf.
> (I don't get the "iatp0: failed reading t44 and t5" message either way.)
> 
> I almost never suspend my laptops. Have you successfully suspended
> this laptop before? Is this a regression?