Re: Some Framework Laptops fail to resume from zzz

2022-10-07 Thread Ian Darwin
On Fri, Oct 07, 2022 at 06:55:56PM +, Renato Aguiar wrote:
> I found this post in framework community blog about battery drain and other
> random problems being resolved after a full bios reset:
> 
>   https://community.frame.work/t/bios-guide/4178/136
> 
> I decided to give it a try and that somehow fixed the resume problem I was
> facing. My framework laptop can now suspend/resume without disabling dwiic.

Confirmed. I just upgraded to bios 3.10 and can likewise suspend/resume w/o
disabling dwiic.



Re: Some Framework Laptops fail to resume from zzz

2022-10-07 Thread Renato Aguiar
I found this post in framework community blog about battery drain and other
random problems being resolved after a full bios reset:

  https://community.frame.work/t/bios-guide/4178/136

I decided to give it a try and that somehow fixed the resume problem I was
facing. My framework laptop can now suspend/resume without disabling dwiic.

--
Renato Aguiar



Re: Some Framework Laptops fail to resume from zzz

2021-12-19 Thread Aaron Bieber


Renato Aguiar  writes:

> "Mark Kettenis"  writes:
>
>>> Date: Tue, 14 Dec 2021 22:54:48 +
>>> From: Renato Aguiar 
>>>
>>> "Mark Kettenis"  writes:
>>>
>>> >
>>> > Does the diff below help?
>>> >
>>> >
>>> > Index: dev/ic/dwiic.c
>>> > ===
>>> > RCS file: /cvs/src/sys/dev/ic/dwiic.c,v
>>> > retrieving revision 1.13
>>> > diff -u -p -r1.13 dwiic.c
>>> > --- dev/ic/dwiic.c7 Nov 2021 14:07:43 -   1.13
>>> > +++ dev/ic/dwiic.c14 Dec 2021 10:56:37 -
>>> > @@ -153,6 +153,10 @@ dwiic_init(struct dwiic_softc *sc)
>>> >   /* disable the adapter */
>>> >   dwiic_enable(sc, 0);
>>> >
>>> > + /* disable interrupts */
>>> > + dwiic_write(sc, DW_IC_INTR_MASK, 0);
>>> > + dwiic_read(sc, DW_IC_CLR_INTR);
>>> > +
>>> >   /* write standard-mode SCL timing parameters */
>>> >   dwiic_write(sc, DW_IC_SS_SCL_HCNT, sc->ss_hcnt);
>>> >   dwiic_write(sc, DW_IC_SS_SCL_LCNT, sc->ss_lcnt);
>>>
>>> No, it doesn't. I had also tried disabling interrupts at some other
>>> places during my initial investigation, but I couldn't make them stop
>>> without completely disabling the device.
>>
>> Are any bits in DW_IC_INTR_STAT set when this happens upon resume?
>
> No, both DW_IC_ENABLE and DW_IC_INTR_STAT are 0 when dwiic_intr() is
> called for dwiic0 after resume.

I recently picked up a Framework too - I am hitting a similar issue but
my devices seem to be a bit different. Unfortunately the bsd.re-config
trick doesn't work for me.

