Date: Mon, 17 Dec 2018 20:08:35 +0000 From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 233414] [PowerPC64] OPTIONS DEBUG_MEMGUARD results in unbootable kernel Message-ID: <bug-233414-21-UlREz8vBHa@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233414-21@https.bugs.freebsd.org/bugzilla/> References: <bug-233414-21@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233414 --- Comment #13 from Sean Bruno <sbruno@FreeBSD.org> --- I'm guessing that memguard is making things too slow to catch whatever was crashing before. I have been running the memguard patch from comment #10 f= or 3 days without issue: sbruno@pylon.nyi:~ % sysctl vm.memguard vm.memguard.maplimit: 3435974656 vm.memguard.mapstart: 16140901064512782336 vm.memguard.divisor: 10 vm.memguard.desc: 16 Bucket vm.memguard.cursor: 16140901067941314560 vm.memguard.mapsize: 3435974656 vm.memguard.phys_limit: 1641385984 vm.memguard.wasted: 2380800 vm.memguard.wrapcnt: 134780 vm.memguard.numalloc: 673191 vm.memguard.fail_kva: 105 vm.memguard.fail_pgs: 0 vm.memguard.options: 1 vm.memguard.minsize: 0 vm.memguard.minsize_reject: 0 vm.memguard.frequency: 0 vm.memguard.frequency_hits: 0 sbruno@pylon.nyi:~ % uptime 8:07PM up 3 days, 2:45, 2 users, load averages: 4.03, 5.05, 5.15 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233414-21-UlREz8vBHa>