[Bug 236710] zfs: clone + resize = dataset is busy

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236710 Bug ID: 236710 Summary: zfs: clone + resize = dataset is busy Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affe

[Bug 236710] zfs: clone + resize = dataset is busy

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236710 --- Comment #1 from Andriy Gapon --- This could be a ZFS<->GEOM interaction indeed. Maybe related to bug 228384, maybe not. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 236475] [ZFS] Invalid VOP_FSYNC options in vdev_file_io_start

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236475 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Fri Mar 22 09:11:46 UTC 2019 New revision: 345410 URL: https://svnweb.freebsd.org/changeset/base/345410 Log: ZFS vdev_file: use correct value

[Bug 236714] Clang problem with rctl(8)

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236714 Bug ID: 236714 Summary: Clang problem with rctl(8) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me

[Bug 236559] Error in the pwd man page

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236559 --- Comment #2 from verma...@interia.pl --- (In reply to Mark Johnston from comment #1) So shell builtin (ZSH) behaves correctly with POSIX standards. IMHO FreeBSD should also be correct with POSIX standards so option -L should be assumed i

[Bug 236714] Clang problem with rctl(8)

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236714 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|toolch...@freebsd.org -- You are r

[Bug 236710] zfs: clone + resize = dataset is busy

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236710 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org -- You are receiv

[Bug 236559] Error in the pwd man page

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236559 --- Comment #3 from Mark Johnston --- (In reply to vermaden from comment #2) It's mostly a question of whether changing the default will break existing scripts. sh, bash and zsh use a builtin implementation for pwd, but tcsh in the base s

[Bug 236475] [ZFS] Invalid VOP_FSYNC options in vdev_file_io_start

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236475 Andriy Gapon changed: What|Removed |Added Assignee|b...@freebsd.org|a...@freebsd.org Status

[Bug 236718] system panics with message: vm_fault_hold: fault on nofault entry, addr: 0

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236718 Bug ID: 236718 Summary: system panics with message: vm_fault_hold: fault on nofault entry, addr: 0 Product: Base System Version: 12.0-STABLE Hardware: Any

[Bug 236718] system panics with message: vm_fault_hold: fault on nofault entry, addr: 0

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236718 lenzi.ser...@gmail.com changed: What|Removed |Added Hardware|Any |i386 -- You are receiving

[Bug 236718] system panics with message: vm_fault_hold: fault on nofault entry, addr: 0

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236718 Mark Linimon changed: What|Removed |Added Keywords||panic -- You are receiving this ma

[Bug 235944] jedec_dimm(4) does not attach to KFA2 (aka Galax) Hall of Fame DDR4 sticks

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944 --- Comment #29 from Ravi Pokala --- > Thanks Greg! I'll massage it as needed and commit it for you sometime in the > next few days. For some very large definitions of "few"... :-/ I've finally circled back around to this, and have a pat

[Bug 236513] Different power states (C1/C2/...) per CPU core

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513 --- Comment #5 from stockhau...@collogia.de --- Finally I got time to retest everything with 12.0-RELEASE. Situation is the same. Only the first CPU can go to C2 state. All other cores only show up with cx_lowest = C1. Only difference this

[Bug 236513] Different power states (C1/C2/...) per CPU core

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513 --- Comment #6 from stockhau...@collogia.de --- Created attachment 203049 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203049&action=edit Screenshot dmesg -- You are receiving this mail because: You are the assignee for the bu

[Bug 236513] Different power states (C1/C2/...) per CPU core

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513 --- Comment #7 from stockhau...@collogia.de --- Just fired up a Fedora 29 on the HP T730. Running a cpu intensive task and looking at the powertop output I would say that C2 states are core independent. Conclusion: Linux kernel detects C

[Bug 236513] Different power states (C1/C2/...) per CPU core

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513 --- Comment #8 from stockhau...@collogia.de --- Created attachment 203050 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203050&action=edit Fedora powertop -- You are receiving this mail because: You are the assignee for the bug

[Bug 236513] Different power states (C1/C2/...) per CPU core

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513 --- Comment #9 from stockhau...@collogia.de --- Bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189267 shows other occurences of CPUs where c states for the first core is C1+C2 while all other cores are C1 only. -- You are receiving

[Bug 236724] igbX interfaces fail to switch active to inactive state

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724 Bug ID: 236724 Summary: igbX interfaces fail to switch active to inactive state Product: Base System Version: 12.0-STABLE Hardware: amd64 OS: Any

[Bug 236724] igbX interfaces fail to switch active to inactive state

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724 Mark Linimon changed: What|Removed |Added Keywords||IntelNetworking, regression

[Bug 199934] [FUSEFS] kernel module fails with filesystems without .create support

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199934 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: asomers Date: Sat Mar 23 00:22:30 UTC 2019 New revision: 345429 URL: https://svnweb.freebsd.org/changeset/base/345429 Log: fusefs: fallback to MKNOD/OP

[Bug 199934] [FUSEFS] kernel module fails with filesystems without .create support

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199934 Alan Somers changed: What|Removed |Added Status|New |In Progress --- Comment #5 from Alan

[Bug 236718] system panics with message: vm_fault_hold: fault on nofault entry, addr: 0

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236718 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable11?, |

[Bug 236718] system panics with message: vm_fault_hold: fault on nofault entry, addr: 0

2019-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236718 --- Comment #1 from Kubilay Kocak --- Created attachment 203059 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203059&action=edit backtrace -- You are receiving this mail because: You are the assignee for the bug. _