linux-kernel - memory corruption after suspend - ultrabook not able to turn on after failed suspend, EHCI workaround

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4F590069.1050207@fisher-privat.net>
Date:	Thu, 08 Mar 2012 19:54:33 +0100
From:	"Oleksij Rempel (fishor)" <bug-track@...her-privat.net>
To:	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: memory corruption  after suspend - ultrabook not able to turn on
 after failed suspend, EHCI workaround - Asus Zenbook UX31E

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/