Bug 72222 - [IVB/HSW] unigine demos frozen at splash screen enabling gome-session when running by 3~5 times on Ubuntu
Summary: [IVB/HSW] unigine demos frozen at splash screen enabling gome-session when ru...
Status: VERIFIED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-02 09:13 UTC by zhoujian
Modified: 2015-01-05 01:18 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments
splash_screen.png (1.51 MB, text/plain)
2013-12-02 09:13 UTC, zhoujian 		Details
splash_screen.png (1.51 MB, image/png)
2013-12-02 09:15 UTC, zhoujian 		Details
ubuntu_gnome-session.log (5.67 KB, text/plain)
2013-12-02 09:16 UTC, zhoujian 		Details
Xorg.0.log (8.73 KB, text/plain)
2013-12-02 09:17 UTC, zhoujian 		Details
Show Obsolete (1) View All

Description zhoujian 2013-12-02 09:13:43 UTC 
Created attachment 90092 [details]
splash_screen.png

System Environment:       
----------------------------------------------------------------------
Platform: IVB/HSW desktop (OS:Ubuntu13.10)
Libdrm: (master)libdrm-2.4.49-2-gc3d96897de647bd5f6d4802c108a3f65a307d61b
Mesa: (master)862044c7f7d55b7e6459e3e948c376e6894a72ff
Xf86_video_intel:(master)2.99.906-65-g3dae8b97151f1d08942e
Cairo: (master)31eff5c6eb57ad379689748fd8c6
Libva: (staging)1264cd81fd8728f18bd2feedf6e9c
Libva_intel_driver:(staging)34627c96f331f7a344270c3d5
Kernel:	(drm-intel-nightly) 164a4cb4c1431a0689f8550786

Bug detailed description:
------------------------------------------------------------------------
unigine demos frozen at splash screen enabling gome-session when running by 3~5 times on Ubuntu 13.10,It works ok on Raw X, The problem doesn’t exist on Fedora19.
Please see Xorg.0.log, ubuntu_gnome-session.log and splash_screen.png


