Bug 6617 - X fails to start after standby on core2-32 (ran on emenlow)
Summary: X fails to start after standby on core2-32 (ran on emenlow)
Status: VERIFIED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.7
Hardware: E-Menlow x86
: Medium normal
Target Milestone: 1.9
Assignee: Saul Wold
QA Contact: Cristina Agurida
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-08-07 13:51 UTC by Costin
Modified: 2015-05-14 09:03 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Costin 2014-08-07 13:51:30 UTC 
Hello,

Though this bug might seem related to others opened on same issue, it is in a way different because i found how to regain access to X after stand-by.

How to reproduce:

1) put system to standby: echo "mem" > /sys/power/state
2) regain functionality by pressing power button/ keyboard or mouse, which one works
3) if X is not showing up on screen, just do a Ctrl+Alt+F1|F2|F3 depends on machine (on core2-32 ...+F2 is fine)

Costin
Comment 1 Andra Necula 2014-08-11 09:32:08 UTC 
Same issue occurs on Core i7 64 on Sugar Bay
Cheers, Andra
Comment 2 Andra Necula 2014-08-11 09:35:24 UTC 
Same issue occurs on Sugarbay
Cheers, Andra
Comment 3 Alexandru Georgescu 2014-08-12 12:29:28 UTC 
(In reply to comment #0)
> Hello,
> 
> Though this bug might seem related to others opened on same issue, it is in
> a way different because i found how to regain access to X after stand-by.
> 
> How to reproduce:
> 
> 1) put system to standby: echo "mem" > /sys/power/state
> 2) regain functionality by pressing power button/ keyboard or mouse, which
> one works
> 3) if X is not showing up on screen, just do a Ctrl+Alt+F1|F2|F3 depends on
> machine (on core2-32 ...+F2 is fine)
> 
> Costin

Guys, it would be helpful to specify what image type was used (minimial, sato, etc) and what poky and meta-intel commit were used as well!
Comment 4 Nitin Kamble 2014-09-08 17:21:59 UTC 
This is getting enough attention due to the other more important tasks. I will try to reproduce the issue locally and see how to fix it.
Comment 5 Costin 2014-09-24 08:52:57 UTC 
Hello,

Sorry for not saying from the start all details:

I tested on core2_32 on sato-sdk image
poky : 7d80f8e9468253496a7097685aac8f468940a9c5
meta-intel : 200ebb54f46f364e7eb1738c5e993374f03f407d


Regards,

Costin
Comment 6 Alexandru Georgescu 2015-02-27 09:29:32 UTC 
(In reply to comment #5)
> Hello,
> 
> Sorry for not saying from the start all details:
> 
> I tested on core2_32 on sato-sdk image
> poky : 7d80f8e9468253496a7097685aac8f468940a9c5
> meta-intel : 200ebb54f46f364e7eb1738c5e993374f03f407d
> 
> 
> Regards,
> 
> Costin

Costin,
Can you update the regression field?
Comment 7 Saul Wold 2015-04-13 21:55:06 UTC 
I tried this on a Sugarbay/HuronRiver Laptop and it restarted correctly, I also tried it on an emenlow, this was with Fido and meta-intel master.
Comment 8 Cristina Agurida 2015-05-14 09:03:26 UTC 
Verified on master: 2d09cb28f25080ed337d37d2d4381b846bbe6247
            meta-intel: f9738ec19d3b2864c0bd71b9bb3418d16e922a12