Subject: port-i386/33033: VM86/KVM86 do not survive an ACPI S3 suspend/resume
To: None <port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: None <jmcneill@NetBSD.org>
List: netbsd-bugs
Date: 03/08/2006 19:00:01
>Number: 33033
>Category: port-i386
>Synopsis: VM86/KVM86 do not survive an ACPI S3 suspend/resume
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: port-i386-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Mar 08 19:00:00 +0000 2006
>Originator: Jared D. McNeill
>Release: NetBSD 3.99.15
>Organization:
>Environment:
Architecture: i386
Machine: i386
>Description:
Not entirely sure yet, but any vm86 or kvm86 calls made after
I resume from S3 suspend fail. Calling them from the kernel causes
an 'asynchronous system trap', and applications that make vm86
calls from userspace dump core.
>How-To-Repeat:
Enable the powerhook in vesafb, try to drop to S3 suspend and resume
>Fix:
Unknown. I'm tentatively using the bioscall interface in vesafb's
powerhook to restore the display on resume; this will not work in
paletted 8bpp mode though (since setting up the palette depends on
kvm86_bios_addpage functionality -- as far as I can tell the
bioscall interface doesn't provide this).
>Unformatted: