https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
--- Comment #24
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #23 from Josh Gitlin ---
We experienced the kmem_back issues as well, and we're running a Skylake:
Intel® Xeon® Bronze 3106 Processor
We haven't seen the issue since reducing ARC size, but the same config had been
stable for ye
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #22 from rai...@ultra-secure.de ---
It's a HP Gen10, using Xeon Scalable Processors.
So, yes, it's Skylake (Xeon variant).
x86info v1.31pre
/dev/cpuctl0: No such file or directory
Found 16 identical CPUs
Extended Family: 0 Exten
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #21 from Mark Johnston ---
(In reply to Mark Johnston from comment #20)
I believe the kevent bug was fixed in r340734.
I think I know what's causing the kmem_back() panic as well. Is the system
using a Skylake CPU? Please try
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #20 from Mark Johnston ---
Hmm, this seems to be unrelated to ZFS - it's a panic in kevent(). Would you
be willing to share the vmcore with me so that I can try and find the bug?
Please mail me if so.
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #19 from rai...@ultra-secure.de ---
It had only booted a couple of minutes at that point.
I had rm -rf'ed /var/db/freebsd-update/*
in order to update the debug-symbols to the current kernel-level.
And bang, it panic'ed again.
T
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #18 from rai...@ultra-secure.de ---
log02-prod ) 0 # kgdb /boot/kernel/kernel /var/crash/vmcore.last
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public Li
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #17 from Mark Johnston ---
(In reply to rainer from comment #16)
kernel-dbg just contains kernel symbols. If you crash a kernel and get a
vmcore in /var/crash, then the symbols can be used to examine the vmcore. The
kernel-dbg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #16 from rai...@ultra-secure.de ---
OK, as soon as some load is on the system (in this case, 10mbit UDP syslog
traffic, it panics again.
supervisor write data, page not present.
How do I install and activate the debug-kernel fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #15 from rai...@ultra-secure.de ---
OK.
I've "fixed" this by adding more memory and reducing ARC, so that I have less %
wired.
I will see what I can do.
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #14
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
--- Comment #13 from rai...@ultra-secure.de ---
Is this one of the issues that is mentioned here:
https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-september-2018/
"Of late I have also been investigatin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
rai...@ultra-secure.de changed:
What|Removed |Added
Summary|smartpqi - kernel panics|smartpqi - and/or ZFS -
13 matches
Mail list logo
