Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

2019-06-17 Thread Julian H. Stacey
Mark Linimon wrote: > On Mon, Jun 17, 2019 at 11:41:03AM +0200, Julian H. Stacey wrote: > > svn_revision 348842 > [ ...] > > /usr/src/sys/modules/sdio/../../dev/sdio/sdiob.c:68:10: fatal error: > > 'opt_cam.h' file not found > > #include "opt_cam.h" > > ^~~ > > 1 error

Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

2019-06-17 Thread Julian H. Stacey
Hi, Reference: > From: "Bjoern A. Zeeb" > Date: Mon, 17 Jun 2019 10:55:45 + "Bjoern A. Zeeb" wrote: > On 17 Jun 2019, at 10:37, Mark Linimon wrote: > > > On Mon, Jun 17, 2019 at 11:41:03AM +0200, Julian H. Stacey wrote: > >> svn_revision 348842 > > [ ...] > >>

Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

2019-06-17 Thread Bjoern A. Zeeb
On 17 Jun 2019, at 10:37, Mark Linimon wrote: On Mon, Jun 17, 2019 at 11:41:03AM +0200, Julian H. Stacey wrote: svn_revision 348842 [ ...] /usr/src/sys/modules/sdio/../../dev/sdio/sdiob.c:68:10: fatal error: 'opt_cam.h' file not found #include "opt_cam.h" ^~~ 1 error

Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

2019-06-17 Thread Mark Linimon
On Mon, Jun 17, 2019 at 11:41:03AM +0200, Julian H. Stacey wrote: > svn_revision 348842 [ ...] > /usr/src/sys/modules/sdio/../../dev/sdio/sdiob.c:68:10: fatal error: > 'opt_cam.h' file not found > #include "opt_cam.h" > ^~~ > 1 error generated. This is extremely unlikely

sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

2019-06-17 Thread Julian H. Stacey
.ctm_status src-cur 14077 .svn_revision 348842 ===> sys/modules/sdio (all) machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/dev/sdio/sdio_if.m -c awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/device_if.m -h

Re: signal 11 for 'conftest' && poudriere jails

2019-06-16 Thread Niclas Zeising
On 2019-06-17 07:32, Matthias Apitz wrote: While running poudriere jails on a very recent CURRENT: FreeBSD jet 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r349041: Sat Jun 15 07:45:13 CEST 2019 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I see messages about signal 11 for

signal 11 for 'conftest' && poudriere jails

2019-06-16 Thread Matthias Apitz
While running poudriere jails on a very recent CURRENT: FreeBSD jet 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r349041: Sat Jun 15 07:45:13 CEST 2019 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I see messages about signal 11 for 'conftest'. The uid 65534 (nobody) let me think in

Re: r349100: buildworld does not compile (ld: error: duplicate symbol: sse42_crc32c)

2019-06-16 Thread Trond Endrestøl
On Sun, 16 Jun 2019 17:49+0200, Rainer Hurling wrote: > This happens with two older cpus, Intel (Core 17-4770) and AMD (Phenom > II X6 1090T). > > Am I the only one, who observes this breakage? Thanks for any hint. No. This also happens on Intel Core i7 960. I will retry buildworld using -D

Re: r349100: buildworld does not compile (ld: error: duplicate symbol: sse42_crc32c)