OpenBSD 7.0-current (GENERIC.MP) #182: Sun Dec 19 00:51:04 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 68475875328 (65303MB)
avail mem = 66384596992 (63309MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x439e2000 (51 entries)
bios0: vendor INSYDE Corp. version "03.06" date 10/18/2021
bios0: Framework Laptop
acpi0 at bios0: ACPI 6.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT SSDT SSDT SSDT SSDT TPM2 SSDT NHLT SSDT 
LPIT WSMT SSDT SSDT DBGP DBG2 ECDT HPET APIC MCFG SSDT DMAR SSDT FPDT PTDT ASF! 
BGRT
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEGP(S4) PEGP(S4) XHCI(S4) XDCI(S4) 
HDAS(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) 
PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz, 4788.96 MHz, 06-8c-01
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 256KB 64b/line disabled L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 38MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.1.2.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz, 4788.96 MHz, 06-8c-01
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 256KB 64b/line disabled L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz, 4290.11 MHz, 06-8c-01
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu2: 256KB 64b/line disabled L2 cache
cpu2: disabling user TSC (skew=194)
cpu2: smt 0, core 2, 

Re: Some Framework Laptops fail to resume from zzz

2021-12-15 Thread Renato Aguiar


"Mark Kettenis"  writes:

>> Date: Tue, 14 Dec 2021 22:54:48 +
>> From: Renato Aguiar 
>>
>> "Mark Kettenis"  writes:
>>
>> >
>> > Does the diff below help?
>> >
>> >
>> > Index: dev/ic/dwiic.c
>> > ===
>> > RCS file: /cvs/src/sys/dev/ic/dwiic.c,v
>> > retrieving revision 1.13
>> > diff -u -p -r1.13 dwiic.c
>> > --- dev/ic/dwiic.c 7 Nov 2021 14:07:43 -   1.13
>> > +++ dev/ic/dwiic.c 14 Dec 2021 10:56:37 -
>> > @@ -153,6 +153,10 @@ dwiic_init(struct dwiic_softc *sc)
>> >/* disable the adapter */
>> >dwiic_enable(sc, 0);
>> >
>> > +  /* disable interrupts */
>> > +  dwiic_write(sc, DW_IC_INTR_MASK, 0);
>> > +  dwiic_read(sc, DW_IC_CLR_INTR);
>> > +
>> >/* write standard-mode SCL timing parameters */
>> >dwiic_write(sc, DW_IC_SS_SCL_HCNT, sc->ss_hcnt);
>> >dwiic_write(sc, DW_IC_SS_SCL_LCNT, sc->ss_lcnt);
>>
>> No, it doesn't. I had also tried disabling interrupts at some other
>> places during my initial investigation, but I couldn't make them stop
>> without completely disabling the device.
>
> Are any bits in DW_IC_INTR_STAT set when this happens upon resume?

No, both DW_IC_ENABLE and DW_IC_INTR_STAT are 0 when dwiic_intr() is
called for dwiic0 after resume.

--
Renato



Re: Some Framework Laptops fail to resume from zzz

2021-12-14 Thread Mark Kettenis
> Date: Tue, 14 Dec 2021 22:54:48 +
> From: Renato Aguiar 
> 
> "Mark Kettenis"  writes:
> 
> >
> > Does the diff below help?
> >
> >
> > Index: dev/ic/dwiic.c
> > ===
> > RCS file: /cvs/src/sys/dev/ic/dwiic.c,v
> > retrieving revision 1.13
> > diff -u -p -r1.13 dwiic.c
> > --- dev/ic/dwiic.c  7 Nov 2021 14:07:43 -   1.13
> > +++ dev/ic/dwiic.c  14 Dec 2021 10:56:37 -
> > @@ -153,6 +153,10 @@ dwiic_init(struct dwiic_softc *sc)
> > /* disable the adapter */
> > dwiic_enable(sc, 0);
> >
> > +   /* disable interrupts */
> > +   dwiic_write(sc, DW_IC_INTR_MASK, 0);
> > +   dwiic_read(sc, DW_IC_CLR_INTR);
> > +
> > /* write standard-mode SCL timing parameters */
> > dwiic_write(sc, DW_IC_SS_SCL_HCNT, sc->ss_hcnt);
> > dwiic_write(sc, DW_IC_SS_SCL_LCNT, sc->ss_lcnt);
> 
> No, it doesn't. I had also tried disabling interrupts at some other
> places during my initial investigation, but I couldn't make them stop
> without completely disabling the device.

Are any bits in DW_IC_INTR_STAT set when this happens upon resume?



Re: Some Framework Laptops fail to resume from zzz

2021-12-14 Thread Renato Aguiar


"Mark Kettenis"  writes:

>
> Does the diff below help?
>
>
> Index: dev/ic/dwiic.c
> ===
> RCS file: /cvs/src/sys/dev/ic/dwiic.c,v
> retrieving revision 1.13
> diff -u -p -r1.13 dwiic.c
> --- dev/ic/dwiic.c7 Nov 2021 14:07:43 -   1.13
> +++ dev/ic/dwiic.c14 Dec 2021 10:56:37 -
> @@ -153,6 +153,10 @@ dwiic_init(struct dwiic_softc *sc)
>   /* disable the adapter */
>   dwiic_enable(sc, 0);
>
> + /* disable interrupts */
> + dwiic_write(sc, DW_IC_INTR_MASK, 0);
> + dwiic_read(sc, DW_IC_CLR_INTR);
> +
>   /* write standard-mode SCL timing parameters */
>   dwiic_write(sc, DW_IC_SS_SCL_HCNT, sc->ss_hcnt);
>   dwiic_write(sc, DW_IC_SS_SCL_LCNT, sc->ss_lcnt);

No, it doesn't. I had also tried disabling interrupts at some other
places during my initial investigation, but I couldn't make them stop
without completely disabling the device.

--
Renato



Re: Some Framework Laptops fail to resume from zzz

2021-12-14 Thread Ian Darwin
On Tue, Dec 14, 2021 at 11:58:56AM +0100, Mark Kettenis wrote:
> > From: Renato Aguiar 
> > 
> > There are 3 devices attaching to `dwiic* at pci0':
> > 
> > dwiic0 at pci0 dev 21 function 0 "Intel 500 Series I2C" rev 0x20: apic 2 
> > int 27
> > 
> >   I have no idea what this one is for, but it keeps sending interrupts
> >   after resume and that is what is causing the laptop to freeze.
> >   Disabling this device alone "fixes" suspend/resume for me.
> > 
> > dwiic1 at pci0 dev 21 function 1 "Intel 500 Series I2C" rev 0x20: apic 2 
> > int 40
> > 
> >   This is for some special keyboard keys, like brightness control.
> 
> BTW, these keyboard keys might need the i2c ihidev(4) equivalent of
> the ucc(4) driver.

FWIW, with Renato's workaround (disabling the first dwiic), brightness control 
still works.

The fix Mark sent for dwiic did not solve the resume problem for my laptop.



Re: Some Framework Laptops fail to resume from zzz

2021-12-14 Thread Anton Lindqvist
On Tue, Dec 14, 2021 at 11:58:56AM +0100, Mark Kettenis wrote:
> > Date: Tue, 14 Dec 2021 02:20:11 +
> > From: Renato Aguiar 
> > 
> > I did some investigation over the weekend and I was able to get more
> > information about the problem and find a better workaround.
> > 
> > There are 3 devices attaching to `dwiic* at pci0':
> > 
> > dwiic0 at pci0 dev 21 function 0 "Intel 500 Series I2C" rev 0x20: apic 2 
> > int 27
> > 
> >   I have no idea what this one is for, but it keeps sending interrupts
> >   after resume and that is what is causing the laptop to freeze.
> >   Disabling this device alone "fixes" suspend/resume for me.
> > 
> > dwiic1 at pci0 dev 21 function 1 "Intel 500 Series I2C" rev 0x20: apic 2 
> > int 40
> > 
> >   This is for some special keyboard keys, like brightness control.
> 
> BTW, these keyboard keys might need the i2c ihidev(4) equivalent of
> the ucc(4) driver.
> 

It would be interesting to examine the hid report descriptor. Does
anyone have it available?



Re: Some Framework Laptops fail to resume from zzz

2021-12-14 Thread Mark Kettenis
> Date: Tue, 14 Dec 2021 02:20:11 +
> From: Renato Aguiar 
> 
> I did some investigation over the weekend and I was able to get more
> information about the problem and find a better workaround.
> 
> There are 3 devices attaching to `dwiic* at pci0':
> 
> dwiic0 at pci0 dev 21 function 0 "Intel 500 Series I2C" rev 0x20: apic 2 int 
> 27
> 
>   I have no idea what this one is for, but it keeps sending interrupts
>   after resume and that is what is causing the laptop to freeze.
>   Disabling this device alone "fixes" suspend/resume for me.
> 
> dwiic1 at pci0 dev 21 function 1 "Intel 500 Series I2C" rev 0x20: apic 2 int 
> 40
> 
>   This is for some special keyboard keys, like brightness control.

BTW, these keyboard keys might need the i2c ihidev(4) equivalent of
the ucc(4) driver.



Re: Some Framework Laptops fail to resume from zzz

2021-12-14 Thread Mark Kettenis
> Date: Tue, 14 Dec 2021 02:20:11 +
> From: Renato Aguiar 
> 
> I did some investigation over the weekend and I was able to get more
> information about the problem and find a better workaround.
> 
> There are 3 devices attaching to `dwiic* at pci0':
> 
> dwiic0 at pci0 dev 21 function 0 "Intel 500 Series I2C" rev 0x20: apic 2 int 
> 27
> 
>   I have no idea what this one is for, but it keeps sending interrupts
>   after resume and that is what is causing the laptop to freeze.
>   Disabling this device alone "fixes" suspend/resume for me.
> 
> dwiic1 at pci0 dev 21 function 1 "Intel 500 Series I2C" rev 0x20: apic 2 int 
> 40
> 
>   This is for some special keyboard keys, like brightness control.
> 
> dwiic2 at pci0 dev 21 function 3 "Intel 500 Series I2C" rev 0x20: apic 2 int 
> 30
> 
>   And this one is for touchpad.
> 
> As a workaround for now, I'm changing `dwiic* at pci*` to attach only to
> touchpad, so I can have suspend/resume working without losing the touchpad.
> 
> # config -ef /bsd
> ukc> find dwiic
> 226 dwiic* at pci* dev -1 function -1 flags 0x0
> 448 dwiic* at acpi0 flags 0x0
> ukc> change 226
> 226 dwiic* at pci* dev -1 function -1 flags 0x0
> change [n] y
> dev [-1] ? 21
> function [-1] ? 3
> flags [0] ?
> 226 dwiic* changed
> 226 dwiic* at pci* dev 0x15 function 3 flags 0x0
> ukc> quit
> 
> Now it only configures dwiic0 for touchpad:
> 
>   "Intel 500 Series I2C" rev 0x20 at pci0 dev 21 function 0 not configured
>   "Intel 500 Series I2C" rev 0x20 at pci0 dev 21 function 1 not configured
>   dwiic0 at pci0 dev 21 function 3 "Intel 500 Series I2C" rev 0x20: apic 2 
> int 30
> 
> To make it survive reboots, I added the configuration to
> `/etc/bsd.re-config`. Be careful when using this one because of the
> hardcoded DevNo.
> 
> $ cat /etc/bsd.re-config
> change 226
> y
> 21
> 3
> 0
> 
> I hope this issue can be fixed soon, but at least I now have a fully
> functional OpenBSD on my Framework laptop :)

