Re: Issue with gpart "Device Busy"

Am 15.04.2020 um 20:35 schrieb i...@dijix.com: I have an issue with gpart, it will not let me delete partition ada0p2 responding with “Device Busy” The man page gpart(8) says this may be shown if a partition exists but I cannot seem to delete partition 2 in my case via gpart delete or gpart

Re: Audio mixer and mixer control

Am 11.04.2020 um 06:57 schrieb O'Connor, Daniel via freebsd-stable: … So if I have dsp0 with line-in and line-out, and dsp3 with a S/PDIF out, there's no way to get the dsp0-"mix" over to dsp3? You can't use mixer to do what you want, but you can probably do something with a sox pipe line

Audio mixer and mixer control

Hello, today I wanted to utilize my optical S/PDIF out with an external D/A converter to empower my garden radio. Unfortunately, it seems mixer(8) isn't really doing what I understand a mixer's job is. As far as I understood, mixer(8) is just controlling/pushing settings to the dsp's

Re: UEFI ISO boot not working in 12.1 ?

Am 09.11.2019 um 18:24 schrieb Kyle Evans: On Sat, Nov 9, 2019 at 10:42 AM Chris Ross wrote: On Thu, Nov 07, 2019 at 02:53:25PM -0500, Chris Ross wrote: On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer wrote: You could try some bisection back along the 12 branch.. Yeah. I was hoping for an

ZVOLs volmode/sync performance influence – affecting windows guests via FC RDM.vmdk

Hello, I noticed a significant guest write performance drop with volmode=dev during my 12.1 fibre channel tests. I remember having heard of such reports by some people oaccasionally during the last years, so I decided to see how far I can track it down. Unfortunately, I found no way to

12.1-prerelease nullfs? related panic

Hello, got this panic today booting a test machine with kernel from 09/09/2019, r352054: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0x80541088 stack pointer   = 0x28:0xfe578420 frame pointer

Re: EFI loader doesn't handle md_preload (md_image) correct?

Am 16.05.2017 um 18:26 schrieb Harry Schmalzbauer: Bezüglich Toomas Soome's Nachricht vom 16.05.2017 18:20 (localtime): On 16. mai 2017, at 19:13, Harry Schmalzbauer wrote: Bezüglich Toomas Soome's Nachricht vom 16.05.2017 18:00 (localtime): On 16. mai 2017, at 18:45, Harry Schmalzbauer

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

Am 22.02.2019 um 04:51 schrieb Eugene Grosbein: 21.02.2019 22:27, Harry Schmalzbauer wrote: The object is clearly corrupted. Thanks to your hint to readelf, I found out that it gets corrupted during dump(8) (or resotore, not yet analyzed). The obj tree contains the good version, the dump

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

Am 21.02.2019 um 10:36 schrieb Konstantin Belousov: … ELF Header: Magic: 7f 45 4c 46 02 01 01 09 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current)

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

Am 21.02.2019 um 09:54 schrieb Konstantin Belousov: On Thu, Feb 21, 2019 at 09:24:43AM +0100, Harry Schmalzbauer wrote: Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: Hello, … gdb shows: Core was generated by `/usr/sbin/auditdistd'. Program terminated with signal 11, Segmentation fault

Strange rtld-elf failure on stable/12 [Was: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)]

Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: Hello, … gdb shows: Core was generated by `/usr/sbin/auditdistd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libutil.so.9...Reading symbols from /usr/lib/debug//lib/libutil.so.9.debug...done. done

libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

Hello, I'm tryint to upgrade a bhyve guest from stable/11 to stable/12. pkg(8) for example crashes with signal 11. I looked for other binaries affected by ldd /usr/sbin/* | & grep 'signal 11$' wich gives /usr/sbin/auditdistd: signal 11 /usr/sbin/bhyve: signal 11 /usr/sbin/bsnmpd: signal

Re: MSI allocation regression, still to be corrected in HEAD and please MFC before release/12.0 gets branched

Am 13.11.2018 um 19:45 schrieb Scott Long: On Nov 13, 2018, at 11:11 AM, Harry Schmalzbauer wrote: Am 13.11.2018 um 19:02 schrieb Scott Long: On Nov 12, 2018, at 10:03 AM, Harry Schmalzbauer wrote: Am 11.06.2018 um 20:28 schrieb Harry Schmalzbauer: Am 05.06.2018 um 19:54 schrieb Scott

Re: MSI allocation regression, still to be corrected in HEAD and please MFC before release/12.0 gets branched

