Re: ZFS problems since recently ?

[Kurt Jaeger]

Hi!

> The sysctl for block cloning is vfs.zfs.bclone_enabled.
> To check if a pool has made use of block cloning:
> zpool get all poolname | grep bclone

One more thing:

I have two pools on that box, and one of them has some bclone files:

# zpool get all ref | grep bclone
ref   bcloneused 21.8M  -
ref   bclonesaved24.4M  -
ref   bcloneratio2.12x  -
# zpool get all pou | grep bclone
pou   bcloneused 0  -
pou   bclonesaved0  -
pou   bcloneratio1.00x  -

The ref pool contains the system and some files.
The pou pool is for poudriere only.

How do I find which files on ref are bcloned and how can I remove the
bcloning from them ?

-- 
p...@freebsd.org +49 171 3101372  Now what ?

Re: ZFS problems since recently ?

[Kurt Jaeger]

Hi!

> Am 2023-12-31 19:34, schrieb Kurt Jaeger:
> > I already have
> > 
> > vfs.zfs.dmu_offset_next_sync=0
> > 
> > which is supposed to disable block-cloning.
> 
> It isn't. This one is supposed to fix an issue which is unrelated to block
> cloning (but can be amplified by block cloning). This issue is fixed since
> some weeks, your Dec 23 build should not need it (when the issues happens,
> you have files with zero as parts of the data instead of the real data,
> and only if you copy files at the same time as those files are modified,
> and then only if you happen to get the timing right).
> 
> The sysctl for block cloning is vfs.zfs.bclone_enabled.
> To check if a pool has made use of block cloning:
> zpool get all poolname | grep bclone

Thanks. I now used that sysctl and my testcase (testbuild of shells/bash)
and it did not crash.

-- 
p...@freebsd.org +49 171 3101372  Now what ?

Re: ZFS problems since recently ?

[Kurt Jaeger]

Hi!

> On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> > markj@ pointed me in
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> > to
> > https://github.com/openzfs/zfs/pull/15719 
> > 
> > So it will probably be fixed sooner or later.
> > 
> > The other ZFS crashes I've seen are still an issue.
> 
>   My poudriere build did eventually fail as well:
>   ...
>   [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success
>   [05:40:24] Stopping 2 builders
>   panic: VERIFY(BP_GET_DEDUP(bp)) failed

That's one of the panic messages I had as well.

See

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276051

for additional crashes and dumps.

>   I didn't tweak this system off defaults for block-cloning.  I haven't been 
> following
> that issue 100%.

Do you have

vfs.zfs.dmu_offset_next_sync=0

?

-- 
p...@freebsd.org +49 171 3101372  Now what ?

Re: ZFS problems since recently ?

[Kurt Jaeger]

Hi!

> >   I can crash mine with "sysctl -a" as well.

markj@ pointed me in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
to
https://github.com/openzfs/zfs/pull/15719 

So it will probably be fixed sooner or later.

The other ZFS crashes I've seen are still an issue.

-- 
p...@freebsd.org +49 171 3101372  Now what ?

ZFS problems since recently ?

[Kurt Jaeger]

Hi!

Short overview:
- Had CURRENT system from around September
- Upgrade on the 23th of December
- crashes in ZFS, see
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538
  for details
- Reinstalled from scratch with new SSDs drives from
https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/
freebsd-openzfs-amd64-2020081900-memstick.img.xz
- Had one crash with
  sysctl -a
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
- Still see crashes with ZFS (and other) when using poudriere to
  build ports.

Problem:

I happen to run in several cases of crashes in ZFS, some of
them fatal (zpool non-recoverable).

The latest was:

panic: VERIFY(BP_GET_DEDUP(bp)) failed

cpuid = 29
time = 1704050745
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe02def538c0
vpanic() at vpanic+0x131/frame 0xfe02def539f0
spl_panic() at spl_panic+0x3a/frame 0xfe02def53a50
dsl_livelist_iterate() at dsl_livelist_iterate+0x2de/frame 0xfe02def53b30
bpobj_iterate_blkptrs() at bpobj_iterate_blkptrs+0x235/frame 0xfe02def53bf0
bpobj_iterate_impl() at bpobj_iterate_impl+0x16e/frame 0xfe02def53c80
dsl_process_sub_livelist() at dsl_process_sub_livelist+0x5c/frame 
0xfe02def53d00
spa_livelist_delete_cb() at spa_livelist_delete_cb+0xf6/frame 0xfe02def53ea0
zthr_procedure() at zthr_procedure+0xa5/frame 0xfe02def53ef0
fork_exit() at fork_exit+0x82/frame 0xfe02def53f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfe02def53f30
--- trap 0x85baac33, rip = 0xdfda59b01bda59f, rsp = 0xaaca3ed7a68a3ed3, rbp = 
0x16f512f91ab512fd ---

before I had to nuke that pool and restart...

I already have

vfs.zfs.dmu_offset_next_sync=0

which is supposed to disable block-cloning.

Does anyone else see this with recent versions or is it just me ?

-- 
p...@freebsd.org +49 171 3101372  Now what ?

Re: Updating motherboard BIOS without MS Windows

[Kurt Jaeger]

Hi!

> How do you update BIOS without Windows since most brands only have bios
> software to windows?
> 
> I'm about to buy a new pc without windows license and I'm looking for
> brands that have bios-cli that work in FreeBSD.

There's

sysutils/flashrom

which allows to flash some BIOS systems. The website is here:

https://www.flashrom.org/

There's an old page which lists the hardware supported:

https://wiki.flashrom.org/Supported_hardware

-- 
p...@freebsd.org+49 171 3101372Now what ?

Re: [UPDATE] FreeBSD 14.0-BETA3 Now Available

[Kurt Jaeger]

Hi!

> On Fri, Sep 22, 2023 at 10:50:08PM +, Glen Barber wrote:
> > === Upgrading ===
> > 
> > Due to a known delay, freebsd-update(8) binary update builds are not yet
> > ready for BETA3.  A separate email will be sent once they are available.
> > 
> 
> Binary updates via freebsd-update(8) are now available for systems
> already running 14.0-BETA.

If I try to update my poudriere 14.0-BETA2 jail with this command:

poudriere jail -u -j 140 -t 14.0-BETA3

it fails, see here:

https://people.freebsd.org/~pi/logs/pou-fail.txt
(short, only 1550 bytes)

I have:

140   14.0-BETA2  amd64 http2023-09-16 08:20:01 /pou/jails/140

with

/usr/local/bin/poudriere installed by package poudriere-devel-3.3.99.20220831

-- 
p...@freebsd.org +49 171 3101372  Now what ?

Re: ZFS deadlock in 14

[Kurt Jaeger]

Hi!

> > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a
> > deadlock was introduced in ZFS.  It is still present as of 9c2823bae9 (4
> > August) and is 100% reproducable just by starting poudriere bulk in a
> > 16-core VM and waiting a few hours until deadlkres kicks in.
> 
> I have a amd based builder, 32 cores, run 437e1e37dfca from
> Thu Jul 27 01:26:39 CEST 2023 and do not see those crashes.
> 
> zpool get feature@block_cloning zroot
> NAME   PROPERTY   VALUE  SOURCE
> zroot  feature@block_cloning  enabledlocal

se@ told me about yet another tunable 8-)

sysctl vfs.zfs.bclone_enabled   
vfs.zfs.bclone_enabled: 0

So while it's enabled in ZFS itself, it's not really active in my
system.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: ZFS deadlock in 14

[Kurt Jaeger]

Hi!

> At some point between 42d088299c (4 May) and f0c9703301 (26 June), a
> deadlock was introduced in ZFS.  It is still present as of 9c2823bae9 (4
> August) and is 100% reproducable just by starting poudriere bulk in a
> 16-core VM and waiting a few hours until deadlkres kicks in.

I have a amd based builder, 32 cores, run 437e1e37dfca from
Thu Jul 27 01:26:39 CEST 2023 and do not see those crashes.

zpool get feature@block_cloning zroot
NAME   PROPERTY   VALUE  SOURCE
zroot  feature@block_cloning  enabledlocal

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: poudriere && git

[Kurt Jaeger]

Hi!

> In the past I created the jails based on svn, for example with
> 
> # poudriere jail  -c -j freebsd-r368166 -m svn+http -v head@r368166

I have the src repo in /usr/src, build the host system
from that tree and then use:

poudriere jail -j head -u -m null -S /usr/src

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: Tooling Integration and Developer Experience

[Kurt Jaeger]

Hi!

> > > This can be as easy as moving everything into Phabricator.
> > There's the issue that Phabricator itself is no longer supported
> > upstream:
[...]
> > https://we.phorge.it/

> Should be no harder than regular update. They even have a HOWTO
> https://we.phorge.it/w/installation_and_setup/update_from_phabricator/

So, as a step 0 we would need a phorge port...
> 1. Upgrade to Phorge
> 2. Setup Maniphest for bugs and tasks
> 3. Migrate bugs into Maniphest
> 4. Enable Harbormaster (Build/CI) - this requires coordination with
> whoever is working on pre-commit CI.
[...]
> Infra operations are hard, and I have experience with it. I'd be happy to
> help.

Do you think you can provide a phorge port ?

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: Tooling Integration and Developer Experience

[Kurt Jaeger]

Hi,

> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >The main idea: to prevent information fragmentation andimprove
> >discoverability, cross-referencing abilities, search, etc.
> 
> With regards to improving discoverability, Phabricator's Owner
> tool could be a good tactical move: it allow to bind code area to
> peoples in order to automatically add them to reviews.

If you know phabricator in more detail, is there any kind of tool
to understand the activity going on ?

