[Bug 255043] ena device is not getting enabled post addition in kernel

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255043

--- Comment #1 from Andriy Gapon  ---
The report is somewhat thing on details.
You did not demonstrate that you have any "hardware" that should be supported
by ena.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255043] ena device is not getting enabled post addition in kernel

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255043

--- Comment #2 from Andriy Gapon  ---
(In reply to Andriy Gapon from comment #1)
s/thing/thin/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254723] [patch] systat -swap to display per-process swap space usage ordered by highest

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254723

--- Comment #2 from Andriy Gapon  ---
Just curious, do you consider adding this functionality to top?
Its current implementation of -w option is useless.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc)

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254841

Andriy Gapon  changed:

   What|Removed |Added

 Status|New |Open

--- Comment #3 from Andriy Gapon  ---
(In reply to Daniel Austin from comment #2)
mps_set.c looks like a new file, you should put your own copyright into it
(assuming you are the author, of course).

Other than that, the change looks good to me and I can commit it unless anyone
objects.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255047] race bug with mount generating same fsid for different mount points

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255047

Bug ID: 255047
   Summary: race bug with mount generating same fsid for different
mount points
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: oliv...@freebsd.org
 Attachment #224098 text/plain
 mime type:

Created attachment 224098
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224098&action=edit
script to reproduce the bug

Here is a small shell script to reproduce a race bug with mount/umount.

A beginning of explanation by Chuck Silvers:
"the umount command prefers to tell the kernel which fs to unmount not by the
path that it is given on the command line, but rather by fsid, which it gets
from the getfsstat() syscall.
There is code in the kernel mount syscall that is supposed to detect this and
generate an unique, ephemeral fsid if an ffs file system being mounted has the
same fsid on disk as another file system that is already mounted, but that code
has a race that can cause it to miss detecting the duplicate fsid if the two
mounts of file systems with the same on-disk fsid happen at the same time."  


Once started this shell script should display this kind of output:

# ./bug.sh
Initializing...
Creating one 500MB file...
Creating md device to newfs it (mkimage ??)...
newfs it...
/dev/md0: 500.0MB (1024000 sectors) block size 32768, fragment size 4096
using 4 cylinder groups of 125.03MB, 4001 blks, 16128 inodes.
super-block backups (for fsck_ffs -b #) at:
 192, 256256, 512320, 768384
Destroying md device md0...
Ready to trigger bug!
[2] Copying /tmp/mount_bug into /tmp/2...
[1] Copying /tmp/mount_bug into /tmp/1...
[1] Creating md device...
[1] mount md0 into /tmp/1.mnt...
[2] Creating md device...
[2] mount md1 into /tmp/2.mnt...
[1] fsid of the mount point /tmp/1.mnt/: superblock location65536   id 
[ 6076b0bb 46c244a6 ]
[1] Creating a file into it /tmp/1.mnt/...
[2] fsid of the mount point /tmp/2.mnt/: superblock location65536   id 
[ 6076b0bb 46c244a6 ]
[2] Creating a file into it /tmp/2.mnt/...
[1] unmount /tmp/1.mnt...
umount: unmount of /tmp/1.mnt failed: Device busy
[2] unmount /tmp/2.mnt...
umount failed because: 1) it umounted the wrong (still creating file) or 2)
already unmount by the other!
[1] Destroying md device md0...
mdconfig: ioctl(/dev/mdctl): Device busy
destroying md device failed, because still mounted
[1] cleaning up...
[2] Destroying md device md1...
[2] cleaning up...
rm: /tmp/1.mnt: Device busy

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc)

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254841

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@freebsd.org

--- Comment #4 from Yuri Pankov  ---
The patch seems to work fine for me, sadly it looks like my board does not have
temp sensor (I was worried about it getting very hot too and even slapped a
small fan on it):

mps0 Adapter:
   Board Name: SAS9211-8i
   Board Assembly: H3-25250-02G
