Re: [UEFI] Boot issues on some UEFI implementations

On Wed, 25 Jul 2018 07:30:32 -0700 (PDT) "Rodney W. Grimes" wrote: > > > On 25 Jul 2018, at 12:10, O. Hartmann wrote: > > > > > > On Wed, 25 Jul 2018 11:46:07 +0300 > > > Toomas Soome wrote: > > > > > >>> On 25 Jul 2018, at 10:59, O. Hartmann wrote: > > >>> > > >>> On Tue, 24 Jul 2018 08:

Re: [UEFI] Boot issues on some UEFI implementations

> On 26 Jul 2018, at 16:58, O. Hartmann wrote: > > On Wed, 25 Jul 2018 07:30:32 -0700 (PDT) > "Rodney W. Grimes" > wrote: > On 25 Jul 2018, at 12:10, O. Hartmann wrote: On Wed, 25 Jul 2018 11:46:07 +0300 Toomas Soome wrote: >>>

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

On 7/25/18 6:52 PM, Mark Millard wrote: > > > On 2018-Jul-25, at 2:10 PM, Mark Millard wrote: > > > >> On 2018-Jul-25, at 10:09 AM, Mark Millard wrote: >> >>> On 2018-Jul-25, at 8:39 AM, John Baldwin wrote: >>> On 7/24/18 11:39 PM, Mark Millard wrote: > On 2018-Jul-24, at 10:32 PM,

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

On 2018-Jul-26, at 10:21 AM, John Baldwin wrote: > On 7/25/18 6:52 PM, Mark Millard wrote: >> >> >> On 2018-Jul-25, at 2:10 PM, Mark Millard wrote: >> >> >> >>> On 2018-Jul-25, at 10:09 AM, Mark Millard wrote: >>> On 2018-Jul-25, at 8:39 AM, John Baldwin wrote: > On 7/24

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

On 7/26/18 10:55 AM, Mark Millard wrote: > > > On 2018-Jul-26, at 10:21 AM, John Baldwin wrote: > >> On 7/25/18 6:52 PM, Mark Millard wrote: >>> >>> >>> On 2018-Jul-25, at 2:10 PM, Mark Millard wrote: >>> >>> >>> On 2018-Jul-25, at 10:09 AM, Mark Millard wrote: > On 2018-Jul-25,

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

On 7/16/18 11:27 PM, Mark Millard wrote: > On 2018-Jul-1, at 6:34 AM, Mark Millard wrote: > >> My brain finally engaged for showing exactly what files are included >> for the gcc builds: the .meta files include that information explicitly >> (along with other files that are opened during the oper

panic in btsocks_l2cap_sockets_mtx @ ng_btsocket_2cap.c:2438

Got this panic while trying to register the bluetooth mouse. See the screenshot: https://imgur.com/a/RXZRIn9 r336271 Yuri ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send a

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

On 2018-Jul-26, at 11:21 AM, John Baldwin wrote: > On 7/26/18 10:55 AM, Mark Millard wrote: >> . . . > > Yes, but the -E from above was when compiled with external GCC and it didn't > change > _Atomic(int). Here's part of the source of bar.c: > > #include > #include > > struct foo { >

Changes to sysctl values

I use devel/py-sysctl in some scripts to get values, using a recent 12-current (r336728) I see at least two values that get a different value type than on 11-stable. Same version of python and port. I have 12-current running in a bhyve on an 11-stable host. Is there a recent change to sysctl call

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

On 2018-Jul-26, at 6:14 PM, Mark Millard wrote: > On 2018-Jul-26, at 11:21 AM, John Baldwin wrote: > >> On 7/26/18 10:55 AM, Mark Millard wrote: >>> . . . >> >> Yes, but the -E from above was when compiled with external GCC and it didn't >> change >> _Atomic(int). Here's part of the sourc

Re: Changes to sysctl values

On Thu, Jul 26, 2018 at 8:52 PM, Shane Ambler wrote: > I use devel/py-sysctl in some scripts to get values, using a recent > 12-current (r336728) I see at least two values that get a different > value type than on 11-stable. Same version of python and port. > ... Hi Shane, At some point, new sys

Re: [UEFI] Boot issues on some UEFI implementations

On Thu, 26 Jul 2018 19:23:43 +0300 Toomas Soome wrote: (reply inline/at the end) > > On 26 Jul 2018, at 16:58, O. Hartmann wrote: > > > > On Wed, 25 Jul 2018 07:30:32 -0700 (PDT) > > "Rodney W. Grimes" > > wrote: > On 25 Jul 2018, at 12:10, O.

Re: [UEFI] Boot issues on some UEFI implementations

> On 27 Jul 2018, at 08:46, O. Hartmann wrote: > > On Thu, 26 Jul 2018 19:23:43 +0300 > Toomas Soome wrote: > > (reply inline/at the end) > > >>> On 26 Jul 2018, at 16:58, O. Hartmann wrote: >>> >>> On Wed, 25 Jul 2018 07:30:32 -0700 (PDT) >>> "Rodney W. Grimes" >>

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

On 2018-Jul-26, at 9:06 PM, Mark Millard wrote: > On 2018-Jul-26, at 6:14 PM, Mark Millard wrote: > >> On 2018-Jul-26, at 11:21 AM, John Baldwin wrote: >> >>> On 7/26/18 10:55 AM, Mark Millard wrote: . . . >>> >>> Yes, but the -E from above was when compiled with external GCC and it >>