Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Oct 2008 19:44:08 -0400
From:      Jung-uk Kim <jkim@FreeBSD.org>
To:        freebsd-acpi@FreeBSD.org
Cc:        Alexander Motin <mav@freebsd.org>, freebsd-amd64@freebsd.org, Nate Lawson <nate@root.org>
Subject:   Re: Semi-working patch for amd64 suspend/resume
Message-ID:  <200810221944.13406.jkim@FreeBSD.org>
In-Reply-To: <48FF9AFA.3030201@root.org>
References:  <1224616985.00027652.1224606603@10.7.7.3> <48FF9925.4090007@FreeBSD.org> <48FF9AFA.3030201@root.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 22 October 2008 05:28 pm, Nate Lawson wrote:
> Alexander Motin wrote:
> > Jung-uk Kim wrote:
> >> When you do 'sysctl debug.acpi.suspend_bounce=1' and 'acpiconf
> >> -s 3', does it bounce back?  If it does not, there are other
> >> problems, e.g., device drivers.  On my desktop, for example,
> >> vga(4) tries to restore previous state while resuming but it
> >> hangs system.  In fact, I believe ISA-era EGA/VGA save/restore
> >> routines do not work for modern graphics cards at all. :-(
> >
> > Test passed from both console and XOrg. I have integrated i965GM
> > video.
> >
> > Here is verbose messages from that trip "there and back again":
> >
> > Oct 23 00:11:55 mavbook acpi: suspend at 20081023 00:11:55
> >
> > Oct 23 00:12:00 mavbook kernel: vga0: saving 68 bytes of video
> > state Oct 23 00:12:00 mavbook kernel: pci0:0:2:0: Transition from
> > D0 to D3 Oct 23 00:12:00 mavbook kernel: pci0:0:2:1: Transition
> > from D0 to D3 Oct 23 00:12:00 mavbook kernel: pci0:0:26:7:
> > Transition from D0 to D3 Oct 23 00:12:00 mavbook kernel: acpi:
> > bad write to port 0x080 (32), val 0xbb
> > Oct 23 00:12:06 mavbook kernel: pci0:0:27:0: Transition from D0
> > to D3 Oct 23 00:12:06 mavbook kernel: pci0:0:31:2: Transition
> > from D0 to D3
> >
> > Oct 23 00:12:06 mavbook kernel: pci0:0:2:0: Transition from D3 to
> > D0 Oct 23 00:12:06 mavbook kernel: pci0:0:2:1: Transition from D3
> > to D0 Oct 23 00:12:06 mavbook kernel: acpi: bad write to port
> > 0x080 (32), val 0xaa
> > Oct 23 00:12:06 mavbook kernel: pci0:0:26:7: Transition from D3
> > to D0 Oct 23 00:12:06 mavbook kernel: pci0:0:27:0: Transition
> > from D3 to D0 Oct 23 00:12:06 mavbook kernel: pci0:0:31:2:
> > Transition from D3 to D0
>
> That's kind of weird.  The above devices were turned off (D3) then
> back on again (D0).  I'm wondering about that blocked write also.

The port 0x80 is usually used for BIOS debugging.

http://www.coreboot.org/FAQ#POST_card

Probably BIOS developer forgot to comment out the lines. :-)

Jung-uk Kim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810221944.13406.jkim>