From nobody@FreeBSD.ORG  Sun Jul 30 14:53:24 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 0960137B81F; Sun, 30 Jul 2000 14:53:24 -0700 (PDT)
Message-Id: <20000730215324.0960137B81F@hub.freebsd.org>
Date: Sun, 30 Jul 2000 14:53:24 -0700 (PDT)
From: mhenrion@cybercable.fr
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: vidcontrol VESA_800x600 causes a kernel panic
X-Send-Pr-Version: www-1.0

>Number:         20308
>Category:       i386
>Synopsis:       [panic] vidcontrol VESA_800x600 causes a kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    mux
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jul 30 15:00:01 PDT 2000
>Closed-Date:    Sun Sep 11 16:24:28 GMT 2005
>Last-Modified:  Sun Sep 11 16:24:28 GMT 2005
>Originator:     Maxime Henrion
>Release:        not a release, see environment
>Organization:
none
>Environment:
FreeBSD nebula.org 4.1-STABLE FreeBSD 4.1-STABLE #0: Sun Jul 30 15:24:27 CEST 2000     root@nebula.org:/usr/src/sys/compile/NEBULA  i386

>Description:
My kernel is compiled with VESA support, and with options SC_PIXEL_MODE for the syscons driver.
Then, when i want to set the vesa mode in my consol typing "vidcontrol VESA_800x600", I can't see anything.
I know it has caused a kernel panic, because it is waiting for two <enter> before rebooting.
I have a Diamond Viper 550 graphic card, with a NVidia TNT1 chipset.
>How-To-Repeat:
See the description.
>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->yokota 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Mon Jul 31 02:39:22 PDT 2000 
Responsible-Changed-Why:  
Over to the syscons maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20308 

From: Hiten Pandya <hiten@uk.FreeBSD.org>
To: bug-followup@FreeBSD.org
Cc: mux@FreeBSD.org
Subject: Re: i386/20308 vidcontrol VESA_800x600 causes a kernel panic
Date: Fri, 29 Mar 2002 02:36:43 +0000

 Does this problem still exist?  Maxim is a committer now, so probably he
 can assign this to himself, or close it if the problem doesn't exist
 anymore. :)
 
 
 -- 
 Hiten Pandya
 http://jfs4bsd.sf.net - JFS for FreeBSD (JFS4BSD)
 http://www.FreeBSD.org - The Power to Serve
 
 Public Key: http://www.pittgoth.com/~hiten/pubkey.asc
 --- 4FB9 C4A9 4925 CF97 9BF3  ADDA 861D 5DBD E4E3 03C3 ---
Responsible-Changed-From-To: yokota->mux 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Mon Aug 30 21:36:23 GMT 2004 
Responsible-Changed-Why:  
Reassign from inactive committer to submitter. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20308 
State-Changed-From-To: open->closed 
State-Changed-By: rodrigc 
State-Changed-When: Sun Sep 11 16:22:39 GMT 2005 
State-Changed-Why:  
Duplicate of kern/84836 
http://www.freebsd.org/cgi/query-pr.cgi?pr=84836 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20308 
>Unformatted:
