[Bug 239849] INTEL X710, WINDOWS SERVER 2019 HYPER-V, FreeBSD Current, iavf

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239849

Bug ID: 239849
   Summary: INTEL X710, WINDOWS SERVER 2019 HYPER-V, FreeBSD
Current, iavf
   Product: Base System
   Version: CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: michael@gmail.com

I am trying to use the SR-IOV ability in a virtual machine. But that
does not work. The host has the latest Intel drivers for the x710
network adapter. Second Generation Virtual Machine with GERERIC
Recompiled FreeBSD-Current Core for today. Host is Windows Server 2019
with Intel drivers (i40ea68.sys 1.10.128.0).

hn0 without SR-IOV function
hn1 with SR-IOV

Log messages from virtual machine:

Aug 14 10:56:18 r03 kernel: ---<>---
Aug 14 10:56:18 r03 kernel: Copyright (c) 1992-2019 The FreeBSD Project.
Aug 14 10:56:18 r03 kernel: Copyright (c) 1979, 1980, 1983, 1986,
1988, 1989, 1991, 1992, 1993, 1994
Aug 14 10:56:18 r03 kernel: The Regents of the University of
California. All rights reserved.
Aug 14 10:56:18 r03 kernel: FreeBSD is a registered trademark of The
FreeBSD Foundation.
Aug 14 10:56:18 r03 kernel: FreeBSD 13.0-CURRENT
a2166b0cec5-c261904(master) R03 amd64
Aug 14 10:56:18 r03 kernel: FreeBSD clang version 8.0.1
(tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
Aug 14 10:56:18 r03 kernel: SRAT: Ignoring memory at addr 0x1fc00
...
Aug 14 10:56:18 r03 kernel: SRAT: Ignoring memory at addr 0xc00
Aug 14 10:56:18 r03 kernel: VT(efifb): resolution 1024x768
Aug 14 10:56:18 r03 kernel: Hyper-V Version: 10.0.17763 [SP0]
Aug 14 10:56:18 r03 kernel:
Features=0x2e7f
Aug 14 10:56:18 r03 kernel:   PM Features=0x0 [C2]
Aug 14 10:56:18 r03 kernel:
Features3=0xbed7b2
Aug 14 10:56:18 r03 kernel: Timecounter "Hyper-V" frequency 1000
Hz quality 2000
Aug 14 10:56:18 r03 kernel: module iavf already present!
Aug 14 10:56:18 r03 kernel: CPU: Intel(R) Xeon(R) CPU E5-2623 v3 @
3.00GHz (2996.53-MHz K8-class CPU)
Aug 14 10:56:18 r03 kernel:   Origin="GenuineIntel"  Id=0x306f2
Family=0x6  Model=0x3f  Stepping=2
...
Aug 14 10:56:18 r03 kernel: vmbus0:  on acpi_syscontainer0
Aug 14 10:56:18 r03 kernel: vmbus_res0:  irq 5 on acpi0
...
Aug 14 10:56:18 r03 kernel: vmbus0: version 4.0
Aug 14 10:56:18 r03 kernel: hvet0:  on vmbus0
Aug 14 10:56:18 r03 kernel: Event timer "Hyper-V" frequency 1000
Hz quality 1000
Aug 14 10:56:18 r03 kernel: hvkbd0:  on vmbus0
Aug 14 10:56:18 r03 kernel: hvheartbeat0:  on vmbus0
Aug 14 10:56:18 r03 kernel: hvkvp0:  on vmbus0
Aug 14 10:56:18 r03 kernel: hvshutdown0:  on vmbus0
Aug 14 10:56:18 r03 kernel: hvtimesync0:  on vmbus0
Aug 14 10:56:18 r03 kernel: hvtimesync0: RTT
Aug 14 10:56:18 r03 kernel: hvvss0:  on vmbus0
Aug 14 10:56:18 r03 kernel: storvsc0:  on vmbus0
Aug 14 10:56:18 r03 kernel: hn0:  on vmbus0
Aug 14 10:56:18 r03 kernel: hn0: Ethernet address: 00:15:5d:00:88:29
Aug 14 10:56:18 r03 kernel: hn0: link state changed to UP
Aug 14 10:56:18 r03 kernel: hn1:  on vmbus0
Aug 14 10:56:18 r03 kernel: hn1: got notify, nvs type 128
Aug 14 10:56:18 r03 kernel: hn1: Ethernet address: 00:15:5d:00:88:2a
Aug 14 10:56:18 r03 kernel: hn1: link state changed to UP
Aug 14 10:56:18 r03 kernel: pcib0:  on vmbus0
Aug 14 10:56:18 r03 kernel: pci0:  on pcib0
Aug 14 10:56:18 r03 kernel: pci0:  at device 2.0
(no driver attached)
Aug 14 10:56:18 r03 kernel: lo0: link state changed to UP
...

root@r03:/# pciconf -lvb
none0@pci2:0:2:0:   class=0x02 card=0x00018086 chip=0x15718086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Virtual Function 700 Series'
class  = network
subclass   = ethernet
bar   [10] = type Prefetchable Memory, range 64, base 0, size 65536,
disabled
bar   [1c] = type Prefetchable Memory, range 64, base 0, size 16384,
disabled

-- 
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 239849] INTEL X710, WINDOWS SERVER 2019 HYPER-V, FreeBSD Current, iavf

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239849

