Attachment 34090 Details for Bug 27100 – Bug details.

Bug details.

BugReport.txt (text/plain), 1.50 KB, created by John on 2010-03-15 16:17:48 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: John

Created: 2010-03-15 16:17:48 UTC

Size: 1.50 KB

patch

obsolete

>
>IntelÂ® G31 + ICH7 Chipset
>
>uname -m = i686
>
>pkg-config --modversion libdrm = 2.4.17
>
>X.Org X Server 1.7.5.901 (1.7.6 RC 1)
>
>Usable kernel =  2.6.31.12-174.2.22.fc12.i686
>
>Not usable kernels:
>2.6.32.9-67
>2.6.32.9-70.fc12.i686
>2.6.33-0.52.rc8 (F13 Alpha)
>
>System: Fedora 12 (Unmodified)
>
>Motherboard = GIGABYTE GA-G31M-ES2L
>(Integrated Intel Graphics Media Accelerator 3100 (Intel GMA 3100) )
>
>VGA connector
>
>===============================
>
>GPU hangs, black screen, keyboard dead - a few seconds after entering password and pressing <Enter>. Before blackout, can see desktop being drawn (does not complete login).
>
>1) Runlevel 3 + startx gives same result.
>
>2) Sometimes the system freezes before the login screen is shown (rare).
>
>3) If I'm quick enough after entering my password and pressing <Enter>, I can start tty4, wait until the disk stops making noise, and then return to tty1 with a working desktop. Logging out from this state usually freezes the system.
>
>4) Fedora 13 Alpha: Graphical install hangs after a "Basic Storage Device" selection, Basic video install says (+/-) "x startup failed, going to text mode".
>
>5) In /var/log/messages
>localhost kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
>Mar 15 10:57:19 localhost kernel: render error detected, EIR: 0x00000000
>Mar 15 10:57:19 localhost kernel: [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 1036 at 1033)
>
>6) Even though system appeared hung, was able to ssh to computer. Got an intel_gpu_dump.
>
>
>

Actions: View

Attachments on bug 27100: 34090 | 34091 | 34092 | 34218 | 34219 | 34265 | 34266 | 34267 | 34304 | 34369 | 34380 | 34381

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.