https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
--- Comment #16
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #15 from Bryan Drewery ---
https://people.freebsd.org/~pho/stress/log/log0110.txt may be the same thing
from misc/cmp.sh stress2 test.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #14 from Bryan Drewery ---
Actually all of that build stuff is a child of the parent tmux process. The
current tmux process is a child that I believe is execing some powerline/status
update handling.
I'm just thinking out what
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #13 from Bryan Drewery ---
Well init -> tmux(panic) -> zsh -> lockf -> time -> screen -> screen -> sh
(/root/build) -> [ttyin]
The open file for sh is also open in vim.
This script runs Poudriere. I suspect it is at the end of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #12 from Bryan Drewery ---
tmux (child) again. tmux -> zsh -> screen -> poudriere.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #11 from Bryan Drewery ---
Just hit it again on a recent kernel from main April 22nd.
panic: vm_page_free_prep: freeing mapped page 0xfe0020bccfe8
cpuid = 4
time = 1651629479
KDB: stack backtrace:
db_trace_self_wrapper() at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #10 from Bryan Drewery ---
The build on this system corresponds to
https://cgit.freebsd.org/src/commit/?id=c7cf100aafb4cb881e05a5153de152907f6c07f3
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #9 from Mark Johnston ---
procvm entry:
map entry 0xf80ae7805360: start=0x811be5000, end=0x8120ce000,
eflags=0x4,
prot=3/7/copy, object=0xf805d279b630, offset=0x0, obj ruid 0 charge
4e9000, copy (done)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #8 from Mark Johnston ---
(In reply to Bryan Drewery from comment #7)
Thanks. So it appears that the referencing pmap belongs to the parent process,
another tmux process:
db> show proc 1634
Process 1634 (tmux) at 0xf809dd3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #7 from Bryan Drewery ---
(In reply to Mark Johnston from comment #5)
https://people.freebsd.org/~bdrewery/allproc.txt
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #6 from Bryan Drewery ---
(In reply to Mark Johnston from comment #5)
Great. I have a script running capturing all of that now.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #5 from Mark Johnston ---
(In reply to Bryan Drewery from comment #4)
If we can run "show proc " for each pid shown in "show all procs" output,
then that'd be good enough.
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
--- Comment #4 from Bryan Drewery ---
(In reply to Mark Johnston from comment #3)
> But it's hard to tell from ddb which process owns that pmap. I think a
> kernel dump is needed to diagnose further, though then we will lose the user
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258932
Bryan Drewery changed:
What|Removed |Added
Summary|panic: vm_page_free_prep: |panic: vm_page_free_prep:
14 matches
Mail list logo