Chip Name: LSISAS2008
Chip Revision: ALL
BIOS Revision: 7.37.00.00
Firmware Revision: 20.00.07.00
  Integrated RAID: no
 SATA NCQ: ENABLED
 PCIe Width/Speed: x8 (5.0 GB/sec)
IOC Speed: Full
  Temperature: Unknown/Unsupported

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc)

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254841

Rodrigo Osorio  changed:

   What|Removed |Added

 CC||rodr...@freebsd.org

--- Comment #5 from Rodrigo Osorio  ---
Created attachment 224099
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224099&action=edit
update mpsutil.8 with set ncq

My two cents to update mpsutil manpage

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc)

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254841

--- Comment #6 from Daniel Austin  ---
(In reply to Yuri Pankov from comment #4)
Hi Yuri,

Could you let me know the output of:

mpsutil show cfgpage 0 7

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc)

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254841

--- Comment #7 from Yuri Pankov  ---
(In reply to Daniel Austin from comment #6)
Daniel, here you go:

Page 0x0: IO Unit 7, Read-only
   00 07 0a 04  ||
0004   01 08 00 00  ||
0008   00 00 00 00  ||
000c   00 00 00 00  ||
0010   01 00 00 00  ||
0014   00 00 00 00  ||
0018   00 01 00 00  ||
001c   00 00 00 00  ||
0020   00 00 00 00  ||
0024   00 00 01 00  ||

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc)

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254841

