From owner-freebsd-current Tue Dec 5 2:26:29 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 02:26:26 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 0049637B400; Tue, 5 Dec 2000 02:26:24 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:wS/o/LbmhUYXzrLZFszj0ENZxDmvBgI2@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.11.0/3.7Wpl2) with ESMTP id eB5AQ8o15844; Tue, 5 Dec 2000 19:26:12 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:7jDE4t5WyNjmQTZmujI0psAvhN7ZWt/H@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id TAA12407; Tue, 5 Dec 2000 19:33:22 +0900 (JST) Message-Id: <200012051033.TAA12407@zodiac.mech.utsunomiya-u.ac.jp> To: Dag-Erling Smorgrav Cc: Andrea Campi , John Baldwin , freebsd-current@FreeBSD.ORG, Andrea Campi , yokota@zodiac.mech.utsunomiya-u.ac.jp Reply-To: kazutaka.yokota@nifty.com Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] In-reply-to: Your message of "05 Dec 2000 10:39:34 +0100." References: <20001205013955.A2351@webcom.it> <20001205032713.B2351@webcom.it> Date: Tue, 05 Dec 2000 19:33:21 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Andrea Campi writes: >> Ok, I will try each one. At the moment, I'm using logo_saver. >> I will let you know. > >Take a long hard look at vesa_set_mode() and vesa_set_origin() in >sys/i386/isa/vesa.c. If the panic occurs while the console is still in >text mode, the bug is in vesa_set_mode(); if it occurs after the >console has switched to graphics mode, it's probably in >vesa_set_origin(). The may be in the VESA BIOS on the video card :-) The vesa module calls the VESA BIOS to change video modes. The bug may not necessarily be in the BIOS "code", but the VESA video mode "table" to which the vesa module refers, when it sets up a new video mode, and calculates and initializes variables in the vesa module. I would like to see full dump of 'vidcontrol -i adapter', 'vidcontrol -i mode' and dmesg after the vesa module is loaded (you get very verbose output from the vesa module init code if you boot the kernel with 'boot -v'). You see, the VESA BIOS support on some video cards is not so complete. For example, we saw in the mailing list recently that the "VGA compatible" bit is somewhat turned off for VESA high resolution modes, didn't we? That possibly was a bug in that VESA BIOS. (OR, those mode ARE genuinely VGA-incompatible and we shouldn't use them the way the vesa modules accesses them...) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message