From owner-freebsd-current Thu Oct 22 22:19:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22503 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:19:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22497 for ; Thu, 22 Oct 1998 22:19:08 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id WAA00430; Thu, 22 Oct 1998 22:18:14 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981022221656.00a1bd00@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 22 Oct 1998 22:18:13 -0700 To: Benjamin Greenwald , freebsd-current@FreeBSD.ORG From: Manfred Antar Subject: Re: VM bug triggered by X server death In-Reply-To: <199810230502.BAA01214@miris.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:02 AM 10/23/98 -0400, Benjamin Greenwald wrote: >Greetings all, > >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). > Same thing happens to me every time I do a shutdown -r now. A kernel from yesterday is fine. Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message