Reproduce steps:
--------------------------------------------------------------------
1. xinit&
2.gnome-session
3. 
export LD_LIBRARY_PATH=bin/:$LD_LIBRARY_PATH 
export force_glsl_extensions_warn=true
vblank_mode=0 ./bin/Sanctuary -video_app opengl -data_path ../ -sound_app null -system_script sanctuary/unigine.cpp -engine_config ../data/unigine.cfg -video_mode -1 -video_fullscreen 1 -extern_define PHORONIX -video_width 1920 -video_height 1080
Comment 1 zhoujian 2013-12-02 09:15:52 UTC 
Created attachment 90093 [details]
splash_screen.png
Comment 2 zhoujian 2013-12-02 09:16:40 UTC 
Created attachment 90094 [details]
ubuntu_gnome-session.log
Comment 3 zhoujian 2013-12-02 09:17:49 UTC 
Created attachment 90095 [details]
Xorg.0.log
Comment 4 Ian Romanick 2014-01-22 00:40:44 UTC 
Does this still occur?
Comment 5 zhoujian 2014-01-22 02:04:38 UTC 
(In reply to comment #4)
> Does this still occur?
Yes,this problem still occur.
Comment 6 zhoujian 2014-01-22 02:19:07 UTC 
With upstream system environment as below: 
 Libdrm:(master)libdrm-2.4.52
 Mesa:(master)ded56746890ea826a32d763b2fe2af9a16755e87
 Xf86_video_intel:(master)2.99.907-40-gf7121bf733e9b02248fa0b7bb
 Cairo:(master)2a7f133639bed86a29dd9693cb78c0aa42eaff30
 Libva:(staging)79ddde6bab54618046f136471c020c08ff4fde50
 Libva_intel_driver:(staging)6736a39fce442a8e5abb2a2e99adf56e3965d35f
 Kernel:git-53cda6
Comment 7 zhoujian 2014-08-20 08:52:14 UTC 
This issue also still exist,detail system environment as below:
----------------------------------------
Libdrm:(master)libdrm-2.4.56-8-gd9ce09de12131fa8c5ff2d7c2dbd6b61d8a5fd14
 Mesa:(master)ce4d3f3104b01b6148ce7b1c7ecd354fd2f062c9
 Xserver:(master)xorg-server-1.15.99.902-121-g2f5cf9ff9a0f713b7e0386364
 Xf86_video_intel:(master)2.99.914-55-gf8e632f396bf4b0473dca0516567d56a29954cf3
 Cairo:(master)7736d08e22ffd7ab9968617164c7e027125b7755
 Libva:(master)acfcd5f0637a951d50c5112c7dfbd46f1d0dcdb3
 Libva_intel_driver:(master)82d2ed8d7da3619c0ea467c06604f5626fc0b901
 Kernel:   (drm-intel-nightly)186631131a9289dad22f51315d78b9b6ac5b425f
----------------------------------------
Comment 8 Kenneth Graunke 2014-08-22 07:00:57 UTC 
I really don't think this is a driver bug.
Comment 9 Eero Tamminen 2014-10-23 16:02:36 UTC 
(In reply to zhoujian from comment #3)
> Created attachment 90095 [details]
> Xorg.0.log

grep 'EE' Xorg.0.log:
[   384.834] (EE) module ABI major version (8) doesn't match the server's version (7)
[   384.834] (EE) Failed to load module "glx" (module requirement mismatch, 0)
[   384.835] (EE) module ABI major version (15) doesn't match the server's version (14)
[   384.835] (EE) Failed to load module "intel" (module requirement mismatch, 0)
[   384.835] (EE) module ABI major version (15) doesn't match the server's version (14)
[   384.835] (EE) Failed to load module "intel" (module requirement mismatch, 0)
[   384.835] (EE) Failed to load module "vesa" (module does not exist, 0)
[   384.835] (EE) Failed to load module "modesetting" (module does not exist, 0)
[   384.836] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   384.836] (EE) No drivers available.

-> Your X server configuration in the attached dmesg is broken.

Fix your X configuration first, then try again.  If this use-case is still broken, attach up to date log file.
Comment 10 lili 2014-10-24 05:53:04 UTC 
(In reply to Eero Tamminen from comment #9)
> (In reply to zhoujian from comment #3)
> Created attachment 90095 [details]
> > Xorg.0.log

grep 'EE' Xorg.0.log:
[   384.834] (EE) module ABI major
> version (8) doesn't match the server's version (7)
[   384.834] (EE) Failed
> to load module "glx" (module requirement mismatch, 0)
[   384.835] (EE)
> module ABI major version (15) doesn't match the server's version (14)
[  
> 384.835] (EE) Failed to load module "intel" (module requirement mismatch, 0)
> [   384.835] (EE) module ABI major version (15) doesn't match the server's
> version (14)
[   384.835] (EE) Failed to load module "intel" (module
> requirement mismatch, 0)
[   384.835] (EE) Failed to load module "vesa"
> (module does not exist, 0)
[   384.835] (EE) Failed to load module
> "modesetting" (module does not exist, 0)
[   384.836] (EE) Failed to load
> module "fbdev" (module does not exist, 0)
[   384.836] (EE) No drivers
> available.

-> Your X server configuration in the attached dmesg is broken.
> Fix your X configuration first, then try again.  If this use-case is still
> broken, attach up to date log file.

Verify the bug on the latest version. When running case unigine demos, there is no longer frozen at splash screen,but there is white screen issue of bug 82900.
Comment 11 lili 2014-10-24 05:59:45 UTC 
(In reply to lili from comment #10)
> (In reply to Eero Tamminen from comment #9)
> (In reply to zhoujian from
> comment #3)
> Created attachment 90095 [details]
> > Xorg.0.log

grep 'EE'
> Xorg.0.log:
[   384.834] (EE) module ABI major
> version (8) doesn't match
> the server's version (7)
[   384.834] (EE) Failed
> to load module "glx"
> (module requirement mismatch, 0)
[   384.835] (EE)
> module ABI major
> version (15) doesn't match the server's version (14)
[  
> 384.835] (EE)
> Failed to load module "intel" (module requirement mismatch, 0)
> [  
> 384.835] (EE) module ABI major version (15) doesn't match the server's
>
> version (14)
[   384.835] (EE) Failed to load module "intel" (module
>
> requirement mismatch, 0)
[   384.835] (EE) Failed to load module "vesa"
>
> (module does not exist, 0)
[   384.835] (EE) Failed to load module
>
> "modesetting" (module does not exist, 0)
[   384.836] (EE) Failed to load
>
> module "fbdev" (module does not exist, 0)
[   384.836] (EE) No drivers
>
> available.

-> Your X server configuration in the attached dmesg is broken.
> > Fix your X configuration first, then try again.  If this use-case is still
> > broken, attach up to date log file.

Verify the bug on the latest version.
> When running case unigine demos, there is no longer frozen at splash
> screen,but there is white screen issue of bug 82900.

bug 82900 is marked as duplicate of bug 82897.
Comment 12 Tapani Pälli 2014-10-24 07:37:50 UTC 
> When running case unigine demos, there is no longer frozen at splash screen

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.