> On Jul 14, 2017, at 10:29 PM, Mike Larkin wrote:
>
> On Fri, Jul 14, 2017 at 03:39:25PM -0700, Nick Briggs wrote:
>>
>>> Synopsis: sys/arch/i386/i386/bios.c won't compile if NACPI ==0 and
>>> NAPM>0
>>> Category: system
>>> Environment:
>> System : OpenBSD 6.1
>> D
On Fri, Jul 14, 2017 at 03:39:25PM -0700, Nick Briggs wrote:
>
> > Synopsis: sys/arch/i386/i386/bios.c won't compile if NACPI ==0 and
> > NAPM>0
> > Category: system
> > Environment:
>System : OpenBSD 6.1
>Details : OpenBSD 6.1-stable (PIGEON) #5: Thu Jul 13 17:
> Synopsis: sys/arch/i386/i386/bios.c won't compile if NACPI ==0 and NAPM>0
> Category: system
> Environment:
System : OpenBSD 6.1
Details : OpenBSD 6.1-stable (PIGEON) #5: Thu Jul 13 17:09:51 PDT
2017
briggs@pigeon:/usr/obj/sys/arch/i386/c
On Thu, Jul 13, 2017 at 09:15:24PM +0200, Mark Kettenis wrote:
> I have an x1 gen3 as well, and it resumes reliably as far as I can
> tell. Can't rule out that there are bugs in the new inteldrm code,
> but there are also some fresh network stack locking diffs in the tree
> that created some fallo
On Fri, Jul 14, 2017 at 08:19:37AM BST, Paul de Weerd wrote:
> On Thu, Jul 13, 2017 at 09:30:27PM +0100, Stuart Henderson wrote:
> | > > Section "Device"
> | > >Identifier "Intel Graphics"
> | > >Driver "intel"
> | > > EndSection
> | >
> | > Is this regression important enough to hol
On Thu, Jul 13, 2017 at 09:30:27PM +0100, Stuart Henderson wrote:
| > > Section "Device"
| > >Identifier "Intel Graphics"
| > >Driver "intel"
| > > EndSection
| >
| > Is this regression important enough to hold off the commit of the
| > driver selection change until we have a better