In bugs.freebsd.org, there is the dashboard:

https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html

I think we might need something similar to help us understand
the current state of the phabricator instance and the work
being done.

Phab allows Dashboards, but no-one had the time to configure some
queries to provide relevant stats.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: Tooling Integration and Developer Experience

[Kurt Jaeger]

Hello,

> I had a similar thing happen to me, the mailing list FreeBSD-doc seemed to
> exist as if no one existed, and there was no one posting in it except for
> the automated bug reports from the bots.
> I have not had any replies to my several posts either.

> So can the admins tell how many people actually
> subscribe to FreeBSD-doc,

The list has 496 subscribers right now. (speaking as one of postmaster@).

> or is this just a place to report bugs and people
> should discuss FreeBSD doc-related issues elsewhere? Or is it that almost
> nobody cares about the FreeBSD documentation?

>From my observation, the last few month led to a huge pile of
workload on many folks that are involved with FreeBSD stuff, so
not many folks had time to reply/think things through/answer.
I had the same problem...

I see doc-stuff happen mostly on reviews.freebsd.org. (speaking
as one of phabric-admins). Pau Amma is the most active docs-person
as far as I can see. I have not calculated stats, just my gut feeling.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: Tooling Integration and Developer Experience

[Kurt Jaeger]

Hi!

ihor@antonovs.family wrote:

> This can be as easy as moving everything into Phabricator.

There's the issue that Phabricator itself is no longer supported
upstream:

https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
https://github.com/phacility/phabricator

I have notes from Oct. 2021 which point to a fork:

https://we.phorge.it/

That fork seems to be somewhat alive. Moving our phab instance
to phorge is probably no trivial task.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: Tachyum Prodigy processors

[Kurt Jaeger]

Hi!

> does anyone have any information regarding the new Tachyum Prodigy
> processors?

golem had an article 3 days ago (written in german), which was detailled
enough to trigger my interest.

https://www.golem.de/news/tachyum-prodigy-t16128-der-wunderkind-prozessor-2206-165307.html

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: recover deleted file

[Kurt Jaeger]

Hi!

> Maybe UFS developer would do a rework so latest deleted inodes would put in
> a "recycle bin"

Use ZFS and snapshots, that should help your use-case.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: VDSO on amd64

[Kurt Jaeger]

Hi!

> I have mostly finished implementation of "proper" vdso for amd64
> native binaries, both 64bit and 32bit.  Vdso wraps signal trampolines
> into real dynamic shared object, which is prelinked into dynamically
> linked image.

Eleven years ago Giuseppe Cocomazzi posted this:

http://lists.freebsd.org/pipermail/freebsd-hackers/2010-April/031553.html

vdso and shared page patch

My question: What's the difference between

https://reviews.freebsd.org/D32960

and those changes from 2010 ? I'm curious and maybe a little explaination
would help me understand what happened between 2010 and now.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: BUG in libm's powf

[Kurt Jaeger]

Hi!

> > > On Mon, Sep 06, 2021 at 10:22:02PM +0200, Gordon Bergling wrote:
> > > > could you turn to test program into an AFT test to prevent further 
> > > > regressions?
> > > 
> > > I cannot tell if you are addressing Mark or me.
> > > For me, I know nothing about ATF.
> > 
> > man 7 atf
> > 
> > has more details.

> % man 7 atf
> No manual entry for atf
> % grep -i tests /etc/src.conf
> WITHOUT_GOOGLETEST="YES"
> WITHOUT_TESTS="YES"

https://www.freebsd.org/cgi/man.cgi?query=atf

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: BUG in libm's powf

[Kurt Jaeger]

Hi!

> On Mon, Sep 06, 2021 at 10:22:02PM +0200, Gordon Bergling wrote:
> > could you turn to test program into an AFT test to prevent further 
> > regressions?
> 
> I cannot tell if you are addressing Mark or me.
> For me, I know nothing about ATF.

man 7 atf

has more details.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: Spam mail being sent via the FreeBSD mailing lists

[Kurt Jaeger]

Hi!

> > On May 25, 2021, at 8:53 PM, jake h  wrote:

> > I have recently received several pieces of spam mail, apparently sent via
> > this mailing list. These pieces of mail are the usual spam formula; Your
> > phone has a virus, Ads, Fake blackmail, so on and so forth.
> > Has anyone else noticed these spam emails, or is it just me?

> I'm receiving these too. It looks like the servers are bouncing some of them 
> just for me, even. And I'm receiving not just from this list; also from 
> freebsd-hackers@ and ports@.

postmaster@ is aware of the problem, we do not yet have a clear-cut
solution and we're investigating.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: ZFS: out of temporary buffer space

[Kurt Jaeger]

Hi!

> ZFS: out of temporary buffer space
> 
> Any ideas on how to fix this ?

Ok, fix was this:

Using the same memstick, I wrote a new efi partition as a copy
from the efi partition on the memstick.

gpart (simplified) showed this:

=>40  2000409184  nvd0  GPT  (954G)
  40  409600 1  efi  (200M)
  4096401024 2  freebsd-boot  (512K)
  410664 984- free -  (492K)
  41164816777216 3  freebsd-swap  (8.0G)
17188864  1983219712 4  freebsd-zfs  (946G)
  2000408576 648- free -  (324K)

=>  1  767  da0  MBR  (3.7G)
1665841  efi  (33M)
66585  21749922  freebsd  [active]  (1.0G)
  2241577  5438423   - free -  (2.6G)

So:

  dd if=/dev/da0s1 of=/dev/nvd0p1

and reboot and there we go!

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ZFS: out of temporary buffer space

[Kurt Jaeger]

Hi!

Upgrading a c256294-g2cf84258922f kernel (14.0 from 27th of January)
to a more recent version displays this error on reboot:

ZFS: out of temporary buffer space

Any ideas on how to fix this ?

I've tried the fix as described in

https://old.reddit.com/r/freebsd/comments/mtx5cf/freebsd_130_upgrade_zfs_out_of_temporary_buffer/

with the memstick from SNAPSHOTS:

FreeBSD-14.0-CURRENT-amd64-20210415-14d0cd7225e-246078-memstick.img

and it did not work on 14.0.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD 13.0-RC3 Now Available

[Kurt Jaeger]

Hi!

> The third RC build of the 13.0-RELEASE release cycle is now available.

Upgrading a 13.0-RC2 poudriere jail to RC3 seems to fail ?

# poudriere jail -u -j 130 -t 13.0-RC3
[...]
To install the downloaded upgrades, run "/usr/sbin/freebsd-update.fixed 
install".
Installing updates...Scanning //usr/share/certs/blacklisted for certificates...
Scanning //usr/share/certs/trusted for certificates...
 done.
No updates are available to install.
Run '/usr/sbin/freebsd-update.fixed fetch' first.
[00:00:42] Error: Fail to upgrade system

A second attempt:

Fetching metadata signature for 13.0-RC3 from update4.freebsd.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 13.0-RC3-p0.
touch: 
f465c3739385890c221dff1a05e578c6cae0d0430e46996d319db7439f884336-install/kernelfirst:
 No such file or directory
To install the downloaded upgrades, run "/usr/sbin/freebsd-update.fixed 
install".
No updates are available to install.
Run '/usr/sbin/freebsd-update.fixed fetch' first.
[00:01:08] Error: Fail to upgrade system

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Is there any OS builtin git command like svnlite ?

[Kurt Jaeger]

Hi!

> I'm working on clean installed VM -current from NFS
> mounted src like :
> 
> admin@tbedfc:~ % df -h
> Filesystem  SizeUsed   Avail 
> Capacity  Mounted on
> /dev/vtbd0p2 11G4.1G5.7G
> 42%/
> devfs   1.0K1.0K  0B   
> 100%/dev
> vm.tfc:/.dake12T843G 11T 
> 7%/.dake
> vm.tfc:/ds/src/freebsd/current/14.0/913e7dc3e0eb 11T 55G 11T 
> 0%/usr/src
> vm.tfc:/ds/obj/freebsd/current/14.0/913e7dc3e0eb 11T322G 11T 
> 3%/usr/obj
> admin@tbedfc:~ % 
> 
> But could not display revison by uname :
> 
> admin@tbedfc:~ % uname -a
> FreeBSD tbedfc 14.0-CURRENT FreeBSD 14.0-CURRENT #0: Fri Mar 12 18:16:41 JST 
> 2021 root@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> admin@tbedfc:~ % 
> 
> I think this is because incapable of using git command with
> `git -C $SRCDIR rev-parse --verify --short HEAD'. In the
> first place, git command does not builtin src like svnlite.
> Is there any solution of this ?

Not yet. There are ports that you can install with 'pkg install':

pkg install git
pkg install gitup

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: libifconfig_sfp.h does not compile for me

[Kurt Jaeger]

Hi!

> This https://cgit.freebsd.org/src/tree/lib/libifconfig/libifconfig_sfp.h 
> includes libifconfig_sfp_tables.h which does not exist.
> 
> My build fails on this. I cleaned /lib/libifconfig and /sbin/ifconfig, but no 
> succes.
> The last change in these files is a few days ago, am I the only one with this 
> problem?
> 
> This is on 14-CURRENT/amd64.

It looks like libifconfig_sfp_tables.h might be created during the
build via the template

https://cgit.freebsd.org/src/tree/lib/libifconfig/libifconfig_sfp_tables.tpl.h

Maybe this fails to build ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: zpool upgrade to draid feature: does it require updated zfs boot code ?

[Kurt Jaeger]

Hi!

> > Short question:
> > Does a zpool upgrade on 14.0 (current) for the draid feature
> > require a boot code update ?

> > Long version of the same question:
> > With the draid update, no message was displayed.
> > 
> > Does it require the bootcode update anyway or, if not, why not ?
> 
> This sounded like a bug.  Is it your boot pool, or just a regular data pool?

Its my boot pool.

> >  gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd0
> >  gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd1
> 
> To answer your short question: do I need to update bootcode?  No if
> draid is the only feature that you have enabled on an existing pool, but
> personally I don't recommend upgrading boot pool right now.

The boot pool shows:

zroot  feature@draid  enabledlocal

> The reason for that "No" answer is 1) the boot code do not currently
> support draid, and 2) enabling the feature won't activate it until draid
> vdev is added to the pool, which is quite unlikely in your case; note
> that if you do add draid vdev, your bootcode won't be able to boot from
> it anymore.

Ok.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

zpool upgrade to draid feature: does it require updated zfs boot code ?

[Kurt Jaeger]

Hi!

Short question:

Does a zpool upgrade on 14.0 (current) for the draid feature
require a boot code update ?

Long version of the same question:

I've upgraded my testbox to FreeBSD 14.0-CURRENT #0 main-c256294-g2cf84258922f
and the system listed the zfs-feature draid as available if I do an
zpool upgrade.

The pool resides on two nvme drives:

 mirror-0  ONLINE   0 0 0
   nvd0p4  ONLINE   0 0 0
   nvd1p4  ONLINE   0 0 0

Normally, when I do the zpool upgrade for the pool, and
the zpool upgrade also requires an upgrade to the bootcode,
some message is displayed, reminding me to do so.

With the draid update, no message was displayed.

Does it require the bootcode update anyway or, if not, why not ?

 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd0
 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd1

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Preparing ZFS drives

[Kurt Jaeger]

Hi!

> How should I label and prepare the drives for ZFS?  Someone ought to write a 
> ???cookbook??? on that!

Basically, what I once did, was this:

zpool create bck raidz2 ada2 ada3 ada4 ada5 ada6 ada7 ada8 ada9

Therefore: raw disks, nothing else.

> Do I need to start the volume on a particular sector boundary?
> 
> Are the 4096 byte sector drives usable?

I think the default is now 4096 anyway.

https://charsiurice.wordpress.com/2016/05/30/checking-ashift-on-existing-pools/

describes the command to check for 4096 blocks:

zdb -C | grep ashift

If it displays

ashift: 9

the blocks are 512 bytes.

If it displays

ashift: 12

the block size is 4096.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Kurt Jaeger]

Hi!

> It's also hard to collect ALL the keys of the devs at any point in
> time to decide if that key is authorized to sign a commit in the
> repo...

We do have most of the keys in docs/share/pgpkeys/ plus history.

> Like if a dev starts in 2021, any commits made by that
> dev prior to 2021 should not be "valid"..  Then there's also the
> issue that people's keys change over time, and now you need to know
> what time period each key was valid for, otherwise a compromised key
> could be used to insert malicious changes into your/the tree...

If we manage keys plus their history in the doc repo, this seems
to be solved.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: firewall choice

[Kurt Jaeger]

Hi!

> What's the "best" [1] choice for firewalling these days, in the list's 
> opinion?

At work, we use pf for complex setups, editing the rules using fwbuilder,
and ipfw for the simple setups and the quick blocks...

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: zpool export: umount failed, device inexplicably busy (lsof found nothing)

[Kurt Jaeger]

Hi!

> If the problem recurs: is it _ever_ sane to get nothing listed by lsof
> for a volume that can not be unmounted?

Use fstat -- this is part of the base system.

Maybe lsof does not catch every corner case ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Deprecating ftpd in the FreeBSD base system?

[Kurt Jaeger]

Hi!

> > I've been advocating removing FTP (and HTTP) from libfetch as well. People
> > should be using HTTPS only.

> Isn't this a bit too much? I often find myself in need to download
> something starting with "http://; or "ftp://; and use fetch for this.

It's a bit too much. Deprecating it, 'add --really if you really
want to use http/ftp' would be more useful for the common
sys-admin 8-)

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Plans for git

[Kurt Jaeger]

Hi!

> Why was the intention to switch NOT announced as such MUCH sooner?

Because communicating complex issues which might cause conflict
and flame wars etc is not easy. Everyone prefers to hack on code,
and possibly procrastinates on the hard stuff 8-}

And all those that do the really heavy work are very, very short on
time and capacity.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Plans for git (was: Please check the current beta git conversions)

[Kurt Jaeger]

Hi!

> On Tuesday,  1 September 2020 at 13:14:10 -0400, Ed Maste wrote:
> > We've been updating the svn-git converter and pushing out a new
> > converted repo every two weeks, and are now approaching the time where
> > we'd like to commit to the tree generated by the exporter,
> > ...
> 
> Somehow I've missed this development.

The list archive

https://lists.freebsd.org/pipermail/freebsd-git/

has additional information.

http://wiki.freebsd.org/GitWorkflow
http://wiki.freebsd.org/UlrichSpoerlein/GitTalkDevSummit

has more. The repo: https://cgit-beta.freebsd.org/

Freshports using git:
devgit.freshports.org

A short intro on git for svn users:
https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Kurt Jaeger]

Hi!

> > > I caution against 'zpool upgrade' for the next few weeks.
> > > https://svnweb.freebsd.org/base?view=revision=364746

> > A system running r363767 can upgrade to some revision after r364746
> > and reboot and come up without big issues, running the new openzfs code ?
> > Or is some additional step required ?

> Barring some unusual configuration that no one else there should not be a
> problem. The only known issue of immediate concern (that was only raised a
> day or two ago :-/) is zfs delegation in poudriere.

This is my package builder box, where I also receive mail, so ... 8-}

> If you rely on that I'd say wait a couple days, otherwise proceed.

It has it's files on a ZPOOL.

How can I find if my poudriere uses zfs delegation ?

https://www.freebsd.org/doc/handbook/zfs-zfs-allow.html

says something about:

sysctl vfs.usermount

which returns 0 (so no usermounts) and:

zfs allow -l zroot/pou

which returns empty. So I guess I can upgrade.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: APM BIOS set to go in FreeBSD

[Kurt Jaeger]

Hi!

> APM BIOS support will likely be removed from FreeBSD for FreeBSD 13. This
> was once quite important for LAPTOP users. However, it is now no longer
> relevant. It stopped being supported around the time that ACPI started to
> be released for laptops. This was around the Pentium 200MHz laptop
> generation, give or take. ACPI was released in 1996 to replace APM, and had
> largely done so by 2000. As such, this is 20-year obsolete technology.

I think I still use it to this day for all my laptops to check
the battery status and put the laptop to sleep.
The commands I use are apm and zzz, and they still work.

What would be replacement commands ?

> To that end, I'm looking for actual users of this APM that have used the
> technology successfully in FreeBSD 12.0 or newer.

I can experiment and even can provide you remote access to laptops of that
kind.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Kurt Jaeger]

Hi!

> r364746 merged OpenZFS support in to HEAD.
> 
> The change should be transparent unless you want to use new features.
> I caution against 'zpool upgrade' for the next few weeks.
> https://svnweb.freebsd.org/base?view=revision=364746

A system running r363767 can upgrade to some revision after r364746
and reboot and come up without big issues, running the new openzfs code ?

Or is some additional step required ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: The spkr driver

[Kurt Jaeger]

Hi!

> I'd like to retire the spkr driver. It was a cute hack before sound cards
> were ubiquitous, but it's not been kept up to date, and it's not clear that
> it still works It is still Giant locked, and though it's not a huge
> effort to do the locking I literally have no way to test it that I trust...

It works on PC Engines APU devices, and together with morse, it's
very, very cool 8-}

So, please keep it and un-giant it, if possible.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Does FreeBSD have an assigned Internet OID?

[Kurt Jaeger]

Hi!

> For the NFS over TLS work, I have a need for an Internet OID.
> (I understand that IETF assigns ones for things like SNMP under
> 1.3.6.1.4.1...)
> 
> I'm referring to the long strings of numbers separated by "."s,
> where each number is a subtree administered by someone.

https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers

says:

2238
  The FreeBSD Project
Poul-Henning Kamp
  phk

> If either the project or Foundation has one assigned to them,
> that I can acquire a subnumber (or whatever they call the next
> layer down), please let me know.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: test suite for NIC features...

[Kurt Jaeger]

Hi!

> Has anyone compiled a script/test suite for testing various NIC
> features to make sure they work/function properly?
> 
> That is, being able to run a couple interfaces back to back, and turn
> off the features off on one, and make sure things like checksum offload
> and the like work properly?

I don't know of any project of that kind, but it sounds very useful.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: editors/libreoffice PDF export/printing broken

[Kurt Jaeger]

Hi!

There is

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247444

which discusses this in more detail.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: lock order reversal and poudriere

[Kurt Jaeger]

Hi!

> > > I am compiling some packages with poudriere on 13-current kernel. I
> > > noticed some strange messages printed into the terminal and dmesg:
> > > 
> > > lock order reversal:
> > [...]
> > > Are those the debug messages that aren't visible on non-current kernel
> > > and should they be reported?
> > Yes, they should be checked and reported.
> > 
> > For more details see:
> > 
> > http://sources.zabbadoz.net/freebsd/lor.html
> > 
> > There's a webpage with a list of all known LORs and a way to
> > report new LORs.

> Thanks Kurt. I can't find those two specific LORs in the list on that
> page. The page also says to report them using a link, which leads to 404
> :-), or on this mailing list, which I did. I am not sure what else should
> I do.

I don't know, either 8-} bz@ is in Cc:, so he'll probably know what
to do.

> How do I know if I have got a backtrace?
> 
> Are those errors:
> 
> pid 43297 (conftest), jid 5, uid 0: exited on signal 11
> 
> related or it's a different issue?

I think that's a different issue.

-- 
p...@freebsd.org +49 171 3101372  Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: lock order reversal and poudriere

[Kurt Jaeger]

Hi!

> I am compiling some packages with poudriere on 13-current kernel. I
> noticed some strange messages printed into the terminal and dmesg:
> 
> lock order reversal:
[...]
> Are those the debug messages that aren't visible on non-current kernel
> and should they be reported?

Yes, they should be checked and reported.

For more details see:

http://sources.zabbadoz.net/freebsd/lor.html

There's a webpage with a list of all known LORs and a way to
report new LORs.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How to enable tcp bbr in FreeBSD???

[Kurt Jaeger]

Hi!

> You can enable the stack globally on new connections without
> restarting the box or daemons by running these commands:
> 
> kldload tcp_bbr
> 
> sysctl net.inet.tcp.functions_inherit_listen_socket_stack=0
> sysctl net.inet.tcp.functions_default=bbr

This fails on the box running 13.0:

# kldload tcp_bbr 
kldload: can't load tcp_bbr: No such file or directory

So it looks it has to be hooked to the build somehow ?

And: man -k bbr has no results as well...

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How to enable tcp bbr in FreeBSD???

[Kurt Jaeger]

Hi!

> > Thanks. Is BBR active automatically or is there a sysctl or
> > socket option to activate it ?
> 
> net.inet.tcp.cc.available: List available congestion control algorithms
> net.inet.tcp.cc.algorithm: Default congestion control algorithm

Hmm, 

On my FreeBSD 13.0-CURRENT amd64 r359631M system:

$ sysctl -a | grep net.inet.tcp.cc
[...]
net.inet.tcp.cc.available: newreno
net.inet.tcp.cc.algorithm: newreno

So it's more recent than the patch, but it does not offer anything
besides newreno ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How to enable tcp bbr in FreeBSD???

[Kurt Jaeger]

Hi!

> > On 24 Apr 2020, at 07:29, ykla  wrote:
> > 
> > I search by Google  but found no results about how to enable bbr in
> > FreeBSD. BBR had developed in 2019. So I want to enable it.
> 
> See: https://svnweb.freebsd.org/base?view=revision=352657

Thanks. Is BBR active automatically or is there a sysctl or
socket option to activate it ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: PCIe NVME drives not detected on Dell R6515

[Kurt Jaeger]

Hi!

> > pciconf -lBc pcib12
> > pciconf -lBc pcib13
> 
> Printscreen attached.

Attachments are stripped from the list -- can you put them somewhere
online ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: New Xorg - different key-codes

[Kurt Jaeger]

Hi!

> On 2020-Mar-11 10:29:08 +0100, Niclas Zeising  wrote:
> >This has to do with switching to using evdev to handle input devices on 
> >FreeBSD 12 and CURRENT.  There's been several reports, and suggested 
> >solutions to this, as well as an UPDATING entry detailing the change.
> 
> The UPDATING entry says that it's switched from devd to udev.  There's no
> mention of evdev or that the keycodes have been roto-tilled.  It's basically
> a vanilla "things have been changed, see the documentation" entry.  Given
> that entry, it's hardly surprising that people are confused.

Thanks. I was wondering myself, what/where there's mention of this.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: lame reverse DNS?

[Kurt Jaeger]

Hi!

> The problem has been resolved but I still sometimes see "connect from
> unknown[2610:1c1:1:606c::19:2]" in the maillog (today: 6 of 131
> connections). Local unbound issue?

That IPv6 has a valid reverse DNS record, so please try to investigate.

Something like the output from:

dig +trace -t ptr 
2.0.0.0.9.1.0.0.0.0.0.0.0.0.0.0.c.6.0.6.1.0.0.0.1.c.1.0.0.1.6.2.ip6.arpa

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> > > You're probably looking for this:
> > > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html
> > 
> > Thanks, that looks like a very useful approach.
> > 
> > Will test that when I'm in the housing facility, and report back.
> 
> I tested it, no change 8-(

Update on this: I did an upgrade to 12.1p1 yesterday and the box
rebooted sucessfully without any manual intervention. The mapping
from /boot/device.hints is ignored, btw (it requested different adaX numbers).

The data pool:

NAMESTATE READ WRITE CKSUM
bck ONLINE   0 0 0
  raidz2-0  ONLINE   0 0 0
ada0ONLINE   0 0 0
ada10   ONLINE   0 0 0
ada2ONLINE   0 0 0
ada3ONLINE   0 0 0
ada13   ONLINE   0 0 0
ada12   ONLINE   0 0 0
ada11   ONLINE   0 0 0
ada1ONLINE   0 0 0

The boot pool:

NAMESTATE READ WRITE CKSUM
zroot   ONLINE   0 0 0
  mirror-0  ONLINE   0 0 0
ada5p3  ONLINE   0 0 0
ada4p3  ONLINE   0 0 0

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> >>> You're probably looking for this:
> >>> https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html
> >> 
> >> Would glabel solve it?
> > 
> > The disks are not gpart-formatted, they are used raw.
> 
> What file system are they formatted with?

ZFS, see

https://lists.freebsd.org/pipermail/freebsd-current/2019-September/074398.html

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> > You're probably looking for this:
> > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html
> 
> Thanks, that looks like a very useful approach.
> 
> Will test that when I'm in the housing facility, and report back.

I tested it, no change 8-(

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> > You're probably looking for this:
> > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html
> 
> Would glabel solve it?

The disks are not gpart-formatted, they are used raw.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> You're probably looking for this:
> https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html

Thanks, that looks like a very useful approach.

Will test that when I'm in the housing facility, and report back.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> >> Also the question is, what you mean with ???system looses track

> > I interpret the hang during boot as 'it looses track'. So I guess
> > it tries to read the kernel from the wrong drives.

> no, loader does probe disks to see which devices make up the pool and hung 
> system is not about reading the kernel from wrong place.

> I bet it is BIOS system?

If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI.

> Since the raidz seems to be created partitionless, what version
> of freebsd are you using?

FreeBSD 12.0p10, amd64.

> BIOS up to date?

The board is an X10SRi-F. dmidecode reports BIOS 3.1, supermicro
has 3.1c, but the release notes do not mention things like that
(or at least I don't understand them that way).

https://www.supermicro.com/en/products/motherboard/X10SRi-F

> can you test pool visibility in loader with latest current
> usb/cd start - like press esc in menu and check lsdev -v
> (assuming you get to menu) ? the same with uefi?

I will test this when I'm at the facility. Will take some time.

Thanks for the pointers!

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

> > I've made a few more details available here:

> > https://people.freebsd.org/~pi/host/gpart.txt

> What about gpart output of the pool drives?

No gpart on the bck pool, raw drives.

> In general you would create zpools using gptids or gpt labels, not the 
> devices, so you???re independent of device numbering. The boot loader should 
> only be installed on drives that contain the boot pool (maybe you have old 
> boot loaders on data drives?).

I think not, because they are used as raw drives.

Maybe that decision was an error in hindsight.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> > We have a system with 10 SATA disks. 2 disks are for the system,
> > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
> > 
> > bck72.8T  38.7T  34.1T- - 1%53%  1.00x  ONLINE  
> > -

> > The problem is that if all 10 disks are connected, the system
> > looses track from where it should boot and fails to boot (serial boot log):

> Why this order does change?  One would expect disks 0 and 1 to be OS disks 
> and the rest for data???

0+1 are 2.5", and the initial setup was:
- we installed system disks as zroot 
- shipped the box to the housing facility
- booted and added the drives

At that time we did not do additional tests about the disk/boot sequence
etc.

> Also the question is, what you mean with ???system looses track

I interpret the hang during boot as 'it looses track'. So I guess
it tries to read the kernel from the wrong drives.

> disk4 becomes adaX? why it matters, are you using ufs on boot disks?

No, zpool only.

I've made a few more details available here:

https://people.freebsd.org/~pi/host/dmesg.txt
https://people.freebsd.org/~pi/host/devlist.txt
https://people.freebsd.org/~pi/host/gpart.txt
https://people.freebsd.org/~pi/host/pciconf.txt
https://people.freebsd.org/~pi/host/zpool.txt

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

We have a system with 10 SATA disks. 2 disks are for the system,
8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:

bck72.8T  38.7T  34.1T- - 1%53%  1.00x  ONLINE  -

The problem is that if all 10 disks are connected, the system
looses track from where it should boot and fails to boot (serial boot log):


/boot/config: -Dh -S115200

Consoles: internal video/keyboard  serial port
BTX loader 1.00  BTX version is 1.02
Consoles: internal video/keyboard  serial port
BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS drive E: is disk2
BIOS drive F: is disk3
BIOS drive G: is disk4
BIOS drive H: is disk5
BIOS drive I: is disk6
BIOS drive J: is disk7
BIOS drive K: is disk8
BIOS drive L: is disk9
//
/


The system disks are detected as ada4 and ada5, when all disks are
plugged in.

The solution right now is this to unplug all disks of the 'bck' pool,
reboot, and re-insert the data disks after the boot is finished.

I looked into the output to kenv(1), but did not find inspiration
on how to fix this.

Now my questions:

- Shuffeling around SATA cables seems the wrong approach to fix this.
- Can we somehow lock down the disk numbering so that the system disks
  are detected as ada0 and ada1 ?
- Would
  rootdev="disk4s1a"
  in /boot/loader.conf work or is that the wrong approach ?
- How could we configure two drivers as root devices in loader.conf ?

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: poudriere, swap full and top says memory is free ?

[Kurt Jaeger]

Hi!

> > Mem: 4598M Active, 2854M Inact, 11G Laundry, 6409M Wired, 6375M Free
> > ARC: 3850M Total, 1721M MFU, 2090M MRU, 665K Anon, 19M Header, 19M Other
> >  3406M Compressed, 3942M Uncompressed, 1.16:1 Ratio
> > Swap: 18G Total, 18G Used, 396K Free, 99% Inuse, 68K In
> > 
> > So: Swap is full, approx. 6 GB memory is reported as free.

> > This is surprising. Can I somehow tune this in any way, so that
> > the memory available is used for the build ? Or is the problem somewhere
> > else ?
> 
> Are you sure that this hasn't just recently completed a large link of
> something like Chromium?

Yes, because I plot memory/swap/etc using nagios. It's not only
a spike.

> There are known to be compiles that can take
> many GB's of memory and if they recently exited, there hasn't been time
> to swap stuff back in...  or is this the steady state over the entire
> compile?

Building a few ports (firefox, libreoffice etc) takes some time,
so it has been stable during that phase.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

poudriere, swap full and top says memory is free ?

[Kurt Jaeger]

Hi!

I'm running

- a poudriere build
- of a list of ports
- on 12.0-RELEASE-p10
- on a 4 core+4 hyperthreads CPU, an Intel(R) Xeon(R) CPU E3-1230 v6
  @ 3.50GHz
- with 32 GB RAM
- zpool with 2x 500 GB SSDs as a mirror

and right now, this can be seen:

last pid: 90922;  load averages:  5.02,  5.14,  5.73up 0+03:53:08  19:31:05
82 processes:  6 running, 76 sleeping
CPU: 60.6% user,  0.0% nice,  2.1% system,  0.0% interrupt, 37.3% idle
Mem: 4598M Active, 2854M Inact, 11G Laundry, 6409M Wired, 6375M Free
ARC: 3850M Total, 1721M MFU, 2090M MRU, 665K Anon, 19M Header, 19M Other
 3406M Compressed, 3942M Uncompressed, 1.16:1 Ratio
Swap: 18G Total, 18G Used, 396K Free, 99% Inuse, 68K In

So: Swap is full, approx. 6 GB memory is reported as free.

This is surprising. Can I somehow tune this in any way, so that
the memory available is used for the build ? Or is the problem somewhere
else ?

Running similar builds on 12.0 without patches reported
swap_pager_getswapspace(24): failed
messages.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Kurt Jaeger]

Hi!

> on APU2C4 from PCengines with latest firmware apu2_v4.9.0.7.rom, SeaBIOS
> rel-1.12.1.3-0-g300e8b7, booting via legacy MBR FreeBSD 12-STABLE r350274 
> (the same with
> r350115) fails to boot with an immediate loader error:

Why did you choose -STABLE ? I have 12.0p7 running on APU2C4 and APU4C4.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fwd: ZFS Crash/Pool in unhealthy state

[Kurt Jaeger]

Hi!

> the drives are fine.
> 
> If I import the pool readonly, zpool status is also fine.
> 
> https://www.lerctr.org/~ler/ZFS_STATUS.png

Interesting. Which version of FreeBSD is this box running ?

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fwd: ZFS Crash/Pool in unhealthy state

[Kurt Jaeger]

Hi!

> Forwarding to -Current as well, since it's a -current box

What is the status of the drives ? zpool status ?

There's a crash recovery tool, if all else fails:

https://www.klennet.com/zfs-recovery/default.aspx

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Crash on very recent CURRENT if using poudriere

[Kurt Jaeger]

Hi!

> > > > [panic] non-zero write count during poudriere run
> > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031
> > > > 
> > > > Ideas on how to proceed ?
> > > 
> > > Try this.
> > 
> > Unfortunatly, I can no longer reproduce the crashes after the
> > update of the kernel to r348454.
> 
> Regardless of that, did you run with the patch applied ?

No -- should I ? How would you or I know that it changed anything ?

Should I try with the previous kernel @ r348371M and that patch ?

-- 
p...@freebsd.org +49 171 3101372  One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Crash on very recent CURRENT if using poudriere

[Kurt Jaeger]

Hi!

> > [panic] non-zero write count during poudriere run
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031
> > 
> > Ideas on how to proceed ?
> 
> Try this.

Unfortunatly, I can no longer reproduce the crashes after the
update of the kernel to r348454.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Crash on very recent CURRENT if using poudriere

[Kurt Jaeger]

Hi!

[panic] non-zero write count during poudriere run
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031

Ideas on how to proceed ?

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD and Coreboot

[Kurt Jaeger]

Hi!

> * The PC Engines boards evidently use coreboot, and I've heard multiple
> reports of them running FreeBSD systems without a problem.

I have approx. 130 of the PC Engines APUs in varius
versions up until the most recent, running with FreeBSD just fine.

No special setup, just the generic coreboot firmware.
Well, they had some issues with 12.0-REL booting from USB sticks
Booting 11.2 sticks, installing and upgrading works fine.
Did not test more recent firmware.

This worked to reflash the BIOS to their most recent versions:

Source of the BIOS:

https://pcengines.github.io/

I used 

flashrom -w apu4_v4.9.0.5.rom  --programmer internal

to upgrade:

Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 
0xff80.

/usr/local/bin/flashrom was installed by package flashrom-1.0_1

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Updating bugzilla password?

[Kurt Jaeger]

Hi!

> > I have forgotten my bugzilla account password.  I've
> > entered the Login: account name, and clicked the 
> > "Forgot Password" button.

> I'll file a bugzilla bug on your behalf in 10-20 mins. There's
> a better mailing list for this kind of query.. it's just evading my mind.

bugmeister@

https://www.freebsd.org/administration.html#t-bugmeister

But, in general, bugzilla should sent out password recovery mails.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> > > Well no longer needed as puc0 has found and allocated the
> > > device(s) which would of shown up had you done this before
> > > you fixed puc0 to find them.
> > 
> > The problem is that the found 4 uarts are not 8 uarts, and they do not
> > seem to work (tested using kermit), either 8-(
> 
> But you showed it found 8, numbered 2-10.

Yes, sorry, that was me being confused. After I plugged the board into
the box, without the pucdata modification, it showed uart0 and 2-5.
I remembered that the board saw uart0 on boot, but it turns out
that it did indeed detect uart0 and uart2-5 in the past already.

cd /dev
ls -l cuau?
crw-rw  1 uucp  dialer  0x8a Jan 21 07:22 cuau0
crw-rw  1 uucp  dialer  0x37 Jan 21 07:25 cuau2
crw-rw  1 uucp  dialer  0x3d Jan 21 07:25 cuau3
crw-rw  1 uucp  dialer  0x43 Jan 21 07:22 cuau4
crw-rw  1 uucp  dialer  0x49 Jan 21 07:22 cuau5
crw-rw  1 uucp  dialer  0x4f Jan 21 07:22 cuau6
crw-rw  1 uucp  dialer  0x55 Jan 21 07:22 cuau7
crw-rw  1 uucp  dialer  0x5b Jan 21 07:22 cuau8
crw-rw  1 uucp  dialer  0x61 Jan 21 07:22 cuau9
crw-rw  1 uucp  dialer  0x6f Jan 21 07:24 cuaua
crw-rw  1 uucp  dialer  0x75 Jan 21 07:25 cuaub
crw-rw  1 uucp  dialer  0x7b Jan 21 07:25 cuauc
crw-rw  1 uucp  dialer  0x81 Jan 21 07:22 cuaud

dmesg | grep uart
uart2: <16750 or compatible> at port 1 on puc0
uart3: <16750 or compatible> at port 2 on puc0
uart4: <16750 or compatible> at port 3 on puc0
uart5: <16750 or compatible> at port 4 on puc0
uart6: <16750 or compatible> at port 5 on puc0
uart7: <16750 or compatible> at port 6 on puc0
uart8: <16750 or compatible> at port 7 on puc0
uart9: <16750 or compatible> at port 8 on puc0
uart10: <16x50 with 256 byte FIFO> iomem 
0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0
uart11: <16x50 with 256 byte FIFO> iomem 
0xfedca000-0xfedcafff,0xfedc8000-0xfedc8fff irq 4 on acpi0
uart12: <16x50 with 256 byte FIFO> iomem 
0xfedce000-0xfedcefff,0xfedcc000-0xfedccfff irq 3 on acpi0
uart13: <16x50 with 256 byte FIFO> iomem 
0xfedcf000-0xfedc,0xfedcd000-0xfedcdfff irq 4 on acpi0
uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.

> I do not know what the other uarts are that are now showing up,
> is there other hardware in this box?

The system board is cuau0 and cuau[a-d]. cuau[2-9] are the ones detected via the
pucdata modifcation. When I look at the board manual

https://dlcdnets.asus.com/pub/ASUS/mb/socketTR4/PRIME_X399-A/E13889_PRIME_X399-A_UM_V3_WEB.pdf

it does not mention any serial ports at all. I'm surprised that it detects
5 other uarts, neither of them can be found anywhere.

> > Any hints on how to debug this ?
> 
> If you remove just the card do the other uarts still show
> up with that same patched kernel?

Then only uart0 and uart2-5 appear, with uart2-5 like uart10-13 now.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> >> > Well no longer needed as puc0 has found and allocated the
> >> > device(s) which would of shown up had you done this before
> >> > you fixed puc0 to find them.

> >> The problem is that the found 4 uarts are not 8 uarts, and they do not
> >> seem to work (tested using kermit), either 8-(

> >> Any hints on how to debug this ?

> > You need to look to get the register width right.

> Hit send too quick... I was going to say you needed to make sure that the
> register width and strides were right, but they look to be because NetBSD
> has
[...]
> for this card. so there's 4 UARTs per bar, like you are seeing. You have
> DEFAULT_RCLK * 8. COM_FREQ in NetBSD is defined:
> sys/dev/ic/comreg.h:#define COM_FREQ 1843200 /* 16-bit baud rate divisor */

Ok, I modified it and rebooted. The behaviour is still the same. I'll retest
more thoroghly in the next 48 hours.

Any idea why uart(4) finds 4 without the puc modification and why it
detects 8 uarts with 16750 with the modification ?

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> Well no longer needed as puc0 has found and allocated the
> device(s) which would of shown up had you done this before
> you fixed puc0 to find them.

The problem is that the found 4 uarts are not 8 uarts, and they do not
seem to work (tested using kermit), either 8-(

Any hints on how to debug this ?

-- 
p...@freebsd.org +49 171 3101372  One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> > none1@pci0:7:4:0:   class=0x070002 card=0x000814a1 chip=0x000814a1
> > rev=0xb0 hdr=0x00
> > vendor = 'Systembase Co Ltd'
> > class  = simple comms
> > subclass   = UART
> > bar   [10] = type I/O Port, range 32, base 0x1040, size 64, enabled
> > bar   [14] = type I/O Port, range 32, base 0x1000, size 64, enabled
> >
> 
> This is the one you want. You'll need to add vendor 14a1 device 8 to the
> puc tables. Do you need help with this?

Yes, see my other post. The card is now detected, but the result is
still strange (uart2-9 is detected as 16750, why?) and the additional
uarts 10 to 13 are also detected, but by some other mechanism I don't
understand.

And all of them do not work with kermit 8-}

> It will be a bit tricky because
> each of these defines several ports, I think.
> 
> and:
> >
> > pcib7@pci0:6:0:0:   class=0x060400 card=0x chip=0x10801b21
> > rev=0x04 hdr=0x01
> > vendor = 'ASMedia Technology Inc.'
> > device = 'ASM1083/1085 PCIe to PCI Bridge'
> > class  = bridge
> > subclass   = PCI-PCI
> >
> 
> This is something else.

It's the PCIe to PCI bridge on the card itself.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> > > uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0
[...]
> > I compared it to a second, similar hardware and there I found the same 
> > uart2,
> > even if no card was installed 8-(
> > 
> > So it seems the card is not detected at all 8-(
> 
> Need to find out why it is not showing up in the PCI
> listings.  Can you post the output from

Sorry for my late answer, I was traveling for a day.

On that box, it was not detected at all. I moved it to a different box,
added the patch below, rebuild the kernel and rebooted.

Effect: 

l cuau?
crw-rw  1 uucp  dialer  0x8a Jan 19 12:10 cuau0
crw-rw  1 uucp  dialer  0x37 Jan 19 12:17 cuau2
crw-rw  1 uucp  dialer  0x3d Jan 19 12:10 cuau3
crw-rw  1 uucp  dialer  0x43 Jan 19 12:10 cuau4
crw-rw  1 uucp  dialer  0x49 Jan 19 13:09 cuau5
crw-rw  1 uucp  dialer  0x4f Jan 19 12:14 cuau6
crw-rw  1 uucp  dialer  0x55 Jan 19 12:10 cuau7
crw-rw  1 uucp  dialer  0x5b Jan 19 12:10 cuau8
crw-rw  1 uucp  dialer  0x61 Jan 19 12:10 cuau9
crw-rw  1 uucp  dialer  0x6f Jan 19 13:58 cuaua
crw-rw  1 uucp  dialer  0x75 Jan 19 13:58 cuaub
crw-rw  1 uucp  dialer  0x7b Jan 19 13:58 cuauc
crw-rw  1 uucp  dialer  0x81 Jan 19 13:58 cuaud

[...]
pcib7@pci0:6:0:0:   class=0x060400 card=0x chip=0x10801b21 rev=0x04 
hdr=0x01
vendor = 'ASMedia Technology Inc.'
device = 'ASM1083/1085 PCIe to PCI Bridge'
class  = bridge
subclass   = PCI-PCI
puc0@pci0:7:4:0:class=0x070002 card=0x000814a1 chip=0x000814a1 rev=0xb0 
hdr=0x00
vendor = 'Systembase Co Ltd'
class  = simple comms
subclass   = UART
bar   [10] = type I/O Port, range 32, base 0x1040, size 64, enabled
bar   [14] = type I/O Port, range 32, base 0x1000, size 64, enabled

dmesg:

dmesg | grep uart
uart2: <16750 or compatible> at port 1 on puc0
uart3: <16750 or compatible> at port 2 on puc0
uart4: <16750 or compatible> at port 3 on puc0
uart5: <16750 or compatible> at port 4 on puc0
uart6: <16750 or compatible> at port 5 on puc0
uart7: <16750 or compatible> at port 6 on puc0
uart8: <16750 or compatible> at port 7 on puc0
uart9: <16750 or compatible> at port 8 on puc0
uart10: <16x50 with 256 byte FIFO> iomem 
0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0
uart11: <16x50 with 256 byte FIFO> iomem 
0xfedca000-0xfedcafff,0xfedc8000-0xfedc8fff irq 4 on acpi0
uart12: <16x50 with 256 byte FIFO> iomem 
0xfedce000-0xfedcefff,0xfedcc000-0xfedccfff irq 3 on acpi0
uart13: <16x50 with 256 byte FIFO> iomem 
0xfedcf000-0xfedc,0xfedcd000-0xfedcdfff irq 4 on acpi0
uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.

-

Index: pucdata.c
===
--- pucdata.c   (revision 343188)
+++ pucdata.c   (working copy)
@@ -870,6 +870,16 @@
},
 
/*
+* Systembase SB16C1058
+ */
+
+   {   0x14a1, 0x0008, 0x14a1, 0x0008,
+   "ExSys EX-44388",
+   DEFAULT_RCLK * 8,
+   PUC_PORT_8S, 0x10, 0, 8,
+   },
+
+   /*
 * Perle boards use Oxford Semiconductor chips, but they store the
 * Oxford Semiconductor device ID as a subvendor device ID and use
 * their own device IDs.


-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> > It only detects four (or six?) serials...
> Are perhaps 2 of them being consumed by sio?

See my other post, the system found 13 uarts 8-}
 
> > So I think I found a 'somehow' working setup and have to add stuff to
> > sys/dev/puc/pucdata.c to match it. Thanks for the pointer!
> 
> Ok, heading in the right direction, try
>   pciconf -lB
> that should show the hierarchy with the simple comms connected
> behind the pci-pci bridge.  More readable without the -v your
> using above.

Here we go:

-
hostb0@pci0:0:0:0:  class=0x06 card=0x87611043 chip=0x14501022 rev=0x00 
hdr=0x00
none0@pci0:0:0:2:   class=0x080600 card=0x14511022 chip=0x14511022 rev=0x00 
hdr=0x00
hostb1@pci0:0:1:0:  class=0x06 card=0x chip=0x14521022 rev=0x00 
hdr=0x00
pcib1@pci0:0:1:1:   class=0x060400 card=0x87611043 chip=0x14531022 rev=0x00 
hdr=0x01
bus range  = 1-9
window[1c] = type I/O Port, range 32, addr 0x1000-0x2fff, enabled
window[20] = type Memory, range 32, addr 0xba30-0xba5f, enabled
window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, 
disabled
pcib10@pci0:0:1:2:  class=0x060400 card=0x87611043 chip=0x14531022 rev=0x00 
hdr=0x01
bus range  = 10-10
window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled
window[20] = type Memory, range 32, addr 0xba70-0xba7f, enabled
window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, 
disabled
hostb2@pci0:0:2:0:  class=0x06 card=0x chip=0x14521022 rev=0x00 
hdr=0x00
hostb3@pci0:0:3:0:  class=0x06 card=0x chip=0x14521022 rev=0x00 
hdr=0x00
hostb4@pci0:0:4:0:  class=0x06 card=0x chip=0x14521022 rev=0x00 
hdr=0x00
hostb5@pci0:0:7:0:  class=0x06 card=0x chip=0x14521022 rev=0x00 
hdr=0x00
pcib11@pci0:0:7:1:  class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00 
hdr=0x01
bus range  = 11-11
window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled
window[20] = type Memory, range 32, addr 0xba00-0xba2f, enabled
window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, 
disabled
hostb6@pci0:0:8:0:  class=0x06 card=0x chip=0x14521022 rev=0x00 
hdr=0x00
pcib12@pci0:0:8:1:  class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00 
hdr=0x01
bus range  = 12-12
window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled
window[20] = type Memory, range 32, addr 0xba60-0xba6f, enabled
window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, 
disabled
intsmb0@pci0:0:20:0:class=0x0c0500 card=0x87611043 chip=0x790b1022 rev=0x59 
hdr=0x00
isab0@pci0:0:20:3:  class=0x060100 card=0x87611043 chip=0x790e1022 rev=0x51 
hdr=0x00
hostb7@pci0:0:24:0: class=0x06 card=0x chip=0x14601022 rev=0x00 
hdr=0x00
hostb8@pci0:0:24:1: class=0x06 card=0x chip=0x14611022 rev=0x00 
hdr=0x00
hostb9@pci0:0:24:2: class=0x06 card=0x chip=0x14621022 rev=0x00 
hdr=0x00
hostb10@pci0:0:24:3:class=0x06 card=0x chip=0x14631022 rev=0x00 
hdr=0x00
hostb11@pci0:0:24:4:class=0x06 card=0x chip=0x14641022 rev=0x00 
hdr=0x00
hostb12@pci0:0:24:5:class=0x06 card=0x chip=0x14651022 rev=0x00 
hdr=0x00
hostb13@pci0:0:24:6:class=0x06 card=0x chip=0x14661022 rev=0x00 
hdr=0x00
hostb14@pci0:0:24:7:class=0x06 card=0x chip=0x14671022 rev=0x00 
hdr=0x00
hostb15@pci0:0:25:0:class=0x06 card=0x chip=0x14601022 rev=0x00 
hdr=0x00
hostb16@pci0:0:25:1:class=0x06 card=0x chip=0x14611022 rev=0x00 
hdr=0x00
hostb17@pci0:0:25:2:class=0x06 card=0x chip=0x14621022 rev=0x00 
hdr=0x00
hostb18@pci0:0:25:3:class=0x06 card=0x chip=0x14631022 rev=0x00 
hdr=0x00
hostb19@pci0:0:25:4:class=0x06 card=0x chip=0x14641022 rev=0x00 
hdr=0x00
hostb20@pci0:0:25:5:class=0x06 card=0x chip=0x14651022 rev=0x00 
hdr=0x00
hostb21@pci0:0:25:6:class=0x06 card=0x chip=0x14661022 rev=0x00 
hdr=0x00
hostb22@pci0:0:25:7:class=0x06 card=0x chip=0x14671022 rev=0x00 
hdr=0x00
xhci0@pci0:1:0:0:   class=0x0c0330 card=0x11421b21 chip=0x43ba1022 rev=0x02 
hdr=0x00
ahci0@pci0:1:0:1:   class=0x010601 card=0x10621b21 chip=0x43b61022 rev=0x02 
hdr=0x00
pcib2@pci0:1:0:2:   class=0x060400 card=0x02011b21 chip=0x43b11022 rev=0x02 
hdr=0x01
bus range  = 2-9
window[1c] = type I/O Port, range 32, addr 0x1000-0x2fff, enabled
window[20] = type Memory, range 32, addr 0xba30-0xba4f, enabled
window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, 
disabled
pcib3@pci0:2:0:0:   class=0x060400 card=0x33061b21 chip=0x43b41022 rev=0x02 
hdr=0x01
bus range  = 3-3
window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled
window[20] = type Memory, 

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> uart is the new thing. sio info should be ignored.
> 
> Chances are good that this device doesn't have the proper entries in the
> puc driver. Do you have any pci devices that show up as unclaimed?

In a different box, I got this:

none1@pci0:7:4:0:   class=0x070002 card=0x000814a1 chip=0x000814a1 rev=0xb0 
hdr=0x00
vendor = 'Systembase Co Ltd'
class  = simple comms
subclass   = UART
bar   [10] = type I/O Port, range 32, base 0x1040, size 64, enabled
bar   [14] = type I/O Port, range 32, base 0x1000, size 64, enabled

and:

pcib7@pci0:6:0:0:   class=0x060400 card=0x chip=0x10801b21 rev=0x04 
hdr=0x01
vendor = 'ASMedia Technology Inc.'
device = 'ASM1083/1085 PCIe to PCI Bridge'
class  = bridge
subclass   = PCI-PCI

The chips on the card are:

  ASMedia asm1083 b0bk4911b3 1543 (?)
  SystemBase SB16C1058PCI 1624

It only detects four (or six?) serials...

So I think I found a 'somehow' working setup and have to add stuff to
sys/dev/puc/pucdata.c to match it. Thanks for the pointer!

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0

Ah, that is a false lead.

I compared it to a second, similar hardware and there I found the same uart2,
even if no card was installed 8-(

So it seems the card is not detected at all 8-(

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

> > Trying to get a 8-port serial PCIe card into operation (Exsys EX-44388).
> > After reboot, dmesg shows:
> >
> > uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0
[...]

> uart is the new thing. sio info should be ignored.
> 
> Chances are good that this device doesn't have the proper entries in the
> puc driver. Do you have any pci devices that show up as unclaimed?

One, but it does not look like a match ?

none0@pci0:0:31:3:  class=0x0c0500 card=0x062415d9 chip=0x1c228086 rev=0x05 
hdr=0x00
vendor = 'Intel Corporation'
device = '6 Series/C200 Series Chipset Family SMBus Controller'
class  = serial bus
subclass   = SMBus
bar   [10] = type Memory, range 64, base 0xdfa21000, size 256, enabled
bar   [20] = type I/O Port, range 32, base 0x580, size 32, enabled

It's a PCIe card, not PCI, does that matter ?

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Multiport serial card Exsys EX-44388, where are the devices ?

[Kurt Jaeger]

Hi!

Trying to get a 8-port serial PCIe card into operation (Exsys EX-44388).
After reboot, dmesg shows:

uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0

and /dev/ has cuau2* devices. It's unclear, which of the 8 ports
is cuau2 (I'll test that later, I promise 8-), but where are the
other ports ?

I've tried to add

hint.uart.3.at="isa"
hint.uart.3.port="0x3e0"
hint.uart.3.irq="10"
hint.uart.4.at="isa"
hint.uart.4.port="0x3d8"
hint.uart.4.irq="10"

to /boot/devices.hint and rebooted, but there are no additional ports found...

I've read

  https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serial.html

and the manpage sio(4). It says to build a kernel with

options COM_MULTIPORT
device sio

which I tried (r343121) and it fails:

/usr/src/sys/dev/sio/sio.c:361:6: error: no member named 't_init_in' in
  'struct tty'
tp->t_init_in.c_ispeed  = tp->t_init_in.c_ospeed =
~~  ^

So, is sio(4) out of fashion ? What is suggested to get my other 7 serial ports 
?

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: UEFI, loader.efi and /boot.config

[Kurt Jaeger]

Hello,

> I was wondering if people will expect /boot.config to still be read and so 
> code should be added to loader to continue to parse it, or if loader.conf can 
> be considered the correct place and boot.config forgotten about?

If the early boot messages are not displayed as Olivier mentioned,
that would be fatal. On some systems no other output besides serial
is useful.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: UEFI, loader.efi and /boot.config

[Kurt Jaeger]

Hi!

> With a recent change I made for UEFI, we now install loader.efi onto the ESP 
> and don???t run boot1. That means that /boot.config is no longer read, and so 
> console settings need to be put in /boot/loader.conf

Which change is that ?

> I was wondering if people will expect /boot.config to still be read and so 
> code should be added to loader to continue to parse it, or if loader.conf can 
> be considered the correct place and boot.config forgotten about?

I have quite a few systems using /boot.config, but can cope if I know about 
this.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: openssl 1.1.1 utils mkerr.pl

[Kurt Jaeger]

Hi!

> Did you try to use the openssl port?

cd security/openssl111
$ grep mkerr pkg-plist 
$ 

does not have it, either.

-- 
p...@freebsd.org +49 171 3101372 One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: kernel config question

[Kurt Jaeger]

Hi!

> FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64
> 
>   to CURRENT (as of last midnight.
>   Does this, in src/UPDATING:
> 
>   [8] In order to have a kernel that can run the 4.x binaries
>   needed to do an installworld, you must include the
>   COMPAT_FREEBSD4 option in your kernel. [...]

>(It seems ... irrational ... one would need compatibility stuff
>  going back to FreeBSD 4 to rebuild/update FreeBSD 13.)

No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed.

-- 
p...@freebsd.org +49 171 3101372 One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg problem on FreeBSD 13.0-CURRENT

[Kurt Jaeger]

Hi!

> On 10/25/18 5:19 PM, Sean Bruno wrote:
> > pkg-static install -f pkg
> 
> It works better now, but there are some complaints.

If it's only the certificate issue, try this:

cd /usr/local/etc
cp pkg.conf.sample pkg.conf
vi pkg.conf
-
PKG_ENV : {
SSL_NO_VERIFY_PEER: 1
}
-

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg problem on FreeBSD 13.0-CURRENT

[Kurt Jaeger]

Hi!

> FreeBSD konjak 13.0-CURRENT FreeBSD 13.0-CURRENT r339705 GENERIC  amd64
> 
> pkg-static install -f pkg
> pkg-static: Warning: Major OS version upgrade detected.  Running
> "pkg-static install -f pkg" recommended
> Updating FreeBSD repository catalogue...
> pkg-static: Repository FreeBSD load error: access repo
> file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory
> pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/meta.txz: Not
> Found

The package builders are not yet providing packages for 13.0-CURRENT.

It's being worked on, but will take a little more time.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: problems on lists.freebsd.org error 503 backend fetch failed

[Kurt Jaeger]

Hi!

> Hi, if there's a better place to report this then please advise

cluster...@freebsd.org or postmas...@freebsd.org -- they are informed
about it already.

> It seems the web-mail-list software for FreeBSD has failed partially (mostly?)

It's the load-balancer in front of the mailman instance that failed.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Bad DHCP Checksums over VLANs

[Kurt Jaeger]

Hi!

> >> ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag 
> >> -vlanhwcsum -vlanhwtso
> >>
> >> Try to disable everything that can be disabled, e.g. LRO etc.
> >
> > Disabling vlanhwtag works around the problem.
> >
> > Also note that only DHCP traffic has this problem.  If I assign an 
> > address manually, all traffic flows normally.  Maybe the problem is in 
> > the BPF send path.
> >
> I had a similar issue, where -vlanhwtag also fixed it.
> That was on a I210 (gib) card (in a FreeNAS mini XL).

I've created a PR for this:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231416

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Bad DHCP Checksums over VLANs

[Kurt Jaeger]

Hi!

> The server NIC is common (I211), so maybe it's easy to reproduce.  I'll 
> help as much as I can, of course.

Can you disable all the options of the NIC ?

ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag -vlanhwcsum 
-vlanhwtso

Try to disable everything that can be disabled, e.g. LRO etc.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: github freebsd and svn freebsd

[Kurt Jaeger]

Hi!

> What's the difference between github freebsd and svn freebsd, other than 
> one is on github and the other is on svn?

The github repo isn't official, because there are still some
consistency issues. The consistency problem is: If an repo-copy
from svn to git is done, how can that repo-copy be done a second
time and still keep the same commit ids (in the git repo) ?

> How does one transcode or translate a git commit reference into a svn 
> reference number?

That's a good question. There's a small team working on the github
stuff:

https://www.freebsd.org/administration.html#t-github-automation

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: NFS via IPv6 between 11.2-REL amd64 and larger (>45 files) directories?

[Kurt Jaeger]

Hi!

> As Rick told me there's a ongoing debate on this, here's a copy
> from my mail to stable@:

PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231050

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: NFS via IPv6 between 11.2-REL amd64 and larger (>45 files) directories?

[Kurt Jaeger]

Hi!

As Rick told me there's a ongoing debate on this, here's a copy
from my mail to stable@:

I've seen a strange effect: NFS via IPv6 between 11.2-REL amd64
boxes failed for directories with more than 45 files or directories.
Small directories worked. It seems to be an issue with
ipv6 fragmentation (?), as can be seen by tcpdump:

17:54:16.855978 IP6 nfs-serv > nfs-client frag (0|1448) 2049 > 709: NFS reply 
xid 1536109002 reply ok 1440 readdir
17:54:16.855979 IP6 nfs-serv > nfs-client frag (1448|36)

As soon as the NFS request is sent with fragments, it stalls.

Using TCP or IPv4 for the nfs mount works, UDP fails.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Unexpected results with 'mergemaster -Ui'

[Kurt Jaeger]

Hi!

>  line 133 onwards, for example.
> 
> I never before found any potential change to
> /etc/group
> 
> Please, is it unusual?

No, it is normal, that happens if you have local changes.
I suggest you discard the incoming /etc/group and go with your
current version and the local changes.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: updates to HEAD online, RSS non-browser ??

[Kurt Jaeger]

Hi!

> secnetix.de used to let me read HEAD updates to src daily.
> About
> several monhts ago, my browsers cannot reach it and the 2ndry site
> is tedious to read in an equivalent manner. AFAIK the site is still up.

I've checked (from .de) and the site is down.

Why don't you use the mailman archive ?

https://lists.freebsd.org/pipermail/svn-src-all/

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: em0 link fail

[Kurt Jaeger]

Hi!

> On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up
> (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I
> can't without the em0 interface stalling :-(

I had a similar case on a current r334918 and saw this in the kern syslog:

  Jun 30 15:40:34 fc kernel: em0: TX(0) desc avail = 1024, pidx = 0

A reboot was necessary to get this fixed.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: swapping is completely broken in -CURRENT r334649?

[Kurt Jaeger]

Hi!

> > I just started it again, and after a while the qemu-ppc64-static
> > was at approx. 23 GB memory and increasing, without much progress.

> Last time I tried (2 weeks ago) qemu-ppc64-static was broken, not sure the
> situation has evolved since that.

Ok, thanks! Then it's not the same problem.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: swapping is completely broken in -CURRENT r334649?

[Kurt Jaeger]

Hi!

> > > The change was committed as r334752.  Are you seeing unexpected OOM
> > > kills on or after that revision?
> > 
> > When I tried to run a qemu-based poudriere run yesterday on a r334918
> > box, it killed a few processes outside of that run and did not
> > work out.
> > 
> > I'm unsure it was because of that problem or a problem with qemu.
> 
> How much memory and swap does the guest have?

It's started by poudriere, I do not really know.

> Were you consistently able to complete a run before?

Two years ago, on a much lower version of FreeBSD, yes.

I just started it again, and after a while the qemu-ppc64-static
was at approx. 23 GB memory and increasing, without much progress.

> If it's happening during a poudriere run, it may well have been a true
> OOM situation.  The patch below prints a few stats to the dmesg before
> the kill.  The output of that together with "sysctl vm" output should be
> enough to determine what's happening.
> 
> diff --git a/sys/vm/vm_pageout.c b/sys/vm/vm_pageout.c
> index 264c98203c51..9c7ebcf451ec 100644
> --- a/sys/vm/vm_pageout.c
> +++ b/sys/vm/vm_pageout.c
> @@ -1670,6 +1670,8 @@ vm_pageout_mightbe_oom(struct vm_domain *vmd, int 
> page_shortage,
>* start OOM.  Initiate the selection and signaling of the
>* victim.
>*/
> + printf("v_free_count: %u, v_inactive_count: %u\n",
> + vmd->vmd_free_count, vmd->vmd_pagequeues[PQ_INACTIVE].pq_cnt);
>   vm_pageout_oom(VM_OOM_MEM);
>  
>   /*

I'll have a look at this.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: swapping is completely broken in -CURRENT r334649?

[Kurt Jaeger]

Hi!

> The change was committed as r334752.  Are you seeing unexpected OOM
> kills on or after that revision?

When I tried to run a qemu-based poudriere run yesterday on a r334918
box, it killed a few processes outside of that run and did not
work out.

I'm unsure it was because of that problem or a problem with qemu.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

What's in FreeBSD12

[Kurt Jaeger]

Hi!

> As OpenBSD fan, who also uses OpenBSD on EdgerouterLite,
> I would be pleased to hear that FreeBSD-12 would be a release where PF
> is updated to some newer version, possibly having parity with OpenBSD.
> 
> In the meantime it looks like I will need to learn IPFW to do QoS.
> 
> BTW: I was looking at the whatsnew-wiki of FreeBSD and I can not find
> any reliable resources of what FreeBSD-12 will be like. On the FreeBSD
> website it is already noted as incomming, however I have no idea what
> will be included in this release. Do you know of some?

https://wiki.freebsd.org/WhatsNew/FreeBSD12

has a few bits.

I have this list, from reviews and posts and things I stumbled over:

- netflow netgraph
  ipfw add ngtee
- ipfw setdscp
  Set specified DiffServ codepoint for an IPv4/IPv6 packet.
  analog:
  ipfw dscp
- vimage will be included in the generic kernel 
  https://svnweb.freebsd.org/base?view=revision=324810
  
https://people.freebsd.org/~olivier/talks/2017_EuroBSDCon-Tuning_FreeBSD_for_routing_and_firewalling.pdf
- ccp(4): experimental driver for AMD Crypto Co-Processor
  https://svnweb.freebsd.org/base?view=revision=328150
- jedec_dimm: report asset info and temperatures for DDR3 and DDR4 DIMMs
- ps aux | some stuff gets full width output
- TCP blackbox recorder code
  https://wiki.freebsd.org/DevSummit/201706/Transport
  https://reviews.freebsd.org/D11085
- VMCI (Virtual Machine Communication Interface) driver
  https://reviews.freebsd.org/D14289
- sysvipc works in jails (I think this is already in some 11.x)
  https://www.skyforge.at/posts/a-note-in-sysvipc-and-jails-on-freebsd/
  bisher:
  allow.sysvipc = 1
  nun:
  sysvmsg, sysvsem and sysvshm
  sysvshm = ["disable"|"inherit"|"new"];
- ether random
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211984
- zpool temporary names
  https://github.com/openzfs/openzfs/pull/600
  https://reviews.freebsd.org/D14972
- isoboot, see https://reviews.freebsd.org/D14914
- control CPU topology in bhyve
  https://reviews.freebsd.org/D9930
- netdump, dump core over the network
  https://lists.freebsd.org/pipermail/freebsd-arch/2018-April/018927.html
  https://reviews.freebsd.org/D15253
- socket-option SO_REUSEPORT_LB
  multiple processes can listen on the same port, for load balancing
  https://reviews.freebsd.org/D11003
- D15234: remove support for ixgb
  This driver was for an early and uncommon legacy PCI 10GbE for a
  single ASIC, Intel 82597EX. Intel quickly shifted to the long
  lived ixgbe family.
- bhyve debug server for gdb, D15022

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pfctl: igb0: driver does not support altq

[Kurt Jaeger]

Hi!

> I get a message:
>   pfctl: igb0: driver does not support altq
> 
> on:
>   12.0-CURRENT FreeBSD 12.0-CURRENT #1 r88:
>   Wed May 9 00:58:52 CEST 2018
>   root@***censored***:/usr/obj/usr/src/amd64.amd64/sys/GUSTIK
>   amd64
[...]
> Problem does not seem to appear on 10-stable, or 11-stable.
> Actually on 10.4 it worked as expected.

There is a long ongoing debate on the future of ALTQ,
and one PR that might be of interest:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257

See also:

http://undeadly.org/cgi?action=article=20140419151959
http://bsdly.blogspot.de/2011/07/anticipating-post-altq-world.html
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: AES67

[Kurt Jaeger]

Hi!

> Is there any known attempt to implement AES67 (is an open standard
> for audio over IP and audio over ethernet interoperability) on FreeBSD?

> http://medianetworkingalliance.com/faq-aes67/

I found

https://www.collabora.com/news-and-blog/blog/2017/04/25/receiving-an-aes67-stream-with-gstreamer/

which describes AES67 as RTP with some clock sync. But it looks
like there is no open source implementation at all right now.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: netmap with ix/igb?

[Kurt Jaeger]

Hi!

> I'm having problems* using netmap with 12-CURRENT from late 2017. Anyone
> know if a newer kernel would work better?

Something like this ?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221317

Look in bugs.freebsd.org for ixgbe, there are several other issues.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"