Date: Sat, 31 Mar 2018 00:52:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 227116] CURRENT doesn't boot with integer divide fault in uma_startup_count Message-ID: <bug-227116-8-d0r3JHqV4P@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227116-8@https.bugs.freebsd.org/bugzilla/> References: <bug-227116-8@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=3D227116 --- Comment #4 from Daniel Kolesa <daniel@octaforge.org> --- (In reply to Konstantin Belousov from comment #3) I believe CoD is disabled right now, considering numactl on Linux shows two memory domains total (one per CPU). $ numactl -s policy: default preferred node: current physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 = 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 = 50 51 52 53 54 55=20 cpubind: 0 1=20 nodebind: 0 1=20 membind: 0 1 If it was on, it should've shown four, two per each CPU, right? This is my primary desktop/workstation computer, with mostly desktop style workloads (= i.e. largely NUMA-unaware) so it's best to keep it disabled. Should I try what happens when I enable it? --=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-227116-8-d0r3JHqV4P>