From: Tim Gardner <tim.gardner@canonical.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Suspend to RAM fault in VT when resuming
Date: Tue, 13 Mar 2007 14:30:42 -0600 [thread overview]
Message-ID: <45F709F2.80504@canonical.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Pavel,
I've chased one of the 'Suspend to RAM' resume problems to a specific
line in drivers/char/vt.c, see attached 2.6.21-rc3 diff with
TRACE_RESUME() instrumentation. The macro scr_writew resolves to '*addr
= val', which appears to be causing the problem. I've verified that the
pointer is not NULL, but don't know if its really valid. Its pretty
tough to tell what is happening, but on a Dell XPS it just hangs. A Dell
Precision blinks the keyboard lights.
Since I don't know anything about video programming, I though perhaps
you might have an opinion.
rtg
--
Tim Gardner tim.gardner@ubuntu.com
[-- Attachment #2: vt.diff --]
[-- Type: text/x-patch, Size: 627 bytes --]
diff --git a/drivers/char/vt.c b/drivers/char/vt.c
index c3f8e38..43a0904 100644
--- a/drivers/char/vt.c
+++ b/drivers/char/vt.c
@@ -98,6 +98,7 @@
#include <linux/pm.h>
#include <linux/font.h>
#include <linux/bitops.h>
+#include <linux/resume-trace.h>
#include <asm/io.h>
#include <asm/system.h>
@@ -2263,7 +2264,9 @@ static void vt_console_print(struct console *co, const char *b, unsigned count)
if (c == 10 || c == 13)
continue;
}
+TRACE_RESUME(0);
scr_writew((vc->vc_attr << 8) + c, (unsigned short *)vc->vc_pos);
+TRACE_RESUME(0);
cnt++;
if (myx == vc->vc_cols - 1) {
vc->vc_need_wrap = 1;
next reply other threads:[~2007-03-13 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 20:30 Tim Gardner [this message]
2007-03-13 21:24 ` Suspend to RAM fault in VT when resuming Pavel Machek
2007-03-14 1:42 ` Tim Gardner
2007-03-19 15:07 ` Pavel Machek
2007-03-19 16:15 ` Tim Gardner
2007-03-19 20:45 ` Pavel Machek
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=45F709F2.80504@canonical.com \
--to=tim.gardner@canonical.com \
--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