Am 13.11.2018 um 19:02 schrieb Scott Long: On Nov 12, 2018, at 10:03 AM, Harry Schmalzbauer wrote: Am 11.06.2018 um 20:28 schrieb Harry Schmalzbauer: Am 05.06.2018 um 19:54 schrieb Scott Long: … Late in the 11.2 phase, I identified this commit as a regression for MSI (non-x) alloctaion

MSI allocation regression, still to be corrected in HEAD and please MFC before release/12.0 gets branched

Am 11.06.2018 um 20:28 schrieb Harry Schmalzbauer: Am 05.06.2018 um 19:54 schrieb Scott Long: … Late in the 11.2 phase, I identified this commit as a regression for MSI (non-x) alloctaion. I have an idea what probably causes the problem here (INTx allocation, although MSI (and MSI-x

12.0-BETA3 isp(4): exclusive sleep mutex CAM device lock (CAM device lock)

Hello, unnfortunately I can't determine if this is begnin, so I'd like to ask the experts: uma_zalloc_arg: zone "64" with the following non-sleepable locks held: exclusive sleep mutex CAM device lock (CAM device lock) r = 0 (0xf8000f1424d0) locked @

Re: ctld(8) 11.2-release lockup with w2k16 [Was: Re: ctld(8), multiple 'portal-group' on same socket (individual 'discovery-auth-group' restrictions)]

Am 05.07.2018 um 18:17 schrieb Harry Schmalzbauer: Am 21.10.2014 um 12:43 schrieb Edward Tomasz Napierała: On 1020T1035, Harald Schmalzbauer wrote:   Hello, I'm trying to move from istgt(1) to ctld(8), but it seems my setup isn't possible with ctld. Besides missing support for virtual-DVDs

ctld(8) 11.2-release lockup with w2k16 [Was: Re: ctld(8), multiple 'portal-group' on same socket (individual 'discovery-auth-group' restrictions)]

Am 21.10.2014 um 12:43 schrieb Edward Tomasz Napierała: On 1020T1035, Harald Schmalzbauer wrote: Hello, I'm trying to move from istgt(1) to ctld(8), but it seems my setup isn't possible with ctld. Besides missing support for virtual-DVDs ('UnitType DVD' in istgt) and real ODD-devices

Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2?

Am 16.06.2018 um 21:42 schrieb Harry Schmalzbauer: … To rule out a known vboxnetflt(4) limitation/failure, I'd like to know if somebody successfully uses vboxnetflt(4) from virtualbox-ose-kmod-5.2.12 on stable/11|11.2. Really nobody out there who has VirtualBox sucessfully running under

Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2?

Hello, I'm observing some kind of congestion with virtualbox-ose-kmod-5.2.12 on -current. Frames from the guest make it through ng_ether(4), but frames coming from ng_ether(4) seem to choke this direction. Initially, the guest successfully can get a DHCP lease (both, v4 and v6) and all DNS

Re: removable storage usability, devd, hald and X11-desktop in general

Am 20.05.2018 um 23:52 schrieb EBFE: On Sat, 19 May 2018 20:35:59 +0200 Harry Schmalzbauer <free...@omnilan.de> wrote: Hi, Biggest question: How are useres expected to handle removable media? I'm a happy user of autofs(5) in several environments (mostly for NFS mounts), but I'm not

removable storage usability, devd, hald and X11-desktop in general

Hello, after 10 years I replaced my personal desktop machine (FreeBSD8 -> FreeBSD12). While aware of OS progress, I haven't followed any development on the X11 planet. To my surprise, things were in better shape 10 years ago, regarding desktop usability. Biggest question: How are useres

11.2 roadmap - Up to date www.freebsd.org/releng/#schedule?

Dear REs et al. commit log indicates that 11.2 is going to be on it's way in not too distant future – my personal interpretation only! Is https://www.freebsd.org/releng/#schedule up to date? Or is there a different/better source for such info (for those without svn accounts)? Thanks, -harry

New in 11? ZFS ACL -> aclinherit stacks synthesized mode ACEs

Hello, quick question, haven't had time to investigate yet, but accidentally noticed that something between FreeBSD 10 and 11 has changed regarding ZFS ACL inheritance. Example: If a parent directory has the file-inherit flag is set in a mode synthesized ACE, the ACL of a file in that directory

Re: EFI loader doesn't handle md_preload (md_image) correct?

Bezüglich Toomas Soome's Nachricht vom 29.06.2017 10:39 (localtime): > >> On 29. juuni 2017, at 11:24, Harry Schmalzbauer <free...@omnilan.de >> <mailto:free...@omnilan.de>> wrote: >> >> Bezüglich Harry Schmalzbauer's Nachricht vom 16.05.2017 18:26 (

Re: buildworld fail in stable/11 @r325033 -- r325029?

Bezüglich Konstantin Belousov's Nachricht vom 27.10.2017 16:42 (localtime): > On Fri, Oct 27, 2017 at 04:12:54AM -0700, David Wolfskill wrote: >> This is observed on systems (both my laptop & my build machine) running >> stable/11 @r325003, after updating sources to r325033: >> >> ---

Re: buildworld fail in stable/11 @r325033 -- r325029?

Bezüglich David Wolfskill's Nachricht vom 27.10.2017 13:12 (localtime): > This is observed on systems (both my laptop & my build machine) running > stable/11 @r325003, after updating sources to r325033: > > --- libprocstat.o --- > In file included from /usr/src/lib/libprocstat/libprocstat.c:69: >

Re: reboot-less zfs volmode property refresh?

Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:57 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:33 (localtime): … >> 3.) Modify existing volmode=dev dataset and write new GPT >> >> zfs set volmode=geom >> hostPsys/bhyveVOL/sys/test

Re: reboot-less zfs volmode property refresh?

Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:33 (localtime): > Hello, > > maybe I'm just missing something obvious, but modifying a dataset's > volmode property seems to force me to reboot the host to have any effect. > > Test to reproduce (parent dataset hostPsys/bhyveVOL/sys has

reboot-less zfs volmode property refresh?

Hello, maybe I'm just missing something obvious, but modifying a dataset's volmode property seems to force me to reboot the host to have any effect. Test to reproduce (parent dataset hostPsys/bhyveVOL/sys has volmode set ot "dev"): 1.) Create new volume with volmode=geom, and write new GPT

bhyve ppt usage can cause severe RAM corruption [Was: Re: panic: Memory modified after free in zio_create, passthru in use]

Bezüglich Harry Schmalzbauer's Nachricht vom 11.06.2017 12:37 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 06.06.2017 14:03 (localtime): >> Hello, >> >> suddenly, I'm getting this error: >> /lib/libc.so.7: Undefined symbol "xdr_accepted_reply" >> >> Very mysterious: It showed up

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

Bezüglich Harry Schmalzbauer's Nachricht vom 03.10.2017 16:39 (localtime): > Bezüglich Andriy Gapon's Nachricht vom 03.10.2017 16:28 (localtime): >> On 03/10/2017 17:19, Harry Schmalzbauer wrote: >>> Have tried several different txg IDs, but the latest 5 or so lead to the >&g

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

Bezüglich Andriy Gapon's Nachricht vom 03.10.2017 16:28 (localtime): > On 03/10/2017 17:19, Harry Schmalzbauer wrote: >> Have tried several different txg IDs, but the latest 5 or so lead to the >> panic and some other random picked all claim missing devices... >> Doh, if I on

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

Bezüglich Andriy Gapon's Nachricht vom 03.10.2017 11:20 (localtime): > On 03/10/2017 11:43, Harald Schmalzbauer wrote: > ... >> action: The pool can be imported despite missing or damaged devices. The >> fault tolerance of the pool may be compromised if imported. > ... >> Is it

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

Bezüglich Andriy Gapon's Nachricht vom 02.10.2017 13:49 (localtime): > On 01/10/2017 00:38, Harry Schmalzbauer wrote: >> Now my striped mirror has all 4 devices healthy available, but all >> datasets seem to be lost. >> No problem for 450G (99,9_%), but there's a 80M dat

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

Bezüglich Scott Bennett's Nachricht vom 01.10.2017 15:20 (localtime): > On Sat, 30 Sep 2017 23:38:45 +0200 Harry Schmalzbauer > <free...@omnilan.de> > wrote: … >> >> OpenIndiana also panics at regular import. >> Unfortunately I don't know the aeq

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

Bezüglich Harry Schmalzbauer's Nachricht vom 30.09.2017 19:25 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 30.09.2017 18:30 (localtime): >> Bad surprise. >> Most likely I forgot to stop a PCIe-Passthrough NIC before shutting down >> that (byhve(8)) guest – jhb@ helped my

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

Bezüglich Harry Schmalzbauer's Nachricht vom 30.09.2017 18:30 (localtime): > Bad surprise. > Most likely I forgot to stop a PCIe-Passthrough NIC before shutting down > that (byhve(8)) guest – jhb@ helped my identifying this as the root > cause for sever memory corruptions I regularly had (on

panic: Solaris(panic): blkptr invalid CHECKSUM1

Bad surprise. Most likely I forgot to stop a PCIe-Passthrough NIC before shutting down that (byhve(8)) guest – jhb@ helped my identifying this as the root cause for sever memory corruptions I regularly had (on stable-11). Now this time, corruption affected ZFS's RAM area, obviously. What I

find(1)'s "newer" primary expression gives wrong results with symbolic links

Hello, utilizing find(1)'s 'newer' primary expression is broken with symbolic links (for a very long time). Anyone who is using find for timestamp comparings should pay special attention regarding symbolic links. The man page states for "-P" (which ist the default), that »the file

Re: Any support creating a Windows Server 2012 unattended install

Bezüglich Paul Webster's Nachricht vom 13.07.2017 10:22 (localtime): > Ah ha we can now see installs, perfect thank you harry! just what I > needed I thought we still had no way of seeing the install process You can run anything that provides a UEFIx64 loader with VNC-graphics, due to the ongoing

Re: EFI loader doesn't handle md_preload (md_image) correct?

Bezüglich Harry Schmalzbauer's Nachricht vom 16.05.2017 18:26 (localtime): > B … The issue is, that current UEFI implementation is using 64MB staging memory for loading the kernel and modules and files. When the boot is called, the relocation code will put the bits from staging

[LOR] 11.1-BETA1 dev/md/md.c <-> vm/vm_pager.c - lost begnin matchlist

Dear hackers, I couldn't find a up to date list for begning LOR reports. Since ffs/vfs.. LORs, which I don't understand, diffused my attention over the time, I'm not aware about the actual importance of them these days (without panic). Here's is one, happening on 11.1-BETA1. which I haven't

panic: Memory modified after free in zio_create, passthru in use [Was: 11.1-pre runtime Undefined symbol "xdr_accepted_reply" /lib/libc.so.7]

Bezüglich Harry Schmalzbauer's Nachricht vom 06.06.2017 14:03 (localtime): > Hello, > > suddenly, I'm getting this error: > /lib/libc.so.7: Undefined symbol "xdr_accepted_reply" > > Very mysterious: It showed up on a running system, which worked > flawlessly for some hours. And that host has

11.1-pre runtime Undefined symbol "xdr_accepted_reply" /lib/libc.so.7

Hello, suddenly, I'm getting this error: /lib/libc.so.7: Undefined symbol "xdr_accepted_reply" Very mysterious: It showed up on a running system, which worked flawlessly for some hours. And that host has root-fs (/) mounted readonly from a memorydisk. So to my understanding, it's completely

Re: [ports] r438901 causes PACKAGES= issues

Bezüglich Harry Schmalzbauer's Nachricht vom 04.06.2017 17:00 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 22.05.2017 12:51 (localtime): >> Bezüglich Julian Elischer's Nachricht vom 22.05.2017 09:52 (localtime): >>> On 22/5/17 3:04 pm, Harry Schmalzbauer wrote

Re: [ports] r438901 causes PACKAGES= issues

Bezüglich Harry Schmalzbauer's Nachricht vom 22.05.2017 12:51 (localtime): > Bezüglich Julian Elischer's Nachricht vom 22.05.2017 09:52 (localtime): >> On 22/5/17 3:04 pm, Harry Schmalzbauer wrote: >>> Bezüglich Harry Schmalzbauer's Nachricht vom 21.05.2017 20:25 >>

ifconfig(4) name and tap(4)'s character special device name

Hello, renaming vmnet/tap(4) interfaces, defined in rc.conf(5) via "cloned_interfaces" e.g, isn't prohibited by rc(8)-network.subr nor by ifconfig(8). If such a interface is renamed, the Ethernet device shows up correctly, with the new name and ifconfig(8) also reports the new name if it's

Re: Update netmap for 11.1-RELEASE

Bezüglich George Amanakis via freebsd-stable's Nachricht vom 24.05.2017 19:09 (localtime): > Regarding the upcoming 11.1-RELEASE: > Could somebody update netmap from CURRENT to STABLE, so that it would make it > into 11.1-RELEASE? > I would really like to see ptnet and ptnetmap in 11.1-RELEASE.

Re: [ports] r438901 causes PACKAGES= issues

Bezüglich Julian Elischer's Nachricht vom 22.05.2017 09:52 (localtime): > On 22/5/17 3:04 pm, Harry Schmalzbauer wrote: >> Bezüglich Harry Schmalzbauer's Nachricht vom 21.05.2017 20:25 >> (localtime): >>> Mk still tells: >>> # PACKAGES - A top leve

Re: [ports] r438901 causes PACKAGES= issues

Bezüglich Harry Schmalzbauer's Nachricht vom 21.05.2017 20:25 (localtime): > Mk still tells: > # PACKAGES - A top level directory where all packages go > (rather than > # going locally to each port). > # Default:

[ports] r438901 causes PACKAGES= issues

Mk still tells: # PACKAGES - A top level directory where all packages go (rather than # going locally to each port). # Default: ${PORTSDIR}/packages Since r438901 (

Re: EFI loader doesn't handle md_preload (md_image) correct?

Bezüglich Toomas Soome's Nachricht vom 16.05.2017 18:20 (localtime): > >> On 16. mai 2017, at 19:13, Harry Schmalzbauer <free...@omnilan.de> wrote: >> >> Bezüglich Toomas Soome's Nachricht vom 16.05.2017 18:00 (localtime): >>> >>>> On 16. mai 2017,

Re: EFI loader doesn't handle md_preload (md_image) correct?

Bezüglich Toomas Soome's Nachricht vom 16.05.2017 18:00 (localtime): > >> On 16. mai 2017, at 18:45, Harry Schmalzbauer <free...@omnilan.de >> <mailto:free...@omnilan.de>> wrote: >> >> Bezüglich Harry Schmalzbauer's Nachricht vom 16.05.2017 17:28 (l

Re: EFI loader doesn't handle md_preload (md_image) correct?

Bezüglich Harry Schmalzbauer's Nachricht vom 16.05.2017 17:28 (localtime): > Bezüglich Toomas Soome's Nachricht vom 16.05.2017 16:57 (localtime): >>> On 16. mai 2017, at 17:55, Harry Schmalzbauer <free...@omnilan.de> wrote: >>> >>> Hello, >>> >>&

Re: EFI loader doesn't handle md_preload (md_image) correct?

Bezüglich Toomas Soome's Nachricht vom 16.05.2017 16:57 (localtime): > >> On 16. mai 2017, at 17:55, Harry Schmalzbauer <free...@omnilan.de> wrote: >> >> Hello, >> >> unfortunately I had some trouble with my preferred MFS-root setups. >> It seems EFI

EFI loader doesn't handle md_preload (md_image) correct?

Hello, unfortunately I had some trouble with my preferred MFS-root setups. It seems EFI loader doesn't handle type md_image correctly. If I load any md_image with loader invoked by gptboot or gptzfsboot, 'lsmod' shows "elf kernel", "elf obj module(s)" and "md_image". Using the same

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

Bezüglich Konstantin Belousov's Nachricht vom 08.03.2017 00:55 (localtime): > On Tue, Mar 07, 2017 at 10:49:01PM +, Rick Macklem wrote: >> Hmm, this is going to sound dumb, but I don't recall generating any >> unionfs patch;-) >> I'll go look for it. Maybe it was Kostik's? > I did not touched

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

Bezüglich Harry Schmalzbauer's Nachricht vom 07.03.2017 19:44 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 07.03.2017 13:42 (localtime): > … >> Something ufs related seems to have tightened the unionfs locking >> problem in stable/11. Now the machine instantaniously panics during

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

Bezüglich Harry Schmalzbauer's Nachricht vom 07.03.2017 13:42 (localtime): … > Something ufs related seems to have tightened the unionfs locking > problem in stable/11. Now the machine instantaniously panics during > boot after mounting root with Rick's latest patch. > > Unfortunately I don't

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

Bezüglich Rick Macklem's Nachricht vom 05.09.2016 23:21 (localtime): > Harry Schmalzbauer <free...@omnilan.de> wrote: >>Bezüglich Rick Macklem's Nachricht vom 18.08.2016 02:03 (localtime): >>> Kostik wrote: >>> [stuff snipped] >>>> insmnque() perf

Re: 'show alllocks' of completely locked machine [Was: Re: Complete IO lockup, state "ufs" from userland, debuging help wanted]

Bezüglich hiren panchasara's Nachricht vom 06.03.2017 21:10 (localtime): > On 03/06/17 at 08:56P, Harry Schmalzbauer wrote: >> Bez?glich Harry Schmalzbauer's Nachricht vom 05.03.2017 22:59 (localtime): >>> Hello, >>> >>> I can easily lock up FreeBSD stab

'show alllocks' of completely locked machine [Was: Re: Complete IO lockup, state "ufs" from userland, debuging help wanted]

Bezüglich Harry Schmalzbauer's Nachricht vom 05.03.2017 22:59 (localtime): > Hello, > > I can easily lock up FreeBSD stable/11 from userland. Not that I want to... > I'm running squid, which starts an authentication helper > "*negotiate_kerberos_auth*", which seems to be the culprit. >

Complete IO lockup, state "ufs" from userland, debuging help wanted

Hello, I can easily lock up FreeBSD stable/11 from userland. Not that I want to... I'm running squid, which starts an authentication helper "*negotiate_kerberos_auth*", which seems to be the culprit. Completely all IO is blocked, there's no way to get anything from any filesystem. All non

Re: FreeBSD 11.0, bxe and lagg

Bezüglich Ingeborg Hellemo's Nachricht vom 21.02.2017 11:23 (localtime): > trond.endres...@fagskolen.gjovik.no said: >> Why does lagg0 refer to bge2 and bge3 in the ifconfig output, and not to >> bxe2 and bxe3? > My bad! No cut and paste from the console of the host without net. Wrote most > of

Re: ASM1062 AHCI timeouts, ppt(4) BAR aligning [Was: Re: svn commit: r309251 - head/sys/dev/ahci]

Bezüglich Alexander Motin's Nachricht vom 29.12.2016 11:32 (localtime): > On 29.12.2016 10:35, Harry Schmalzbauer wrote: >> I'd like to report that this doesn't fix timeouts for me (applied to >> 11-stable). >> >> For example my REV120 works without problems on Intel

ASM1062 AHCI timeouts, ppt(4) BAR aligning [Was: Re: svn commit: r309251 - head/sys/dev/ahci]

Bezüglich Alexander Motin's Nachricht vom 28.11.2016 17:23 (localtime): > Author: mav > Date: Mon Nov 28 16:23:32 2016 > New Revision: 309251 > URL: https://svnweb.freebsd.org/changeset/base/309251 > > Log: > Process port interrupt even is PxIS register is zero. > > ASMedia ASM1062 AHCI

share/mk/bsd.cpu.mk disables lang/gcc48 build with CPUTYPE

Hello, I'm unsure if I'd better file a bug report, but I'm also unsure if it's ports or base… When one defines CPUTYPE in make.conf(5), share/mk/bsd.cpu.mk translates 'core-avx-i' into 'ivybridge' e.g. This breaks building e.g. ports/lang/gcc48: configure:3374:

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 09:12 (localtime): > Hi, > >> Am 07.11.2016 um 09:04 schrieb Harry Schmalzbauer <free...@omnilan.de>: >>> create the EFI boot volume like this? >>> >>> gpart add -t efi -l efi -a 512k -s 512k &

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

Bezüglich Harry Schmalzbauer's Nachricht vom 07.11.2016 09:04 (localtime): > Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 08:10 (localtime): >> Hi, all, >> >>> Am 06.11.2016 um 18:14 schrieb Dimitry Andric : >>> >>> Please do, so it is not forgotten. It is relatively

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 08:10 (localtime): > Hi, all, > >> Am 06.11.2016 um 18:14 schrieb Dimitry Andric : >> >> Please do, so it is not forgotten. It is relatively easy to change the >> volume label, by editing sys/boot/efi/boot1/generate-fat.sh,

boot1.efifat's FAT12 volume label prevents booting (some systems)

Recently I played with bsdinstall and UEFI setup, which left the system unbootable (11.0-Release). The culprit is the MS-DOS volume lable "EFI" of the EFI partition. At least on Intel Single-Socket Servers (for Xeon E3 IvyBridge/BearToot + Haswell/RainbowPass), the UEFI firmware can't

Re: pax(1) needs to learn POSIX-pax format (by libarchive(3)?)

Bezüglich David Magda's Nachricht vom 04.11.2016 03:56 (localtime): > On Nov 1, 2016, at 13:44, Harry Schmalzbauer <free...@omnilan.de> wrote: > >> Has anyone ever thought about? Unfortunately I'm lacking skills and time :-( > > You’ll want to talk to the fol

pax(1) needs to learn POSIX-pax format (by libarchive(3)?)

Dear hackers, I'm frequently missing pax(1) ability to handle the pax (the POSIX pax) format. Backing up real-world file names and lengths doesn't work with ustar format - which pax(1) uses and also tar(1) by default. I'd prefer using pax(1) because of it's cli usage – personal taste… But in

bhyve(8) passthru affects ahci-hd with device backend [Was: Re: Unexpected ahci-hd bytes when running in bhyve(8)]

Bezüglich Harry Schmalzbauer's Nachricht vom 29.10.2016 19:35 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 29.10.2016 17:32 (localtime): > > … >> Like mentioned, while reading the first 448 bytes on the host, I get >> identical results from /usr/local/guest.img and /dev/ada4, but

Re: Unexpected ahci-hd bytes when running in bhyve(8)

Bezüglich Harry Schmalzbauer's Nachricht vom 29.10.2016 17:32 (localtime): … > Like mentioned, while reading the first 448 bytes on the host, I get > identical results from /usr/local/guest.img and /dev/ada4, but when > attaching /dev/ada4 to ahci-hd (-s 7,ahci-hd,/dev/ada4) and inspecting >

Re: Unexpected ahci-hd bytes when running in bhyve(8)

Bezüglich Harry Schmalzbauer's Nachricht vom 27.10.2016 20:05 (localtime): > Hello, > > I wanted to use a "roaming" ssd with byhve/vmm, which is the home of a > GPT based FreeBSD setup. > I've been using this for years with ESXi and bare-metal-hosts, and > wanted to try out bhyve. >

Unexpected ahci-hd bytes when running in bhyve(8)

Hello, I wanted to use a "roaming" ssd with byhve/vmm, which is the home of a GPT based FreeBSD setup. I've been using this for years with ESXi and bare-metal-hosts, and wanted to try out bhyve. Unfortunately this doesn't work the way I'm used to. Booting of ufs:/dev/gpt/myROOT fails with error

Re: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe]

Bezüglich Vincenzo Maffione's Nachricht vom 15.10.2016 09:32 (localtime): > 2016-10-14 15:38 GMT+02:00 Harry Schmalzbauer <free...@omnilan.de>: … >> I'm familar with epair(4), but not with tap(4). >> I don't understand the man page for tap, perhaps I should read pty(4)… &

Re: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe]

Bezüglich Vincenzo Maffione's Nachricht vom 14.10.2016 15:08 (localtime): > Hi, > > Thanks for your feedback. > … >> Accidentally I found out that 'vale-ctl -n testif0' creates a artificial >> interface, which is reported by ifconfig(8): >> testif0: flags=8801 metric 0

vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe]

