Date: Sat, 07 Jul 2012 23:14:20 -0400 From: Steve Wills <steve@mouf.net> To: freebsd-current@freebsd.org Subject: Re: panic after starting X with r238120 Message-ID: <4FF8FB0C.4050706@mouf.net> In-Reply-To: <4FF62A6C.7090408@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>
next in thread | previous in thread | raw e-mail | index | archive | help
Following up to myself, with some things I should have mentioned before: On 07/05/12 19:59, Steve Wills wrote: > On 07/05/12 03:00, Alan Cox wrote: >> On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills <swills@freebsd.org> wrote: >> >>> Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set >>> it to 1 for some reason that I can't recall. >>> >>> >> That shouldn't cause a crash in pmap_enter(). What is line 3587 of pmap.c >> in your sources? > > 3587 if ((newpte & PG_RW) == 0) > >> You mentioned DRM. Are you using the new Intel graphics >> driver? >> > > No, I'm using ATI Radeon. > 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. This wasn't the case before, I think the last time I updated was about a month ago, May 6. Also, I have these other shared memory related settings in sysctl.conf: kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 kern.ipc.shm_allow_removed=1 I'm wondering if this is an indication that I have/had some bad settings and they finally bit me, or if this is an indication of a bug. Thanks, Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FF8FB0C.4050706>