[Bug 237067] ZFS: Crash in vdev_dtl_reassess when using GELI with autodetach

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237067 --- Comment #1 from v...@endrift.com --- Created attachment 203438 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203438=edit Core dump log Found a core.txt from the live system where I first ran into this. Also tried

[Bug 237067] ZFS: Crash in vdev_dtl_reassess when using GELI with autodetach

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237067 Kubilay Kocak changed: What|Removed |Added Summary|[PANIC] [ZFS] [GELI] Crash |ZFS: Crash in

[Bug 237063] After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063 --- Comment #6 from Mark Millard --- (In reply to Mark Millard from comment #5) While I do not have access to the system currently, looking around it appears that acpidump output for the MADT may provide a way to reasonably report a bios

[Bug 237067] [PANIC] [ZFS] [GELI] Crash in vdev_dtl_reassess when using GELI with autodetach

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237067 Bug ID: 237067 Summary: [PANIC] [ZFS] [GELI] Crash in vdev_dtl_reassess when using GELI with autodetach Product: Base System Version: 12.0-RELEASE Hardware: Any

[Bug 142802] [ata] [panic] on removing drive: recursed on non-recursive mutex ATA state lock

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=142802 Andriy Voskoboinyk changed: What|Removed |Added Status|Open|Closed

[Bug 234793] Failed unknown for $USER in sshd logs even if I got authenticated

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793 --- Comment #15 from Jamie Baxter --- (In reply to Jamie Baxter from comment #14) Or instead of touching the sshguard.conf file, you can just set the rc.conf variable sshguard_danger_thresh to something greater than 30. -- You are

[Bug 234793] Failed unknown for $USER in sshd logs even if I got authenticated

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793 Jamie Baxter changed: What|Removed |Added CC||jamie.bax...@tutanota.com ---

[Bug 237064] Fix a memory leak in pw when invoked with -V or -R

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237064 Bug ID: 237064 Summary: Fix a memory leak in pw when invoked with -V or -R Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New

[Bug 236922] Virtio fails as QEMU-KVM guest with Q35 chipset on Ubuntu 18.04.2 LTS

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922 --- Comment #12 from Tommy P --- (In reply to Bryan Venteicher from comment #11) Hi Brian, I've just built the kernel using the entire src tree from Git. The buildkernel was successful. Upon reboot, I think the Virtio PCI are detected

[Bug 237063] After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063 --- Comment #5 from Mark Millard --- (In reply to Mark Millard from comment #4) Looking with ps I do see 31 for the likes of: [kernel/softirq_31] [kernel/if_io_tqg_31] [kernel/crypto_31] (I also see 0-30 for them.) With cpu31 missing

[Bug 237063] After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063 --- Comment #4 from Mark Millard --- (In reply to Conrad Meyer from comment #2) For reference, from dmesg -a: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 1 package(s) x 2 groups x 2 cache groups x 4 core(s) x 2

[Bug 237063] After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063 --- Comment #3 from Conrad Meyer --- (I have this exact CPU and my devinfo topology is the same, except I am not missing cpu31...) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 237063] After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063 --- Comment #1 from Mark Millard --- Created attachment 203431 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203431=edit pciconf -lvcb outout for 1950X context -- You are receiving this mail because: You are the assignee for

[Bug 237063] After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063 Bug ID: 237063 Summary: After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context Product: Base System Version: CURRENT Hardware: amd64

[Bug 237062] boot1.elf cannot find loader on ufs partition, failing to boot on powerpc SLOF

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237062 Bug ID: 237062 Summary: boot1.elf cannot find loader on ufs partition, failing to boot on powerpc SLOF Product: Base System Version: 12.0-RELEASE Hardware: powerpc

[Bug 225624] can't load 'kernel' after enabled soft update journaling

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225624 Pokemon changed: What|Removed |Added CC||ssvv17...@gmail.com --- Comment #1 from