From owner-freebsd-current Tue Aug 21 22:11:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id 554A437B411 for ; Tue, 21 Aug 2001 22:11:15 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f7M5Ar552818; Wed, 22 Aug 2001 14:10:53 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f7M5Arc89665; Wed, 22 Aug 2001 14:10:53 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:JMiov4v0xcHZBAfFewUSWsJRiesZGuot@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id OAA04225; Wed, 22 Aug 2001 14:20:35 +0900 (JST) Message-Id: <200108220520.OAA04225@zodiac.mech.utsunomiya-u.ac.jp> To: kc5vdj@yahoo.com Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons VTY switch panic... In-reply-to: Your message of "Tue, 21 Aug 2001 23:42:54 EST." <3B83384E.1010604@yahoo.com> References: <3B820F12.7050209@yahoo.com> <200108220350.MAA03898@zodiac.mech.utsunomiya-u.ac.jp> <3B83384E.1010604@yahoo.com> Date: Wed, 22 Aug 2001 14:20:34 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Would you please remove the vesa driver from the kernel and do not try loading the vesa module either, and see if things work? >Actually, I have tried to get the VESA splash thing going, but never can get a >nything to display... I can try removing that... I >believe it is still set up this way... > >What are the limitations on image size and color-depth for the boot splash thi >ng? The image must have 256 colors. Its size must be 1024x768 or smaller. If you don't have the vesa support in the kernel, the maximum size is 320x200. Kazu >Kazutaka YOKOTA wrote: > >> Do you by any chance use a VESA mode in text vtys? >> >> The vesa module in -CURRENT has problems now. If you try to >> set the VESA_800x600 mode in syscons, you will likely to >> hang your machine. This is a known problem, and is somewhat >> related to vm86 and context switching. I am afraid there is >> no immediate fix for it. >> >> Kazu >> >> >>>I am getting this with regularity now. >>> >>>The one time I was available to see the panic, I forgot to go into the debug >ge >>>r and do a traceback, but it had something to do with >>>a mwrite, and had a line concerning [maybe a buffer is....?]... >>> >>>I know this isn't much to go on, but that's what I have. I'll get more info > w >>>hen I feel like wasting ten or fifteen minutes for a >>>double-reboot... [is it necessary to do the `shutdown -r now` to write a ne >w >>>entropy, or can we just keep going if it boots without >>>the proper entropy?]... >>> >>>I have pretty much isolated this to VTY switching via syscons. Occasionally >, >>>it will leave the system speaker in a constant tone >>>until it reboots. This is very noticable then X exits. > >jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message