[Bug 241980] panic: I/O to pool appears to be hung on vdev

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241980 --- Comment #27 from Eugene Grosbein --- (In reply to Andriy Gapon from comment #25) I still think "core ZFS" logic of panicing system is wrong. It should just disconnect "non-responding" device from pool having redundancy instead. And con

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #26 from Michael --- I clarify the nature of the appearance of the fatal trap. When the SR-IOV is off, it boots normally. If you boot the VM with the SR-IOV is on the port "turned on" - a fatal trap. I attach a screenshot and a

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #27 from Michael --- Created attachment 209474 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209474&action=edit screenshot of fatal trap 12 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #28 from Michael --- Created attachment 209475 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209475&action=edit verbose output of boot process, and, fatal trap 12 -- You are receiving this mail because: You are the

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #29 from Michael --- (In reply to Konstantin Belousov from comment #24) And this patch did not help. Fatal trap - one to one, as without this patch. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #30 from Hans Petter Selasky --- Can you show the patch you tried as a diff in your source tree? It is very strange neither of the patches work. --HPS -- You are receiving this mail because: You are the assignee for the bug.

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #31 from Michael --- Only the patch from comment #24 was applied and the GENERIC kernel was compiled. No other changes were made to the source code. The kernel compiles with options: include GENERIC-NODEBUG ident

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #32 from Michael --- With a clean system (installed from scratch) and only with the GENERIC kernel git clone git://github.com/freebsd/freebsd.git --progress -v --single-branch -b master /usr/src make cleanworld && make cleandir

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #33 from Michael --- The same fatal trap was noticed when doing checkpoint the virtual machine. Not always - once out of fifty approximately. Checkpoint like this https://www.nakivo.com/blog/need-know-hyper-v-checkpoints/ -- Y

[Bug 242266] CLang 6.0.1 (Part of the System 12.0) can not Build CLang 8.0.1 from the Port Collection

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242266 Bug ID: 242266 Summary: CLang 6.0.1 (Part of the System 12.0) can not Build CLang 8.0.1 from the Port Collection Product: Base System Version: 12.0-RELEASE Hardware:

[Bug 163830] device smbios: missing documentation, no manpage

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163830 Gordon Bergling changed: What|Removed |Added CC||gbergl...@gmail.com --- Comment

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #34 from Hans Petter Selasky --- Hi, Can you try this patch and get those prints off the DMESG? Maybe some memory is not zero-initialized ... --HPS diff --git a/sys/kern/kern_linker.c b/sys/kern/kern_linker.c index 6dc218860

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #35 from Michael --- Created attachment 209482 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209482&action=edit verbose output of boot process with printf TD_PROC & P_FD -- You are receiving this mail because: You

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #36 from Konstantin Belousov --- (In reply to Michael from comment #35) Sigh, try this diff --git a/sys/kern/kern_linker.c b/sys/kern/kern_linker.c index 6dc21886066..ed6a8f793ea 100644 --- a/sys/kern/kern_linker.c +++ b/sys/ke

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #37 from Michael --- (In reply to Konstantin Belousov from comment #36) Yes! Its work! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@free

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #38 from Michael --- Firs, I turn on SR-IOV on port and made screenshot -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #39 from Michael --- Created attachment 209483 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209483&action=edit Turn ON SR-IOV on working VM -- You are receiving this mail because: You are the assignee for the bug.

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #40 from Michael --- Then, I recompiled the kernel with such changes -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing li

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #41 from Michael --- Created attachment 209485 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209485&action=edit make + patch -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #42 from Michael --- Created attachment 209486 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209486&action=edit verbose output with working patch -- You are receiving this mail because: You are the assignee for the

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #43 from Konstantin Belousov --- https://reviews.freebsd.org/D22571 should be the committable fix. Please retest with it. -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #44 from Michael --- Created attachment 209487 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209487&action=edit verbose output when 'chekpoint' have been made -- You are receiving this mail because: You are the ass

[Bug 242261] nvme0: aborting outstanding i/o

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242261 Alexandr Krivulya changed: What|Removed |Added CC||shur...@shurik.kiev.ua --- Com

[Bug 242270] Network stack leaks ifnet references when creating VLAN

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242270 Bug ID: 242270 Summary: Network stack leaks ifnet references when creating VLAN Product: Base System Version: CURRENT Hardware: Any OS: Any

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #45 from Michael --- (In reply to Konstantin Belousov from comment #43) Yes. https://reviews.freebsd.org/D22571 also work Made changes in file sys/kern/kern_linker.c and sys/kern/subr_firmware.c OS boot and work ok! -- You are

[Bug 242272] LinuxKPI combines all RCU and SRCU domains together, leading to deadlock

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242272 Bug ID: 242272 Summary: LinuxKPI combines all RCU and SRCU domains together, leading to deadlock Product: Base System Version: CURRENT Hardware: Any O

[Bug 242266] CLang 6.0.1 (Part of the System 12.0) can not Build CLang 8.0.1 from the Port Collection

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242266 Brooks Davis changed: What|Removed |Added CC||bro...@freebsd.org --- Comment #1 f

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #46 from Michael --- https://reviews.freebsd.org/D22571 and GENERIC kernel with options device xz device mlxfw device firmware device mlx4 device mlx4en device mlx5 device

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #47 from Michael --- Created attachment 209493 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209493&action=edit verbose boot log with 'patch' and precompiled mlx4 -- You are receiving this mail because: You are the

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #48 from Michael --- Created attachment 209494 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209494&action=edit verbose log 'chekpoint' maded -- You are receiving this mail because: You are the assignee for the bug

[Bug 242225] "fstyp -l" does not report exfat filesystem volume label

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225 --- Comment #11 from Conrad Meyer --- Created attachment 209495 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209495&action=edit Fixes the bug and adds matching test case Here's a patch that adds the missing functionality, as w

[Bug 242225] "fstyp -l" does not report exfat filesystem volume label

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225 Conrad Meyer changed: What|Removed |Added Attachment #209495|0 |1 is obsolete|

[Bug 242225] "fstyp -l" does not report exfat filesystem volume label

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225 Conrad Meyer changed: What|Removed |Added Version|11.3-RELEASE|CURRENT -- You are receiving this

[Bug 232350] periodic: pkg-checksum and pkg-backup interfere with 'overnight' port builds

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232350 --- Comment #26 from Tatsuki Makino --- Should we adjust LOCK_RETRIES and LOCK_WAIT in /usr/local/etc/pkg.conf? LOCK_WAIT = 10 LOCK_RETRIES = 50 -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 242132] fix wrong GSS credentials cache expiration date for indefinite tickets

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242132 Rick Macklem changed: What|Removed |Added Assignee|b...@freebsd.org|rmack...@freebsd.org

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en

2019-11-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #49 from Michael --- If someone could help fix the following bugs https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238095 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 we get a wonderful super-router for cloud infras