dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 34102] radeon drm/kms: please use suspend/hibernate notifiers for allocating memory in suspend routines
Date: Mon, 9 May 2011 15:15:53 GMT	[thread overview]
Message-ID: <201105091515.p49FFr7F015562@demeter2.kernel.org> (raw)
In-Reply-To: <bug-34102-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=34102





--- Comment #10 from Martin Steigerwald <Martin@Lichtvoll.de>  2011-05-09 15:15:49 ---
This wasn't a hang I think, see there.

I tried to hibernate two running KDE 4 sessions with reserved_size upto 64 MiB:

shambhala:/sys/power> cat reserved_size 
67108864

Which failed with:

May  9 16:41:47 localhost kernel: PM: freeze of devices complete after 524.427
msecs
May  9 16:41:47 localhost kernel: PM: late freeze of devices complete after
0.509 msecs
May  9 16:41:47 localhost kernel: ACPI: Preparing to enter system sleep state
S4
May  9 16:41:47 localhost kernel: PM: Saving platform NVS memory
May  9 16:41:47 localhost kernel: Extended CMOS year: 2000
May  9 16:41:47 localhost kernel: PM: Creating hibernation image:
May  9 16:41:47 localhost kernel: PM: Need to copy 218459 pages
May  9 16:41:47 localhost kernel: PM: Normal pages needed: 113686 + 1024,
available pages: 113492
May  9 16:41:47 localhost kernel: PM: Not enough free memory
May  9 16:41:47 localhost kernel: PM: Error -12 creating hibernation image
May  9 16:41:47 localhost kernel: Extended CMOS year: 2000
May  9 16:41:47 localhost kernel: ACPI: Waking up from system sleep state S4
May  9 16:41:47 localhost kernel: PM: early recover of devices complete after
0.366 msecs

Does it make sense to go to even higher values? I am a bit puzzled, since for
one KDE 4 session a value of 2 MiB has turned out to be enough for about 5-10
attempts - it didn't fail once.

Maybe here there is simply not enough memory available no matter what I reserve
for driver allocation? If so, then so be it. That might be just a limit for a 2
GB RAM machine.

Is there a way to tell for sure whether reserved size is too low or there are
general memory constraints? TuxOnIce logged how much of the reserved extra
pages it used. Can in-kernel-hibernation do this too?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  parent reply	other threads:[~2011-05-09 15:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 16:06 [Bug 34102] New: radeon drm/kms driver: please use suspend/hibernate notifiers for allocating memory in suspend routines bugzilla-daemon
2011-04-29 16:06 ` [Bug 34102] radeon drm/kms: " bugzilla-daemon
2011-05-03 20:45 ` bugzilla-daemon
2011-05-03 21:33 ` bugzilla-daemon
2011-05-03 21:44 ` bugzilla-daemon
2011-05-03 21:44 ` bugzilla-daemon
2011-05-04 14:23 ` bugzilla-daemon
2011-05-04 16:31 ` bugzilla-daemon
2011-05-04 19:37 ` bugzilla-daemon
2011-05-04 20:05 ` bugzilla-daemon
2011-05-05 19:53 ` bugzilla-daemon
2011-05-09 12:15 ` bugzilla-daemon
2011-05-09 15:15 ` bugzilla-daemon [this message]
2011-05-09 15:59 ` bugzilla-daemon
2011-05-09 19:06 ` bugzilla-daemon
2011-05-30  7:56 ` bugzilla-daemon
2012-06-13 15:05 ` bugzilla-daemon
2012-06-13 15:05 ` bugzilla-daemon

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=201105091515.p49FFr7F015562@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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