Re: console: no USB keyboard!

On Sun, 14 Mar 2021 11:42:13 +0200 Andriy Gapon wrote: > On 13/03/2021 21:01, Hartmann, O. wrote: > > Running 14-CURRENT on several boxes (i.e. FreeBSD 14.0-CURRENT #49 > > main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 amd64) with custom > > and/or > >

Re: On 14-CURRENT: no ports options anymore?

On Sat, 13 Mar 2021 15:13:15 -0500 Michael Butler via freebsd-current wrote: > On 3/13/21 3:00 PM, Hartmann, O. wrote: > > On Sat, 13 Mar 2021 19:52:47 + (UTC) > > Filippo Moretti via freebsd-current wrote: > > > >> > >> I had the same pro

Re: On 14-CURRENT: no ports options anymore?

On Sat, 13 Mar 2021 19:52:47 + (UTC) Filippo Moretti via freebsd-current wrote: > > I had the same problem in console modeFiippo > On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefan Esser > wrote: > > Am 13.03.21 um 20:17 schrieb Hartmann, O.: > > Since

On 14-CURRENT: no ports options anymore?

Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set options via "make config" or via poudriere accordingly. I always get "===> Options unchanged" (when options has been already set and I'd expect a dialog menu). This misbehaviour is throughout ALL 14-CURRENT systems

console: no USB keyboard!

Running 14-CURRENT on several boxes (i.e. FreeBSD 14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 amd64) with custom and/or GENERIC kernel and USB-only equipment (mouse if available, keyboard). In multiuser mode, there is no problem using the USB keyboard. On single user

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

On Wed, 10 Feb 2021 07:21:20 +0100 "Hartmann, O." wrote: > On Tue, 9 Feb 2021 15:15:38 -0800 > John Baldwin wrote: > > > On 2/9/21 2:16 PM, Hartmann, O. wrote: > > > On Wed, 3 Feb 2021 17:34:24 +0100 > > > Guido Falsi via freebsd-current wrote

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

On Tue, 9 Feb 2021 15:15:38 -0800 John Baldwin wrote: > On 2/9/21 2:16 PM, Hartmann, O. wrote: > > On Wed, 3 Feb 2021 17:34:24 +0100 > > Guido Falsi via freebsd-current wrote: > > > >> On 03/02/21 17:02, John Baldwin wrote: > >>> On 2/2/21 10:16

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

On Wed, 3 Feb 2021 17:34:24 +0100 Guido Falsi via freebsd-current wrote: > On 03/02/21 17:02, John Baldwin wrote: > > On 2/2/21 10:16 PM, Hartmann, O. wrote: > >> On Mon, 1 Feb 2021 03:24:45 + > >> Rick Macklem wrote: > >> > >>>

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

On Mon, 1 Feb 2021 03:24:45 + Rick Macklem wrote: > Rick Macklem wrote: > >Guido Falsi wrote: > >[good stuff snipped] > >>Performed a full bisect. Tracked it down to commit aa906e2a4957, adding > >>KTLS support to embedded OpenSSL. > >> > >>I filed a bug report about this: > >> > >>https://

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

On Sat, 30 Jan 2021 16:22:50 +0100 Guido Falsi via freebsd-current wrote: > On 30/01/21 12:34, Guido Falsi via freebsd-current wrote: > > On 30/01/21 11:25, Tomoaki AOKI wrote: > >> On Sat, 30 Jan 2021 07:39:23 +0100 > >> "Hartmann, O." wrote: > >&g

(n244517-f17fc5439f5) svn stuck forever in /usr/ports?

We recently updated to FreeBSD 14.0-CURRENT #9 main-n244517-f17fc5439f5: Fri Jan 29 16:29:50 CET 2021 amd64. After make delete-oldfiles/delete-old-libs, the command make update issued in /usr/ports on those 14-CURRENT boxes remains stuck forever or it is working like a snail! Hitting Ctrl-t

(n244517-f17fc5439f5) svn stuck forever in /usr/ports?

We recently updated to FreeBSD 14.0-CURRENT #9 main-n244517-f17fc5439f5: Fri Jan 29 16:29:50 CET 2021 amd64. After make delete-oldfiles/delete-old-libs, the command make update issued in /usr/ports on those 14-CURRENT boxes remains stuck forever or it is working like a snail! Hitting Ctrl-t

WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0.

Running FreeBSD CURRENT on a USB only platform with a customised kernel, I see this message all the time I reboot or log console messages: [...] WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0. Where does this message come from and what is causing the warning? I trie

CURRENT, usr/src on git, howto "mergemaster"?

Now, since /usr/src has been siwtched to git on several boxes and the former svn tag $FreeBSD$ seem not valid/useful anymore, how am I (or any other here) supposed to "mergemaster"? I did a full "mergemaster -CUFi" lately and did the same again, but when mergemaster ran the second (or n-th) tim

Re: Terminal colours in current

On Sat, 2 Jan 2021 08:40:55 +0300 Rozhuk Ivan wrote: > On Sat, 2 Jan 2021 06:33:55 +0100 > "Hartmann, O." wrote: > > > Colour settings seem to be broken since a couple of months. Out of > > the blue, coloured kernel messages vanished - this problem is on 1

Re: Terminal colours in current

On Sat, 2 Jan 2021 08:25:49 +0300 Rozhuk Ivan wrote: > Hi! > > I am tring current and found that kernel options: > options TERMINAL_NORM_ATTR = (FG_GREEN|BG_BLACK) # def to > SC_NORM_ATTR / 2 | 0x00 options TERMINAL_KERN_ATTR = > (FG_YELLOW|BG_BLACK) # def t

Re: # Fssh_packet_write_wait: Connection to 77.183.250.3 port 22: Broken pipe

On Wed, 30 Dec 2020 12:13:44 +0100 Michael Tuexen wrote: > On 30. Dec 2020, at 08:04, Hartmann, O. wrote: > > > > On recent 12-STABLE, 12.1-RELENG and 12.2-RELENG I face a very nasty > > problem which > > occured a while ago after it seemed to have vanished for a w

# Fssh_packet_write_wait: Connection to 77.183.250.3 port 22: Broken pipe

On recent 12-STABLE, 12.1-RELENG and 12.2-RELENG I face a very nasty problem which occured a while ago after it seemed to have vanished for a while: running ssh in a xterm on FreeBSD boxes as mentioned at the beginning ends up very rapidly in a lost connection with # Fssh_packet_write_wait: Con

Re: AMNESIA:33 and FreeBSD TCP/IP stack involvement

> Hartmann, O. wrote this message on Wed, Dec 09, 2020 at 06:58 +0100: > > I've got a question about recently discovered serious > > vulnerabilities in certain TCP stack implementations, designated as > > AMNESIA:33 (as far as I could follow the recently made > &

AMNESIA:33 and FreeBSD TCP/IP stack involvement

Hello, I've got a question about recently discovered serious vulnerabilities in certain TCP stack implementations, designated as AMNESIA:33 (as far as I could follow the recently made announcements and statements, please see, for instance, https://www.zdnet.com/article/amnesia33-vulnerabilities-imp

r366623: lock order reversal in ZFS

On a recent CURRENT bos acting as poudriere host, we face after a crash under heavy load and extensive swap usage now this lock order reversal warning on the console: lock order reversal: 1st 0xf8007bdd9e00 zfs (zfs, lockmgr) @ /usr/src/sys/kern/vfs_mount.c:1018 2nd 0xf8034abfc070 devfs (

CURRENT: cross compiling 12-STABLE failure in: bin/cp/utils.c:517:14: error: member reference base type 'void' is not a structure or union

For a couple of weeks now cross-compiling 12-STBALE on CURRENT fails due to an compiler error in bin/cp/utils.c, see details below. At this moment, CURRENT is at FreeBSD 13.0-CURRENT #39 r366364: Fri Oct 2 17:51:39 CEST 2020 amd64 and the sources for 12-STABLE are at revision 366437. The compila

bin/cp/utils.c:517:14: error: member reference base type 'void' is not a structure or union (RESCUE)

A couple of weeks for now it is impossible to compile nanoBSD (based on 12-STABLE, most recent r365925), compiled on a host running recent CURRENT (FreeBSD 13.0-CURRENT #0 r365487: Fri Sep 18 16:31:04 CEST 2020 amd64). Since the introduction of LLVM 10 to 12-STABLE and LLVM 11 to CURRENT, the (cros

Re: buildworld: "cp: /dev/null: Invalid argument"

On Sat, 12 Sep 2020 10:03:18 +0200 Michael Gmelin wrote: > > On 12. Sep 2020, at 09:55, Hartmann, O. > > wrote: > > > > On Fri, 11 Sep 2020 07:18:33 -0600 > > Alan Somers wrote: > > > >>> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann > &g

Re: buildworld: "cp: /dev/null: Invalid argument"

On Fri, 11 Sep 2020 07:18:33 -0600 Alan Somers wrote: > On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann > wrote: > > > On Thu, 10 Sep 2020 10:44:08 -0600 > > Alan Somers wrote: > > > > > No, it's devfs. I'll fix it. > > > > > > On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone > > > wrote: > > > >

cp/utils.c:517:14: error: member reference base type 'void' is not a structure or union

Building recent 12-STABLE (revision 365643) for a nanobsd environment on a CURRENT host fails since a couple of weeks for now with the weird error shown below. The CURRENT host is running at FreeBSD 13.0-CURRENT #20 r365382: Fri Sep 11 19:01:26 CEST 2020 amd64. Building 12-STABLE jails at the very

Re: buildworld: "cp: /dev/null: Invalid argument"

On Thu, 10 Sep 2020 10:35:08 -0400 Michael Butler wrote: > Is anyone else seeing failures like this in building world and, in my > case, cron jobs as well? > > > Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr > --- all_subdir_sbin --- > Building /usr/obj/usr/src/amd64.amd6

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

On Fri, 28 Aug 2020 13:16:05 +0200 Mateusz Guzik wrote: > On 8/28/20, Hartmann, O. wrote: > > On Fri, 28 Aug 2020 12:31:21 +0200 > > Mateusz Guzik wrote: > > > >> Can you show more of the log? > >> > >> When you installkernel you should see: &

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

Do these dirs exist now? It is not existent, as expected: # ll /usr/lib/debug/boot/kernel/ ls: /usr/lib/debug/boot/kernel/: No such file or directory > > On 8/28/20, Hartmann, O. wrote: > > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 16:10:50 > > CEST 2020 am

installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 16:10:50 CEST 2020 amd64), /usr/src at revision 364907, installkernel fails now due to an error as shown below. For the record, "options ZFS" ist statically in the kernel config file. Also deleting /usr/obj and restarting buildworld and bu

Re: ld: error: duplicate symbol:

On Mon, 17 Aug 2020 21:49:52 +0200 Dimitry Andric wrote: > On 17 Aug 2020, at 15:42, O. Hartmann wrote: > > > > On CURRENT 9not necessarily most recent with LLVM11, but since noon > > of today it is FreeBSD 13.0-CURRENT #15 r364297: Mon Aug 17 > > 14:39:06 CEST 2020 amd64) I'm faced with some v

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

On Fri, 3 Jul 2020 17:58:27 +0200 Stefan Eßer wrote: > Am 03.07.20 um 17:24 schrieb O. Hartmann: > > Hello list, > > > > running some scripts caluclating via bc() the expression shown > > below: > > > > bc -e '6582031 - 1048576 - 0 - 409600 - 1024 - 40 - 4096' -e quit > > The bc in -CURRENT

Re: weird Ctrl-T debug messages

On Sat, 27 Jun 2020 06:21:17 -0700 John Baldwin wrote: > On 6/27/20 2:59 AM, Michael Gmelin wrote: > > > > > > On Sat, 27 Jun 2020 12:06:17 +0300 > > Andriy Gapon wrote: > > > >> On 27/06/2020 10:44, Li-Wen Hsu wrote: > >>> On

weird Ctrl-T debug messages

Running poudriere on recent CURRENT with (recent) 12-STABLE and CURRENT jails reveals a weird behaviour recently when hitting Ctrl-T: [...] [13:37:48] [01] [00:00:00] Building databases/sqlitestudio | sqlitestudio-3.2.1.1002 load: 26.95 cmd: sh 99331 [piperd] 49375.18r 0.59u 0.59s 0% 2144k #0 0x

Re: Compiling MOD_CC into kernel (TCP congestion control)?

On Sat, 25 Apr 2020 22:13:08 +0200 Michael Tuexen wrote: > > On 25. Apr 2020, at 19:28, Hartmann, O. > > wrote: > > > > On a firewall/router project of ours I try to experiment with > > several options/algorithms for mod_cc(4). The kernel is compiled > >

Compiling MOD_CC into kernel (TCP congestion control)?

On a firewall/router project of ours I try to experiment with several options/algorithms for mod_cc(4). The kernel is compiled statically, so that no kernel module can be loaded at runtime, therefor I need to compile the different modules mod_cc into the kernel. The manpage mod_cc(4) states: " ...

Re: 12-STABLE: BEARSSL: liblua compiler error: too few arguments to function call

On Thu, 9 Apr 2020 22:07:59 -0700 "Simon J. Gerraty" wrote: > Hartmann, O. wrote: > > > While recent CURRENT doesn't show any problems, 12-STABLE (r359768) > > drops out from buildworld with the error shown below when option > > > > WITH_BEARSSL= Y

12-STABLE: BEARSSL: liblua compiler error: too few arguments to function call

While recent CURRENT doesn't show any problems, 12-STABLE (r359768) drops out from buildworld with the error shown below when option WITH_BEARSSL= YES is set in /etc/src.conf [...] Building /usr/obj/usr/src/amd64.amd64/stand/liblua/lutils.o --- lstd.o --- /usr/src/stand/liblua/lstd.c:86:44: erro

Re: Supermicro X9SCV-Q: no boot options to define

On Wed, 11 Dec 2019 10:48:22 +0100 Gary Jennejohn wrote: > On Wed, 11 Dec 2019 08:23:59 +0100 > "Hartmann, O." wrote: > > > Hello folks, > > > > my apology for polluting this list with a non-FreeBSD specific > > problem, but since Supermicro is a

Supermicro X9SCV-Q: no boot options to define

Hello folks, my apology for polluting this list with a non-FreeBSD specific problem, but since Supermicro is a veryy often used vendor in the FreeBSD user/developer community I might find help here much fast. I got hands on onto an oldish Supermicro X9SCV-Q mainboard, equipted with an older i5-25

hdac0: Unexpected unsolicited response from address 0: 00000000

Hello list, on a Lenovo E540 I get this weird error since I used 12-STABLE/CURRENT on this specific notebook. I guess it has a Optimus Intel iGPU/nVidia NV940 GPU system and usable is only the iGPU with port graphics/drm-fbsd12.0-kmod. The notebook doesn't have audio anymore, nor can I use vlc, m

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

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" > > schrieb: > >> -BEGIN PG

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

Updated Fujitsu Celsius M740 to its lates UEFI firmware today. After this update, the box won't boot FreeBSD 12-STABLE anymore! With disabled CSM, the firmware doesn't recognise the boot SSD's freebsd-efi partition for UEFI boot anymore - which was no problem before. When trying FreeBSD 13-CURRENT

/usr/doc: can not build documentation: parser error : Failure to process entity chap.mirrors.ftp.index.inc

Last time I built the documentation was 2017. Since then my attempts to build the /usr/doc failed. Just retrieving the recent /usr/doc via svn (r52522), reinstalling textproc/docproj via portmaster -df (recursively to ensure nothing is missing), ends up in errors. One of the prominent error after p

WiFi QCA986x/988x 802.11ac Wireless Network Adapter support?

For a while 802.11ac adapters are out and some of them made by Qualcomm/Atheros are considered useful for building accesspoints, like the QCA9882. Running revent 12-ALPHA6 on an APU from PCengines equipted with such an WiFi adaptor (I think this product is named Compex WLE600V) and ath/ath_hal dri

ppp.linkup: How is the !bg argument expanded and substituted?

Hello list, my question may sound blunt but I miss something with the documentation of ppp(8). Background: My homeoffice is running a network and server infrastructure I'd like to access from the internet, therefore, I use a DDNS service. My gateway is a FreeBSD based small, efficient NanoBSD bas

r338446: network access freezing on em/igb NICs

Running CURRENT (FreeBSD 12.0-ALPHA4 #19 r338446: Mon Sep 3 21:07:45 CEST 2018 amd64) on a PCengine APU2C4 (NIC is 3x Intel i210: [...] igb0@pci0:2:0:0:class=0x02 card=0x8086 chip=0x157b8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'I210 Gigabit Network C

CURRENT r331284: crashing with USB

Hello. Incident: CURRENT r331284 can be brought down reliably with an USB flash drive plugged in and out without mounting or doing anything with it. I first recognized the incident with a ZFS on a SanDisk 32GB USB 3.0 flash drive. Plugging the USB flash and typing "zpool import" revealed the very

Re: Speed up CD/DVD-based FreeBSD

On Mon, 12 Mar 2018 09:00:28 +0100 Andreas Nilsson wrote: Sorry for the late reply, I'll answer inline, see below. > On Mon, Mar 12, 2018 at 8:30 AM, Rodney W. Grimes < > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > We have a special case of running FreeBSD (actually a NanoBSD) > > > fr

/lib/casper: read error: Invalid argument

Again, I ran into a havoc update of CURRENT last night. While booting a freshly installed kernel and performing "make -j4 installworld", the box suddenly rebooted - out of the blue. With the wrecked CURRENT left behind (r327866), I'm not able to boot even into single user mode. The box halts with

Re: SMART: disk problems on RAIDZ1 pool: (ada6:ahcich6:0:0:0): CAMstatus: ATA Status Error

On Tue, 12 Dec 2017 14:58:28 -0800 Cy Schubert wrote: > There are a couple of ways you can address this. You'll need to > offline the vdev first. If you've done a smartcrl -t long and if the > test failed, smartcrl -a will tell you which block it had an issue > with. You can use dd, ddrescue or d

CURRENT: kernel crash r326347: Cannot access memory at address 0x65657246

Since yesterday's CURRENT update, I face worse and nasty problems on all of our CURRENT systems! Most recent CURRENT, as with r326363, crashes on booting the kernel, in another case the kernel is stuck and freezing after initialising the USB subsystem (the last thing I see on screen, keyboard full

src.conf: setting WITHOUT_DEBUG_FILES has no effect

Setting WITHOUT_DEBUG_FILES=YES in /etc/src.conf is supposed to prevent building debug files for shared libs and binaries - that is my interpretation of the manpage of src.conf(5). After each run of buildworld buildkernel && installkernel && installworld and performing a make delete-old the

Re: SIGSEGV in /bin/sh after r322740 -> r322776 update

On Tue, 22 Aug 2017 06:38:36 -0700 David Wolfskill wrote: I also ran into this problem after "upgrading" to r322769 and now I have on ALL systems, I did this "upgrade", a wrecked system which isn't even capable of compiling a new kernel or world. I can understand that something weird and havoc

Re: static routes on VLAN on CURRENT

On Sun, 2 Jul 2017 14:39:34 +0200 Milan Obuch wrote: > On Sun, 2 Jul 2017 13:40:01 +0200 > "Hartmann, O." wrote: > > [ snip ] > > > On igb1.2 (vlan tag 2) I want to run an asterisk PBX (that is the > > main goal). The interface is attached with the IP 192.

static routes on VLAN on CURRENT

Fiddling around with a self-brewn router/firewall based on 12-CURRENT and ipfw, I run into problems when setting up a trunk port with different VLANs and static routes. The "router" has three NICs, igb0, igb1, igb2 (it is de facto an APU 2C4 from PCengines). igb0 is attached to an external VDSL2+

Re: ino64: desastrous update - recommendations not working!!!

On Wed, 24 May 2017 14:31:08 +0300 Konstantin Belousov wrote: > On Wed, May 24, 2017 at 12:42:19PM +0200, Hartmann, O. wrote: > > On almost every CURRENT that has been updated according to UPDATING > > entry 2017-05-23 regarding ino64, the recommended update process > > end

ino64: desastrous update - recommendations not working!!!

On almost every CURRENT that has been updated according to UPDATING entry 2017-05-23 regarding ino64, the recommended update process ends up in a desaster or, if the old environemnt/kernel is intact, itr doesn't work. Procedure: make -jX buildworld buildkernel [successful] make installkernel [suc

Re: r316677:EFI boot failure: Can't load kernel

t; Toomas Soome schrieb: > > > > > >>> On 10. apr 2017, at 15:58, Hartmann, O. > > >>> wrote: > > >>> > > >>> After today's update to r316677, some UEFI boxes (Fujitsu > >

Re: r316677:EFI boot failure: Can't load kernel

t; Toomas Soome schrieb: > > > > > >>> On 10. apr 2017, at 15:58, Hartmann, O. > > >>> wrote: > > >>> > > >>> After today's update to r316677, some UEFI boxes (Fujitsu > >

r316677:EFI boot failure: Can't load kernel

After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740 XEON) reject to boot properly. They die immediately after loading /boot/loader.efi and jump into loader prompt: [...] \ can't load 'kernel' I had to investigate with an USB flashdrive the filesystem, but everything seems to b

Help! Howto installworld crashed system with USB image?

Within the past several hours, FreeBSD crashed due to serious bugs and some boxes of ours hang with the uncomplete workaround with EARLY_AP_STARTUP. During a recompilation and installworld/installkernel, one of my workstations suddenly crashed and spontaneously rebooted. After that, the loader comp

r312349 crashes: null filesizes: rescue with usb stick impossible due to lack of CC

FreeBSD crashes (r312349): during installworld and installkernel, the running system crashed and left me with a nullyfied Samsung 850 PRO SSD, means: almost every binary in /bin, /sbin, /usr/bin, /usr/sbin has filesize NULL, execpt /bin/sh. Booting is impossible. Since it is unknown what the crash

r312348: igb broken: reporting wrong linkspeed!

12-CURRENT (FreeBSD 12.0-CURRENT #74 r312348: Tue Jan 17 19:54:58 CET 2017 am64) reports the wrong linkspeed on a dualport Intel i350 NIC: igb0: flags=8843 metric 0 mtu 1500 options=653dbb ether xx:xx:xx:xx:xx:xx inet 192.168.0.111 netmask 0xff00 broadcast 192.168.0.255 nd6 options=29

r311977: kernel build failure when NANDFS in kernel

On r311977, buildkernel fails with the error shown below. Kernel ist customised and "options NANDFS" has been added as well as "device nand" - the error shown suggest that is has to do with NANDFS. [...] ===> cc/cc_cdg (all) --- nand_geom.o --- /usr/src/sys/dev/nand/nand_geom.c:419:2: error: mus

iwm: loosing sporadically connection - iwm has never been stable

Using a Lenovo E540 laptop equipted with a Intel i7260 WiFi adapter (iwm0: mem 0xf0c0-0xf0c01fff at device 0.0 on pci3), this adaptor has never been fully operational since it got supported by FreeBSD on that specific laptop of mine. I'm running CURRENT(12.0-CURRENT #29 r310417: Thu Dec 22 17

Re: CURRENT: pkg broken on r309320

On Wed, 30 Nov 2016 12:10:31 + Matthew Seaman wrote: > On 2016/11/30 10:14, Baptiste Daroussin wrote: > > revert r309314 the issue is there: > > > > The ports tree defines PKG_CMD as pkg register but now bsd.own.mk > > predefines it to simply pkg. > > > > There is a collision there. > >

Re: CURRENT: re(4) crashing system

On Mon, 31 Oct 2016 11:12:22 +0900 YongHyeon PYUN wrote: > On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote: > > On Thu, 27 Oct 2016 10:00:04 +0900 > > YongHyeon PYUN wrote: > > > > > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote:

Re: CURRENT: re(4) crashing system

On Thu, 27 Oct 2016 10:00:04 +0900 YongHyeon PYUN wrote: > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > On Tue, 25 Oct 2016 11:05:38 +0900 > > YongHyeon PYUN wrote: > > > > [...] > > > > I'm not sure but it's likely t

Re: CURRENT: re(4) crashing system

On Tue, 25 Oct 2016 11:05:38 +0900 YongHyeon PYUN wrote: > On Mon, Oct 24, 2016 at 02:03:37PM +0200, O. Hartmann wrote: > > On Mon, 24 Oct 2016 14:14:00 +0900 > > YongHyeon PYUN wrote: > > > > > On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote: >

r307877: buildkernel fails: x86/cpu_machdep.c:564:1: error: function definition is not allowed here {

r307877 fails to buildkernel with the error shown below: [...] /usr/src/sys/x86/x86/cpu_machdep.c:564:1: error: function definition is not allowed here { ^ /usr/src/sys/x86/x86/cpu_machdep.c:574:2: error: expected '}' } ^ /usr/src/sys/x86/x86/cpu_machdep.c:541:1: note: to match this '{' { ^ 2 err

CURRENT: re(4) crashing system

I tried to report earlier here that CURRENT does have some serious problems right now and one of those problems seems to be triggered by the recent re(4) driver. The problem is also present in recen 11-STABLE! Below, you'll find pciconf-output reagrding the device on a Lenovo E540 Laptop I can tes

options EFIRT: immediate crash of CURRENT

Playing around with some EFI related options and putting options EFIRT into the kernel config, results in an immediate crash after booting, see screenshot attached. This happens on non-EFI booting systems as well as EFI capable systems. The screenshot is taken from a box with UEFI firmware, bu

Re: CURRENT: "service netif restart" looses default route

On Thu, 6 Oct 2016 09:27:53 +0200 Oliver Peter wrote: > On Wed, Oct 05, 2016 at 06:47:48PM +0200, O. Hartmann wrote: > > > > Today, I checked on two servers of ours running both a recent > > CURRENT (i.e. FreeBSD 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 > > CEST 2016) via "service netif res

Destroy GPT partition scheme absolutely, how?

I ran into a very nasty and time consuming problem. Creating a NanoBSD image with a modified script framework creating GPT partitions, I put the imaes via "dd(1)" on USB flash or SD flash. Because the images are usually much smaller than the overall capacity of the USB or SD, the OS (FreeBSD CURREN

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

Am 03/11/13 11:17, schrieb Dimitry Andric: > On 2013-03-10 00:39, Steve Kargl wrote: > ... >> If you have a clang built FreeBSD-current, then it is no >> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >> the upcoming gcc-4.8.0. AFAICT, the problem is related >> to /usr/bin/cpp. I haven'

Re: r247839: broken pipe - for top, sudo and ports

Am 03/10/13 21:44, schrieb Pawel Jakub Dawidek: > On Wed, Mar 06, 2013 at 08:04:57AM -0500, John Baldwin wrote: >> On Tuesday, March 05, 2013 2:35:48 pm Hartmann, O. wrote: >>> On recent FreeBSD 10.0-CURRENT/amd64 (CLANG buildworld, serveral systems >>> (3) the same sym

Re: CURRENT (r248061):Thunderbird SIGNAL 11 with OpenLDAP / nscd(1) broken pipe/

Am 03/09/13 23:21, schrieb Per olof Ljungmark: > On 2013-03-09 10:25, Hartmann, O. wrote: >> Am 03/09/13 10:07, schrieb Hartmann, O.: >>> For the introduction, I filed a PR for this at beginning of 2012 and >>> suffered from the very same problem close to two year

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

Am 03/09/13 18:07, schrieb David Wolfskill: > On Sat, Mar 09, 2013 at 06:06:05PM +0100, Hartmann, O. wrote: >> ... >> No, it isn't. Same error, system is at revision: >> FreeBSD 10.0-CURRENT #1 r248106: Sat Mar 9 16:44:58 CET 2013 amd64 >> >> The error i

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

Am 03/09/13 17:46, schrieb Ruslan Makhmatkhanov: > Hartmann, O. wrote on 09.03.2013 20:45: >> Am 03/09/13 17:38, schrieb Ruslan Makhmatkhanov: >>> Hartmann, O. wrote on 09.03.2013 20:31: >>>> I rebuild the kernel module for x11/nvidia-driver on a regular basis >&

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

Am 03/09/13 17:02, schrieb Dimitry Andric: > On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote: >> I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 >> r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build >> either lang/gcc or lang

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

Am 03/09/13 17:38, schrieb Ruslan Makhmatkhanov: > Hartmann, O. wrote on 09.03.2013 20:31: >> I rebuild the kernel module for x11/nvidia-driver on a regular basis via >> /etc/src.conf setting of >> >> PORTS_MODULES+=x11/nvidia-driver > > I answer

CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of PORTS_MODULES+=x11/nvidia-driver but this time, the port gets deleted and - fails to compile (tried 310.32 and 313.26, the latter worked for me before very well). The compilation err

CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build either lang/gcc or lang/gcc46 with the very same error shown below. The box is compiled with CLANG (buildworld/kernel). It doesn't matter whether I compile tho

Re: pw is broken?

Am 03/09/13 15:34, schrieb hiren panchasara: > On Mar 8, 2013 9:44 PM, "KT Sin" wrote: >> >> pw is crashing with seg fault due to this change? >> >> > http://svnweb.freebsd.org/base/head/lib/libutil/gr_util.c?r1=245390&r2=247919 > > I think the correct fix is committed with: > http://svnweb.freeb

r248093: Kernel build failure: /usr/src/sys/net80211/ieee80211_output.c:600:23: error: unused variable 'ic' [-Werror,-Wunused-variable]

On CURRENT, r248093, build of kernel fails due to the below shown error. [...] cc -c -O3 -O3 -Wno-error=unused-variable -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wn

Re: CURRENT (r248061):Thunderbird SIGNAL 11 with OpenLDAP / nscd(1) broken pipe/

Am 03/09/13 10:07, schrieb Hartmann, O.: > For the introduction, I filed a PR for this at beginning of 2012 and > suffered from the very same problem close to two years before on ALL > FreeBSD versions and platforms using OpenLDAP as the user backend: > > ports/164239: [PATCH] m

CURRENT (r248061):Thunderbird SIGNAL 11 with OpenLDAP / nscd(1) broken pipe/

For the introduction, I filed a PR for this at beginning of 2012 and suffered from the very same problem close to two years before on ALL FreeBSD versions and platforms using OpenLDAP as the user backend: ports/164239: [PATCH] mail/thunderbird: crash with nss_ldap Even with the suggested patch by

CURRENT: "broken pipe" / SIGNAL 13 / no X11 / OpenLDAP/nscd weirdness

The most recent CURRENT (FreeBSD 10.0-CURRENT #0 r247865: Wed Mar 6 08:52:15 CET 2013/amd64, built with CLANG and CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++11 set in /etc/src.conf, for the record) does have some serious issues and I'm wondering why others do not. The

Re: r247839: broken pipe - for top, sudo and ports

On 03/05/13 20:35, Hartmann, O. wrote: > On recent FreeBSD 10.0-CURRENT/amd64 (CLANG buildworld, serveral systems > (3) the same symptoms)), many services drop a sporadic > > broken pipe > > This happesn to system's top (I have to type it several times to get > fin

r247839: broken pipe - for top, sudo and ports

0.0CURRENT with CLANG can confirm this. Regards, Oliver On 03/05/13 10:33, Dimitry Andric wrote: > On 2013-03-05 10:16, Hartmann, O. wrote: >> On FreeBSD 10.0-CURRENT #3 r247829: Tue Mar 5 08:12:19 CET 2013/amd64 I >> run into a mess and can not figure out what happens. &

Re: r247835: drm2 code breaks buildkernel

On 03/05/13 11:46, Jean-Sébastien Pédron wrote: > On 05.03.2013 11:20, Hartmann, O. wrote: >> On r247835 build kernel fails: >> >> (...) >> /usr/src/sys/modules/drm2/drm2/../../../dev/drm2/drm_global.c:63:27: >> error: unused variable 'item' [-Werror,-

r247835: drm2 code breaks buildkernel

On r247835 build kernel fails: cc -O2 -pipe -O3 -pipe -march=native -O3 -march=native -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GATE/opt_global.h -I. -I@ -I@/contrib/altq -fno-common -fno-omit-frame-pointer -I/us

Re: r247829: dbus fails to start. portmaster SIGNAL 13 when doing extraction

On 03/05/13 10:33, Dimitry Andric wrote: > On 2013-03-05 10:16, Hartmann, O. wrote: >> On FreeBSD 10.0-CURRENT #3 r247829: Tue Mar 5 08:12:19 CET 2013/amd64 I >> run into a mess and can not figure out what happens. >> >> Suddenly, after upgrading, buildworld etc., dbus

Re: r247829: dbus fails to start. portmaster SIGNAL 13 when doing extraction

On 03/05/13 10:33, Dimitry Andric wrote: > On 2013-03-05 10:16, Hartmann, O. wrote: >> On FreeBSD 10.0-CURRENT #3 r247829: Tue Mar 5 08:12:19 CET 2013/amd64 I >> run into a mess and can not figure out what happens. >> >> Suddenly, after upgrading, buildworld etc., dbus

r247829: dbus fails to start. portmaster SIGNAL 13 when doing extraction

On FreeBSD 10.0-CURRENT #3 r247829: Tue Mar 5 08:12:19 CET 2013/amd64 I run into a mess and can not figure out what happens. Suddenly, after upgrading, buildworld etc., dbus fails to start so X11 is without mouse. Trying to rebuild the port dbus fails in a SIGNAL 13 while [do-extract]. This is

Re: loopback interface broken on current

On 01/04/13 09:45, Gary Jennejohn wrote: > On Thu, 03 Jan 2013 20:30:18 +0900 > KAHO Toshikazu wrote: > >> Hello, >> >>> There is still >ifa_del_loopback_route: deletion failed: 3 >>> that wasn't there before,but the 127.0.0.1 seems to be configured now: >> >> Do you have a line like net

Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2

On 08/16/12 17:44, Glen Barber wrote: > On Thu, Aug 16, 2012 at 05:33:20PM +0200, Hartmann, O. wrote: >> >> I ran into a very delicate and nasty situation. >> >> On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of >> CURRENT sources from yesterda

HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2

I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On

VirtualBox: Eating up 100% CPU, freezing Windows 7

I discover that when running Windows 7 in a VirtualBox On FreeBSD 10 (r238968: Wed Aug 1 14:26:40 CEST 2012), VBox is most recent from the ports, that the VirtualBox eats up 100% CPU time and freezes Windows 7 for more than a minute. For a minute or so, I can work, then, the freeze occurs again. I

  1   2   3   >