Date: Mon, 29 Oct 2007 13:36:58 +0200 From: "Gleb Kozyrev" <gkozyrev@gmail.com> To: "Kris Kennaway" <kris@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Deadlock, exclusive sx so_rcv_sx, amd64 Message-ID: <ca661e8a0710290436o18f461b5j511fceb109773b4f@mail.gmail.com> In-Reply-To: <4725B7EA.5080807@FreeBSD.org> References: <ca661e8a0710211529y2a48b4a9h78da4211b3f09274@mail.gmail.com> <200710251435.58984.jhb@freebsd.org> <ca661e8a0710260252u4f5c1c3di22828143e81e3df2@mail.gmail.com> <200710261222.28656.jhb@freebsd.org> <20071026184536.GE37471@deviant.kiev.zoral.com.ua> <ca661e8a0710261302j188a05c4h63728eab67f6068@mail.gmail.com> <ca661e8a0710281849g7147a3ao97d68fd2f12b3daf@mail.gmail.com> <4725B7EA.5080807@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/10/2007, Kris Kennaway <kris@freebsd.org> wrote: > > It now just takes longer until freeze with shpgperproc = 5000 (originally 200). > > > > So how about vm.pmap.pv_entry_max? Have you obtained the usual > debugging information (DDB backtraces, etc) when the system freezes? vm.pmap.pv_entry_max and vm.pmap.shpgperproc turn out to be related and raising one of them automatically raises the other. If there's a bug those sysctls won't help, will they? If there's no bug what values can you suggest? Defaults are vm.pmap.pv_entry_max: 1479365 vm.pmap.shpgperproc: 200 Backtraces, etc are provided in this thread. <http://docs.FreeBSD.org/cgi/mid.cgi?ca661e8a0710261302j188a05c4h63728eab67f6068>; -- With best regards, Gleb Kozyrev.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ca661e8a0710290436o18f461b5j511fceb109773b4f>