linux-kernel - Re: [linux-pm] Problems with STR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20060910192625.GA5308@elf.ucw.cz>
Date:	Sun, 10 Sep 2006 21:26:25 +0200
From:	Pavel Machek <pavel@....cz>
To:	David Brownell <david-b@...bell.net>
Cc:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Problems with STR

On Sun 2006-09-10 08:03:23, David Brownell wrote:
> > From pavel@...e.cz  Thu Sep  7 15:10:51 2006
> > Date: Fri, 8 Sep 2006 00:07:18 +0200
> > From: Pavel Machek <pavel@...e.cz>
> > To: David Brownell <david-b@...bell.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/