Date: Sun, 8 Jul 2012 16:06:50 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Jean-S?bastien P?dron <dumbbell@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: panic after starting X with r238120 Message-ID: <20120708130650.GV2338@deviant.kiev.zoral.com.ua> In-Reply-To: <4FF941EC.9050900@FreeBSD.org> References: <7F5E65B1-24AF-4942-A273-093EBAE94B7D@FreeBSD.org> <168031EF-1CBD-4B14-A99E-D5C90B01111C@FreeBSD.org> <CAJUyCcMO_244tK6kp73mGq1gFx-uFETmO9n-F7Qu2=ZoaYb9cQ@mail.gmail.com> <4FF62A6C.7090408@FreeBSD.org> <4FF8FB0C.4050706@mouf.net> <4FF941EC.9050900@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sun, Jul 08, 2012 at 10:16:44AM +0200, Jean-S?bastien P?dron wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08.07.2012 05:14, Steve Wills wrote: > > For what it's worth, I discovered that twm and xterm don't trigger > > the issue, but konsole and other kde things do, which is what led > > me to discover that setting kern.ipc.shm_use_phys back to default > > fixed it. > > I encountered the same issue with x11-wm/awesome, but everything's ok > with twm. A kernel from 2012-06-23 doesn't crash but a kernel from > 2012-07-03 does crash. > > Here're the sysctls/tunables I have regarding shm: > > In /boot/loader.conf: > kern.ipc.shmmni="1024" > kern.ipc.shmseg="1024" > > In /etc/sysctl.conf: > kern.ipc.shmmax=2147483648 > kern.ipc.shm_use_phys=1 > kern.ipc.shm_allow_removed=1 > You know, this is not much useful ? Backtrace is. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk/5heoACgkQC3+MBN1Mb4iYmQCfU8nyuNFWmRKeyBhcqr5P3ES3 KBYAn14yI/NvAjkQilEF5jzMxMoYcreM =+85o -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120708130650.GV2338>