From owner-freebsd-current Sun Jul 12 17:49:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13984 for freebsd-current-outgoing; Sun, 12 Jul 1998 17:49:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@38.nyack.fcc.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13965; Sun, 12 Jul 1998 17:49:53 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id UAA09290; Sun, 12 Jul 1998 20:48:47 -0400 (EDT) (envelope-from nathan) Message-ID: <19980712204846.A9285@rtfm.net> Date: Sun, 12 Jul 1998 20:48:46 -0400 From: Nathan Dorfman To: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Display locked when X server dies Mail-Followup-To: Daniel O'Connor , freebsd-current@FreeBSD.org, current@FreeBSD.ORG References: <19980712191515.A195@rtfm.net> <199807130037.KAA04389@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807130037.KAA04389@cain.gsoft.com.au>; from Daniel O'Connor on Mon, Jul 13, 1998 at 10:07:20AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 10:07:20AM +0930, Daniel O'Connor wrote: > > > Killing the X server from a regular vty works fine. Try > > this: > > > > vty$ startx > > vty$ kill -9 [pid of X server] > > --- > > vty$ startx > > xterm$ kill -9 [pid of X server] > > > > The first example works fine, the X server exits as expected. In the > > second form, you'll see your X session freeze. Please post your > > results, as I'd like to know if this is a problem in -current or > Nope, thats perfectly normal behaviour.. > If you send the X process a normal kill then it will be able to exit and take > the video card out of gfx mode, if you muke it with -9 then the kernel will > kill the process before it can do anything useful to the garphics card (a > program can't catch a kill -9) > > The reason you can't fix it is because the kernel doesn't know how to take the > video card out of graphics mode (thats what the drivers are for in X :) > This makes sense. The reason that it is a "problem" is that XFree86 is doing this to itself, it seems at random. I could just be moving the mouse from one xterm to another, when *wham*. This has been happening since a long's ago -current, around the same time I stopped seeing the "recommend more swap space" messages on console. Any ideas? -- ________________ ___________________________________________ / Nathan Dorfman \ / "My problems start when the smarter bears / nathan@rtfm.net \/ and the dumber visitors intersect." / finger for PGP key \ Steve Thompson, Yosemite wildlife biologist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message