That is a good find.  It seems we don't mask interrupts upon resume.
And the interrupt handler is written in a way such that it doesn't
necessarily acknowledge interrupts if the controller is currently
disabled, which will always be the case for controllers with no
attached devices.

Does the diff below help?


Index: dev/ic/dwiic.c
===
RCS file: /cvs/src/sys/dev/ic/dwiic.c,v
retrieving revision 1.13
diff -u -p -r1.13 dwiic.c
--- dev/ic/dwiic.c  7 Nov 2021 14:07:43 -   1.13
+++ dev/ic/dwiic.c  14 Dec 2021 10:56:37 -
@@ -153,6 +153,10 @@ dwiic_init(struct dwiic_softc *sc)
/* disable the adapter */
dwiic_enable(sc, 0);
 
+   /* disable interrupts */
+   dwiic_write(sc, DW_IC_INTR_MASK, 0);
+   dwiic_read(sc, DW_IC_CLR_INTR);
+
/* write standard-mode SCL timing parameters */
dwiic_write(sc, DW_IC_SS_SCL_HCNT, sc->ss_hcnt);
dwiic_write(sc, DW_IC_SS_SCL_LCNT, sc->ss_lcnt);



Re: Some Framework Laptops fail to resume from zzz

2021-12-13 Thread Renato Aguiar
I did some investigation over the weekend and I was able to get more
information about the problem and find a better workaround.

