From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Leo L. Schwab" <ewhac@best.com>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Weird Resume Problem
Date: Sat, 24 Nov 2007 19:43:19 +0100 [thread overview]
Message-ID: <200711241943.20054.rjw@sisk.pl> (raw)
In-Reply-To: <20071124013014.GA4605@best.com>
On Saturday, 24 of November 2007, Leo L. Schwab wrote:
> Today I saw a resume-from-RAM problem that I've never witnessed
> before.
>
> I have a ThinkPad Z61t running the Debian version of kernel
> 2.6.22.10 (linux-source-2.6.22.6). I normally avoid suspend-to-RAM, as
> there's a bug in the Intel graphics code that can lock up the machine when
> switching virtual terminals. But with the latest xserver-xorg-video-intel,
> in which this bug is reputedly fixed, I've been trying it more often.
>
> I suspended-to-RAM yesterday afternoon, and attempted to resume
> roughly 24 hours later. It's the longest I've ever left the machine in a
> suspend-to-RAM state. Up until this point, resume-from-RAM has always
> worked.
>
> Normally, when resuming from RAM, I see the display wake up to a text
> console. At the top of the display in yellow text appears, "inu". I never
> gave much thought to this, assuming it was some sort of glitched attempt to
> print "Linux" to the console. After that, I normally see kernel resume
> messages appear, followed by the restoration of the X display.
>
> Today, when I resumed, I got the text console, but instead of a
> yellow "inu" at the top, only "i" appeared. A few moments later, the
> ThinkPad BIOS/boot screen appeared, and the machine proceeded with a fresh
> reboot (praise be to journalled filesystems).
This "Linux" string is a part of debugging code that has been removed recently,
because we suspected it might interact badly with some graphics adapters.
Perhaps something like this happened on your system.
Greetings,
Rafael
prev parent reply other threads:[~2007-11-24 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 1:30 Weird Resume Problem Leo L. Schwab
2007-11-24 18:43 ` Rafael J. Wysocki [this message]
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=200711241943.20054.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ewhac@best.com \
--cc=linux-pm@lists.linux-foundation.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