Andrey V. Elsukov  changed:

   What|Removed |Added

 CC||a...@freebsd.org

--- Comment #1 from Andrey V. Elsukov  ---
It looks like iavf_vendor_info_array[] lacks I40E_DEV_ID_VF_HV id, thus the
iavf driver doesn't hook it.
You can try add corresponding line into sys/dev/ixl/if_iavf.c and recompile
your kernel and modules.

--- if_iavf.c   (revision 350972)
+++ if_iavf.c   (working copy)
@@ -57,6 +57,7 @@
 static pci_vendor_info_t iavf_vendor_info_array[] =
 {
PVID(I40E_INTEL_VENDOR_ID, I40E_DEV_ID_VF, "Intel(R) Ethernet Virtual
Function 700 Series"),
+   PVID(I40E_INTEL_VENDOR_ID, I40E_DEV_ID_VF_HV, "Intel(R) Ethernet
Virtual Function 700 Series"),
PVID(I40E_INTEL_VENDOR_ID, I40E_DEV_ID_X722_VF, "Intel(R) Ethernet
Virtual Function 700 Series (X722)"),
PVID(I40E_INTEL_VENDOR_ID, I40E_DEV_ID_ADAPTIVE_VF, "Intel(R) Ethernet
Adaptive Virtual Function"),
/* required last entry */

-- 
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 239849] INTEL X710, WINDOWS SERVER 2019 HYPER-V, FreeBSD Current, iavf

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239849

Andrey V. Elsukov  changed:

   What|Removed |Added

   Keywords||IntelNetworking

-- 
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 237077] possible race in build: /usr/src/sys/amd64/linux/linux_support.s:38:2: error: expected relocatable expression

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237077

Li-Wen Hsu  changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|emulat...@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 224496] mpr and mps drivers seems to have issues with large seagate drives

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496

--- Comment #17 from Matthias Pfaller  ---
(In reply to Francois Baillargeon from comment #14)
We have cache and log devices:
NAME SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUP
 HEALTH  ALTROOT
k-zb1   87.2T  35.5T  51.8T- -20%40%  1.91x
 ONLINE  -
  raidz287.2T  35.5T  51.8T- -20%40%
gpt/k-zb1-0 -  -  -- -  -  -
gpt/k-zb1-1 -  -  -- -  -  -
gpt/k-zb1-2 -  -  -- -  -  -
gpt/k-zb1-3 -  -  -- -  -  -
gpt/k-zb1-4 -  -  -- -  -  -
gpt/k-zb1-5 -  -  -- -  -  -
gpt/k-zb1-6 -  -  -- -  -  -
gpt/k-zb1-7 -  -  -- -  -  -
log -  -  - -  -  -
  mirror11.5G  0  11.5G- - 0% 0%
gpt/k-zb1-zil0  -  -  -- -  -  -
gpt/k-zb1-zil1  -  -  -- -  -  -
cache   -  -  - -  -  -
  gpt/k-zb1-cache0  80.0G  29.9G  50.1G- - 0%37%
  gpt/k-zb1-cache1  80.0G  30.0G  50.0G- - 0%37%

The only solution for us was to use the onboard sata ports instead of the
LSI-controller. We have keep the other machines that need the LSI-controllers
(not enough ports on the mainboard) at 11.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 233362] Building riscv with BSD_CRTBEGIN fails

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233362

Ed Maste  changed:

   What|Removed |Added

 Blocks||228919


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228919
[Bug 228919] GCC 4.2.1 removal
-- 
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 233361] mips build with BSD_CRTBEGIN, Clang, LLD fails

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233361

Ed Maste  changed:

   What|Removed |Added

 Blocks||228919


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228919
[Bug 228919] GCC 4.2.1 removal
-- 
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 239851] BSD_CRTBEGIN does not work on sparc64

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239851

