From owner-freebsd-current@FreeBSD.ORG  Tue Mar  1 23:24:00 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 652A916A4CE; Tue,  1 Mar 2005 23:24:00 +0000 (GMT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP
	id 163CD43D2F; Tue,  1 Mar 2005 23:23:59 +0000 (GMT)
	(envelope-from iedowse@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <ab80767@salmon>; 1 Mar 2005 23:23:58 +0000 (GMT)
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: Your message of "Tue, 01 Mar 2005 17:03:50 EST."
             <200503011703.50828.jhb@FreeBSD.org> 
Date: Tue, 01 Mar 2005 23:23:57 +0000
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID: <200503012323.ab80767@salmon.maths.tcd.ie>
cc: freebsd-acpi@FreeBSD.org
cc: freebsd-current@FreeBSD.org
cc: filippo.forti@fastwebnet.it
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: Tue, 01 Mar 2005 23:24:00 -0000

In message <200503011703.50828.jhb@FreeBSD.org>, John Baldwin writes:
>On Tuesday 01 March 2005 03:30 pm, Filippo Forti wrote:
>> Hi,
>> I got a fully reproduceable panic while trying to suspend (to S3) on my
>> laptop. FreeBSD is -CURRENT from Monday.
>>
>> I'm using a modified DSDT which used to work before I updated on Monday.
>> dmesg from after reboot is attacched.

Sorry, this my fault - I thought I was correctly mapping an 8k
region in vm86 space, but got it very wrong. I've set the save state
limit back to 4k now, which should fix the panic but will mean that
the new VESA save/restore feature will be disabled for now on systems
that require more than 4k of storage.

You can either update to version 1.49 of sys/i386/isa/vesa.c, or
else disable VESA support as a workaround.

Ian