On Tue, 25 Jun 2019 at 13:50, Jason Tubnor wrote:
>
> On Tue, 25 Jun 2019 at 12:25, Mike Larkin wrote:
>
>> On Mon, Jun 24, 2019 at 07:16:20PM -0700, guent...@openbsd.org wrote:
>>
>> > where it loaded the LAPIC register into %ecx and then tested that
>> value;
>> > now it combines them and does
On Tue, 25 Jun 2019 at 12:25, Mike Larkin wrote:
> On Mon, Jun 24, 2019 at 07:16:20PM -0700, guent...@openbsd.org wrote:
>
> > According to objdump -d, that's:
> > f7 04 25 00 d3 d1 81testl $0x1000,0x81d1d300
> > 00 10 00 00
> > 74 08 je
> > f3 90
On Mon, Jun 24, 2019 at 07:16:20PM -0700, guent...@openbsd.org wrote:
> On Mon, 24 Jun 2019, Jason Tubnor wrote:
> > Following daily snapshots, I have hit a bug that was introduced between
> > 6.5-current #61 and 6.5-current #66 (not sure if it was related to the LLVM
> > upgrade).
> >
> > Referen
On Mon, 24 Jun 2019, Jason Tubnor wrote:
> Following daily snapshots, I have hit a bug that was introduced between
> 6.5-current #61 and 6.5-current #66 (not sure if it was related to the LLVM
> upgrade).
>
> Reference system is bhyve on FreeBSD 11.2 with an OpenBSD guest. #61 boots
> fine and ru
On Tue, Jun 25, 2019 at 11:03:24AM +1000, Jason Tubnor wrote:
> Hi,
>
> Following daily snapshots, I have hit a bug that was introduced between
> 6.5-current #61 and 6.5-current #66 (not sure if it was related to the LLVM
> upgrade).
>
> Reference system is bhyve on FreeBSD 11.2 with an OpenBSD g
Hi,
Following daily snapshots, I have hit a bug that was introduced between
6.5-current #61 and 6.5-current #66 (not sure if it was related to the LLVM
upgrade).
Reference system is bhyve on FreeBSD 11.2 with an OpenBSD guest. #61 boots
fine and runs as expected. However, #66 get to the followi