Bug ID: 239851
   Summary: BSD_CRTBEGIN does not work on sparc64
   Product: Base System
   Version: CURRENT
  Hardware: sparc64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ema...@freebsd.org
Blocks: 228919

Disabled in Makefile.inc1 with a comment "PowerPC and Sparc64 need extra crt*.o
files"


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228919
[Bug 228919] GCC 4.2.1 removal
-- 
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 239851] BSD_CRTBEGIN does not work on sparc64

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239851

Warner Losh  changed:

   What|Removed |Added

 CC||i...@freebsd.org

--- Comment #1 from Warner Losh  ---
PowerPC has now been fixed :)

-- 
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 233405] sparc64: DWARF unwinder required for GCC 4.2.1 retirement

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405

--- Comment #2 from Ed Maste  ---
Attempting to enable LLVM libunwind on sparc64 resulted in:

In file included from
/scratch/tmp/emaste/freebsd/contrib/libunwind/src/libunwind.cpp:29:
/scratch/tmp/emaste/freebsd/contrib/libunwind/src/UnwindCursor.hpp:1155:3:
error: static_assert failed due to requirement
'check_fit, unw_cursor_t>::does_fit' "UnwindCursor<> does not
fit in unw_cursor_t"
  static_assert((check_fit, unw_cursor_t>::does_fit),
  ^  ~
/scratch/tmp/emaste/freebsd/contrib/libunwind/src/libunwind.cpp:78:24: note: in
instantiation of member function
'libunwind::UnwindCursor::UnwindCursor' requested here
  new ((void *)cursor) UnwindCursor(
   ^

-- 
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 239822] deadlock since FreeBSD 12.0 p9

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822

Martin Birgmeier  changed:

   What|Removed |Added

Summary|deadlock|deadlock since FreeBSD 12.0
   ||p9

-- 
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 239822] deadlock since FreeBSD 12.0 p9

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822

--- Comment #2 from Martin Birgmeier  ---
I just had another of these deadlocks:
- Running firefox
- Opening a context menu
- Firefox does not respond anymore
- Klicked on upper right corner to close it
- KDE says that window does not close, do I want to forcibly close it
- "yes"
- result: complete system deadlocked

-- 
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 239822] deadlock since FreeBSD 12.0 p9

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #3 from Mark Johnston  ---
(In reply to Martin Birgmeier from comment #2)
Are you able to capture the output of "procstat -kka" once an application
changes?

-- 
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 239822] deadlock since FreeBSD 12.0 p9

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822

--- Comment #4 from Mark Johnston  ---
s/changes/hangs/

-- 
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 239822] deadlock since FreeBSD 12.0 p9

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822

--- Comment #5 from Martin Birgmeier  ---
I'll try it next time.

Currently I am recompiling all those ports with kernel modules.

-- Martin

-- 
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 233362] Building riscv with BSD_CRTBEGIN fails

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233362

--- Comment #3 from Ed Maste  ---
This was probably a temporary local problem, checking what config I had...

-- 
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 224496] mpr and mps drivers seems to have issues with large seagate drives

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496

--- Comment #18 from Paul Thornton  ---
(In reply to Bane Ivosev from comment #16)

Thanks for the confirmation.  I'm in the process of downgrading the affected
NAS machine (they are an identical pair) from 12.0 to 11.1, I need to test this
in the lab first but will report back once we have the production machine on
the older release.

I need to do this before it next crashes and reboots, 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 233362] Building riscv with BSD_CRTBEGIN fails

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233362

--- Comment #2 from Andrew Turner  ---
Is this still an issue? BSD_CRTBEGIN should be enabled on riscv and I haven't
heard any other complaints it fails to build.

-- 
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 239566] panic: solaris assert: avl_find(>scn_queue, sds, ) .... dsl_scan.c line 1029

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239566

--- Comment #1 from Andriy Gapon  ---
Some debugging information for the crash:
Unread portion of the kernel message buffer:
panic: solaris assert: avl_find(>scn_queue, sds, ) == ((void *)0)
(0xf80f108a1ac0 == 0x0), file:
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_scan.c, line: 1029
cpuid = 6
time = 1565487588
KDB: stack backtrace:
#0 0x80be7967 at kdb_backtrace+0x67
#1 0x80b9b543 at vpanic+0x1a3
#2 0x80b9b393 at panic+0x43
#3 0x829fe22c at assfail3+0x2c
#4 0x826cafbb at dsl_scan_ds_clone_swapped+0x1db
#5 0x826ba4e5 at dsl_dataset_clone_swap_sync_impl+0x8c5
#6 0x826a0de0 at dmu_recv_end_sync+0x310
#7 0x826c369e at dsl_sync_task_sync+0xae
#8 0x826c204b at dsl_pool_sync+0x3cb
#9 0x826eb635 at spa_sync+0xab5
#10 0x826f8f98 at txg_sync_thread+0x208
#11 0x80b5bf13 at fork_exit+0x83
#12 0x810506ae at fork_trampoline+0xe
Uptime: 14h3m53s
netdump: overwriting mbuf zone pointers
netdump in progress. searching for server...
netdumping to 10.10.5.2 (ac:1f:6b:48:3a:ac)
Dumping 21259 out of 196556
MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

