Bug 742674 - [965GM] Badly wedged after screen turned off (during heavy I/O load) "first get vblank counter failed: Invalid argument"
Summary: [965GM] Badly wedged after screen turned off (during heavy I/O load) "first g...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:modesetting]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-01 09:15 UTC by James
Modified: 2018-04-11 08:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:46:21 UTC
Type: ---


Attachments (Terms of Use)
dmesg output (124.03 KB, text/plain)
2011-10-01 09:15 UTC, James
no flags Details
i915_error_state for device 0 (759.98 KB, text/plain)
2011-10-01 09:16 UTC, James
no flags Details
i915_error_state for device 64 (759.98 KB, text/plain)
2011-10-01 09:16 UTC, James
no flags Details
Xorg.0.log (1.53 MB, text/plain)
2011-10-01 09:17 UTC, James
no flags Details
Today's kernel messages in /var/log/messages (98.17 KB, text/plain)
2011-10-01 09:19 UTC, James
no flags Details

Description James 2011-10-01 09:15:20 UTC
Created attachment 525861 [details]
dmesg output

Description of problem:
I left my notebook with Intel X3100 graphics, 2 GiB RAM doing a heavy I/O task copying around 15 GiB from the ext4 system disc to an external USB device formatted with BTRFS. Generally bad systemwide latency ensued. When I returned to the machine, the display would not wake up but it was accessible by ssh. Hence I captured a dmesg, Xorg.0.log, /var/log/messages, and the contents of i915_error_state (attached).

Machine had been operating for ~16 days, between suspend/resume cycles.

Version-Release number of selected component (if applicable):
kernel-2.6.40.4-5.rhapsody.fc15.x86_64  (built from kernel-2.6.40.4-5.fc15.x86_64 sources as official build breaks ACPI)
xorg-x11-drv-intel-2.15.0-5.fc15.x86_64

Comment 1 James 2011-10-01 09:16:02 UTC
Created attachment 525862 [details]
i915_error_state for device 0

Comment 2 James 2011-10-01 09:16:36 UTC
Created attachment 525863 [details]
i915_error_state for device 64

Comment 3 James 2011-10-01 09:17:18 UTC
Created attachment 525864 [details]
Xorg.0.log

Comment 4 James 2011-10-01 09:19:51 UTC
Created attachment 525865 [details]
Today's kernel messages in /var/log/messages

Comment 5 Matěj Cepl 2011-10-02 15:51:46 UTC
I see in dmesg log lines like 

[1164587.202488] [drm:i915_wait_request] *ERROR* something (likely vbetool) disabled interrupts, re-enabling

Do you have vbetool installed? Why? What happens without it?

Comment 6 James 2011-10-02 15:57:58 UTC
(In reply to comment #5)
> Do you have vbetool installed?

No.

Comment 7 Matěj Cepl 2011-10-04 20:24:21 UTC
/var/log/Xorg.0.log contains many error messages:

[1003588.723] (WW) intel(0): first get vblank counter failed: Invalid argument

Comment 8 Fedora End Of Life 2012-08-07 14:46:25 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.