[Bug 242954] EBR management continues to remain dysfunctional under FreeBSD

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242954 Bug ID: 242954 Summary: EBR management continues to remain dysfunctional under FreeBSD Product: Base System Version: 12.1-RELEASE Hardware: Any OS: An

[Bug 242955] kld loading broken inside chroot

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242955 Bug ID: 242955 Summary: kld loading broken inside chroot Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects O

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 Bug ID: 242961 Summary: Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series Product: Base System Version: CURRENT

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #1 from Mark Johnston --- This doesn't look directly related to my changes. Can you print *m from frame 10 and fs from frame 11? -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #2 from Greg V --- (In reply to Mark Johnston from comment #1) (kgdb) frame 10 #10 0x806d461f in vm_fault_dirty (entry=0xf8003205e000, m=0xfe0008806d60, prot=, fault_type=, fault_flags=0) at /usr/src/sys/vm

[Bug 237357] Not resuming from suspend with IOMMU DMAR enabled

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237357 --- Comment #3 from Greg V --- ( WIP code at https://reviews.freebsd.org/D22642 ) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing l

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #3 from Greg V --- Debug kernel (also not reverting PMAP_ENTER_NOREPLACE anymore, it's for i386 anyway), different panic: panic: Bad link elm 0xfe0009572b20 next->prev != elm #4 0x80423673 in panic (fmt=) at /usr/

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #4 from Mark Johnston --- Are you able to trigger this with r356173 applied? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org ma

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #5 from Greg V --- (In reply to Mark Johnston from comment #4) Yes. Different once again. On nondebug kernel, back to coredump, but different stuff inside: <6>pid 47948 (wayfire), jid 0, uid 1001: exited on signal 10 (core dum

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #6 from Mark Johnston --- (In reply to Greg V from comment #5) This is strange, my changes really shouldn't be affecting the page lifecycle. The only thing to try at this step is an INVARIANTS kernel. The panic in comment 3 co

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #7 from Greg V --- (In reply to Mark Johnston from comment #6) INVARIANTS doesn't catch this, when I said debug kernel, invariants were enabled. This is from debug kernel also: #0 __curthread () at /usr/src/sys/amd64/include/

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #8 from Mark Johnston --- I found a bug by causing some of my desktop applications to dump core. I suspect this is what you are hitting. TTM uses the plinks.q fields for its own purpose, but we were inadvertently putting TTM-m

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #9 from Greg V --- (In reply to Mark Johnston from comment #8) Now panicked inside ttm_pool_populate (that's progress I guess!) Fatal trap 12: page fault while in kernel mode

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #10 from Greg V --- And now for something different… ZFS! (also still inside coredump) panic: vm_radix_insert: key fe321 is already present #4 0x80425fa3 in panic (fmt=) at /usr/src/sys/ker

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #11 from Mark Johnston --- (In reply to Greg V from comment #10) I presume these are all with INVARIANTS enabled? Can you try this patch instead of the last one? diff --git a/sys/vm/vm_page.c b/sys/vm/vm_page.c index e99732028

[Bug 242891] mlx5_core0 ERR

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242891 --- Comment #4 from Michael --- (In reply to Konstantin Belousov from comment #3) Yes, FreeBSD is truly virtualized in Hyper-V. Without this, I would go broke on servers and electricity. Well, maybe the specifics of the vendor are not scary

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 --- Comment #12 from Greg V --- (In reply to Mark Johnston from comment #11) Not all of them, no.. And the one with vm_page_wired seems to help, everything works so far! Thanks for the very fast response :) -- You are receiving this ma

[Bug 242967] [patch] powerd free freqstr if sysctl fails

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242967 Bug ID: 242967 Summary: [patch] powerd free freqstr if sysctl fails Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Sev

[Bug 242961] Crashes (elf64_coredump … vm_object_set_writeable_dirty) after the recent vm patch series

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242961 Mark Johnston changed: What|Removed |Added Status|New |In Progress Assignee|b..

[Bug 242891] mlx5_core0 ERR

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242891 --- Comment #5 from Michael --- By the way, there are no errors in virtualized Windows systems. Later I will look at virtualized Linux for such errors. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 242967] [patch] powerd free freqstr if sysctl fails

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242967 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: markj Date: Sun Dec 29 20:57:49 UTC 2019 New revision: 356184 URL: https://svnweb.freebsd.org/changeset/base/356184 Log: powerd(8): Fix a memory leak w

Problem reports for b...@freebsd.org that need special attention

2019-12-29 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 242971] Casper-related files are installed even if WITHOUT_CASPER=true ; some of them are not removed by "make delete-old"

2019-12-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242971 Bug ID: 242971 Summary: Casper-related files are installed even if WITHOUT_CASPER=true ; some of them are not removed by "make delete-old" Product: Base System