__curthread () at ./machine/pcpu.h:234
234 struct thread *td;
(kgdb) bt
#0  __curthread () at ./machine/pcpu.h:234
#1  doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:366
#2  0x80b9b12b in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:446
#3  0x80b9b5a3 in vpanic (fmt=, ap=0xfe0171b705c0)
at /usr/src/sys/kern/kern_shutdown.c:872
#4  0x80b9b393 in panic (fmt=) at
/usr/src/sys/kern/kern_shutdown.c:799
#5  0x829fe22c in assfail3 (a=, lv=,
op=, rv=, f=, l=) at
/usr/src/sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c:91
#6  0x826cafbb in scan_ds_queue_insert (scn=,
dsobj=85951, txg=1) at
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_scan.c:1029
#7  dsl_scan_ds_clone_swapped (ds1=, ds2=,
tx=0xf8013b108b00) at
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_scan.c:2036
#8  0x826ba4e5 in dsl_dataset_clone_swap_sync_impl
(clone=0xf8186d34f800, origin_head=0xf80bf0b90800, tx=)
at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_dataset.c:3663
#9  0x826a0de0 in dmu_recv_end_sync (arg=0xfe0171b93510,
tx=0xf8013b108b00) at
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_send.c:3302
#10 0x826c369e in dsl_sync_task_sync (dst=0xfe0171b932e8,
tx=0xf8013b108b00) at
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_synctask.c:234
#11 0x826c204b in dsl_pool_sync (dp=, txg=) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_pool.c:819
#12 0x826eb635 in spa_sync (spa=, txg=)
at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c:8088
#13 0x826f8f98 in txg_sync_thread (arg=0xf80106632800) at
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/txg.c:543
#14 0x80b5bf13 in fork_exit (callout=0x826f8d90
, arg=0xf80106632800, frame=0xfe0171b70c00) at
/usr/src/sys/kern/kern_fork.c:1057
#15 
(kgdb) fr 8
#8  0x826ba4e5 in dsl_dataset_clone_swap_sync_impl
(clone=0xf8186d34f800, origin_head=0xf80bf0b90800, tx=)
at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_dataset.c:3663
(kgdb) p clone->ds_object
$1 = 85951
(kgdb) p origin_head->ds_object
$2 = 85918

-- 
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 239566] panic: solaris assert: avl_find(>scn_queue, sds, ) .... dsl_scan.c line 1029

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239566

Andriy Gapon  changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|f...@freebsd.org

--- Comment #2 from Andriy Gapon  ---
The root cause is that both 85951 and 85918 were already in scn_queue and the
code in dsl_scan_ds_clone_swapped fails to properly handle that case.
It has other logic problems as well.

-- 
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 239620] 12-STABLE: boot failure due to bootloader issue on PCengine APU2C4 ( > r349288)

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239620

--- Comment #1 from O. Hartmann  ---
I found the cause of this problem.

When compiling world with the option

WITH_BEARSSL

the result is a broken loader unwilling to boot a legacy MBR system on this
specific piece of hardware. I have enabled this option also on an older
Core2duo based Fujitsu server, booting off from an mfi0 handled volume (MBR,
this type of hardware is BIOS driven and can not handle secure boot or any
fancy UEFI stuff) without problems.

Disabling the option mentioned above (with all the consequences as described in
src.conf) results in a working loader as expected.

-- 
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 233405] sparc64: DWARF unwinder required for GCC 4.2.1 retirement

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405

--- Comment #3 from Conrad Meyer  ---
Would an acceptable unwind implementation on Sparc be "raise(SIGKILL);"?

-- 
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 233405] sparc64: DWARF unwinder required for GCC 4.2.1 retirement

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405

--- Comment #4 from Ed Maste  ---
(In reply to Conrad Meyer from comment #3)
Sure, if those who have an interest in FreeBSD/sparc64 want to make that change
and are happy enough with the result.

-- 
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"