Dear all, I found great papers about netmap(4)s desigen and implementation details, and I'm sure it's one other masterpeace of rizzo-quality :-) Thanks to all participants for that great code! To be honest, I haven't read all of that, because I'm short in time and my first mission is to see if

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

Bezüglich Rick Macklem's Nachricht vom 18.08.2016 02:03 (localtime): > Kostik wrote: > [stuff snipped] >> insmnque() performs the cleanup on its own, and that default cleanup isnot >> suitable >for the situation. I think that insmntque1() would betterfit your >> requirements, your >need to

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

Bezüglich Mark Johnston's Nachricht vom 09.08.2016 08:02 (localtime): … >> >> Just for anybody else needing unionfs: >> https://people.freebsd.org/~attilio/unionfs_missing_insmntque_lock.patch >> >> This patch still applies and I'm successfully using this (unmodified) up >> to FreeBSD-10.3 and

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

Bezüglich Kurt Jaeger's Nachricht vom 09.08.2016 07:32 (localtime): > Hi! > >> Since then I'm draging a minimal patch which prevents at least the >> kernel panics for me. >> Unfortunately I don't have the skills to continue Attilio Raos work. >> >> Just for anybody else needing unionfs: >>

unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:190

Bezüglich Rick Macklem's Nachricht vom 07.08.2016 23:34 (localtime): > Harry Schmalzbauer wrote: >> Hello, >> >> I had another crash which I'm quite sure was triggered by mount_unionfs: > Just in case you are not already aware, unionfs is always broken. Read > the BUGS &

