mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Problems with STR
Date: Sun, 10 Sep 2006 21:26:25 +0200	[thread overview]
Message-ID: <20060910192625.GA5308@elf.ucw.cz> (raw)
In-Reply-To: <20060910150323.5DE2019FFB5@adsl-69-226-248-13.dsl.pltn13.pacbell.net>

On Sun 2006-09-10 08:03:23, David Brownell wrote:
> > From pavel@suse.cz  Thu Sep  7 15:10:51 2006
> > Date: Fri, 8 Sep 2006 00:07:18 +0200
> > From: Pavel Machek <pavel@suse.cz>
> > To: David Brownell <david-b@pacbell.net>
> > Subject: Re: [linux-pm] Problems with PM_FREEZE
> >
> > Hi!
> >
> > > > > Just for the record, I tried those tricks and no success on either
> > > > > the NF3 or NF2 boxes.  And the NF3 ran into 's2ram' problems,
> > > > > it seems vbetool etc don't work in 64bit mode yet ...
> > > >
> > > > Any chance to try it in 32-bit mode? Recovery cd, or something?
> > > 
> > > Not for a few weeks, but that wouldn't have affected the NF2 ...
> >
> > Ok, can you do bugreport on bugzilla.kernel.org?
> 
> You mean, like bugid 6906?

Ahha, okay, feel free to Cc me on suspend bugs.

> > Is the resume (with minimal modules, init=/bin/bash, no acpi_sleep=
> > parameter) completely broken, or is just the video dead?
> 
> Completely broken.

Ok, this is beeping patch. It would be interesting to know what result
you get if you attempt to resume from S3 with this applied.

diff --git a/arch/i386/kernel/acpi/wakeup.S b/arch/i386/kernel/acpi/wakeup.S
index b781b38..88d4cba 100644
--- a/arch/i386/kernel/acpi/wakeup.S
+++ b/arch/i386/kernel/acpi/wakeup.S
@@ -11,7 +11,22 @@
 #
 # If physical address of wakeup_code is 0x12345, BIOS should call us with
 # cs = 0x1234, eip = 0x05
-# 
+#
+
+#define BEEP \
+	inb	$97, %al; 	\
+	outb	%al, $0x80; 	\
+	movb	$3, %al; 	\
+	outb	%al, $97; 	\
+	outb	%al, $0x80; 	\
+	movb	$-74, %al; 	\
+	outb	%al, $67; 	\
+	outb	%al, $0x80; 	\
+	movb	$-119, %al; 	\
+	outb	%al, $66; 	\
+	outb	%al, $0x80; 	\
+	movb	$15, %al; 	\
+	outb	%al, $66;
 
 ALIGN
 	.align	4096
@@ -20,6 +35,7 @@ wakeup_code:
 	wakeup_code_start = .
 	.code16
 
+	BEEP
  	movw	$0xb800, %ax
 	movw	%ax,%fs
 	movw	$0x0e00 + 'L', %fs:(0x10)


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

           reply	other threads:[~2006-09-10 19:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20060910150323.5DE2019FFB5@adsl-69-226-248-13.dsl.pltn13.pacbell.net>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060910192625.GA5308@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome