Bug 1843 - Error screen when I input "clear" in the terminal
Summary: Error screen when I input "clear" in the terminal
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-configuration (show other bugs)
Version: unspecified
Hardware: E-Menlow x86
: Medium normal
Target Milestone: 1.3
Assignee: Tom Zanussi
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-12-19 00:18 UTC by MaNing
Modified: 2012-04-25 04:01 UTC (History)
8 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MaNing 2011-12-19 00:18:07 UTC
Tree/Branch: Poky/1.2_M1
Commit: b806f726b1db2cb605869c1022ef727c1110255b
Meta: Master
Commit: b6d5d9a3b06caf578103a04dc5fcf5e476343205

with 20111213-4 images for emenlow, boot system successful and then launch the Terminal, error screen when I input "clear" in the Terminal

The error log of these failure cases show:
######
it: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
GL_RENDERER   = Mesa DRI Intel(R) GMA500 20081116 - 5.0.1.0046 x86/MMX/SSE2
GL_VERSION    = 2.0 Mesa 7.4
GL_VENDOR     = Tungsten Graphics, Inc
######
Comment 1 Darren Hart 2012-01-18 11:19:17 UTC
Is this reproducable on other platforms?
Comment 2 yilong, sun 2012-01-18 17:02:27 UTC
The command "clear" run well on other platforms.
Comment 3 Tom Zanussi 2012-04-19 14:02:27 UTC
With current master of both poky and meta-intel, I'm not seeing this problem - 'clear' clears the screen fine.

poky: 1a03b7dfba464fde770ba69b618427d13e0a3b8b
meta-intel: f75f9b6f68473eb0efac802409608f8389be0030
Comment 4 MaNing 2012-04-24 02:47:38 UTC
This issue still exist in denzil testing(20120418-1 image).

Tree/Branch: denzil
Commit id:2c3d4f5beee8f57a74244495511b9294df1085ea

Meta branch:master
Commit id:f75f9b6f68473eb0efac802409608f8389be0030
Comment 5 MaNing 2012-04-24 06:49:14 UTC
This issue still exist in denzil testing(20120418-1 image).

Tree/Branch: denzil
Commit id:2c3d4f5beee8f57a74244495511b9294df1085ea

Meta branch:master
Commit id:f75f9b6f68473eb0efac802409608f8389be0030

20120418-1 enemlow image URL:
http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120418-1
Comment 6 Tom Zanussi 2012-04-25 04:01:02 UTC
Apparently the problem is that mesa-demos builds and installs a demo program called 'clear' into /usr/bin on emenlow, which is what gets run instead of the system 'clear'.  mesa-demos is included only when enabling tools-testapps.  The reason it worked for me is that the build I tested didn't enable tools-testapps.

The solution is to test with a build that doesn't include tools-testapps.  The real fix probably would be to modify mesa-demos to not install into /usr/bin but rather into a separate demo apps directory.