Re: ACPI Error: No handler for Region [ECOR]

2018-11-20 Thread Ben Widawsky
On 18-11-20 11:28:56, Ben Widawsky wrote: > On 18-11-20 14:09:08, Jung-uk Kim wrote: > > On 18. 11. 20., Charlie Li wrote: > > > Somewhere between r340491 and r340650, probably starting from r340595, > > > my ThinkPad W550s started spewing these messages repeatedly in the > > > system log since boo

Re: ACPI Error: No handler for Region [ECOR]

2018-11-20 Thread Ben Widawsky
On 18-11-20 14:09:08, Jung-uk Kim wrote: > On 18. 11. 20., Charlie Li wrote: > > Somewhere between r340491 and r340650, probably starting from r340595, > > my ThinkPad W550s started spewing these messages repeatedly in the > > system log since boot: > > > > Nov 20 09:35:19 ardmore kernel: ACPI Err

Re: ACPI Error: No handler for Region [ECOR]

2018-11-20 Thread Jung-uk Kim
On 18. 11. 20., Charlie Li wrote: > Somewhere between r340491 and r340650, probably starting from r340595, > my ThinkPad W550s started spewing these messages repeatedly in the > system log since boot: > > Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR] > (0xf8000366230

Re: [regression] drm-stable-kmod doesn't work in i386 jail on amd64 host

2018-11-20 Thread Jan Beich
Jan Beich writes: > Jan Beich writes: > >> I often test Firefox on 10.4 i386 and sometimes play games via Wine. >> Both require working OpenGL for COMPAT_FREEBSD32. My GPU is Skylake >> which worked fine a few weegs ago i.e., before r338990. >> >> Any clue? > > I've opened https://github.com/Fre

ACPI Error: No handler for Region [ECOR]

2018-11-20 Thread Charlie Li
Somewhere between r340491 and r340650, probably starting from r340595, my ThinkPad W550s started spewing these messages repeatedly in the system log since boot: Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR] (0xf80003662300) [EmbeddedControl] (20181031/evregion-288) N

Re: Devd / devmatch(8) -- netif race 12-RC1

2018-11-20 Thread Bjoern A. Zeeb
On 20 Nov 2018, at 8:17, dan_parte...@rdsor.ro wrote: No, that's not what's happening. wlan0 isn't racing anything, because it's no longer listed in ifconfig But when is created lagg0 ? Acording rc output on screen , creation of cloned interface lagg0 takes place before wlan0 is created. The

Re: Panic on kern_event.c

2018-11-20 Thread Sylvain GALLIANO
No issue using patched kernel on 2 servers (under stress test since +2 hours), Thanks ! Le mar. 20 nov. 2018 à 07:45, Mark Johnston a écrit : > On Mon, Nov 19, 2018 at 10:26:51AM +0100, Sylvain GALLIANO wrote: > > With this latest patch, after stressing syslog-ng few minutes, it do not > > log

Re: Devd / devmatch(8) -- netif race 12-RC1

2018-11-20 Thread dan_partelly
No, that's not what's happening. wlan0 isn't racing anything, because it's no longer listed in ifconfig But when is created lagg0 ? Acording rc output on screen , creation of cloned interface lagg0 takes place before wlan0 is created. Then this means SIOCLAGPORT will fail with Invalid argume