Re: efiboot: allow bigger ucodes

2019-05-17 Thread Mark Kettenis
> Date: Fri, 17 May 2019 17:56:52 -0400 > From: Patrick Wildt > > Hi, > > claudio@ has a Kaby Lake that exceeds the 128 kB limit, being as big as > 190 kB. So, for him the ucode isn't being loaded. > > On EFI systems we can simply ask EFI to allocate some memory for us. > I'm not sure why

Re: efiboot: allow bigger ucodes

2019-05-17 Thread Mike Larkin
On Fri, May 17, 2019 at 05:56:52PM -0400, Patrick Wildt wrote: > Hi, > > claudio@ has a Kaby Lake that exceeds the 128 kB limit, being as big as > 190 kB. So, for him the ucode isn't being loaded. > > On EFI systems we can simply ask EFI to allocate some memory for us. > I'm not sure why this

efiboot: allow bigger ucodes

2019-05-17 Thread Patrick Wildt
Hi, claudio@ has a Kaby Lake that exceeds the 128 kB limit, being as big as 190 kB. So, for him the ucode isn't being loaded. On EFI systems we can simply ask EFI to allocate some memory for us. I'm not sure why this file is duplicated 4 times, but it looks like for efiboot this one is

Re: scheduler small changes

2019-05-17 Thread Alexandre Ratchov
On Wed, May 15, 2019 at 09:05:32AM -0500, Amit Kulkarni wrote: > > This diff survived multiple tens of kernel builds, a bsd.sp build, > bsd.rd build, a bsd.mp without these changes, userland/xenocara, a > make regress a few days ago all on 3 desktops on amd64. Ran under > all possible scenarios

Re: NSD & Unbound refusing to bind to IPv6 when anycast flag set ?

2019-05-17 Thread Job Snijders
On Fri, May 17, 2019 at 2:13 PM Stuart Henderson wrote: > On 2019/05/16 23:37, Rachel Roch wrote: > > > RFC3513 says this: > > > > > > o An anycast address must not be used as the source address of > > > an IPv6 packet. > > > > > > o An anycast address must not be assigned to an IPv6 host,

Re: NSD & Unbound refusing to bind to IPv6 when anycast flag set ?

2019-05-17 Thread Henry Bonath
To chime in here, how I have always implemented Anycast DNS is by creating additional Loopback adapters in the OS, and then using BGP or OSPF to distribute said Loopback IPs into a routing table. Each DNS server participating in Anycast would have the same IPv4 and IPv6 address configured on that

inteldrm: cleanup_done timed out (ThinkPad X250)

2019-05-17 Thread Sven M. Hallberg
Hi, Since updating my snapshot machine last night, I'm seeing the folloing. This is with one external monitor attached through the dock (DisplayPort). The "timed out" lines appear when X starts and halt it for a few minutes. Once X does come up, the error no longer appears. The last line ("FIFO

Re: scheduler small changes

2019-05-17 Thread Amit Kulkarni
On Thu, 16 May 2019 15:15:24 -0300 Martin Pieuchot wrote: > On 16/05/19(Thu) 00:08, Amit Kulkarni wrote: > > [...] > > > Regarding the choice of deriving quantum from the priority, are you sure > > > the priorities are correct? Should we keep priorities? Or if userland > > > needs priorities

Re: NSD & Unbound refusing to bind to IPv6 when anycast flag set ?

2019-05-17 Thread Stuart Henderson
On 2019/05/16 23:37, Rachel Roch wrote: > > > > RFC3513 says this: > > > > o An anycast address must not be used as the source address of > > an IPv6 packet. > > > > o An anycast address must not be assigned to an IPv6 host, that > > is, it may be assigned to an IPv6 router only. > > > > And

Re: enable pfctl to flush all rules and tables

2019-05-17 Thread Alexandr Nedvedicky
Hello Klemens, I think what you see is actually somewhat desired/expected behavior of current PF. stay tuned for explanation further below. > > Clean up: > > # ./obj/pfctl -Fa -aregress/* > 0 tables deleted. > rules cleared > 0 tables deleted. > rules cleared >