There are 3 devices attaching to `dwiic* at pci0':

dwiic0 at pci0 dev 21 function 0 "Intel 500 Series I2C" rev 0x20: apic 2 int 27

  I have no idea what this one is for, but it keeps sending interrupts
  after resume and that is what is causing the laptop to freeze.
  Disabling this device alone "fixes" suspend/resume for me.

dwiic1 at pci0 dev 21 function 1 "Intel 500 Series I2C" rev 0x20: apic 2 int 40

  This is for some special keyboard keys, like brightness control.

dwiic2 at pci0 dev 21 function 3 "Intel 500 Series I2C" rev 0x20: apic 2 int 30

  And this one is for touchpad.

As a workaround for now, I'm changing `dwiic* at pci*` to attach only to
touchpad, so I can have suspend/resume working without losing the touchpad.

# config -ef /bsd
ukc> find dwiic
226 dwiic* at pci* dev -1 function -1 flags 0x0
448 dwiic* at acpi0 flags 0x0
ukc> change 226
226 dwiic* at pci* dev -1 function -1 flags 0x0
change [n] y
dev [-1] ? 21
function [-1] ? 3
flags [0] ?
226 dwiic* changed
226 dwiic* at pci* dev 0x15 function 3 flags 0x0
ukc> quit

Now it only configures dwiic0 for touchpad:

  "Intel 500 Series I2C" rev 0x20 at pci0 dev 21 function 0 not configured
  "Intel 500 Series I2C" rev 0x20 at pci0 dev 21 function 1 not configured
  dwiic0 at pci0 dev 21 function 3 "Intel 500 Series I2C" rev 0x20: apic 2 int 
30

To make it survive reboots, I added the configuration to
`/etc/bsd.re-config`. Be careful when using this one because of the
hardcoded DevNo.

$ cat /etc/bsd.re-config
change 226
y
21
3
0

I hope this issue can be fixed soon, but at least I now have a fully
functional OpenBSD on my Framework laptop :)

--
Renato



Re: Some Framework Laptops fail to resume from zzz

2021-12-07 Thread Ian Darwin
> >Description:
>   There are multiple people using OpenBSD on Framework 
> (https://frame.work) laptops.
>   ...
>   Suspend appears to work: screen goes off, and power
>   light goes into normal "suspended" cycling. However, on tapping power 
> button
>   to wake up, the screen lights up, to show all the USB detaches, and 
> only two
>   lines of "reattach", usb0 and usb1. 

To anyone who is following this closely and having this issue, you can work 
around
it *temporarily* (i.e., until there's a proper fix) just by disabling the 
trackpad
driver dwiic, either in "config -ef /bsd" or in "boot -c". Of course you'll need
a USB mouse then as the trackpad won't work, but that's a small price for a 
working
laptop with suspend/resume. This has been tested on at least two laptops that 
were
having the resume issue described in the original post.



Re: Some Framework Laptops fail to resume from zzz

2021-12-07 Thread Ian Darwin
I mistakenly sent a non-MP dmesg with my report. Here is the latest snapshot
dmesg from GENERIC.MP

OpenBSD 7.0-current (GENERIC.MP) #151: Tue Dec  7 01:34:37 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16936267776 (16151MB)
avail mem = 16406986752 (15646MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x439e2000 (50 entries)
bios0: vendor INSYDE Corp. version "03.06" date 10/18/2021
bios0: Framework Laptop
acpi0 at bios0: ACPI 6.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT SSDT SSDT SSDT SSDT TPM2 SSDT NHLT SSDT 
LPIT WSMT SSDT SSDT DBGP DBG2 ECDT HPET APIC MCFG SSDT DMAR SSDT FPDT PTDT BGRT
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEGP(S4) PEGP(S4) XHCI(S4) XDCI(S4) 
HDAS(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) 
PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 4190.34 MHz, 06-8c-01
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 256KB 64b/line disabled L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 38MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.1.2.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 4190.35 MHz, 06-8c-01
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 256KB 64b/line disabled L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 3791.26 MHz, 06-8c-01
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu2: 256KB 64b/line disabled L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 3791.26 MHz, 06-8c-01
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu3: 256KB 64b/line disabled L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xc000, bus 0-255
acpiprt0 at acpi0: bus 0 (PC00)
acpiprt1 at acpi0: bus 1 (PEG0)
acpiprt2 at acpi0: bus -1 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus -1 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus -1 (RP07)
acpiprt9 at acpi0: bus -1 (RP08)
acpiprt10 at acpi0: bus -1 (RP09)
acpiprt11 at acpi0: bus -1 (RP10)
acpiprt12 at acpi0: bus -1 (RP11)
acpiprt13 at acpi0: bus -1 (RP12)
acpiprt14 at acpi0: bus -1 (RP13)
acpiprt15 at acpi0: bus -1 (RP14)
acpiprt16 at acpi0: bus -1 (RP15)
acpiprt17 at acpi0: 

Re: Some Framework Laptops fail to resume from zzz

2021-12-07 Thread Crystal Kolipe
On Tue, Dec 07, 2021 at 10:53:33AM -0500, Ian Darwin wrote:
>   Dmesg is from MP but SP behaves the same.

> dmesg:
> OpenBSD 7.0-current (GENERIC) #150: Tue Dec  7 01:26:44 MST 2021

This is SP.