From owner-freebsd-current@FreeBSD.ORG  Thu Mar  3 01:32:32 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7577316A4CE; Thu,  3 Mar 2005 01:32:32 +0000 (GMT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP
	id 3B68243D48; Thu,  3 Mar 2005 01:32:31 +0000 (GMT)
	(envelope-from iedowse@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa82163@salmon>; 3 Mar 2005 01:32:30 +0000 (GMT)
To: filippo.forti@fastwebnet.it
In-Reply-To: Your message of "Wed, 02 Mar 2005 17:55:16 +0100."
             <20050302165516.GB674@portatile.fastwebnet.it> 
Date: Thu, 03 Mar 2005 01:32:29 +0000
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID: <200503030132.aa82163@salmon.maths.tcd.ie>
cc: freebsd-acpi@freebsd.org
cc: freebsd-current@freebsd.org
cc: Nate Lawson <nate@root.org>
Subject: Re: Panic on suspend 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2005 01:32:32 -0000

In message <20050302165516.GB674@portatile.fastwebnet.it>, Filippo Forti writes
:
>On Tue, Mar 01, 2005 at 03:19:42PM -0800, Nate Lawson wrote:
>> That is in the VGA BIOS.  Try setting this sysctl before suspending:
>> 
>> hw.acpi.reset_video=0
>Unfortunately this doesn't make the trick
>Thanks anyway

Did updating to the version 1.49 of vesa.c fix the crash for you?
There is a new patch at:

	http://people.freebsd.org/~iedowse/vesa_restore.diff

This needs to be applied on top of version 1.49, and should hopefully
correct the behaviour when the VESA state requires more than 4k of
space. Would you be able to test that this version does not crash
for you on suspend?

I don't fully understand why the previous version was faulting at
0x2000, since that page should have been mapped into the VM86 address
space. However my code was definitely handling the kernel virtual
addresses incorrectly, so maybe that was causing something to be
overwritten. The updated patch allocates a contiguous virtual buffer
and then maps each page into the VM86 address space starting at
0x1000.

Ian