--- Comment #8 from Daniel Austin  ---
(In reply to Yuri Pankov from comment #7)
Ah, sadly that means there are no temperature sensors on your board or
controller ICs :-(

I've never seen a lsisas2008 chip overheat so long as it had airflow though, so
your fan will be working fine... I managed to clock my lsisas2308 at 111C with
a fan nearby... now with better more direct fans i've got it down to around
70C.
I've never seen cards run as hot as the 2308s!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc)

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254841

--- Comment #9 from Yuri Pankov  ---
(In reply to Daniel Austin from comment #8)
In any case, works with 2308 for me too, thanks for the patch!

mps0 Adapter:
   Board Name: SAS9205-8e
   Board Assembly: H3-25360-04G
Chip Name: LSISAS2308
Chip Revision: ALL
BIOS Revision: 7.35.00.00
Firmware Revision: 18.00.00.00
  Integrated RAID: no
 SATA NCQ: ENABLED
 PCIe Width/Speed: x8 (5.0 GB/sec)
IOC Speed: Full
  Temperature: 49 C

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255048] ROCKPRO64 freeze during heavy IO on external USB 3 disk

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255048

Bug ID: 255048
   Summary: ROCKPRO64 freeze during heavy IO on external USB 3
disk
   Product: Base System
   Version: 13.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: h...@restart.be

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

Mark Millard  changed:

   What|Removed |Added

 CC||marklmi26-f...@yahoo.com

--- Comment #1 from Mark Millard  ---
Looks like 1ae20f7c70e is a detection of inappropriate use
of M_WAITOK in a context where it is not allowed because
it might sleep when sleeping is not allowed:

diff --git a/sys/kern/kern_malloc.c b/sys/kern/kern_malloc.c
index 48383358e3ad..0d6f9dcfcab7 100644
--- a/sys/kern/kern_malloc.c
+++ b/sys/kern/kern_malloc.c
@@ -537,7 +537,7 @@ malloc_dbg(caddr_t *vap, size_t *sizep, struct malloc_type
*mtp,
 #ifdef EPOCH_TRACE
epoch_trace_list(curthread);
 #endif
-   KASSERT(1, 
+   KASSERT(0,
("malloc(M_WAITOK) with sleeping prohibited"));
}
}

Letting the inappropriate activity happen by reverting the change
does not look reasonable from what I can tell. (Not that I'm
expert, however.)

More likely the context needs to be analyzed for what allocation
is happening in what kind of restricted context and then, with
that information, a fix that avoids the bad type of activity
would be developed. It is not obvious what all code would need
to change at this point.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255048] ROCKPRO64 freeze during heavy IO on external USB 3 disk

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255048

Henri Hennebert  changed:

   What|Removed |Added

 CC||h...@restart.be

--- Comment #1 from Henri Hennebert  ---
FreeBSD keystone.lab.bel 13.0-STABLE FreeBSD 13.0-STABLE #0
stable/13-n245189-236d1f8c1773

The disk is under zfs

During a `git pull` in /usr/ports the system show the da0 disk 100% busy and
afer ~2 minutes the system freeze.

The system respond to ping

I connect on the serial console (CR ~ ^B) to ddb:

db> show msgbuf
...
swap_pager: cannot allocate bio
swap_pager: cannot allocate bio
swap_pager: cannot allocate bio
swap_pager: cannot allocate bio
swap_pager: cannot allocate bio
swap_pager: cannot allocate bio

db> show allchains
chain 1:
 thread 115444 (pid 87479, git) is sleeping on 0xef3dfc08 "aw.aew_cv"
chain 2:
 thread 115446 (pid 87479, git) is sleeping on 0xa00058d653e8 "zio->io_cv"
chain 3:
 thread 115447 (pid 87479, git) is sleeping on 0xa000b26cf3e8 "zio->io_cv"
chain 4:
 thread 115450 (pid 87479, git) is sleeping on 0xef3cbc08 "aw.aew_cv"
chain 5:
 thread 115452 (pid 87479, git) is sleeping on 0xa91518b8 "zio->io_cv"
chain 6:
 thread 115453 (pid 87479, git) is sleeping on 0xef3e9c08 "aw.aew_cv"
chain 7:
 thread 115455 (pid 87479, git) is sleeping on 0xa00058d028b8 "zio->io_cv"
chain 8:
 thread 115458 (pid 87479, git) is blocked on sx "zfsvfs->z_hold_mtx[i]" XLOCK
 thread 115455 (pid 87479, git) is sleeping on 0xa00058d028b8 "zio->io_cv"
chain 9:
 thread 115459 (pid 87479, git) is sleeping on 0xa000971718b8 "zio->io_cv"
chain 10:
 thread 115460 (pid 87479, git) is sleeping on 0x00010420dc08 "aw.aew_cv"
chain 11:
 thread 115462 (pid 87479, git) is sleeping on 0x000104217c08 "aw.aew_cv"
chain 12:
 thread 115463 (pid 87479, git) is sleeping on 0x00010421cc08 "aw.aew_cv"
chain 13:
 thread 101506 (pid 1214, god.plugin) is sleeping on 0xecdb70a8
"aw.aew_cv"
chain 14:
 thread 101508 (pid 1214, god.plugin) is sleeping on 0xa000e430da80 "vmpfw"
chain 15:
 thread 101510 (pid 1214, god.plugin) is sleeping on 0xecc5e0a8
"aw.aew_cv"
chain 16:
 thread 101513 (pid 1214, god.plugin) is sleeping on 0xecd990a8
"aw.aew_cv"
chain 17:
 thread 101352 (pid 1211, apps.plugin) is sleeping on 0xa00058d658b8
"zio->io_cv"
chain 18:
 thread 101448 (pid 1195, httpd) is sleeping on 0xecc9f0a8 "aw.aew_cv"
chain 19:
 thread 101366 (pid 1179, httpd) is sleeping on 0xa0008c253d88 "zio->io_cv"
chain 20:
 thread 101346 (pid 1141, netdata) is sleeping on 0xe9424cb8
"aw.aew_cv"
chain 21:
 thread 101355 (pid 1121, sshd) is sleeping on 0x00b24d80 "pfault"
chain 22:
 thread 101350 (pid 1083, sendmail) is sleeping on 0x00b24d80 "vmwait"
chain 23:
 thread 101349 (pid 1079, inetd) is sleeping on 0xa00027577b40 "select"
chain 24:
 thread 101347 (pid 1050, ntpd) is sleeping on 0xe93fd0a8 "aw.aew_cv"
chain 25:
 thread 101314 (pid 970, syslogd) is sleeping on 0x00b24d80 "pfault"
chain 26:
 thread 100152 (pid 31, syncer) is sleeping on 0x00d5f480 "syncer"
chain 27:
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
 thread 100151 (pid 30, vnlru) is blocked on lockmgr  DEXCL
... 
...continue for at least 1400 lines.
...
db> show proc 30
Process 30 (vnlru) at 0xa6449000:
 state: NORMAL
 uid: 0  gids: 0
 parent: pid 0 at 0x00cf1828
 ABI: null
 flag: 0x1204  flag2: 0
 reaper: 0x00cf1828 reapsubtree: 30
 sigparent: 20
 vmspace: 0x00cf22c8
   (map 0x00cf22c8)
   (map.pmap 0x00cf2388)
   (pmap 0x00cf23e8)
 threads: 1
100151   D   vlruwt  0xa6449000  [vnlru]
db> 

[Bug 255048] ROCKPRO64 freeze during heavy IO on external USB 3 disk

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255048

--- Comment #2 from Henri Hennebert  ---
In case it may be important to the problem:

[root@keystone ~]# sysctl dev.cpu.{0,1,2,3,4,5}.freq
dev.cpu.0.freq: 1416
dev.cpu.1.freq: 1416
dev.cpu.2.freq: 1416
dev.cpu.3.freq: 1416
dev.cpu.4.freq: 1800
dev.cpu.5.freq: 1800

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255051] Remove mention of coldsync from devd.conf

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255051

Bug ID: 255051
   Summary: Remove mention of coldsync from devd.conf
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: conf
  Assignee: b...@freebsd.org
  Reporter: c...@submonkey.net

Created attachment 224104
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224104&action=edit
devd.conf patch

The coldsync project is very, very dormant and was removed from ports in 2012.
Remove it, therefore, from devd.conf along with the typo I came here to fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255043] ena device is not getting enabled post addition in kernel

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255043

--- Comment #3 from shamsher  ---
Hi Andriy,
Using Intel NIC of model 82599EB 10-Gigabit X520-SR2 for n/w interface.
In Amazon, want to enable C5 for VM, but it need ENA module to be enabled. So,
before loading it to Amazon using AMI image, locally checking in target with
same configuration with Intel Xeon processor and above NIC. But not able to see
ENA modules as enabled.

Post config change and build, only it shows as ENA is integrated as part of
kernel.
Also tried with [if_ena_load="YES"] in loader.conf file (which may not be
needed as I haven't made it as loadable module) but still no help.

Thanks
shamsher

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

Li-Wen Hsu  changed:

   What|Removed |Added

 CC||kev...@freebsd.org,
   ||lw...@freebsd.org

--- Comment #2 from Li-Wen Hsu  ---
CC author of https://reviews.freebsd.org/D29125

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

--- Comment #3 from Kyle Evans  ---
(In reply to Masachika ISHIZUKA from comment #0)

Hi,

Can you please provide some information about the panic you received? We'll
need at least a backtrace to have even some remote idea of what's happening.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 150620] [request] Please include utility programs for ncurses

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=150620

Yuri Pankov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Assignee|b...@freebsd.org|b...@freebsd.org
Version|Unspecified |CURRENT
 CC||b...@freebsd.org
 Status|Open|Closed

--- Comment #4 from Yuri Pankov  ---
Done in base 61f66a1f4403.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255054] jng fails to run ngctl msg vtnet0: setpromisc 1

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255054

Bug ID: 255054
   Summary: jng fails to run ngctl msg vtnet0: setpromisc 1
   Product: Base System
   Version: 13.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: t...@puroto.org

Having recently upgraded to 13.0-STABLE, I found that none of my jng-enabled
jails were coming up after boot.

root@puroto:/ # service jail start pupuru
Starting jails: cannot start jail  "pupuru":
ngctl: send msg: Operation not supported
jail: pupuru: jng bridge pupuru vtnet0: failed
.
root@puroto:/ #

In this case the jails.conf entry was:

pupuru {
  exec.prestart += "jng bridge pupuru vtnet0";
  exec.poststop += "jng shutdown pupuru";
}

Digging into what jng was doing, we were trying to switch the parent interface
to promiscuous mode, failing, and then bailing out:

# ngctl msg vtnet0: setpromisc 1
ngctl: send msg: Operation not supported

Just commenting out that line in jng seemed to be sufficient, though I don't
know
what side effects that might have. My jails all came up ok after that, and were
at least able to send/recv traffic, ping the jail host, etc.

306 # Set promiscuous mode and don't overwrite src addr
307 # ngctl msg $iface: setpromisc 1 || return
308 ngctl msg $iface: setautosrc 0 || return

I checked that my copy of /usr/sbin/jng wasn't significantly different to the
one being shipped in /usr/share/examles/jails.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255056] 13.0-RELEASE - Boot from ZFS after upgrade broken

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255056

