Re: CURRENT: bc -e results in empty string/result

2020-07-03 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Fri, 3 Jul 2020 17:24:36 +0200 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello list, > > running some scripts caluclating via bc() the expression shown below: > > bc

CURRENT: bc -e results in empty string/result

2020-07-03 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello list, running some scripts caluclating via bc() the expression shown below: bc -e '6582031 - 1048576 - 0 - 409600 - 1024 - 40 - 4096' -e quit results on recent CURRENT ( FreeBSD 13.0-CURRENT #80 r362884: Thu Jul 2 10:08:23 CEST 2020

CURRENT: swap issues and dying jails

2020-06-29 Thread O. Hartmann
Due to the circumstance I have no access anymore to the host in question, I'll report a problem occured out of the blue around last week's update of CURRENT with poudriere and swapspace. Problem: under heavy load, the host dies - no ssh connection possible anymore, all jails are in the state

Re: r360294: buildkernel failure: etinet/tcp_stacks/bbr.c:5605:35: error: incomplete definition of type

2020-04-25 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Sat, 25 Apr 2020 11:32:49 +0100 Alexander V. Chernikov schrieb: > 25.04.2020, 11:18, "O. Hartmann" : > > Hello, > > > > recent commits to CURRENT makes buildkernel to fail due to some incomplete > > d

r360294: buildkernel failure: etinet/tcp_stacks/bbr.c:5605:35: error: incomplete definition of type

2020-04-25 Thread O. Hartmann
struct nhop_object' struct nhop_object *ro_nh; ^ - --- all_subdir_sound --- Kind regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -B

r358858: ipfw: bad destination address any

2020-03-11 Thread O. Hartmann
ia rc.conf or using own scripts containing "any" as keyword for either source or destination to brick the system. Kind regards, O. Hartmann ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To u

Re: r358062(ncurses) breaks installed ports, howto check?

2020-02-27 Thread O. Hartmann
t 08:28:03PM -0500, Thomas Dickey wrote: > > > > On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote: > > > > > On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote: > > > > > > On Tue, Feb 25, 2020 at 04:37:11AM +

r358062(ncurses) breaks installed ports, howto check?

2020-02-24 Thread O. Hartmann
installed on a system rely on ncurses provided by the system? Thanks in advance, oh -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). ___ freebsd-current

r358220: compiler error: fatal error: '__errc' file not found #include <__errc>

2020-02-21 Thread O. Hartmann
145:10: fatal error: '__errc' file not found #include <__errc> [...] Kind regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN P

svn commit: r357771 - in head/sys: kern sys breaks port x11/nvidia-driver

2020-02-11 Thread O. Hartmann
ity) >= 0 && (priority) <= 255);\ ^ 1 error generated. *** Error code 1 - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Ab

WifI support missing: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

2019-11-28 Thread O. Hartmann
this chip although it seems very common and well supported by several Linux distributions including the OpenWRT router project (I think that is the ath10k driver suite as far as I recall). Thanks in adavnce, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für

r354673: compiler error: error: unable to execute command: Segmentation fault (core dumped) cpp: error:

2019-11-12 Thread O. Hartmann
Trying to buildworld and/or buildkernel fails after upgrading 13-CURRENT today to FreeBSD 13.0-CURRENT #25 r354673: Wed Nov 13 06:47:48 CET 2019 amd64. After a "make -j8 cleanworld cleandir" (trying to circumvent the problem) I still face the ccp error shown below rendering the system impossible

> r353680: multiuser crash due to: m_getzone: Inavlid cluster size 0

