From owner-freebsd-current Thu Oct 28 13:58:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 7A8CF14D40 for ; Thu, 28 Oct 1999 13:58:18 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id QAA28372; Thu, 28 Oct 1999 16:58:18 -0400 (EDT) (envelope-from luoqi) Date: Thu, 28 Oct 1999 16:58:18 -0400 (EDT) From: Luoqi Chen Message-Id: <199910282058.QAA28372@lor.watermarkgroup.com> To: current@FreeBSD.ORG, khetan@os.org.za Subject: Re: CMAP2 busy ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. > > I've been experiencing problems with my machine crashing when in X, > when idle overnight. > > Normally it panics with XF86_S3. Today however the machine returned > something a little different, which I haven't seen before. > I hope this helps someone. > > The machine worlds with no problems, and is perfectly stable > when in console mode. X has been rebuilt several times. > > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > IdlePTD 3559424 > initial pcb at 29d280 > panicstr: pmap_zero_page: CMAP2 busy > panic messages: > --- > panic: pmap_zero_page: CMAP2 busy > It looked like an interrupt hit when the cpu was in an idle loop replenishing zero filled pages, and the interrupt handler somehow also tried to zero some pages itself. In vm_page_zero_idle(), pmap_zero_page should be called at splvm() to prevent this from happening, or allocate another pte exclusively for the idle loop. The latter seems to be preferable. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message