Bug ID: 255056
   Summary: 13.0-RELEASE - Boot from ZFS after upgrade broken
   Product: Base System
   Version: 13.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: conf
  Assignee: b...@freebsd.org
  Reporter: christiangutz...@gmail.com

Hi, just did an upgrade from 12.4-RELEASE to 13.0-RELEASE and could not boot
from ZFS.
After removing "opensolaris_load="YES" from /boot/loader.conf, everything
worked again.

Shouldn´t this change be done automatically during update?

Regards
Christian

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255054] jng fails to run ngctl msg vtnet0: setpromisc 1

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255054

Li-Wen Hsu  changed:

   What|Removed |Added

 CC||lw...@freebsd.org
   Assignee|b...@freebsd.org|j...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254343] 13.0-RC2: adding a vtnet (VirtIO network) interface to bridge fails

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254343

Kristof Provost  changed:

   What|Removed |Added

 Blocks||255054


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255054
[Bug 255054] jng fails to run ngctl msg vtnet0: setpromisc 1
-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 223127] find(1) does not explain what "-f" option does

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223127

Ceri Davies  changed:

   What|Removed |Added

 CC||c...@submonkey.net

--- Comment #2 from Ceri Davies  ---
Created attachment 224108
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224108&action=edit
manpage patch

Patch attached.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

--- Comment #4 from Masachika ISHIZUKA  ---
Created attachment 224109
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224109&action=edit
core.txt.2.xz

crash dump

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

Kyle Evans  changed:

   What|Removed |Added

 CC||a...@freebsd.org

