public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] PM: suspend/resume debugging should depend on SOFTWARE_SUSPEND
Date: Mon, 27 Nov 2006 13:20:52 +0100	[thread overview]
Message-ID: <20061127122052.GA14752@suse.de> (raw)
In-Reply-To: <45693E25.9010504@shaw.ca>

On Sun, Nov 26, 2006 at 01:11:33AM -0600, Robert Hancock wrote:
> options seem to work, and vbetool appears to helpfully segfault on any operation so that's out. 

Try this one:

From: Matthew Garrett
Subject: Fix failures on AMD64

This patch fixes at least some of the cases where vbetool segfaulted on x86_64
while the x86 emulator was executing BIOS code.

--- x86-common.c
+++ x86-common.c
@@ -33,8 +33,8 @@
 
 #include "include/lrmi.h"
 
-#define REAL_MEM_BASE 	((void *)0x10000)
-#define REAL_MEM_SIZE 	0x90000
+#define REAL_MEM_BASE 	((void *)0x1000)
+#define REAL_MEM_SIZE 	0xa0000
 #define REAL_MEM_BLOCKS 	0x100
 
 struct mem_block {


I have this in our vbetool-0.7 packages and have no reports about
segfaults since then.
-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 

  parent reply	other threads:[~2006-11-27 20:01 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.U3NcOE+DHLOUMSq6HkaGglGl7hQ@ifi.uio.no>
     [not found] ` <fa.YMVQ6sabKF/IkEHUCoiQoxoHWZA@ifi.uio.no>
     [not found]   ` <fa.c5fVj98hBgqoUumwbA9jymiSXr8@ifi.uio.no>
     [not found]     ` <fa.zMBHTAXYfXNe2TVX89s3qsC2HRk@ifi.uio.no>
     [not found]       ` <fa.yA6cvuiGulIRQfqY+E9joR2nWog@ifi.uio.no>
     [not found]         ` <fa.bo0iOgKqELDD50VEZpxeUpzPsMg@ifi.uio.no>
2006-11-26  7:11           ` [patch] PM: suspend/resume debugging should depend on SOFTWARE_SUSPEND Robert Hancock
2006-11-26 10:13             ` Rafael J. Wysocki
2006-11-26 20:30               ` Robert Hancock
2006-11-27 13:51                 ` Matthew Garrett
2006-12-03 12:49                 ` Rafael J. Wysocki
2006-11-27 12:20             ` Stefan Seyfried [this message]
2006-11-19  8:18 Chuck Ebbert
2006-11-19  8:29 ` Pavel Machek
2006-11-19 17:33 ` Linus Torvalds
2006-11-19 17:44   ` Rafael J. Wysocki
2006-11-19 18:21     ` Linus Torvalds
2006-11-19 18:55       ` Rafael J. Wysocki
2006-11-19 19:54         ` Linus Torvalds
2006-11-19 21:25           ` Rafael J. Wysocki
2006-11-19 23:21             ` Linus Torvalds
2006-11-19 22:59         ` Romano Giannetti
2006-11-20 22:17       ` Theodore Tso
2006-11-21  2:02         ` Matthew Garrett
2006-11-23 13:28       ` Pavel Machek
2006-11-19 17:52   ` Mike Galbraith
2006-11-19 18:25     ` Linus Torvalds
2006-11-19 19:02       ` Mike Galbraith
2006-11-19 19:55         ` Linus Torvalds
2006-11-19 18:58     ` Rafael J. Wysocki
2006-11-19 19:53       ` Mike Galbraith
2006-11-23 13:39         ` Pavel Machek
2006-11-23 21:36           ` Mike Galbraith
2006-11-23 21:36             ` Rafael J. Wysocki
2006-11-24  6:39               ` Mike Galbraith
2006-11-24 18:08                 ` Linus Torvalds
2006-11-25  0:22                   ` Mike Galbraith
2006-11-25 14:11                   ` Mike Galbraith
2006-11-25 17:12                     ` Rafael J. Wysocki
2006-11-26  4:53                       ` Mike Galbraith
2006-11-28 10:01                         ` Mike Galbraith
2006-11-29 10:21                           ` Mike Galbraith
2006-11-19 21:41   ` Nigel Cunningham
2006-11-19 22:04   ` Christer Weinigel
2006-12-03 21:40     ` Kyle Moffett
2006-12-04 10:50       ` Pavel Machek
2006-12-04 13:56         ` Henrique de Moraes Holschuh
2006-11-22 15:23   ` Adrian Bunk
2006-11-22 15:42     ` Alan
2006-11-24 23:40       ` Pavel Machek
2006-11-25 16:08         ` Alan
2006-11-25 17:18           ` Rafael J. Wysocki
2006-11-26 20:52           ` Pavel Machek
2006-11-22 23:05   ` Mark Lord

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=20061127122052.GA14752@suse.de \
    --to=seife@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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