2019-06-16 Thread Rainer Hurling
Am 16.06.19 um 18:33 schrieb Warner Losh: > > > On Sun, Jun 16, 2019, 9:51 AM Rainer Hurling > wrote: > > If I try to build world almost recent sources (r349100) on HEAD amd64 > (r348775), it stops with the following error: > > > [..snip..] > (cd

Re: r349100: buildworld does not compile (ld: error: duplicate symbol: sse42_crc32c)

2019-06-16 Thread Warner Losh
On Sun, Jun 16, 2019, 9:51 AM Rainer Hurling wrote: > If I try to build world almost recent sources (r349100) on HEAD amd64 > (r348775), it stops with the following error: > > > [..snip..] > (cd /usr/src/tests/sys/kern && DEPENDFILE=.depend.libkern_crc32 > NO_SUBDIR=1 make -f

r349100: buildworld does not compile (ld: error: duplicate symbol: sse42_crc32c)

2019-06-16 Thread Rainer Hurling
If I try to build world almost recent sources (r349100) on HEAD amd64 (r348775), it stops with the following error: [..snip..] (cd /usr/src/tests/sys/kern && DEPENDFILE=.depend.libkern_crc32 NO_SUBDIR=1 make -f /usr/src/tests/sys/kern/Makefile _RECURSING_PROGS=t PROG=libkern_crc32 ) echo

Re: FreeBSD CI Weekly Report 2019-06-09

2019-06-15 Thread Kristof Provost
On 15 Jun 2019, at 11:35, Kristof Provost wrote: On 12 Jun 2019, at 16:49, Li-Wen Hsu wrote: * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * Same as amd64: * sys.netinet.socket_afinet.socket_afinet_bind_zero * Others: * sys.netpfil.pf.forward.v6 *

Re: FreeBSD CI Weekly Report 2019-06-09

2019-06-15 Thread Kristof Provost
On 12 Jun 2019, at 16:49, Li-Wen Hsu wrote: * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * Same as amd64: * sys.netinet.socket_afinet.socket_afinet_bind_zero * Others: * sys.netpfil.pf.forward.v6 * sys.netpfil.pf.forward.v4 *

CTF: UEFI HTTP boot support

2019-06-14 Thread Rebecca Cran
I've been working with D Scott Phillips to test the UEFI HTTP loader code he's written, and we're now ready for wider testing. In the testing I've done I've discovered a couple of bugs in the TianoCore EDK2 firmware, so I'd appreciate any testing people can do on various different systems to

Re: building x11-wm/plasma5-kwin w/ poudriere results in out of swap space

2019-06-13 Thread Matthias Apitz
El día Thursday, June 13, 2019 a las 04:38:25PM +0800, Martin Wilke escribió: > On 2019-06-11 14:59, Matthias Apitz wrote: > >Hello, > > > >I'm build the latest port svn checkout (June 10) on r342378 with > >poudriere and (after isolating it) have the problem that building > >x11-wm/plasma5-kwin

Re: building x11-wm/plasma5-kwin w/ poudriere results in out of swap space

2019-06-13 Thread Martin Wilke
On 2019-06-11 14:59, Matthias Apitz wrote: Hello, I'm build the latest port svn checkout (June 10) on r342378 with poudriere and (after isolating it) have the problem that building x11-wm/plasma5-kwin runs reproducible out of swap during 'configure' phase: [00:00:49] Cleaning the build queue

Re: adding a syscall to libc?

2019-06-12 Thread Brooks Davis
On Sat, Jun 08, 2019 at 01:47:39PM +0200, Oliver Pinter wrote: > On Saturday, June 8, 2019, Konstantin Belousov wrote: > > > On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote: > > > Hi, > > > > > > I've started working of a copy_file_range() syscall for FreeBSD. I think > > I have the

FreeBSD CI Weekly Report 2019-06-09

2019-06-12 Thread Li-Wen Hsu
(Please send the followup discussions to freebsd-testing@ list.) FreeBSD CI Weekly Report 2019-06-09 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-06-03 to 2019-06-09. During this period, we have: * 2444 builds

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-12 Thread Baptiste Daroussin
On Tue, Jun 11, 2019 at 11:52:31AM -0700, Johannes Lundberg wrote: > Hi > > This is probably overkill but I've attached a diff that show my patches > to image.sh. It's just a hack so far to make it do what I want and not > meant as general purpose. Use the changes you need for your application. >

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-11 Thread Joseph Ward
Thank you!  I only added the mount line, but it seemed to work. On 2019-06-11 14:52, Johannes Lundberg wrote: > Hi > > This is probably overkill but I've attached a diff that show my patches > to image.sh. It's just a hack so far to make it do what I want and not > meant as general purpose. Use

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-11 Thread Johannes Lundberg
Hi This is probably overkill but I've attached a diff that show my patches to image.sh. It's just a hack so far to make it do what I want and not meant as general purpose. Use the changes you need for your application. Changes (only meant to work for building usb images on amd64 and i386) -

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-11 Thread jbwlists
I'm having the same issue with poudriere image; could you please let me know what you did to fix it? I'm assuming the image.sh you're referring to is /usr/local/share/poudriere/image.sh, but I'm not sure where the change would need to be made. Thanks in advance, Joseph On 2019-06-04 13:02,

building x11-wm/plasma5-kwin w/ poudriere results in out of swap space

2019-06-11 Thread Matthias Apitz
Hello, I'm build the latest port svn checkout (June 10) on r342378 with poudriere and (after isolating it) have the problem that building x11-wm/plasma5-kwin runs reproducible out of swap during 'configure' phase: [00:00:49] Cleaning the build queue [00:00:49] Sanity checking build queue

patch to add a Linux compatible copy_file_range(2) syscall

2019-06-09 Thread Rick Macklem
Hi, I just put a patch in phabricator that is intended to add a Linux compatible copy_file_range(2) syscall. My main interest in having this is that NFSv4.2 will know how to do file copying locally on the NFS server, saving all the reads/writes across the wire. It copies the file byte range in

Re: adding a syscall to libc?

2019-06-09 Thread Konstantin Belousov
On Sun, Jun 09, 2019 at 06:12:59AM +, Rick Macklem wrote: > Konstantin Belousov wrote: > >On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote: > >> Hi, > >> > First off, thanks Kostik for the fine explanation. I agree with Oliver that > it should > be captured somewhere like the

Re: adding a syscall to libc?

2019-06-09 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote: >> Hi, >> First off, thanks Kostik for the fine explanation. I agree with Oliver that it should be captured somewhere like the wiki. I'm no wiki guy, so hopefully someone else will do this? >> I've started

Re: adding a syscall to libc?

2019-06-08 Thread Oliver Pinter
On Saturday, June 8, 2019, Konstantin Belousov wrote: > On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote: > > Hi, > > > > I've started working of a copy_file_range() syscall for FreeBSD. I think > I have the > > kernel patched and ready for some testing. > > However, I'm confused

Re: adding a syscall to libc?

2019-06-08 Thread Konstantin Belousov
On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote: > Hi, > > I've started working of a copy_file_range() syscall for FreeBSD. I think I > have the > kernel patched and ready for some testing. > However, I'm confused about what I need to do in src/lib/libc/sys? > - Some syscalls have

adding a syscall to libc?

2019-06-07 Thread Rick Macklem
Hi, I've started working of a copy_file_range() syscall for FreeBSD. I think I have the kernel patched and ready for some testing. However, I'm confused about what I need to do in src/lib/libc/sys? - Some syscalls have little .c files, but other ones do not. When is one of these little .c

FreeBSD CI Weekly Report 2019-06-02

2019-06-05 Thread Li-Wen Hsu
(Please send the followup discussions to freebsd-testing@ list.) FreeBSD CI Weekly Report 2019-06-02 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-05-27 to 2019-06-02. During this period, we have: * 1752 builds

Re: UEFI boot broken in 13?

2019-06-05 Thread Tomoaki AOKI
On Tue, 4 Jun 2019 08:58:43 -0600 Warner Losh wrote: > On Tue, Jun 4, 2019 at 8:16 AM Warner Losh wrote: > > > > > > > On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI > > wrote: > > > >> Hi. > >> > >> Try attached patch for stand/efi/boot1/boot1.c. > >> This partially reverts r347193 and works at

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-04 Thread Johannes Lundberg
On 6/3/19 10:44 PM, Baptiste Daroussin wrote: > On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote: >> Hello List, >> >> lately I ran into a serious problem installing packages in a nanoBSD >> environment, in which the package repository server is "remotely" on site. >> The >> issue as

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-04 Thread Rodney W. Grimes
> On 04/06/2019 06:32, O. Hartmann wrote: > > As far as I know,, the package installation is performed via "chroot'ed" > > environment and somehow /dev/null is out of a sudden not accessible anymore > > while pkg tries to delegate some output to /dev/null. > > Assuming you're chroot'd to /chroot,

Re: UEFI boot broken in 13?

2019-06-04 Thread Warner Losh
On Tue, Jun 4, 2019 at 8:16 AM Warner Losh wrote: > > > On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI > wrote: > >> Hi. >> >> Try attached patch for stand/efi/boot1/boot1.c. >> This partially reverts r347193 and works at least for me. >> >> Without this, boot1.efi (bootx64.efi) forcibly boot from

Re: UEFI boot broken in 13?

2019-06-04 Thread Warner Losh
On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI wrote: > Hi. > > Try attached patch for stand/efi/boot1/boot1.c. > This partially reverts r347193 and works at least for me. > > Without this, boot1.efi (bootx64.efi) forcibly boot from > first physical HDD/SSD, even if forcibly booted from other >

FreeBSD Quarterly Status Report - First Quarter 2019

2019-06-04 Thread Edward Tomasz Napierała
FreeBSD Project Quarterly Status Report - 1st Quarter 2019 As spring leads into summer, we reflect back on what the FreeBSD project has accomplished in the first quarter of 2019. Events included FOSDEM and AsiaBSDCon, the FreeBSD Journal is now free to everyone, ASLR is available in

Re: UEFI boot broken in 13?

2019-06-04 Thread Tomoaki AOKI
Hi. Try attached patch for stand/efi/boot1/boot1.c. This partially reverts r347193 and works at least for me. Without this, boot1.efi (bootx64.efi) forcibly boot from first physical HDD/SSD, even if forcibly booted from other physical drive via BIOS (UEFI firmware) menu. Remaining parts of

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-04 Thread O. Hartmann
On Tue, 4 Jun 2019 07:44:09 +0200 Baptiste Daroussin wrote: > On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote: > > Hello List, > > > > lately I ran into a serious problem installing packages in a nanoBSD > > environment, in which the package repository server is "remotely" on site. >

Re: UEFI boot broken in 13?

2019-06-04 Thread Toomas Soome
> On 4 Jun 2019, at 04:38, Johannes Lundberg wrote: > > Hi > > I'm using poudriere-image to create usb memstick images. The images are > identical except OS version. They are tested on a laptop with 13-CURRENT > installed as only OS, having UEFI boot and root on zfs. > > 12-STABLE memstick

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-04 Thread Matthew Seaman
On 04/06/2019 06:32, O. Hartmann wrote: > As far as I know,, the package installation is performed via "chroot'ed" > environment and somehow /dev/null is out of a sudden not accessible anymore > while pkg tries to delegate some output to /dev/null. Assuming you're chroot'd to /chroot, then:

Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-03 Thread Baptiste Daroussin
On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote: > Hello List, > > lately I ran into a serious problem installing packages in a nanoBSD > environment, in which the package repository server is "remotely" on site. The > issue as documented below occurs on both 12-STABLE r348529 and

pkg: Cannot open /dev/null:No such file or directory

2019-06-03 Thread O. Hartmann
Hello List, lately I ran into a serious problem installing packages in a nanoBSD environment, in which the package repository server is "remotely" on site. The issue as documented below occurs on both 12-STABLE r348529 and CURRENT r348600 and must have been introduced shortly, since the last

Re: UEFI boot broken in 13?

2019-06-03 Thread Johannes Lundberg
On 6/3/19 7:25 PM, Rodney W. Grimes wrote: >> Hi >> >> I'm using poudriere-image to create usb memstick images. The images are >> identical except OS version. They are tested on a laptop with 13-CURRENT >> installed as only OS, having UEFI boot and root on zfs. >> >> 12-STABLE memstick boots

Re: UEFI boot broken in 13?

2019-06-03 Thread Rodney W. Grimes
> Hi > > I'm using poudriere-image to create usb memstick images. The images are > identical except OS version. They are tested on a laptop with 13-CURRENT > installed as only OS, having UEFI boot and root on zfs. > > 12-STABLE memstick boots fine with in UEFI mode. Does it actually boot via a

UEFI boot broken in 13?

2019-06-03 Thread Johannes Lundberg
Hi I'm using poudriere-image to create usb memstick images. The images are identical except OS version. They are tested on a laptop with 13-CURRENT installed as only OS, having UEFI boot and root on zfs. 12-STABLE memstick boots fine with in UEFI mode. With 13-CURRENT memstick it boots the

Re: One True Awk upgrade

2019-06-03 Thread Jamie Landeg-Jones
Warner Losh wrote: > OK. I've resolved all the diffs between the git-tree I had and what made it > into the tree. the upgrade is now complete, and I've pushed my notion of > what awk should be to the bsd-ota branch in > https://github.com/bsdimp/awk.git I'll work on folding them into upstream, >

Re: Enabling synaptics and elantech touchpads by default

2019-06-03 Thread Greg V
On June 3, 2019 11:31:21 PM GMT+03:00, Niclas Zeising wrote: >Hi! >I've created a reveiew, https://reviews.freebsd.org/D20507, to enable >synaptics and elantech touchpads by default. > >Today, these tunables needs to be set on boot for users to get full use > >of their touchpads, even when

Enabling synaptics and elantech touchpads by default

2019-06-03 Thread Niclas Zeising
Hi! I've created a reveiew, https://reviews.freebsd.org/D20507, to enable synaptics and elantech touchpads by default. Today, these tunables needs to be set on boot for users to get full use of their touchpads, even when using X. By enabling this, things like two finger scroll will work in

Re: installworld breakage r348516 -> r348572

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 9:35 PM O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Make installworld after a successful build of r348572 fails due to: > > >>> Making hierarchy > - -- > cd /usr/src; make -f

installworld breakage r348516 -> r348572

2019-06-03 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Make installworld after a successful build of r348572 fails due to: >>> Making hierarchy - -- cd /usr/src; make -f Makefile.inc1 LOCAL_MTREE= hierarchy - --- hierarchy --- cd

Re: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread David Wolfskill
On Mon, Jun 03, 2019 at 08:15:18AM -0600, Warner Losh wrote: > I just committed this as a stop-gap fix. > > Warner > Cool. I encountered the issue on my build box -- laptop was still busy with other stuff. Later, when the laptop was ready for the same update to head, I applied the change

Re: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread Warner Losh
I just committed this as a stop-gap fix. Warner On Mon, Jun 3, 2019 at 5:33 AM Andreas Nilsson wrote: > On Mon, Jun 3, 2019 at 1:27 PM David Wolfskill > wrote: > > > On Mon, Jun 03, 2019 at 01:17:44PM +0200, Andreas Nilsson wrote: > > > ... > > > > Any hints? > > > > > > > > Might this

Re: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 1:27 PM David Wolfskill wrote: > On Mon, Jun 03, 2019 at 01:17:44PM +0200, Andreas Nilsson wrote: > > ... > > > Any hints? > > > > > Might this be the same I noticed with "make packages", ie: > > diff --git a/Makefile.inc1 b/Makefile.inc1 > > index

Re: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread David Wolfskill
On Mon, Jun 03, 2019 at 01:17:44PM +0200, Andreas Nilsson wrote: > ... > > Any hints? > > Might this be the same I noticed with "make packages", ie: > diff --git a/Makefile.inc1 b/Makefile.inc1 > index 6c77c8abdb8..60ac6493c95 100644 > --- a/Makefile.inc1 > +++ b/Makefile.inc1 > @@ -888,7

Re: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 1:06 PM David Wolfskill wrote: > I see: > > ... > -- > >>> Installing everything completed on Mon Jun 3 03:48:55 PDT 2019 > -- > Mon Jun 3 03:48:55 PDT

Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread David Wolfskill
I see: ... -- >>> Installing everything completed on Mon Jun 3 03:48:55 PDT 2019 -- Mon Jun 3 03:48:55 PDT 2019 *** Creating the temporary root environment in

Re: make packages broken

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 10:40 AM Andreas Nilsson wrote: > Hello all, > > It was time for the weekly update so git gave > me: c7cdb4a80779a0451dc2c04c3d6b30769049d402 . > > It compiled fined, but when I tried to build packages I get: > make -C /usr/src PKG_VERSION=13.0.s20190603083918

make packages broken

2019-06-03 Thread Andreas Nilsson
Hello all, It was time for the weekly update so git gave me: c7cdb4a80779a0451dc2c04c3d6b30769049d402 . It compiled fined, but when I tried to build packages I get: make -C /usr/src PKG_VERSION=13.0.s20190603083918 real-packages make[5]: "/usr/obj/usr/src/amd64.amd64/toolchain-metadata.mk" line

Re: One True Awk upgrade

2019-06-02 Thread Warner Losh
On Sun, Jun 2, 2019 at 10:55 AM Warner Losh wrote: > I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a > problem, but there's a number of small differences I'm still trying > to figure out due to our... contorted history. Some of the revisions we had > in the vendor

Re: One True Awk upgrade

2019-06-02 Thread Warner Losh
On Sun, Jun 2, 2019 at 11:06 AM Shawn Webb wrote: > On Sun, Jun 02, 2019 at 10:55:41AM -0600, Warner Losh wrote: > > I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a > > problem, but there's a number of small differences I'm still trying > > to figure out due to our...

Re: Crash on very recent CURRENT if using poudriere

2019-06-02 Thread Konstantin Belousov
On Sun, Jun 02, 2019 at 07:45:34PM +0200, Kurt Jaeger wrote: > Hi! > > > > > > [panic] non-zero write count during poudriere run > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 > > > > > > > > > > Ideas on how to proceed ? > > > > > > > > Try this. > > > > > > Unfortunatly,

Re: Crash on very recent CURRENT if using poudriere

2019-06-02 Thread Kurt Jaeger
Hi! > > > > [panic] non-zero write count during poudriere run > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 > > > > > > > > Ideas on how to proceed ? > > > > > > Try this. > > > > Unfortunatly, I can no longer reproduce the crashes after the > > update of the kernel to

Re: Crash on very recent CURRENT if using poudriere

2019-06-02 Thread Konstantin Belousov
On Sun, Jun 02, 2019 at 06:48:51PM +0200, Kurt Jaeger wrote: > Hi! > > > > [panic] non-zero write count during poudriere run > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 > > > > > > Ideas on how to proceed ? > > > > Try this. > > Unfortunatly, I can no longer reproduce the

Re: One True Awk upgrade

2019-06-02 Thread Shawn Webb
On Sun, Jun 02, 2019 at 10:55:41AM -0600, Warner Losh wrote: > I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a > problem, but there's a number of small differences I'm still trying > to figure out due to our... contorted history. Some of the revisions we had > in the

One True Awk upgrade

2019-06-02 Thread Warner Losh
I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a problem, but there's a number of small differences I'm still trying to figure out due to our... contorted history. Some of the revisions we had in the vendor branch of our repo were accepted as-is, some completely, and some

Re: Crash on very recent CURRENT if using poudriere

2019-06-02 Thread Kurt Jaeger
Hi! > > [panic] non-zero write count during poudriere run > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 > > > > Ideas on how to proceed ? > > Try this. Unfortunatly, I can no longer reproduce the crashes after the update of the kernel to r348454. -- p...@opsec.eu

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-06-01 Thread Rodney W. Grimes
> rai...@ultra-secure.de wrote: > > > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > > department who is technically responsible for the service gets around > > redoing that service. > > >From my understanding from reading the bug (though it's not entirely clear > in this

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-31 Thread Jamie Landeg-Jones
rai...@ultra-secure.de wrote: > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > department who is technically responsible for the service gets around > redoing that service. >From my understanding from reading the bug (though it's not entirely clear in this thread), this

Re: Crash on very recent CURRENT if using poudriere

2019-05-31 Thread Konstantin Belousov
On Fri, May 31, 2019 at 12:49:11PM +0200, Kurt Jaeger wrote: > Hi! > > [panic] non-zero write count during poudriere run > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 > > Ideas on how to proceed ? Try this. diff --git a/sys/fs/nullfs/null_vnops.c b/sys/fs/nullfs/null_vnops.c index

Crash on very recent CURRENT if using poudriere

2019-05-31 Thread Kurt Jaeger
Hi! [panic] non-zero write count during poudriere run https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 Ideas on how to proceed ? -- p...@opsec.eu+49 171 3101372One year to go ! ___ freebsd-current@freebsd.org

Re: Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Johannes Lundberg
On 5/30/19 1:25 PM, Miroslav Lachman wrote: > Greg Rivers wrote on 2019/05/30 18:37: > > [...] > >>> Do I have something weird in my setup causing this? I don't recall ever >>> having this issue when not using failover lagg. Running recent >>> 13-CURRENT. >>> >> I think there's a (unknown?)

Re: Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Poul-Henning Kamp
This sounds like handbook material ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.

Re: Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Miroslav Lachman
Greg Rivers wrote on 2019/05/30 18:37: [...] Do I have something weird in my setup causing this? I don't recall ever having this issue when not using failover lagg. Running recent 13-CURRENT. I think there's a (unknown?) problem that makes lagg(4) incompatible with bridge(4). I've never been

Re: Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Johannes Lundberg
On 5/30/19 12:37 PM, Cy Schubert wrote: > In message <85a5bf45-231e-1bb4-4c26-677e414af...@freebsd.org>, Johannes > Lundber > g writes: >> On 5/30/19 9:37 AM, Greg Rivers wrote: >>> On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: Hi I have a bridge and an

Re: Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Cy Schubert
In message <85a5bf45-231e-1bb4-4c26-677e414af...@freebsd.org>, Johannes Lundber g writes: > > On 5/30/19 9:37 AM, Greg Rivers wrote: > > On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: > >> Hi > >> > >> I have a bridge and an ethernet/wifi lagg failover like this: > >> > >> #

Re: Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Johannes Lundberg
On 5/30/19 9:37 AM, Greg Rivers wrote: > On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: >> Hi >> >> I have a bridge and an ethernet/wifi lagg failover like this: >> >> # First define all cloned interfaces >> cloned_interfaces="bridge0 lagg0" >> >> # bhyve bridge >>

Re: Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Greg Rivers
On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: > Hi > > I have a bridge and an ethernet/wifi lagg failover like this: > > # First define all cloned interfaces > cloned_interfaces="bridge0 lagg0" > > # bhyve bridge > ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" > > #

Inconsistent behavior with wpa / devd / network interfaces

2019-05-30 Thread Johannes Lundberg
Hi I have a bridge and an ethernet/wifi lagg failover like this: # First define all cloned interfaces cloned_interfaces="bridge0 lagg0" # bhyve bridge ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" # Ethernet/WiFi failvoer ifconfig_em0="up" wlans_iwm0="wlan0" ifconfig_wlan0="WPA up"

Re: FreeBSD contrib/one-true-awk now it's own fork?

2019-05-30 Thread Warner Losh
On Thu, May 30, 2019, 5:48 AM Jamie Landeg-Jones wrote: > contrib/one-true-awk hasn't been synced with the official src maintained > by Brian Kernighan for a number of years, though in that time a number > of FreeBSD changes have been made, independently of the official branch. > > Is this the

FreeBSD contrib/one-true-awk now it's own fork?

2019-05-30 Thread Jamie Landeg-Jones
contrib/one-true-awk hasn't been synced with the official src maintained by Brian Kernighan for a number of years, though in that time a number of FreeBSD changes have been made, independently of the official branch. Is this the official policy now? There are some useful bugfixes and changes out

[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

2019-05-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Kubilay Kocak changed: What|Removed |Added Keywords|patch |needs-patch

[Bug 197921] [patch] [sched] Allow non-migratable threads to bind to their current CPU.

2019-05-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from

Re: impossible to installkernel without a compiler?

2019-05-29 Thread Warner Losh
There's already a list of targets to except... It's hard to have an opt-in list, however :( Warner On Wed, May 29, 2019 at 4:26 AM Andriy Gapon wrote: > > Just want to note that the problem extends to doing such things as "make > aliases" in /etc/mail on a system installed without a compiler.

Built in database for tcsh (dbcsh?)

2019-05-29 Thread abhja kaanlani
Something that would creating a nice messaging system like in c++ or maybe objc that would be transparent to hardware to end user I have some sample code of a mdmdbt on https://unidef.net Sent from my iPhone ___ freebsd-current@freebsd.org mailing

Re: impossible to installkernel without a compiler?

2019-05-29 Thread Andriy Gapon
Just want to note that the problem extends to doing such things as "make aliases" in /etc/mail on a system installed without a compiler. I guess it would be nice if COMPILER_TYPE was enforced only when a compiler is actually needed. make can be used for more things than building C code. --

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-28 Thread Xin LI
On Mon, May 27, 2019 at 7:08 AM wrote: > Hello, > I wanted to discuss about bug 231768 a bit: it is about keeping > COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. > > The patch attached for the bug is for disabling these options by > default, following a few reasons which I'm going

Re: FreeBSD and Coreboot

2019-05-28 Thread Edward Napierala
On Tue, 28 May 2019 at 12:17, Eric McCorkle wrote: [..] > > Now that the loader supports a ram disk, we are almost to something > > useful... but yea, almost and crummy often go hand in hand. > > This is looking out ahead of my current roadmap, but if you were to do a > kernel as the coreboot

Re: FreeBSD and Coreboot

2019-05-28 Thread Rodney W. Grimes
> On 5/28/19 12:46 AM, Warner Losh wrote: > > > > > > On Mon, May 27, 2019, 10:44 PM Nathan Whitehorn > > wrote: > > > > > > > > On 2019-05-27 19:14, Warner Losh wrote: > > > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > >

Re: FreeBSD and Coreboot

2019-05-28 Thread Eric McCorkle
On 5/28/19 12:46 AM, Warner Losh wrote: > > > On Mon, May 27, 2019, 10:44 PM Nathan Whitehorn > wrote: > > > > On 2019-05-27 19:14, Warner Losh wrote: > > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > mailto:nwhiteh...@freebsd.org>> > >

Re: FreeBSD and Coreboot

2019-05-28 Thread Piotr Kubaj
I have been running coreboot on many boards with FreeBSD for a few years now. I've been getting mixed results. E.g. on ASUS F2A85-M there's no fan control in coreboot so the OS must do it itself and FreeBSD doesn't support it. After running it for some time, my CPU eventually burned...

Re: FreeBSD and Coreboot

2019-05-27 Thread Warner Losh
On Mon, May 27, 2019, 10:44 PM Nathan Whitehorn wrote: > > > On 2019-05-27 19:14, Warner Losh wrote: > > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > > wrote: > > > >> > >> On 2019-05-27 15:50, Eric McCorkle wrote: > >>> On 5/27/19 5:53 PM, Edward Napierala wrote: > On Mon, 27 May 2019

Re: FreeBSD and Coreboot

2019-05-27 Thread Nathan Whitehorn
On 2019-05-27 19:14, Warner Losh wrote: > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > wrote: > >> >> On 2019-05-27 15:50, Eric McCorkle wrote: >>> On 5/27/19 5:53 PM, Edward Napierala wrote: On Mon, 27 May 2019 at 16:14, Eric McCorkle >> wrote: [..] > My plan is

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Warner Losh
On Mon, May 27, 2019, 8:23 PM Enji Cooper wrote: > > On May 27, 2019, at 7:20 PM, Warner Losh wrote: > > On Mon, May 27, 2019, 6:49 PM Enji Cooper wrote: > >> >> > On May 27, 2019, at 08:27, rai...@ultra-secure.de wrote: >> > >> > Am 2019-05-27 17:05, schrieb Conrad Meyer: >> >> Hi Rainier, >>

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Enji Cooper
> On May 27, 2019, at 7:20 PM, Warner Losh wrote: > > On Mon, May 27, 2019, 6:49 PM Enji Cooper > wrote: > > > On May 27, 2019, at 08:27, rai...@ultra-secure.de > > wrote: > > > > Am 2019-05-27 17:05, schrieb Conrad Meyer: > >>

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Warner Losh
On Mon, May 27, 2019, 6:49 PM Enji Cooper wrote: > > > On May 27, 2019, at 08:27, rai...@ultra-secure.de wrote: > > > > Am 2019-05-27 17:05, schrieb Conrad Meyer: > >> Hi Rainier, > >> On Mon, May 27, 2019 at 7:47 AM wrote: > >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until

Re: FreeBSD and Coreboot

2019-05-27 Thread Warner Losh
On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn wrote: > > > On 2019-05-27 15:50, Eric McCorkle wrote: > > On 5/27/19 5:53 PM, Edward Napierala wrote: > >> On Mon, 27 May 2019 at 16:14, Eric McCorkle > wrote: > >> > >> [..] > >> > >>> My plan is roughly this: > >>> > >>> * Refurbish the GRUB

Re: FreeBSD and Coreboot

2019-05-27 Thread Nathan Whitehorn
On 2019-05-27 15:50, Eric McCorkle wrote: > On 5/27/19 5:53 PM, Edward Napierala wrote: >> On Mon, 27 May 2019 at 16:14, Eric McCorkle wrote: >> >> [..] >> >>> My plan is roughly this: >>> >>> * Refurbish the GRUB port, get it working again in QEMU (possibly on one >>> of my machines), also

Re: FreeBSD and Coreboot

2019-05-27 Thread Eric McCorkle
On 5/27/19 11:13 AM, Eric McCorkle wrote: > My plan is roughly this: > > * Refurbish the GRUB port, get it working again in QEMU (possibly on one > of my machines), also possibly push a patch to GRUB to use the keybufs > mechanism to pass in GELI keys. I managed to get the grub2 port compiling

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Enji Cooper
> On May 27, 2019, at 08:27, rai...@ultra-secure.de wrote: > > Am 2019-05-27 17:05, schrieb Conrad Meyer: >> Hi Rainier, >> On Mon, May 27, 2019 at 7:47 AM wrote: >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the >>> department who is technically responsible for the service

Re: FreeBSD and Coreboot

2019-05-27 Thread Eric McCorkle
On 5/27/19 5:53 PM, Edward Napierala wrote: > On Mon, 27 May 2019 at 16:14, Eric McCorkle wrote: > > [..] > >> My plan is roughly this: >> >> * Refurbish the GRUB port, get it working again in QEMU (possibly on one >> of my machines), also possibly push a patch to GRUB to use the keybufs >>

  1   2   3   4   5   6   7   8   9   10   >