2019-10-24 Thread O. Hartmann
The last known good update of CURRENT on a Fujitsu Primergy RX2530-M5 (only one of two sockets equipted, 64 GB RAM) was October, 17th, 2019 before 15 o'clock, I suppose that was r353680 that time. Today's update to r353881 resulted in an immediate crash when the network (igb0-igb3, two built-in

> r353680: multiuser crash due to: m_getzone: Inavlid cluster size 0

2019-10-23 Thread O. Hartmann
The last known good update of CURRENT on a Fujitsu Primergy RX2530-M5 (only one of two sockets equipted, 64 GB RAM) was October, 17th, 2019 before 15 o'clock, I suppose that was r353680 that time. Today's update to r353881 resulted in an immediate crash when the network (igb0-igb3, two built-in

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-10-13 Thread O. Hartmann
On Tue, 27 Aug 2019 08:43:53 +0300 Toomas Soome wrote: > > On 27 Aug 2019, at 08:08, Warner Losh wrote: > > > > On Mon, Aug 26, 2019, 5:32 PM Rebecca Cran > <mailto:rebe...@bsdio.com>> wrote: > >> On 8/26/19 5:22 AM, O. Hartmann wrote: > >>

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-10-13 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 21 Aug 2019 22:34:21 +0300 Toomas Soome schrieb: > > On 21 Aug 2019, at 22:30, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Wed, 21 Aug 2019 22:14:

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-10-13 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 21 Aug 2019 22:29:29 + greg@unrelenting.technology schrieb: > August 22, 2019 12:23 AM, "O. Hartmann" wrote: > > > Am Wed, 21 Aug 2019 15:58:24 -0500 > > Karl Denninger schrieb: > > > >&g

Re: r352239: install failure: make[10]: exec(btxld) failed (No such file or directory)

2019-09-12 Thread O. Hartmann
On Thu, 12 Sep 2019 06:27:00 +0200 "O. Hartmann" wrote: > Hello, > > we install several pkg-based systems and poudriere from a dedicated tree of > sources, instead of /usr/src it is in our case /pool/sources/CURRENT/src and > 12-STABLE/src. Compilation of the sour

r352239: install failure: make[10]: exec(btxld) failed (No such file or directory)

2019-09-11 Thread O. Hartmann
Hello, we install several pkg-based systems and poudriere from a dedicated tree of sources, instead of /usr/src it is in our case /pool/sources/CURRENT/src and 12-STABLE/src. Compilation of the sources is done within a JAIL! For a couple of days now, both trees, CURRENT (r352239 now) and

Re: jails, ZFS, deprecated jail variables and poudriere problems

2019-08-29 Thread O. Hartmann
On Wed, 28 Aug 2019 13:57:00 +0200 Alexander Leidinger wrote: > Quoting "O. Hartmann" (from Tue, 27 Aug 2019 > 10:11:54 +0200): > > > We have a single ZFS pool (raidz), call it pool00 and this pool00 conatins a > > ZFS dataset pool00/poudriere which we want

jails, ZFS, deprecated jail variables and poudriere problems

2019-08-27 Thread O. Hartmann
Hello list, trying to setup a poudriere jail on recent CURRENT and have some severe trouble. We have a single ZFS pool (raidz), call it pool00 and this pool00 conatins a ZFS dataset pool00/poudriere which we want to exclusively attach to a jail. pool00/poudriere contains a complete clone of a

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-26 Thread O. Hartmann
On Thu, 22 Aug 2019 08:58:55 +0300 Toomas Soome wrote: > > On 22 Aug 2019, at 06:04, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Wed, 21 Aug 2019 22:29:29 + > > greg@unrelenting.technology schrieb

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 21 Aug 2019 15:58:24 -0500 Karl Denninger schrieb: > BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Wed, 21 Aug 2019 22:34:21 +0300 > > Toomas Soome schrieb: > > > > >>

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 21 Aug 2019 22:34:21 +0300 Toomas Soome schrieb: > > On 21 Aug 2019, at 22:30, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Wed, 21 Aug 2019 22:14:

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 21 Aug 2019 22:34:21 +0300 Toomas Soome schrieb: > > On 21 Aug 2019, at 22:30, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 >

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread O. Hartmann
top to gain access to the shell; there is no timeframe to hit any key to stop by and access the efi shell. Kind regards, oh > > > On 21 Aug 2019, at 20:58, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > I ran into

HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread O. Hartmann
I ran into serious trouble booting several boxes off UEFI. On modern hardware, the ESP is around 200 - 300 MB in size and usually I install /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some older hardware, specifically on a Lenovo E540 with latest available firmware (2.28),

HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread O. Hartmann
anks in advance, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2GbQAKCRA4N1Z

r351247: buildkernel failure: error: use of undeclared identifier 'miibus_statchg_XXXX

2019-08-20 Thread O. Hartmann
Recent CURRENT (r351247) fails to buildkernel due to a compilation error, pointing to an mii issue. For almost every mii-related if_ the compiler drops an error like: [...] Building /usr/obj/usr/src/amd64.amd64/sys/WOTAN/modules/usr/src/sys/modules/usb/udl/udl.ko ===> usb/uether (all) Building

Re: CURRENT: supeblock hash failure - CURRENT wrecking disks

2019-08-07 Thread O. Hartmann
Tomorrow I try to install a prepared pkg tar arcive FreeBSD-kernel from aCURRENT pkg base and hope this will fix the issue. Regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder

CURRENT: supeblock hash failure - CURRENT wrecking disks

2019-08-07 Thread O. Hartmann
Hello, today I ran into a ctastrophy with r350671. After installing a fresh compiled system and rebooted the box, UEFI loader dropped a bunch of errors, like some hex numbers stating, that a hash/superblock has is wrong and then the booting stopped at the OK loader prompt. Rebooting the machine

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-08-04 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Tue, 30 Jul 2019 17:01:57 +0300 Toomas Soome schrieb: > > On 30 Jul 2019, at 15:43, O. Hartmann wrote: > > > > On Wed, 24 Jul 2019 18:07:22 +0300 > > Toomas Soome wrote: > > > >>> On

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-30 Thread O. Hartmann
On Wed, 24 Jul 2019 18:07:22 +0300 Toomas Soome wrote: > > On 24 Jul 2019, at 16:48, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Wed, 24 Jul 2019 12:06:53 +0200 > > "O. Hartmann" mailto:o.hartm

CURRENT: rc script/kernel freeze after r349267

2019-07-30 Thread O. Hartmann
ling debug messages in /etc/rc.conf results in a last line showing some code containing "devmatch()" (can't remember, box is at a remote site now). The machine is a two socket box but with only one socket populated and 64GB RAM, see the following dmesg. Kind regards, O. Hartmann [...] -

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-24 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 24 Jul 2019 12:06:53 +0200 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Am Wed, 24 Jul 2019 12:09:16 +0300 > Toomas Soome schrieb: > > > > On 24 J

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-24 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 24 Jul 2019 12:09:16 +0300 Toomas Soome schrieb: > > On 24 Jul 2019, at 11:11, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Hallo, > > > &g

PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-24 Thread O. Hartmann
prove concurrent Fortuna performance kern.random.fortuna.concurrent_read="1" # Forward Information Bases (FIBs) net.fibs=10 net.add_addr_allfibs=0 [...] Again, with the exact same setting 12-STABLE r349288 boots fine, rr350274 doesn't. FreeBSD 12-STABLE r Can someone pleas

CURRENT >r349150: boot failure in rc.conf.local

2019-06-18 Thread O. Hartmann
On all CURRENT boxes running CURRENT > r349150 we face the very same boot failure, if /etc/rc.conf.local is present (i.e. on CURRENT, 13.0-CURRENT #7 r349169: Tue Jun 18 10:34:13 CEST 2019 amd64): The box boots and thentries to start services denominated in /etc/rc.conf.local, like

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 s

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

installworld breakage r348516 -> r348572

2019-06-03 Thread O. Hartmann
d/11.edit /usr/share/doc/usd/12.vi /usr/share/doc/usd/13.viref; do if [ -f /${file} ]; then rm -f /${file}; fi; done --- distrib-dirs --- -deU -i - -f /usr/src/etc/mtree/BSD.root.dist -p / sh: -deU: not found *** [distrib-dirs] Error code 127 Greetings, oh - -- O. Hartmann Ich widersp

12-STABLE: poudriere jail installation/updating is failing

2019-05-15 Thread O. Hartmann
Recently an error seem to have spread across our 12-STABLE platforms offering poudriere. Building the binaries for FreeBSD 12-STABLE (recent version r347613) on systems running FreeBSD 12-STABLE (r347613) worked very well before, but now the install process seem to fail on all boxes the very same

12-STABLE/CURRENT: Dell PowerEdge 2950: Allied Telesis AT-2711FX/SC 100MBit fibre NIC not recognized

2019-05-08 Thread O. Hartmann
need supported fibre NICs for both 100 MBit and 1GBit for FreeBSD 11 as well as 12 and if there is a suggestion, please, I'm open to it. Thanks in advance, O. Hartmann ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/list

Re: r346025: ZFS filesystems do not mount anymore

2019-04-09 Thread O. Hartmann
On Tue, 9 Apr 2019 10:42:47 +0200 (CEST) Trond Endrestøl wrote: > On Tue, 9 Apr 2019 10:06+0200, Trond Endrestøl wrote: > > > On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > >

r346025: ZFS filesystems do not mount anymore

2019-04-08 Thread O. Hartmann
ng all ZFS filesystems via "zfs mount -a" operates as expected and all filesystems are available as usual. Kind regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).

Re: r344798: c++: error: linker command failed with exit code

2019-03-06 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Tue, 5 Mar 2019 23:08:32 +0100 Dimitry Andric schrieb: > On 5 Mar 2019, at 21:54, O. Hartmann wrote: > > > > Am Tue, 5 Mar 2019 13:16:26 -0500 > > Shawn Webb schrieb: > > > > > On Tue, Mar 05, 2019 at

Re: r344798: c++: error: linker command failed with exit code

2019-03-05 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Tue, 5 Mar 2019 13:16:26 -0500 Shawn Webb schrieb: > On Tue, Mar 05, 2019 at 05:45:11PM +0100, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Hello, > > > > recent bu

r344798: c++: error: linker command failed with exit code

2019-03-05 Thread O. Hartmann
archive >>> /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm/libllvm.a c++: error: linker command failed with exit code 1 (use -v to see invocation) *** [clang] Error code 1 make[4]: stopped in /usr/src/usr.bin/clang/clang [...] I tried to rebuild world from a fresh /usr/s

Re: 12-STABLE revision 344629: pid 26 (sh), jid 0, uid 0: exited on signal 11

2019-02-27 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 27 Feb 2019 14:18:28 -0500 Shawn Webb schrieb: > On Wed, Feb 27, 2019 at 08:08:24PM +0100, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Running 12-STABLE and CURRENT on a

12-STABLE revision 344629: pid 26 (sh), jid 0, uid 0: exited on signal 11

2019-02-27 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Running 12-STABLE and CURRENT on a PCengine APU4C (CPU: AMD GX-412TC SOC, Coreboot Version: v4.9.0.2), I ran into trouble running latest 12-STABLE on that hardware. The box is quitting with [...] mmcsd0: 31GB at mmc0 50.0MHz/4bit/65535-block

Re: poudriere: 12-STABLE install fails after r344230

2019-02-18 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Mon, 18 Feb 2019 08:06:54 +0100 "O. Hartmann" schrieb: > On Sun, 17 Feb 2019 19:07:53 +0100 > "O. Hartmann" wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Hell

Re: poudriere: 12-STABLE install fails after r344230

2019-02-17 Thread O. Hartmann
On Sun, 17 Feb 2019 19:07:53 +0100 "O. Hartmann" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello, > > after the bump of 12-STABE to 1200503 I'm unable to update AMD64 poudriere > jails's to this version anymore! Now I r

Re: What is evdev and autoloading?

2019-02-17 Thread O. Hartmann
On Sun, 17 Feb 2019 18:35:25 -0800 (PST) "Rodney W. Grimes" wrote: > > On Sun, Feb 17, 2019 at 03:04:41PM -0800, Mark Millard wrote: > > > > > > > > > On 2019-Feb-17, at 10:03, Steve Kargl > > troutmask.apl.washington.edu> wrote: > > > > > > Anyone have insight into what evdev is? There

poudriere: 12-STABLE install fails after r344230

2019-02-17 Thread O. Hartmann
-STABLE revision). How to fix this? Thanks in advance, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE

Re: icmp (IPv4) issues with VIMAGE JAILs and IPv6

2019-01-31 Thread O. Hartmann
On Tue, 29 Jan 2019 11:36:37 +0300 "Andrey V. Elsukov" wrote: > On 28.01.2019 15:44, O. Hartmann wrote: > > Stopping all jails, destroying all epairs and bridge0 doesn't change > > anything. The problems occured when IPv6 came into play on the specific > > host in

syslogd: using IPv6 as hostnames results in "IP mismatch"

2019-01-31 Thread O. Hartmann
Hello out there. I'm using some dual stack installations and I'd like to configure FreeBSD's (CURRENT at the moment) syslogd on a syslog-server to handle incoming logging messages from remote FBSD boxes (mixed, 11.2, 12.0 and CURRENT). I' facing a very weird situation. Scenario: The server has

icmp (IPv4) issues with VIMAGE JAILs and IPv6

2019-01-28 Thread O. Hartmann
I ran into severe problems on CURRENT ( FreeBSD 13.0-CURRENT #193 r343521: Mon Jan 28 10:26:36 CET 2019 amd64), VIMAGE enabled host with jails utilizing IPv6. Scenario: The main host has two Braodcom (bce0|1) NICs. bce0 is the physical NIC attached to a routed/switched network for the main host.

Re: CUPS: [Client 1] Unable to encrypt connection: An illegal parameter has been received.

2019-01-21 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 16 Jan 2019 18:33:36 +0100 Tijl Coosemans schrieb: > On Wed, 16 Jan 2019 15:23:40 +0100 "O. Hartmann" > wrote: > > We have an experimental IPV6 network and within this network, FreebSD > > CURRENT > > (

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-19 Thread O. Hartmann
to use to boot. Some will even create new Boot > variables that they use when you choose a raw device to boot from. > > There's other people that have efi programs that will pop up a menu for you > to select a particular BootXXXX to use. They then set BootNext and exit. > I've no

CUPS: [Client 1] Unable to encrypt connection: An illegal parameter has been received.

2019-01-16 Thread O. Hartmann
We have an experimental IPV6 network and within this network, FreebSD CURRENT (r343087) is acting as a CUPS print server, while a bunch FreeBSD 12-STABLE boxes are CUPS clients. The setup, so far, worked with IPv4. Introducing IPv6 addresses on both server and host results in the error [Client

Re: kernel panic in wireless-related sysctl walk

2019-01-12 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 10 Jan 2019 22:22:05 +0100 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Am Thu, 10 Jan 2019 12:02:15 -0800 > Cy Schubert schrieb: > > > I'm not able to reproduce this

Re: kernel panic in wireless-related sysctl walk

2019-01-10 Thread O. Hartmann
em is a "pkg system" completely, so I have to switch on debugging without kernel rebuilds. Any advice? Kind regards, O. Hartmann - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BD

Re: efibootmgr: Cannot translate unix loader path xxx\xxx\xxx to UEFI: No error: 0

2018-12-28 Thread O. Hartmann
On Thu, 27 Dec 2018 08:38:20 -0700 Warner Losh wrote: > On Dec 27, 2018 7:42 AM, "O. Hartmann" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Am Thu, 27 Dec 2018 13:29:44 +0100 > "Hartmann, O." schrieb: > > > > Updated

Re: efibootmgr: Cannot translate unix loader path xxx\xxx\xxx to UEFI: No error: 0

2018-12-27 Thread O. Hartmann
No error: 0 > > What the heck is that? > > What does this error mean? No error: 0? > > The box is unusable. > > > Kind regards, > > O. Hartmann > > > I found this PR, Bug 229191, from June, 2018: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2

bind 9.12.3-P1 dies after change of IP on outbound interface

2018-12-20 Thread O. Hartmann
gate named[3195]: starting BIND 9.12.3-P1 Prior to the last update of dns/bind912, this router/firewall appliance was running more than a month without having such trouble, even the ISP is randomly changing the IPv4/IPv6 addresses spread over the day. What is wrong? Kind regards, O. Hartman

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

2018-12-18 Thread O. Hartmann
istake? I'm out of clues. Thanks in advance and kind regards, O. Hartmann - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ4

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

2018-12-14 Thread O. Hartmann
have textproc/docproj installed (FOP and DBLATEX enabled, as it seems they are needed by some PDF tools necessary to aim for the PDF build). What is wrong? Thanks in advance and kind regards, O. Hartmann [...] dbook/imagelib/callouts/'" --maxdepth 12000 -o eresources.xml.www.inde

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,

WITH_META_MODE: any effect? Tree built twice!

2018-12-12 Thread O. Hartmann
d XEON box, base system on UFS/FFS 256 GB Samsung 850 Pro SSD, ZFS RAIDZ volume of 16 TB as data graveyard). Thanks in advance. oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).

Re: r111 build error

2018-12-12 Thread O. Hartmann
lang/lib/Serialization/GeneratePCH.cpp:51) > > >>> GeneratePCH.o:(clang::PCHGenerator::HandleTranslationUnit(clang::ASTContext&)) > > >>> in > > >>> archive /usr/obj/usr/src/amd64.amd64/lib/clang/libclang/libclang.a > > > > ld: error: un

SDHCI: serious issues with USB SD Card reader/writer

2018-12-10 Thread O. Hartmann
riter just in case the error indicates a hardware failure. Kind regards, O. Hartmann - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iLUEARMKAB0WIQQZ

Re: Fujitsu Lifebook E751 (iGPU: HM65): distorted console with UEFI boot

2018-12-03 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Mon, 3 Dec 2018 09:26:14 +0100 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Fri, 30 Nov 2018 23:14:07 +0900 > Tomoaki AOKI schrieb: > > > On Wed, 28 Nov 2018 19:39

Re: Fujitsu Lifebook E751 (iGPU: HM65): distorted console with UEFI boot

2018-12-03 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Fri, 30 Nov 2018 23:14:07 +0900 Tomoaki AOKI schrieb: > On Wed, 28 Nov 2018 19:39:21 +0100 > "O. Hartmann" wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Am Wed, 28

Re: ipv6/ppp: FreeBSD obtains linklocal on tun0 only

2018-12-02 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Fri, 30 Nov 2018 14:32:52 + Gary Palmer schrieb: > On Fri, Nov 30, 2018 at 01:12:32PM +0100, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > My ISP is offering IPv6 only "a

Re: ipv6/ppp: FreeBSD obtains linklocal on tun0 only

2018-12-02 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Fri, 30 Nov 2018 16:41:02 + "Bjoern A. Zeeb" schrieb: Sorry for the late reply, had a long weekend off ... > On 30 Nov 2018, at 15:59, Christoph Moench-Tegeder wrote: > > > ## O. Hartmann (ohartm...@walstatt.org):

ipv6/ppp: FreeBSD obtains linklocal on tun0 only

2018-11-30 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 My ISP is offering IPv6 only "as an experimental feature", so I had to ask to enable the IPv6 stack on my connection. I'm using FreeBSD 12-STABLE as the basis for a router/firewall/PBX system, FreeBSD's onboard ppp client is performing the uplink

Re: Fujitsu Lifebook E751 (iGPU: HM65): distorted console with UEFI boot

2018-11-28 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Wed, 28 Nov 2018 15:00:42 +0100 Emmanuel Vadot schrieb: > Hi, > > On Wed, 28 Nov 2018 10:51:11 +0100 > "O. Hartmann" wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > &

Fujitsu Lifebook E751 (iGPU: HM65): distorted console with UEFI boot

2018-11-28 Thread O. Hartmann
) but no chance. Before starting investigating this issue further I'd like to ask wether there is a general support provided or is that type of notebook dead matter for FreeBSD of the modern kind? Thanks in advance, oh p.s. please CC me, I'm not subscribing all lists. - -- O. Hartmann -BEGIN PGP

Re: HEADS-UP: OpenSSL 1.1.1 in 12.0

2018-10-10 Thread O. Hartmann
inked to /usr/lib/libssl.so.8 where the > > openssl update creates libssl.so.9. There may be more I haven't found yet, > > add multimedia/ffmpeg to this list .. > > imb > > ___ > freebsd-current@freebsd.org mailing l

Re: HEADS-UP: OpenSSL 1.1.1 in 12.0

2018-10-10 Thread O. Hartmann
list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" dns/samba-nsupdate net/liboauth - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Mark

Re: 12-ALPHA3: (NanoBSD): ld-elf.so.1: Shared object "libibverbs.so.1" not found, required by "libpcap.so.8"

2018-08-30 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Thu, 30 Aug 2018 10:44:25 -0500 Kyle Evans schrieb: > On Thu, Aug 30, 2018 at 10:41 AM O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Running a NanoBSD with lots of

12-ALPHA3: (NanoBSD): ld-elf.so.1: Shared object "libibverbs.so.1" not found, required by "libpcap.so.8"

2018-08-30 Thread O. Hartmann
monolithic on that appliance in question - I do not allow the loading of kernel modules. I guess this is a bug or do I miss something here? Kind regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Mei

pkg-base: how to avoid FreeBSD-$PACKAGE-{profile|development} when using FreeBSD pkg-base

2018-08-25 Thread O. Hartmann
opment stuff, so is there a way to avoid building those unwanted packages in the first place? At the end my PINE64 wnats to install 313 packages. This seems 2/3 unnecessary. Kind regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die

[CURRENT, ezjail] rc, rc.subr and other rc. scripts gone: ezjail fails on 12-ALPHA

2018-08-25 Thread O. Hartmann
unsure whether this is a "real" bug or I did just miss some important changes and I didn't catch up. Thanks in advance, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

2018-08-20 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Mon, 20 Aug 2018 21:24:21 +0200 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Building NanoBSD world on CURRENT r338113 fails due to: > > [...] > cd /pool/sources/CURRENT/sr

buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

2018-08-20 Thread O. Hartmann
UT_LLVM_TARGET_ALL=YES WITH_ZONEINFO_LEAPSECONDS_SUPPORT=YES WITHOUT_SVN=YES WITH_SORT_THREADS=YES WITH_EXTRA_TCP_STACKS=YES # INSTALL_NODEBUG=YES ' - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). --

LUA loader: non UEFI boxes have weird ssh output

2018-08-19 Thread O. Hartmann
brain-dead" systems work, sshd is dead. This isn't the case on UEFI boxes with the very same revision (r338057). Is this a coincidence or is this/could this related to the switch to LUA loader? - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke od

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-19 Thread O. Hartmann
't take care of the "set" you may have used to optimise. But this is something you're able to deal with easily yourself after having setup your basic build environment. Regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder fü

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

2018-08-15 Thread O. Hartmann
On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > >> i also attempted to boot using UEFI but the system hangs very early in the > >> boot process. i have reverted to legacy mode for now so

Re: EFIRT on machines with pcid after r337773

2018-08-15 Thread O. Hartmann
On Wed, 15 Aug 2018 01:17:55 +0300 Konstantin Belousov wrote: > If you use UEFI boot, have EFIRT compiled in kernel (the case of > GENERIC) or pre-loaded as module, and efirt is not disabled by a tunable, > and the machine resets during kernel initialization, try this. > > diff --git

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

2018-08-14 Thread O. Hartmann
On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > >> i also attempted to boot using UEFI but the system hangs very early in the > >> boot process. i have reverted to legacy mode for now so

Re: svn commit: r336940 - in head/sys: netinet netinet6 [This broke ci.freebsd.org 's FreeBSD-head-mips*-build 's]

2018-07-30 Thread O. Hartmann
On Mon, 30 Jul 2018 18:44:24 -0700 Mark Millard via svn-src-head wrote: > https://ci.freebsd.org/job/FreeBSD-head-mips-build/3577/consoleText shows: > > --- tcp_usrreq.o --- > cc1: warnings being treated as errors > /usr/src/sys/netinet/tcp_usrreq.c: In function 'tcp_usr_send': >

Re: console spam during mergemaster

2018-07-29 Thread O. Hartmann
: warning: duplicate > script for target "/var/tmp/temproot/etc/pam.d" ignored > > imb > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-curre

Re: EFI issues

2018-07-29 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Sun, 29 Jul 2018 15:17:53 +0400 Roman Bogorodskiy schrieb: > O. Hartmann wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Am Sun, 29 Jul 2018 12:09:58 +0400 > > Roman Bogorodskiy

Re: EFI issues

2018-07-29 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Sun, 29 Jul 2018 12:09:58 +0400 Roman Bogorodskiy schrieb: > O. Hartmann wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Am Sat, 28 Jul 2018 11:29:40 +0400 > > Roman B

Re: EFI issues

2018-07-29 Thread O. Hartmann
ot is the same as Boot0001 and is defined due to some "bug" Warner Losh has fixed recently, it is the same as Boot0001 Kind regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs.

Re: [UEFI] Boot issues on some UEFI implementations

2018-07-27 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Fri, 27 Jul 2018 13:59:44 +0300 Toomas Soome schrieb: > > On 27 Jul 2018, at 13:02, O. Hartmann wrote: > > > > On Fri, 27 Jul 2018 08:54:48 +0300 > > Toomas Soome wrote: > > > >>> On

Re: [UEFI] Boot issues on some UEFI implementations

2018-07-27 Thread O. Hartmann
On Fri, 27 Jul 2018 08:54:48 +0300 Toomas Soome wrote: > > 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

Re: [UEFI] Boot issues on some UEFI implementations

2018-07-26 Thread O. Hartmann
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" > <mailto:freebsd-...@pdx.rh.cn85.dnsmgr.net>&

Re: [UEFI] Boot issues on some UEFI implementations

2018-07-26 Thread O. Hartmann
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,

  1   2   3   4   5   6   7   8   9   10   >