mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Oleksij Rempel (fishor)" <bug-track@fisher-privat.net>
To: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: memory corruption  after suspend - ultrabook not able to turn on after failed suspend, EHCI workaround - Asus Zenbook UX31E
Date: Thu, 08 Mar 2012 19:54:33 +0100	[thread overview]
Message-ID: <4F590069.1050207@fisher-privat.net> (raw)

Hallo all,

Alan Stern suggested me to ask on this lists. The problems seems to be 
complicated. https://bugzilla.kernel.org/show_bug.cgi?id=42728

So now to the problem.

Symptoms are fallowing, after initiating suspend this laptop freezes. 
After forcing after poweroff, it is really hard to power on this laptop. 
linux kernel gets oops, windows will get BSOD.

I tried /sys/power/pm_test and i got fallowing result. Setting 
pm_test=devices do not make any problems. With pm_test=processors the 
test runs ok, but after power off i get same result as with filed suspend.

Steps to reproduce:
- echo 0 > pm_async
- echo processors > pm_test
- echo mem > state
(here the display will go off, usb mouse powered off too, after one 
second it returns back to console .... no freezes)
- poweroff
- after power on, start memtest .... here i will get lots of bad memory 
blocks.

the processor is Intel Core i7-2677M. According to the specification it 
has build in memory controller. I assume the controller is some how 
misconfigured at suspend, this is why i get bad blocks with memtest86+. 
It looks like the laptop stay in this broken supend mode even after 
poweroff. To bring it back to normal i need to completely poweroff it, 
it mean unplug battery and powersupply.

                 reply	other threads:[~2012-03-08 18:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F590069.1050207@fisher-privat.net \
    --to=bug-track@fisher-privat.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.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

all inboxes | Powered by JetHome®