Bug 6828

Summary:

core2-32 refuses to display the prompt when set to boot from run level 3

Product:

[Build System, Metadata & Runtime] BSPs

Reporter:

Costin <costin.c.constantin>

Component:

bsps-meta-intel

Assignee:

Saul Wold <sgw>

Status:

RESOLVED WONTFIX

QA Contact:

Severity:

normal

Priority:

Medium

CC:

alexandru.c.georgescu, cristina-danielax.agurida, georgex.l.musat, tom.zanussi

Version:

1.7

Target Milestone:

1.8

Hardware:

E-Menlow

OS:

x86

Whiteboard:

OS type for building Yocto:

---

Type of Regression:

---

Verified:

Documentation change:

Don't know

Attachments:

Description	Flags
messages.txt	none
dmesg.txt	none

Description Costin 2014-10-13 11:22:22 UTC

Hello,

While performig TC 198 - boot from runlevel 3. 


TC content:

1. Boot into system and edit /etc/inittab to make sure system enter init 3 by default

########

id:3:initdefault

########

2. Reboot system, and press Tab to enter "grub"
3. Edit "kernel" line and add "psplash=false text" at the end
4. Press "F10" or "ctrl+x" to boot system

Expected results:
System should boot to runlevel 3 

it gets to a point where the screen gets into standby mode, without possibility to recover. ssh connection works well and can connect to the machine itself.

Attached: dmesg.txt and /var/log/messages

poky: 505a6b696ae990442de720e5e1135a3e44d5f75c
meta-intel: 8e5fe6c0f5cf710e1a46c5f203e52f069874768a

Costin

Comment 1 Costin 2014-10-13 11:22:57 UTC

Created attachment 2181 [details]
messages.txt

messages file

Comment 2 Costin 2014-10-13 11:23:41 UTC

Created attachment 2182 [details]
dmesg.txt

dmesg result

Comment 3 Lucian Musat 2015-03-10 15:22:28 UTC

Reproduced this on build 5c1c8af083ca7b57cc339d16ce0513b27c5dac90, meta-intel 367fd4758d23318b3adab8021d7bdc8b56e04917.


Last dmesg lines excepting networking messages:

[    3.239178] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    3.239426] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
[    3.264896] acpi device:03: registered as cooling_device2
[    3.265407] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
[    3.265795] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.265802] [drm] No driver support for vblank timestamp query.
[    4.932355] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[    4.933006] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[    5.264209] gma500 0000:00:02.0: I2C transfer error
[    5.267898] [drm] Initialized gma500 1.0.0 20140314 for 0000:00:02.0 on minor 0
[    5.391833] cfg80211: Calling CRDA to update world regulatory domain

Comment 4 Saul Wold 2015-04-16 03:15:19 UTC

Tested this with intel-core2-32 using fido and the 3.19 kernel, this appears to be working correctly now, no additional dmesg  entries, it times out correctly and then pressing a keyboard key wakes up the screen again correctly.

Comment 5 Cristina Agurida 2015-05-14 07:34:14 UTC

This issue still appear on poky build 2d09cb28f25080ed337d37d2d4381b846bbe6247, meta-intel f9738ec19d3b2864c0bd71b9bb3418d16e922a12.

In dmesg log it is nothing interesting, except this line:
 - [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness

Comment 6 Saul Wold 2015-05-14 18:06:39 UTC

The Firmware bug is a bit of a red herring or false trail, it occurs regardless of which graphics driver is used, I tried this with both the gma500 and without.  The Firmware bug message happens in both cases.  In the case of not using the gma500 driver, the screen is able to come out of standby mode, but in the case of the gma500 driver is loaded it takes control of graphics and does not come out of standby.

Marking this as WONTFIX as it's older hardware and this problem is know issue.