/usr/doc can not be build neither can it be installed

2018-12-18 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello FreeBSD users out there. My last build and update of /usr/doc was end of May 2017; since then any attempt building the doc from /usr/doc failed on 12-CURRENT to 12-STABLE and now on 13-CURRENT. I believe all the required ports (following

Re: The future of ZFS in FreeBSD

2018-12-18 Thread Enji Cooper
Hello Matthew, I appreciate the long write up, as someone who still uses FreeBSD ZFS on my NAS box and knowing some of the history with ZFS on *Solaris, etc. Something like this was bound to happen with post the Oracle buyout. > On Dec 18, 2018, at 10:49 PM, Matthew Macy wrote: > > The

The future of ZFS in FreeBSD

2018-12-18 Thread Matthew Macy
The sources for FreeBSD's ZFS support are currently taken directly from Illumos with local ifdefs to support the peculiarities of FreeBSD where the Solaris Portability Layer (SPL) shims fall short. FreeBSD has regularly pulled changes from Illumos and tried to push back any bug fixes and new

Re: possible POLA violation for NFS server to make it Linux compatible

2018-12-18 Thread Conrad Meyer
On Tue, Dec 18, 2018 at 5:07 PM Rick Macklem wrote: > The change to make the FreeBSD NFSv4 server use vfs.nfsd.nfs_privport is > trivial > and I think being compatible with Linux is important (I see it as the defacto > standard NFS implementation these days). > > What do others think I should

possible POLA violation for NFS server to make it Linux compatible

2018-12-18 Thread Rick Macklem
It was my understanding that the NFSv4 working group believed that the requirement for the NFSv4 client to use a priviledged port# (< 1024) should not exist. As such, I coded the server to ignore the vfs.nfsd.nfs_privport sysctl and allow the mount for NFSv4. PR#234106 has reported this as a

Re: 12.0 - (zpool upgrade ) /bootpool/boot/* new location for /boot/* ?

2018-12-17 Thread John Baldwin
On 12/14/18 4:45 PM, Bruce Cantrall wrote: > Hi, First time poster. > Did the location for the files in /boot move to /bootpool/boot but the zpool > upgrade did not know this in 12.0? > > # uname -a > FreeBSD filestore1b.phishline.com 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 > GENERIC amd64 >

Re: Ports build fails on 13-CURRENT r341690

2018-12-15 Thread Yasuhiro KIMURA
From: Justin Hibbits Subject: Re: Ports build fails on 13-CURRENT r341690 Date: Wed, 12 Dec 2018 10:37:25 -0600 > I see the exact same problem on one of my powerpc64 machines (a > P5020-based machine). I see it intermittently on my POWER9, so thought > it was a race condition, but it's 100%

12.0 - (zpool upgrade ) /bootpool/boot/* new location for /boot/* ?

2018-12-14 Thread miltonott
On Sat Dec 15 00:45:35 UTC 2018 Bruce Cantrall wrote: > Did the location for the files in /boot move to /bootpool/boot but the zpool > upgrade did not know this in 12.0? O right and honourable member, this puzzles me. Moving forward I will be researching:

12.0 - (zpool upgrade ) /bootpool/boot/* new location for /boot/* ?

2018-12-14 Thread Bruce Cantrall
Hi, First time poster. Did the location for the files in /boot move to /bootpool/boot but the zpool upgrade did not know this in 12.0? # uname -a FreeBSD filestore1b.phishline.com 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC amd64 # zpool upgrade zroot This system supports ZFS pool

vnet_alloc: panic: Memory modified after free 0xfffffe002efc8ed0(8) val=deadc0df

2018-12-14 Thread Andriy Gapon
I wonder if people are aware of this issue and if anyone is looking into it. I got notified about it by Jenkins after an unrelated commit (ichwd). panic: Memory modified after free 0xfe002efc8ed0(8) val=deadc0df @ 0xfe002efc8ed0 11:51:33 cpuid = 0 11:51:33 time = 1544788293 11:51:33

Re: src committer please

2018-12-14 Thread rb
Hi, > On 14 Dec 2018, at 00:03, Cy Schubert wrote: > > Have you tried -CURRENT? Yes, as noted in my update to the bug yesterday. Problem is still there, patch still applies and workaround still works. > --- > Sent using a tiny phone keyboard. > Apologies for any typos and autocorrect. >

/usr/doc: make fails: parser error : Failure to process ...

2018-12-14 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'm loosing hair over trying over and over building the FreeBSD documentation from /usr doc via cd /usr/doc ; make update ; make all The tree of /usr/doc is at Revision: 52685 and taken from URL: https://svn.freebsd.org/doc/head. I always face

Re: src committer please

2018-12-13 Thread Greg 'groggy' Lehey
On Thursday, 13 December 2018 at 13:07:54 +, Bob Bishop wrote: > Hi, > > Please could somebody take a look at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 > > It???s been open for over a year with a patch that solves the problem. > > Failing to install out of the box on

Re: Whine: "Could not open /dev/crypto: No such file or directory"

2018-12-13 Thread Jung-uk Kim
On 18. 12. 13., Yuri Pankov wrote: > David Wolfskill wrote: >> After update from r341844 to r342042, I see the above-cited "whine" when >> I attempt to use an SSH client on the upgraded machine.  SSH client >> function seems OK, so the message is (apparently) merely annoying: >> >>

Re: enabling inode hashes results in kernel panics

2018-12-13 Thread Kirk McKusick
As the person resposible for ading the inode check-hashes, sorry for the problems that they are causing you. Gary, I may want your crash dumps and the core.txt files, but let me do some preliminary investigation of fsck to see if I can figure out why it is failing to fix the inode check-hashes.

RE: src committer please

2018-12-13 Thread Cy Schubert
Have you tried -CURRENT? --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -Original Message- From: Bob Bishop Sent: 13/12/2018

Re: WITH_META_MODE: any effect? Tree built twice!

2018-12-13 Thread Simon J. Gerraty
O. Hartmann wrote: > I'm able to reproduce this behaviour easily: make cleanworld; kldload filemon > (if not > already loaded); make buildworld buildkernel Why are you doing cleanworld? > After the build has finished, install everything accordingly and reboot. Then > kldload > filemon and

Re: WITH_META_MODE: any effect? Tree built twice!

2018-12-13 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Wed, 12 Dec 2018 16:25:56 -0800 "Simon J. Gerraty" schrieb: Hello, thanks for your resonse. > O. Hartmann wrote: > > delete-old|-libs afterwards, I started again a build (filemon loaded!). > > And, surprise, > > surprise, compilation of

Re: enabling inode hashes results in kernel panics

2018-12-13 Thread Gary Jennejohn
On Thu, 13 Dec 2018 07:45:36 -0800 Cy Schubert wrote: > In message <20181213113925.5f100...@ernst.home>, Gary Jennejohn writes: > > On Thu, 13 Dec 2018 10:47:13 +0100 > > Gary Jennejohn wrote: > > > > > I just had two panics as a result of enabling inode hashes on a > > > file system

Re: enabling inode hashes results in kernel panics

2018-12-13 Thread Cy Schubert
In message <20181213113925.5f100...@ernst.home>, Gary Jennejohn writes: > On Thu, 13 Dec 2018 10:47:13 +0100 > Gary Jennejohn wrote: > > > I just had two panics as a result of enabling inode hashes on a > > file system yesterday when I had to run fsck on it. > > > > The filesystem showed no

Re: Whine: "Could not open /dev/crypto: No such file or directory"

2018-12-13 Thread Yuri Pankov
David Wolfskill wrote: After update from r341844 to r342042, I see the above-cited "whine" when I attempt to use an SSH client on the upgraded machine. SSH client function seems OK, so the message is (apparently) merely annoying: freebeast(13.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org

Re: nda(4) does not work (reliably) in VMware Workstation

2018-12-13 Thread Chuck Tuffli
On Sun, Dec 9, 2018 at 3:50 PM Chuck Tuffli wrote: > On Sun, Dec 9, 2018 at 3:43 PM Yuri Pankov wrote: > >> Chuck Tuffli wrote: >> > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov > > > wrote: >> > >> > Hi, >> > >> > Running -HEAD in VMware Workstation 15.0.2 VM.

src committer please

2018-12-13 Thread Bob Bishop
Hi, Please could somebody take a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 It’s been open for over a year with a patch that solves the problem. Failing to install out of the box on commodity HP kit is not a good look. Thanks -- Bob Bishop r...@gid.co.uk

Whine: "Could not open /dev/crypto: No such file or directory"

2018-12-13 Thread David Wolfskill
After update from r341844 to r342042, I see the above-cited "whine" when I attempt to use an SSH client on the upgraded machine. SSH client function seems OK, so the message is (apparently) merely annoying: freebeast(13.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org 13.0-CURRENT FreeBSD

Re: enabling inode hashes results in kernel panics

2018-12-13 Thread Gary Jennejohn
On Thu, 13 Dec 2018 10:47:13 +0100 Gary Jennejohn wrote: > I just had two panics as a result of enabling inode hashes on a > file system yesterday when I had to run fsck on it. > > The filesystem showed no problems at all yesterday, the problem > didn't appear until I accessed it today. > >

enabling inode hashes results in kernel panics

2018-12-13 Thread Gary Jennejohn
I just had two panics as a result of enabling inode hashes on a file system yesterday when I had to run fsck on it. The filesystem showed no problems at all yesterday, the problem didn't appear until I accessed it today. NOTE that my fsck was installed from r341840 yesterday morning, so it

Re: head -r341836 (jump to clang 7): amd64 -> armv7 cross build failed: ld: error: unable to find library -lh_csu

2018-12-12 Thread Li-Wen Hsu
On Thu, Dec 13, 2018 at 3:25 AM Mark Millard via freebsd-toolchain wrote: > Looks like this might have been from a race condition or some such. > Rerunning the meta-mode build again had no such problem and completed. It is also happening in clean build, I've filed a PR about this:

Re: WITH_META_MODE: any effect? Tree built twice!

2018-12-12 Thread Simon J. Gerraty
O. Hartmann wrote: > delete-old|-libs afterwards, I started again a build (filemon loaded!). And, > surprise, > surprise, compilation of all the long-haul taking LLVM/CLANG stuff starts > again! That is > not funny. If you have META_MODE enabled -dM will tell you if meta_oodate decided the

Re: r111 build error

2018-12-12 Thread Ed Maste
On Wed, 12 Dec 2018 at 10:19, Ed Maste wrote: > > While we could take this to > root cause I think the most expedient fix is probably just to check > for evidence of clang 6 in the object tree, and rm the .depend files > and objects if found. A patch implementing this is available for review in

Re: head -r341836 (jump to clang 7): amd64 -> armv7 cross build failed: ld: error: unable to find library -lh_csu

2018-12-12 Thread Mark Millard
On 2018-Dec-11, at 17:27, Mark Millard wrote: > [This was after amd64 updating to -r341836 successfully ( from -r341766 ). > The below was a meta-mode cross build, also going from -r341766 to > -r341836 .] > > # >

Re: cannot build i386 12.0-RELEASE kernel on -current

2018-12-12 Thread Enji Cooper
Hi Henry, > On Dec 12, 2018, at 8:29 AM, Henry Vogt wrote: > > Hi, > > my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok for amd64, > world for i386 ok, but fails 'make buildkernel' for i386: > > -- snip > > ... > > --- if_vte.o --- >

Re: cannot build i386 12.0-RELEASE kernel on -current

2018-12-12 Thread Ian Lepore
On Wed, 2018-12-12 at 19:33 +0300, Yuri Pankov wrote: > Henry Vogt wrote: > > > > Hi, > > > > my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok > > for amd64, world for i386 ok, but fails 'make buildkernel' for > > i386: > > > > -- snip > > > > ... > > > > --- if_vte.o --- >

Re: cannot build i386 12.0-RELEASE kernel on -current

2018-12-12 Thread Henry Vogt
Dear Yuri, Am 12.12.18 um 17:33 schrieb Yuri Pankov: > Henry Vogt wrote: >> Hi, >> >> my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok for >> amd64, world for i386 ok, but fails 'make buildkernel' for i386: >> >> -- snip >> >> ... >> >> --- if_vte.o --- >>

Re: Ports build fails on 13-CURRENT r341690

2018-12-12 Thread Justin Hibbits
On Mon, 10 Dec 2018 17:34:03 +0900 (JST) Yasuhiro KIMURA wrote: > Hello, > > yasu@rolling-vm-freebsd1[2018]% uname -a > FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD > 13.0-CURRENT r341690 GENERIC amd64 yasu@rolling-vm-freebsd1[2019]% > LANG=C svn info /usr/src Path:

Re: cannot build i386 12.0-RELEASE kernel on -current

2018-12-12 Thread Yuri Pankov
Henry Vogt wrote: > Hi, > > my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok for amd64, > world for i386 ok, but fails 'make buildkernel' for i386: > > -- snip > > ... > > --- if_vte.o --- > /usr/src/12/sys/dev/vte/if_vte.c:76:10: fatal error: 'miibus_if.h' file not > found

cannot build i386 12.0-RELEASE kernel on -current

2018-12-12 Thread Henry Vogt
Hi, my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok for amd64, world for i386 ok, but fails 'make buildkernel' for i386: -- snip ... --- if_vte.o --- /usr/src/12/sys/dev/vte/if_vte.c:76:10: fatal error: 'miibus_if.h' file not found #include "miibus_if.h"

Re: pkg-base noise

2018-12-12 Thread Enji Cooper
> On Dec 11, 2018, at 11:14 AM, Ian Lepore wrote: > > On Tue, 2018-12-11 at 11:40 -0700, Sean Bruno wrote: >> make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: >> warning: duplicate script for target "_testsFILESINS_cleanup.ksh" >> ignored >> make[8]:

Re: r111 build error

2018-12-12 Thread Ed Maste
On Wed, 12 Dec 2018 at 07:35, Lev Serebryakov wrote: > > On 12.12.2018 14:59, Dimitry Andric wrote: > > ld: error: undefined symbol: clang::CallExpr::getLocStart() const > >>> referenced by MacOSXAPIChecker.cpp:86 > >>>

WITH_META_MODE: any effect? Tree built twice!

2018-12-12 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I just updated sources /usr/src to r341879 (13-CURRENT). To have a clean, new build, performing of "make cleanwolrd cleandir" has been issued and I have set WITH_META_MODE= in /etc/src-env.conf. Loading filemon.ko and rebuilding world and kernel

Re: r111 build error

2018-12-12 Thread Lev Serebryakov
On 12.12.2018 14:59, Dimitry Andric wrote: ld: error: undefined symbol: clang::CallExpr::getLocStart() const >>> referenced by MacOSXAPIChecker.cpp:86 >>> (/usr/src/contrib/llvm/tools/clang/lib/StaticAnalyzer/Checkers/MacOSXAPIChecker.cpp:86) >>> MacOSXAPIChecker.o:((anonymous

Re: r111 build error

2018-12-12 Thread Dimitry Andric
On 12 Dec 2018, at 10:24, O. Hartmann wrote: > > Am Wed, 12 Dec 2018 10:06:02 +0100 > Gary Jennejohn schrieb: > > > On Wed, 12 Dec 2018 02:11:10 +0300 > > Lev Serebryakov wrote: > > > > > Hello Freebsd-current, > > > > > > I'm building very last r341836 (with new llvm/clang 7) on r341726 and

Re: freebsd-current Digest, Vol 789, Issue 3

2018-12-12 Thread Mikhail V Afanasiev
Отмена 12 дек. 2018 г. 14:30 пользователь написал: Send freebsd-current mailing list submissions to freebsd-current@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.freebsd.org/mailman/listinfo/freebsd-current or, via email, send a message

Re: r111 build error

2018-12-12 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Wed, 12 Dec 2018 10:06:02 +0100 Gary Jennejohn schrieb: > On Wed, 12 Dec 2018 02:11:10 +0300 > Lev Serebryakov wrote: > > > Hello Freebsd-current, > > > > I'm building very last r341836 (with new llvm/clang 7) on r341726 and get > > this

Re: r111 build error

2018-12-12 Thread Gary Jennejohn
On Wed, 12 Dec 2018 02:11:10 +0300 Lev Serebryakov wrote: > Hello Freebsd-current, > > I'm building very last r341836 (with new llvm/clang 7) on r341726 and get > this build > error (with MALLOC_PRODUCTION=yes): > Worked for me from r341824 to r341840, but I deleted /usr/obj/usr before

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-11 Thread Anthony Jenkins
On 12/11/18 9:02 AM, Emiel Kollof wrote: Anthony Jenkins schreef op 2018-12-10 18:00: Hi all, I'm trying to port an Intel PCI I2C controller from Linux to FreeBSD.  Linux represents this device as an MFD (multi-function device), meaning it has these "sub-devices" that can be handed off to

head -r341836 (jump to clang 7): amd64 -> armv7 cross build failed: ld: error: unable to find library -lh_csu

2018-12-11 Thread Mark Millard
[This was after amd64 updating to -r341836 successfully ( from -r341766 ). The below was a meta-mode cross build, also going from -r341766 to -r341836 .] # ~/sys_build_scripts.amd64-host/make_armv7_nodebug_clang_bootstrap-amd64-host.sh -j28 buildworld buildkernel Script started, output file is

test

2018-12-11 Thread Sean Bruno
Just testing mailing lists. Delete. sean signature.asc Description: OpenPGP digital signature

Re: r341836 build error

2018-12-11 Thread Lev Serebryakov
Hello Lev, Wednesday, December 12, 2018, 2:11:10 AM, you wrote: Sorry for messed up subject, I mean r341836 of course. -- Best regards, Levmailto:l...@freebsd.org ___ freebsd-current@freebsd.org mailing list

r111 build error

2018-12-11 Thread Lev Serebryakov
Hello Freebsd-current, I'm building very last r341836 (with new llvm/clang 7) on r341726 and get this build error (with MALLOC_PRODUCTION=yes): ===> usr.bin/clang/clang (all) c++ -target x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp

Re: Linux is considering dropping x32.

2018-12-11 Thread Hadi Rezaee
:))) On Wed, Dec 12, 2018 at 12:56 AM Nathan Whitehorn wrote: > > > On 12/11/18 1:04 PM, Kris Moore wrote: > > On 12/11/18 4:01 PM, Alexandre C. Guimarães wrote: > >> Hi. > >> > >> This is just informative. > >> > >> Apparently Linux is considering deprecate x32 support: > >> > >>

Re: Linux is considering dropping x32.

2018-12-11 Thread Nathan Whitehorn
On 12/11/18 1:04 PM, Kris Moore wrote: > On 12/11/18 4:01 PM, Alexandre C. Guimarães wrote: >> Hi. >> >> This is just informative. >> >> Apparently Linux is considering deprecate x32 support: >> >> https://lkml.org/lkml/2018/12/10/1151 >> >> Cheers! >> > Hey that's great! Now that the precedent

Re: Linux is considering dropping x32.

2018-12-11 Thread Jung-uk Kim
On 18. 12. 11., Alexandre C. Guimarães wrote: > Hi. > > This is just informative. > > Apparently Linux is considering deprecate x32 support: > > https://lkml.org/lkml/2018/12/10/1151 x32 != i386 https://en.wikipedia.org/wiki/X32_ABI FYI, FreeBSD never supported x32 ABI. Jung-uk Kim

Re: Linux is considering dropping x32.

2018-12-11 Thread Kris Moore
On 12/11/18 4:15 PM, Konstantin Belousov wrote: > On Tue, Dec 11, 2018 at 04:04:15PM -0500, Kris Moore wrote: >> On 12/11/18 4:01 PM, Alexandre C. Guimarães wrote: >>> Hi. >>> >>> This is just informative. >>> >>> Apparently Linux is considering deprecate x32 support: >>> >>>

Re: Linux is considering dropping x32.

2018-12-11 Thread Konstantin Belousov
On Tue, Dec 11, 2018 at 04:04:15PM -0500, Kris Moore wrote: > On 12/11/18 4:01 PM, Alexandre C. Guimarães wrote: > > Hi. > > > > This is just informative. > > > > Apparently Linux is considering deprecate x32 support: > > > > https://lkml.org/lkml/2018/12/10/1151 > > > > Cheers! > > > > Hey

Re: Linux is considering dropping x32.

2018-12-11 Thread Kris Moore
On 12/11/18 4:01 PM, Alexandre C. Guimarães wrote: > Hi. > > This is just informative. > > Apparently Linux is considering deprecate x32 support: > > https://lkml.org/lkml/2018/12/10/1151 > > Cheers! > Hey that's great! Now that the precedent is set, we start the timer to deprecate on FreeBSD in

Linux is considering dropping x32.

2018-12-11 Thread Alexandre C . Guimarães
Hi. This is just informative. Apparently Linux is considering deprecate x32 support: https://lkml.org/lkml/2018/12/10/1151 Cheers! -- Best Regards, Alexandre C. Guimarães. https://bitbucket.org/rigoletto-freebsd/ signature.asc Description: PGP signature

Re: pkg-base noise

2018-12-11 Thread Ian Lepore
On Tue, 2018-12-11 at 11:40 -0700, Sean Bruno wrote: > make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: > warning: duplicate script for target "_testsFILESINS_cleanup.ksh" > ignored > make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: > warning: using previous

pkg-base noise

2018-12-11 Thread Sean Bruno
make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: warning: duplicate script for target "_testsFILESINS_cleanup.ksh" ignored make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: warning: using previous script for "_testsFILESINS_cleanup.ksh" defined here Is this

FreeBSD 12.0 RC3 PPC report

2018-12-11 Thread Alex McKeever
It’s working fine on my eMac G4/1.25 GHz retail model. The CDE Desktop Environment is oddly broken, but I am pleased to report that most of the packages I’ve compiled have done so successfully unlike 11.1! Sent from Yahoo Mail for iPhone ___

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-11 Thread Emiel Kollof
Anthony Jenkins schreef op 2018-12-10 18:00: Hi all, I'm trying to port an Intel PCI I2C controller from Linux to FreeBSD. Linux represents this device as an MFD (multi-function device), meaning it has these "sub-devices" that can be handed off to other drivers to actually attach devices

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-10 Thread John Baldwin
On 12/10/18 12:19 PM, Ian Lepore wrote: > On Mon, 2018-12-10 at 14:42 -0500, Anthony Jenkins wrote: >> On 12/10/18 1:26 PM, John Baldwin wrote: >>> >>> On 12/10/18 9:00 AM, Anthony Jenkins wrote: Hi all, I'm trying to port an Intel PCI I2C controller from Linux to FreeBSD.

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-10 Thread Ian Lepore
On Mon, 2018-12-10 at 14:42 -0500, Anthony Jenkins wrote: > On 12/10/18 1:26 PM, John Baldwin wrote: > > > > On 12/10/18 9:00 AM, Anthony Jenkins wrote: > > > > > > Hi all, > > > > > > I'm trying to port an Intel PCI I2C controller from Linux to > > > FreeBSD. > > > Linux represents this device

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-10 Thread Anthony Jenkins
On 12/10/18 1:26 PM, John Baldwin wrote: On 12/10/18 9:00 AM, Anthony Jenkins wrote: Hi all, I'm trying to port an Intel PCI I2C controller from Linux to FreeBSD. Linux represents this device as an MFD (multi-function device), meaning it has these "sub-devices" that can be handed off to other

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-10 Thread John Baldwin
On 12/10/18 9:00 AM, Anthony Jenkins wrote: > Hi all, > > I'm trying to port an Intel PCI I2C controller from Linux to FreeBSD.  > Linux represents this device as an MFD (multi-function device), meaning > it has these "sub-devices" that can be handed off to other drivers to > actually attach

Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-10 Thread Anthony Jenkins
Hi all, I'm trying to port an Intel PCI I2C controller from Linux to FreeBSD.  Linux represents this device as an MFD (multi-function device), meaning it has these "sub-devices" that can be handed off to other drivers to actually attach devices to the system.  The Linux "super" PCI device is

Re: Suppose a user on a pilgrimage to /usr/src, modified UPDATING

2018-12-10 Thread Jamie Landeg-Jones
miltonott wrote: > O great and powerful FreeBSD biome. May I redirect from here to a paste > site > service, a rearrangement of development directory head file /usr/src/UPDATING. sorry, but left & right justified text is horrible, especially with a monospaced font!

SDHCI: serious issues with USB SD Card reader/writer

2018-12-10 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Using the USB attached SD card reader/writer of my Dell screen, since 13-CURRENT is out recently I have serious trouble with the assortment of SD cards I use. While 12-PRE seems to not have any problems, 13-CURRENT (FreeBSD 13.0-CURRENT #912

Re: Suppose a user on a pilgrimage to /usr/src, modified UPDATING

2018-12-10 Thread David Wolfskill
On Mon, Dec 10, 2018 at 09:49:13AM +, miltonott wrote: > O great and powerful FreeBSD biome. May I redirect from here to a paste > site > service, a rearrangement of development directory head file /usr/src/UPDATING. > > UPDATING.ORIG -> http://dpaste.com/1WRWG26.txt > - > UPDATING

Suppose a user on a pilgrimage to /usr/src, modified UPDATING

2018-12-10 Thread miltonott
O great and powerful FreeBSD biome. May I redirect from here to a paste site service, a rearrangement of development directory head file /usr/src/UPDATING. UPDATING.ORIG -> http://dpaste.com/1WRWG26.txt - UPDATING -> http://dpaste.com/1Z4E3H1.txt - UPDATING.DIFF ->

Ports build fails on 13-CURRENT r341690

2018-12-10 Thread Yasuhiro KIMURA
Hello, yasu@rolling-vm-freebsd1[2018]% uname -a FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT r341690 GENERIC amd64 yasu@rolling-vm-freebsd1[2019]% LANG=C svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: https://svn.freebsd.org/base/head

Re: nda(4) does not work (reliably) in VMware Workstation

2018-12-09 Thread Chuck Tuffli
On Sun, Dec 9, 2018 at 3:43 PM Yuri Pankov wrote: > Chuck Tuffli wrote: > > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov > > wrote: > > > > Hi, > > > > Running -HEAD in VMware Workstation 15.0.2 VM. Trying to use nda(4) > > instead of nvd(4) shows the

Re: nda(4) does not work (reliably) in VMware Workstation

2018-12-09 Thread Chuck Tuffli
On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov wrote: > Hi, > > Running -HEAD in VMware Workstation 15.0.2 VM. Trying to use nda(4) > instead of nvd(4) shows the following list of errors, and eventually > panics: > > https://people.freebsd.org/~yuripv/nda1.png >

Re: nda(4) does not work (reliably) in VMware Workstation

2018-12-09 Thread Yuri Pankov
Chuck Tuffli wrote: > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov > wrote: > > Hi, > > Running -HEAD in VMware Workstation 15.0.2 VM.  Trying to use nda(4) > instead of nvd(4) shows the following list of errors, and eventually > panics: > >

nda(4) does not work (reliably) in VMware Workstation

2018-12-08 Thread Yuri Pankov
Hi, Running -HEAD in VMware Workstation 15.0.2 VM. Trying to use nda(4) instead of nvd(4) shows the following list of errors, and eventually panics: https://people.freebsd.org/~yuripv/nda1.png https://people.freebsd.org/~yuripv/nda2.png nvd(4) works without issues in this VM. nda(4) works as

ZFS sends TIRMs to agressively? (Was: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system)

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 7:58:37 PM, you wrote: >> Can you please narrow the problem down to a specific kernel revision? > I'm still not sure it is software or hardware problem. Looks like Samsung 850 EVO doesn't like TRIMs sent by ZFS (and I've thought it is good SSD,

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Mateusz, Saturday, December 8, 2018, 5:27:42 PM, you wrote: >> Looks like each next compiler invocation is slower and more stressful than >> previous one. > Is this a fresh install? Almost fresh. It was installed from some rather fresh 13 snapshot and then upgraded to r341157 and custom

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Mateusz Guzik
On 12/8/18, Lev Serebryakov wrote: > Hello Lev, > > Saturday, December 8, 2018, 2:13:03 PM, you wrote: > > >> Even when build is single-job, system becomes unresponsive. With >> 4-job build running it could takes up to minute to switch screen's >> windows! > And even with 1-job kernel build

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Eugene Grosbein
08.12.2018 18:13, Lev Serebryakov wrote: > I'm completely lost. Is it problem of software? Hardware? If it is > hardware problem what should I blame? Try using different kern.timecounter.hardware and/or kern.eventtimer.timer but first try kern.eventtimer.periodic=1 instead of default 0. If

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Eugene, Saturday, December 8, 2018, 4:27:13 PM, you wrote: >> I'm completely lost. Is it problem of software? Hardware? If it is >> hardware problem what should I blame? > Try using different kern.timecounter.hardware and/or kern.eventtimer.timer > but first try

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > Even when build is single-job, system becomes unresponsive. With > 4-job build running it could takes up to minute to switch screen's windows! And even with 1-job kernel build upsmon's connection to remote upsd flickers!

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > Another strange thing I noticed: when system is in such state, "top -SH" > shows that sometimes very low-profile processes, like clock software > interrupt (!) could consume large amount of CPU for short periods time. When >

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Waitman Gobble
‐‐‐ Original Message ‐‐‐ On Saturday, December 8, 2018 8:18 AM, Lev Serebryakov wrote: > Hello Lev, > > Saturday, December 8, 2018, 2:13:03 PM, you wrote: > > > Another strange thing I noticed: when system is in such state, "top -SH" > > shows that sometimes very low-profile processes,

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > I've checked all "standard" places — CPU is not throttling, SSD looks > perfectly Ok according to SMART and there is no complains from AHCI driver > about timeouts and such, system doesn't start to use swap. ZFS ARC was checked

Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Freebsd-hackers, I'm experiencing very strange situation on my lab system which is E3-1220v2, 8GiB of RAM and 850 EVO SATA SSD (with single ZFS pool). It runs CURRENT r341157. Kernel is built *without* INVARIANTS and other heavy debug aids. Everything works great — but compilation.

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 05:02:03PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > > > Most

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Konstantin Belousov
On Fri, Dec 07, 2018 at 05:02:03PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > > > Most

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > Most likely this is an issue fixed by r339350. > > > > My tree is at r341703.

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Konstantin Belousov
On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > > > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > > > On Fri, Dec 07, 2018 at

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > > > make core dumps.

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Konstantin Belousov
On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > make core dumps. > > > devd core dumps. > > > init core dumps. > > > cc core dumps. > > >

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > make core dumps. > > > devd core dumps. > > > init core dumps. > > > cc core dumps. > > >

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > make core dumps. > > devd core dumps. > > init core dumps. > > cc core dumps. > > c++ core dumps. > > > > Something seems to be broken. > > > > Further

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 06:23:57PM -0500, Shawn Webb wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > Dell 7510 laptop was happily running FreeBSD12-alpha9 > > from Oct. 10th. I decided to update to top-of-tree > > today, which would be FreeBSD13 at r341703. > > analysis

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > make core dumps. > devd core dumps. > init core dumps. > cc core dumps. > c++ core dumps. > > Something seems to be broken. > Further investigation, as core dumps. cpp core dumps. /rescue/vi core dumps. All of these

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Shawn Webb
On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > Dell 7510 laptop was happily running FreeBSD12-alpha9 > from Oct. 10th. I decided to update to top-of-tree > today, which would be FreeBSD13 at r341703. > > % cd /usr/obj > % rm -rf usr > % cd ../src > % svn update > % make -j6

HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
Dell 7510 laptop was happily running FreeBSD12-alpha9 from Oct. 10th. I decided to update to top-of-tree today, which would be FreeBSD13 at r341703. % cd /usr/obj % rm -rf usr % cd ../src % svn update % make -j6 buildwould (OK) % make -j6 buildkernel (OK) % make installkernel(OK) %

Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2

2018-12-07 Thread Willem Jan Withagen
On 05/12/2018 00:48, Toomas Soome wrote: Yes, that must be true but it does not hurt to get checked. And of course, lsdev -v from 11.x loader would be good too. Anyhow, I am afraid we have reached to point where more specific debug info is needed (printed out), with lack of output about disks

Re: iflib.tx_abdicate: very strange behavior on incoming IPsec traffic (regression?)

2018-12-07 Thread Lev Serebryakov
On 07.12.2018 18:02, Lev Serebryakov wrote: >> (I'm not sure, that it is exactly "bug" or "defect" and want to > ... discuss it here before filing PR. > >> Now I'm throwing IPsec into mix. All incoming traffic is tunneled with >> IPsec policy, with aes-128-gcm encryption. And with IPsec

Re: iflib.tx_abdicate: very strange behavior on incoming IPsec traffic (regression?)

2018-12-07 Thread Lev Serebryakov
On 07.12.2018 16:40, Lev Serebryakov wrote: > (I'm not sure, that it is exactly "bug" or "defect" and want to ... discuss it here before filing PR. > Now I'm throwing IPsec into mix. All incoming traffic is tunneled with > IPsec policy, with aes-128-gcm encryption. And with IPsec tx_abdicate

iflib.tx_abdicate: very strange behavior on incoming IPsec traffic (regression?)

2018-12-07 Thread Lev Serebryakov
(I'm not sure, that it is exactly "bug" or "defect" and want to I've found very strange behavior of 13-CURRENT system I210 (igb) interfaces and enabled "dev.igb.X.iflib.tx_abdicate". I'm measuring "router" performance with BSDRP's "equilibrium" script (thank you, Oliver, for this great

  1   2   3   4   5   6   7   8   9   10   >