Bug 82457 - GPU hung on i3-4350T - ref 3403-1
Summary: GPU hung on i3-4350T - ref 3403-1
Status: CLOSED DUPLICATE of bug 80229
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Mika Kuoppala
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-11 10:22 UTC by Barry Scott
Modified: 2017-07-24 22:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
player-intel-gpu-error.info in tar file (798.46 KB, application/octet-stream)
2014-08-11 10:24 UTC, Barry Scott
no flags Details
player-kernel-messages.info (57.71 KB, text/plain)
2014-08-11 10:25 UTC, Barry Scott
no flags Details

Description Barry Scott 2014-08-11 10:22:26 UTC
Here are the version of key RPMs.

gstreamer1-1.2.4-91.fc20.x86_64
gstreamer1-libav-1.2.4-1.fc20.x86_64
gstreamer1-plugins-bad-free-1.2.4-91.fc20.x86_64
gstreamer1-plugins-bad-free-extras-1.2.4-91.fc20.x86_64
gstreamer1-plugins-bad-freeworld-1.2.4-90.fc20.x86_64
gstreamer1-plugins-base-1.2.4-1.fc20.x86_64
gstreamer1-plugins-good-1.2.4-90.fc20.x86_64
gstreamer1-plugins-good-extras-1.2.4-90.fc20.x86_64
gstreamer1-plugins-ugly-1.2.4-1.fc20.x86_64
gstreamer1-vaapi-0.5.9-0.94.git22dc8c42.fc20.x86_64
intel-gpu-tools-2.21.15-7.fc20.x86_64
kernel-3.15.4-900.fc20.x86_64
libdrm-2.4.54-1.fc20.x86_64
libva-intel-driver-1.3.2-90.fc20.x86_64
python-gstreamer1-1.1.90-1.fc20.x86_64
xorg-x11-drv-intel-2.21.15-7.fc20.x86_64
xorg-x11-server-Xorg-1.14.4-90.fc20.x86_64
Comment 1 Barry Scott 2014-08-11 10:24:55 UTC
Created attachment 104422 [details]
player-intel-gpu-error.info in tar file
Comment 2 Barry Scott 2014-08-11 10:25:32 UTC
Created attachment 104423 [details]
player-kernel-messages.info
Comment 3 Chris Wilson 2014-08-11 10:34:24 UTC

*** This bug has been marked as a duplicate of bug 80229 ***


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.