1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1905

Hello, I had another crash which I'm quite sure was triggered by mount_unionfs: Unread portion of the kernel message buffer: panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1905 cpuid = 3 KDB: stack backtrace:

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

Bezüglich Craig Rodrigues's Nachricht vom 02.08.2016 22:31 (localtime): > Thanks for the feedback. Please consider posting your questions > on freebsd-current so that other people can jump in and help > answer your questions. > > I don't have an LDAP server to test against, so don't know the

11-BETA3 Panic with ip6+ESP, Fatal trap 12, severe outage

Hello, unfortunately my upgrade from 10.3 to 11-BETA3 caused machine outage. ESP encrypted IPv6-traffic acauses a immediate crash. Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211486 whereI provided this info: Unread portion of the kernel message buffer: Kernel page fault with

Re: mfi driver performance too bad on LSI MegaRAID SAS 9260-8i

Bezüglich Jason Zhang's Nachricht vom 17.06.2016 09:16 (localtime): > Hi, > > I am working on storage service based on FreeBSD. I look forward to a good > result because many professional storage company use FreeBSD as its OS. But > I am disappointed with the Bad performance. I tested the

pkg(8) still not part of stable/11 (yet)???

Hello, I just tried 11-beta2 – as usual, many thanks for all your hard work, Devs and REs! I'm very concerned that there's still just a bootstrap-pkg :-( Most of the machines I'm responsible for don't have internet access – and won't ever have. Currently, I don't have a 11-machine for building

Re: ahci-timeout regression in beta3

Bezüglich John Baldwin's Nachricht vom 05.03.2016 22:50 (localtime): > On Saturday, March 05, 2016 01:11:13 PM Harry Schmalzbauer wrote: >> Bezüglich John Baldwin's Nachricht vom 02.03.2016 18:32 (localtime): … >> With BETA3-iso, where booting fails, "random: unblocking devic

Re: ahci-timeout regression in beta3

Bezüglich John Baldwin's Nachricht vom 02.03.2016 18:32 (localtime): > On Monday, February 29, 2016 07:29:03 PM Harry Schmalzbauer wrote: >> Bezüglich Harry Schmalzbauer's Nachricht vom 28.02.2016 20:55 (localtime): >>> Hello, >>> >>> I have a remote m

Re: ahci-timeout regression in beta3

Bezüglich Harry Schmalzbauer's Nachricht vom 28.02.2016 20:55 (localtime): > Hello, > > I have a remote machine with a probably defective ODD, but until r294989 > (from Jan 28th) I could boot with just these warnings: > (cd1:ahcich1:0:0:0): READ(10). CDB: 28 00 00 38 85 e0 00 00 01 00 >

ahci-timeout regression in beta3

Hello, I have a remote machine with a probably defective ODD, but until r294989 (from Jan 28th) I could boot with just these warnings: (cd1:ahcich1:0:0:0): READ(10). CDB: 28 00 00 38 85 e0 00 00 01 00 (cd1:ahcich1:0:0:0): CAM status: SCSI Status Error (cd1:ahcich1:0:0:0): SCSI status: Check

Re: FreeBSD and UDF

Bezüglich Eugene M. Zheganin's Nachricht vom 25.02.2016 13:17 (localtime): > Hi, > > recenlty I needed to mount the Windows 2012 R2 iso image, which pappened > to ba an UDF image. After mdconfiging it and attempting to mount I got: > > # mount -t udf /dev/md1 cdrom01 > mount_udf: /dev/md1:

Re: svn commit: r294958 - in stable/10: share/man/man4 sys/dev/e1000 sys/dev/ixgb sys/dev/netmap

Bezüglich Mike Tancsa's Nachricht vom 29.01.2016 19:08 (localtime): > On 1/27/2016 5:31 PM, Marius Strobl wrote: >> Author: marius >> Date: Wed Jan 27 22:31:08 2016 >> New Revision: 294958 >> URL: https://svnweb.freebsd.org/changeset/base/294958 >> >> Log: >> Sync the e1000 drivers with what's

em(4) watchdog timeout redemption [Was: Re: svn commit: r294958 - in stable/10: share/man/man4 sys/dev/e1000 sys/dev/ixgb sys/dev/netmap]

Bezüglich Marius Strobl's Nachricht vom 27.01.2016 23:31 (localtime): > Author: marius > Date: Wed Jan 27 22:31:08 2016 > New Revision: 294958 > URL: https://svnweb.freebsd.org/changeset/base/294958 > > Log: > Sync the e1000 drivers with what's in head as of r294327, modulo parts > that don't

Big geli proglem: MD5 hash checksum mismatch for da0

Hello, I tried to change my passphrase for a geli provider. Like man page tells, I attached the provider (da0) and used 'geli setkey da0' to change the key (only one key, no keyfile used). Everything seemd to work but after detaching any attach attempt fails with: MD5 hash checksum mismatch for