--- Comment #5 from Kyle Evans  ---
(In reply to Masachika ISHIZUKA from comment #4)

CC'ing Andrey, looks like b99a6823204f0ecbefef21af585dde03c4d76ba1 ("Rework
ipfw dynamic states implementation to be lockless on fast path.") started doing
M_WAITOK allocations in a callout (dyn_tick -> dyn_grow_hashtable), which is a
non-sleepable context.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

--- Comment #6 from Masachika ISHIZUKA  ---
(In reply to Masachika ISHIZUKA from comment #4)
# cat info.2
Dump header from device: /dev/gpt/fbswap
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 525697024
  Blocksize: 512
  Compression: none
  Dumptime: 2021-04-15 00:44:38 +0900
  Hostname: carrot.ish.org
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 14.0-CURRENT #28 0c80ad2dc: Thu Apr 15 00:32:41 JST
2021
ishiz...@carrot.ish.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
  Panic String: malloc(M_WAITOK) with sleeping prohibited
  Dump Parity: 4198134333
  Bounds: 2
  Dump Status: good
carrot# cat /var/crash/info.2
Dump header from device: /dev/gpt/fbswap
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 525697024
  Blocksize: 512
  Compression: none
  Dumptime: 2021-04-15 00:44:38 +0900
  Hostname: carrot.ish.org
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 14.0-CURRENT #28 0c80ad2dc: Thu Apr 15 00:32:41 JST
2021
ishiz...@carrot.ish.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
  Panic String: malloc(M_WAITOK) with sleeping prohibited
  Dump Parity: 4198134333
  Bounds: 2
  Dump Status: good
#

vmcore is too large, so it put to https://www.ish.org/files/vmcore.2.xz

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

--- Comment #7 from Masachika ISHIZUKA  ---
(In reply to Masachika ISHIZUKA from comment #6)
> vmcore is too large, so it put to https://www.ish.org/files/vmcore.2.xz

Sorry, 
https://www.ish.org/files/vmcore.2-0c80ad2dc.xz

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

--- Comment #8 from Andrey V. Elsukov  ---
(In reply to Kyle Evans from comment #5)

I think the problem was here in earlier implementation too, I'll fix this next
tomorrow. Thanks for the report.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255041] panic: system freeze/panic with D29125 patch

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255041

--- Comment #9 from Kyle Evans  ---
(In reply to Andrey V. Elsukov from comment #8)

Ah, sorry, I did not look much further than `git blame` and the message.
Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255048] ROCKPRO64 freeze during heavy IO on external USB 3 disk

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255048

--- Comment #3 from Henri Hennebert  ---
I reproduce the freeze, same output _without_ 

"swap_pager: cannot allocate bio"

in msgbuf.

db> sysctl vfs.numvnodes
vfs.numvnodes: 151830
db> sysctl kern.maxvnodes
kern.maxvnodes: 80

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255061] [PATCH] Proof of concept nested mounts for automounter -hosts map

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255061

Bug ID: 255061
   Summary: [PATCH] Proof of concept nested mounts for automounter
-hosts map
   Product: Base System
   Version: 12.2-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: kreu...@progn.net

Created attachment 224112
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224112&action=edit
Extend automountd, autounmountd, and autofs to understand nested automounted
mount points.

(This is perhaps a duplicate of bug #195564, but I don't know whether the
project prefers reopening things vs. new reports.)

I'm interested in enhancing the automounter to be able to handle
nested/hierarchical keys in the -hosts map (mostly as a complement to zfs,
which makes it convenient to organize data sets in nested hierarchies), so I'm
attaching a working proof-of-concept implementation of the capability.

This picture shows the net result on a test machine that exports some zfs
shares rooted at /t to itself:

# mount | grep /net
map -hosts on /net (autofs)
localhost:/t/a on /net/localhost/t/a (nfs, nosuid, automounted)
map -hosts on /net/localhost/t/a/b (autofs, automounted)
localhost:/t/a/b on /net/localhost/t/a/b (nfs, nosuid, automounted)
map -hosts on /net/localhost/t/a/b/c (autofs, automounted)

That is, I've added the idea of "automounted autofs" mount points. Because
they're automounted, they are created dynamically by automountd and destroyed
by autounmountd. Because they're autofs mounts, they eventually cause something
else to get mounted.

The attachment is a tar file, here's a description of its contents:

report.txt -- this PR writeup.

notes.txt -- detailed description of the approach, limitations, future work

automountd.diff -- add the notion of automounted autofs mounts

autounmountd.diff -- teach autounmountd about unmount order dependencies.

autofs.diff -- have an automounted autofs pass getattr calls through.

These diffs apply against the releng-12.2 branch (it's what I was running when
I started), but should be pretty cleanly applicable to CURRENT or HEAD, since
not much has changed in the automounter.

Note that the diffs are named "logically"; in fact the first 2 diffs touch
multiple files in usr.sbin/autofs, and and must be applied in the order I've
mentioned them.

This set of changes is lightly tested, but does what I want it to so far under
repeated, but manual, testing. That said, the approach I've taken isn't the
only conceivable way to do things; it was just the shortest path I could think
of from what was there to the behavior I wanted to see.

Anyhow, there's work to do before this might be merge-worthy (e.g., I haven't
gotten to "automount -u" yet.) If there's an interest in incorporating this
approach, I'd be very happy to iterate on this effort, ideally with some
guidance/help from those who know this stuff.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255056] 13.0-RELEASE - Boot from ZFS after upgrade broken

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255056

--- Comment #1 from Christian Gutzler  ---
Meant 12.2-RELEASE of course

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255065] Accept filters do not timeout inactive

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255065

Bug ID: 255065
   Summary: Accept filters do not timeout inactive
   Product: Base System
   Version: 12.2-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: d...@jetcafe.org

