From: Bill Davidsen <davidsen@tmr.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Tino Keitel <tino.keitel+xorg@tikei.de>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: Suspend hangs since 2.6.34
Date: Thu, 10 Jun 2010 17:14:24 -0400 [thread overview]
Message-ID: <4C1155B0.7030605@tmr.com> (raw)
In-Reply-To: <4C108091.3060204@msgid.tls.msk.ru>
Michael Tokarev wrote:
> 10.06.2010 03:42, Rafael J. Wysocki пишет:
>> On Wednesday, June 09, 2010, Tino Keitel wrote:
>>> Hi,
>>>
>>> as of kernel 2.6.34 I sometimes get a strange hang during suspend to
>>> RAM. After echo mem> /sys/power/state, the suspend script hangs, Xorg
>>> eats 100% CPU, and the desktop is frozen. I can kill the script and the
>>> computer will then suspend and resume fine. The kernel log shows
>>> nothing interesting when the hang happens:
>>>
>>> usblp0: removed
>>> usbcore: deregistering interface driver dvb_usb_vp7045
>>> dvb-usb: Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II)
>>> successfully deinitialized and disconnected.
>>> PM: Syncing filesystems ... done.
>
> Sounds very much like the problem I have with 2.6.34 final. Did not
> happen with 2.6.34-rc7 which suspended just fine, but happens quite
> regularly on 2.6.34 final - not every suspend but each 2nd or 3rd
> attempt. I stopped doing suspend-to-ram due to this, because it's
> unreliable. Suspend-to-disk works just fine.
>
>>> Is this a known problem?
>>
There are two things you can try if you wish, one is to go the text console
before suspend, the other is to run your system in VESA video mode (assuming you
are a lucky person and any other mode is supported).
I'm not running on 2.6.34 for production (2.6.33.5) but I did try when it first
came out, and saw some issues there.
>> No, it's not.
>>
>>> I had rock stable suspend with 2.3.33.x. The
>>> computer is a Mac mini Core2 Duo with i945 graphics. I use KMS. I will
>>> compile a kernel with suspend debug to get more information if the hang
>>> happens next time.
>
> It's amd780g athlon-based machine here, with radeon graphics, also with
> KMS.
>
>> Yes, please try to get more information.
>
> Got it ;)
>
> /mjt
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2010-06-10 21:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 17:53 Suspend hangs since 2.6.34 Tino Keitel
2010-06-09 23:42 ` Rafael J. Wysocki
2010-06-10 6:05 ` Michael Tokarev
2010-06-10 6:07 ` Tino Keitel
2010-06-10 15:41 ` Rafael J. Wysocki
2010-06-10 21:14 ` Bill Davidsen [this message]
2010-06-13 11:00 ` Rafael J. Wysocki
2010-06-20 22:56 ` Tino Keitel
2010-06-21 19:24 ` Rafael J. Wysocki
2010-06-21 21:32 ` Tino Keitel
2010-06-21 22:27 ` Tino Keitel
2010-06-21 22:31 ` Alan Stern
2010-06-23 20:32 ` Tino Keitel
2010-06-23 21:22 ` Rafael J. Wysocki
2010-06-14 14:42 ` Maciej Rutecki
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=4C1155B0.7030605@tmr.com \
--to=davidsen@tmr.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjt@tls.msk.ru \
--cc=rjw@sisk.pl \
--cc=tino.keitel+xorg@tikei.de \
/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