From owner-freebsd-current Thu Oct 22 22:26:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23158 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:26:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23150 for ; Thu, 22 Oct 1998 22:26:38 -0700 (PDT) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA12629; Thu, 22 Oct 1998 22:27:10 -0700 (PDT) Message-Id: <199810230527.WAA12629@implode.root.com> To: Kris Kennaway cc: Benjamin Greenwald , freebsd-current@FreeBSD.ORG Subject: Re: VM bug triggered by X server death In-reply-to: Your message of "Fri, 23 Oct 1998 14:41:41 +0930." From: David Greenman Reply-To: dg@root.com Date: Thu, 22 Oct 1998 22:27:10 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Fri, 23 Oct 1998, Benjamin Greenwald wrote: > >> With the most recent kernel, every time my X server dies (reboot, explicit >> kill, whatever) the kernel panics. Looks like some sort of VM bug. A >> backtrace follows. This problem is easily and completely reproducible >> (translate it happens every time) and it occurs with both my Xi Graphics X >> server as well as the XSuSE XFCom_3DLabs server (I have a Fire GL 1000 Pro). > >I also get a panic in this case running a current kernel (ELF, and since >dg's recent changes in this area). Mine however dies with (from memory): > >vm_object_terminate: not freeing wired page; wire_count=1 That will be coming out in Ben's case as well, just before the panic. The problem was caused by two bugs, actually. Fixed in rev 1.131 of vm_object.c. Thanks for the bug reports. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message