The accept filter mechanism apparently has no methodology to timeout inactive
connections. This allows one to connect to an application using accept filter,
and simply hold the connection open indefinitely without sending data. 

Sockets that connect to an accept filter should timeout after some reasonable
period of inactivity.

This ancient bug is related: 

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

I do realize this behavior is (thankfully) limited by the setting of
kern.ipc.soacceptqueue, which defaults to 4096. I also realize that the 4097th
socket will cause the oldest socket to be dropped by the kernel. Even so, this
is still a potential waste of resource. 

Is it possible to allow an explicit timeout to be set, either by sysctl or by
API?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255065] Accept filters do not timeout inactive connections

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255065

d...@jetcafe.org changed:

   What|Removed |Added

Summary|Accept filters do not   |Accept filters do not
   |timeout inactive|timeout inactive
   ||connections

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255069] net.link.ether.ipfw=1 leads to kernel panic under 13.0-RELEASE amd64

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255069

Bug ID: 255069
   Summary: net.link.ether.ipfw=1 leads to kernel panic under
13.0-RELEASE amd64
   Product: Base System
   Version: 13.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: niels=free...@bakker.net

Created attachment 224119
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224119&action=edit
/var/crash/core.txt.5 scrubbed of private information like IPs, MACs

Upgrading from 12.2-RELEASE-p4 to 13.0-RELEASE made the kernel crash minutes
after boot if /etc/sysctl.conf contained the line "net.link.ether.ipfw=1". No
ipfw rule has a layer2 clause. Before the kernel panic there may be several
SIGSEGV's of other processes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

Bug ID: 255070
   Summary: Jumbo frames work poorly out of the box
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: kbowl...@freebsd.org

Jumbo frames work poorly on FreeBSD out of the box.  There are a variety of
opinions on this issue, but the status quo leaves users in the position to find
this out the hard way.

A definition of done for this issue:
Jumbo frames work better out of the box

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

Kevin Bowling  changed:

   What|Removed |Added

 CC||dgilb...@eicat.ca

--- Comment #1 from Kevin Bowling  ---
*** Bug 210901 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

Kevin Bowling  changed:

   What|Removed |Added

 Blocks||218894


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218894
[Bug 218894] Network dropouts on em(4) due to jumbo cluster failures
-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

Kevin Bowling  changed:

   What|Removed |Added

 Blocks||237720


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237720
[Bug 237720] [tcp] tcpip network stack seized for six hours after large
high-throughput file transfer
-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

Kevin Bowling  changed:

   What|Removed |Added

 Blocks|237720  |


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237720
[Bug 237720] [tcp] tcpip network stack seized for six hours after large
high-throughput file transfer
-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

Kevin Bowling  changed:

   What|Removed |Added

 Blocks||246003


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246003
[Bug 246003] em(4) Intel I219-V6 on NUC8i5BEH randomly loses carrier or fails
over to 100Mbit
-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

--- Comment #2 from Kevin Bowling  ---
See also https://reviews.freebsd.org/rS344817

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255070] Jumbo frames work poorly out of the box

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255070

--- Comment #3 from Kevin Bowling  ---
See also
https://lists.freebsd.org/pipermail/freebsd-net/2020-January/055164.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254723] [patch] systat -swap to display per-process swap space usage ordered by highest

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254723

--- Comment #3 from o...@j.email.ne.jp ---
(In reply to Andriy Gapon from comment #2)

We can consider adding to top as well if such demand is popular

When I'm interested in swap in/out activities, I'd like to see each of swap
device usages and also disk I/O activities.  systat -swap shows both and had
spaces in the middle.  It was more attractive place to add.  I have been adding
extra displays to systat over years and familiar than top.

I had to access all vm page usage via libprocstat to calculate swap usage for
each process. Top uses kinfo_proc.  We will need to query libprocstat for every
process and I wonder how much it weight it adds to top.  I think we can do that
only when -w is passed, though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254723] [patch] systat -swap to display per-process swap space usage ordered by highest

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254723

--- Comment #4 from o...@j.email.ne.jp ---
By the way, https://reviews.freebsd.org/D29337, systat: Handle SIGWINCH to
properly window resizing and adjust -swap disk stat based on new size., is a
separate review that goes very well with this new feature.

Before I dived into "systat -swap", I wondered if I could add swap usage to
"systat -pigs" and created https://reviews.freebsd.org/D29303 to reduce memory
re-allocations.
  -pigs also uses kinfo_proc like top and wasn't a good place to
add/experiment, though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 223127] find(1) does not explain what "-f" option does

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223127

Guangyuan Yang  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|y...@freebsd.org
 Status|New |Open
   Keywords||needs-qa, patch
 CC||y...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 255043] ena device is not getting enabled post addition in kernel

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255043

--- Comment #4 from shamsher  ---
Tried in AWS with same AMI image of same kernel with ENA integration but not
help, the C5 instance is not getting enabled as it seems ENA module didn't get
enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254645] Build and publish official OCI images for FreeBSD releases

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254645

--- Comment #5 from Samuel Karp  ---
(In reply to Mateusz Kwiatkowski from comment #0)
Hi Mateusz!

> I wanted to start discussion about providing official OCI images by FreeBSD 
> project and publishing them in one of public registries (eg. Docker HUB).

I think this is a great idea!  While runj (which you referenced) is a personal
project, my day job is very container-centric and I have a few suggestions
here.

Docker, Inc. sponsors an "Official Images" program that publishes images to
Docker Hub.  The program is managed on GitHub [1] and would enable a FreeBSD
developer to be in control of the images.  The advantage of going through the
"Official Images" program is the use of a short name that most of the container
ecosystem will recognize (for example, "docker pull debian" implicitly pulls
the "Official Image" of Debian located at docker.io/library/debian [2]; FreeBSD
could have the "freebsd" short name).

Docker Hub also supports "organizations" (similar to GitHub organizations); the
FreeBSD project could potentially get the "freebsd" organization, though it
appears to be already taken by an inactive account [3].

In my day job at Amazon I work alongside the Amazon ECR team, who maintains a
public registry [4].  Like Docker Hub, Amazon ECR Public allows for friendly
names associated with an AWS account and for verified publishers.  I use a
friendly alias with the image I published [5] and the FreeBSD project could
have the "freebsd" alias.

(In reply to Luca Pizzamiglio from comment #2)

> AFAIK, zfs is supported (it would be ideal)

Hi Luca! containerd has a zfs snapshotter [6] which works on Linux, but I have
not yet tried it on FreeBSD.

> one important information that FreeBSD OCI images should have is the 
> os.version, to enforce proper check on jails and host messages.

I'm still new to FreeBSD, so my apologies for asking a stupid question.  Is
there a requirement that a FreeBSD userland program is built to run on a
particular version of FreeBSD?  Do the kernel or syscall interfaces change
between versions?

The Windows container images use os.version to indicate compatibility as
Windows does require the container images to correspond with the underlying
host.

(In reply to Mateusz Kwiatkowski from comment #3)

> Yes, we can put whatever is needed for runtime to validate images. I created 
> minimal draft of runtime spec for FreeBSD for my needs

I believe Luca was referring to the image spec [7], which already includes
os.version in the index platform object.  I'm generating OCI images [8], but
not currently including os.version.

> FreeBSD specific subtree of schema

For the runtime config, agreed!  I'd be happy to collaborate on this with you.

Thanks!
Sam

[1] https://github.com/docker-library/official-images/
[2] https://hub.docker.com/_/debian
[3] https://hub.docker.com/u/freebsd
[4]
https://docs.aws.amazon.com/AmazonECR/latest/public/public-repositories.html
[5] https://gallery.ecr.aws/samuelkarp/freebsd
[6] https://github.com/containerd/zfs
[7] https://github.com/opencontainers/image-spec
[8] https://github.com/samuelkarp/runj/blob/main/demo/rootfs.go#L102-L152

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"