Bug 397631 - drm:i915_vblank_swap *ERROR Invalid pipe 0
Summary: drm:i915_vblank_swap *ERROR Invalid pipe 0
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-24 05:30 UTC by MASAO TAKAHASHI
Modified: 2008-03-01 05:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-01 05:00:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
cat /proc/dri/0/* (1.10 KB, text/plain)
2007-11-24 05:30 UTC, MASAO TAKAHASHI
no flags Details
Xorg.0.log (22.14 KB, text/plain)
2007-11-27 08:14 UTC, MASAO TAKAHASHI
no flags Details
configuration file (66.04 KB, application/octet-stream)
2007-11-27 23:15 UTC, MASAO TAKAHASHI
no flags Details
dmesg log (17.05 KB, application/octet-stream)
2007-11-27 23:16 UTC, MASAO TAKAHASHI
no flags Details
lsmod log (1.80 KB, text/plain)
2007-11-27 23:17 UTC, MASAO TAKAHASHI
no flags Details
dmesg with verbose drm debug messages on linux-2.6.24-0.45.rc3.git1.fc9 (49.35 KB, application/octet-stream)
2007-11-28 01:08 UTC, MASAO TAKAHASHI
no flags Details
more verbose drm debug messages (32.23 KB, application/octet-stream)
2007-12-04 07:02 UTC, MASAO TAKAHASHI
no flags Details
more verbose X.org.0.log (19.43 KB, application/octet-stream)
2007-12-04 07:04 UTC, MASAO TAKAHASHI
no flags Details
X.org.0.log (19.04 KB, application/octet-stream)
2008-01-09 00:48 UTC, MASAO TAKAHASHI
no flags Details
X.org.0.log with 2.6.24-0.138.rc7.bz397631.fc9 (18.88 KB, application/octet-stream)
2008-01-10 00:01 UTC, MASAO TAKAHASHI
no flags Details

Description MASAO TAKAHASHI 2007-11-24 05:30:24 UTC
Description of problem:
Invoking Googleearth, I got a error log in dmesg as belows.
 "[drm:i915_vblank_swap] *ERROR* Invalid pipe 0"

And driconf gives a message "Could not detect any configurable direct-rendering
capable devices. DRIconf will be started in expert mode."
But there exists /dev/dri/card0.

Chipset : intel 82865G

Version-Release number of selected component (if applicable):
linux-2.6.24-0.41.rc3.git1.fc9
libdrm-2.4.0-0.1.fc9
driconf-0.9.1-6.fc9
googleearth-4.2.0198.2451 (beta)
How reproducible:
always

Steps to Reproduce:
1. To invoke googleearth or driconf
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 MASAO TAKAHASHI 2007-11-24 05:30:26 UTC
Created attachment 267941 [details]
cat /proc/dri/0/*

Comment 2 MASAO TAKAHASHI 2007-11-27 08:14:44 UTC
Created attachment 269511 [details]
Xorg.0.log

Comment 3 MASAO TAKAHASHI 2007-11-27 08:16:26 UTC
I have tested on linux-2.4.26-0.45.rc3.git1.fc9.
But, X server cannot recognize dri.
Xorg.0.log is attached

Comment 4 Kyle McMartin 2007-11-27 15:43:12 UTC
Could you please attach a copy of your "dmesg" and "lsmod" so we can determine
if the correct modules are loaded?

Comment 5 MASAO TAKAHASHI 2007-11-27 23:14:37 UTC
I generate kernel with config options such as  "CONFIG_DRM=y" and 
  "CONFIG_DRM_i915=y".
I tried to generate kernel with "CONFIG_DRM=m" and "CONFIG_DRM_I915=m".
But, I get a same result.
I attach dmesg and ".config" and a lsmod log 


Comment 6 MASAO TAKAHASHI 2007-11-27 23:15:35 UTC
Created attachment 270581 [details]
configuration file

configuration file

Comment 7 MASAO TAKAHASHI 2007-11-27 23:16:34 UTC
Created attachment 270591 [details]
dmesg log

Comment 8 MASAO TAKAHASHI 2007-11-27 23:17:14 UTC
Created attachment 270601 [details]
lsmod log

Comment 9 MASAO TAKAHASHI 2007-11-28 01:08:09 UTC
Created attachment 270641 [details]
dmesg with verbose drm debug messages on linux-2.6.24-0.45.rc3.git1.fc9

Comment 10 MASAO TAKAHASHI 2007-12-04 06:55:30 UTC
(In reply to comment #4)
> Could you please attach a copy of your "dmesg" and "lsmod" so we can determine
> if the correct modules are loaded?
I attached already.
And Now, I tested linux-2.6.24-0.69.rc3.git7.fc9.
The "drm:i915_vblank_swap *ERROR Invalid pipe 0" error is still alive 
when invoking googleearth.
My hardware is as follows
 pentium 4 2.6GHz
 512MB memory
 8MB AGP memory
 82865G intel chip



Comment 11 MASAO TAKAHASHI 2007-12-04 07:02:21 UTC
Created attachment 276591 [details]
more verbose drm debug messages

Comment 12 MASAO TAKAHASHI 2007-12-04 07:04:56 UTC
Created attachment 276601 [details]
more verbose X.org.0.log

Comment 13 Kyle McMartin 2008-01-07 18:29:19 UTC
Can you retry with the latest kernel in rawhide?
cheers, Kyle

Comment 14 MASAO TAKAHASHI 2008-01-09 00:44:10 UTC
I retry with linux-2.6.24-0.138.rc7.fc9.
The error message does not appered.
But, "glxgear" is failed displaying following message.
"glxgears: intel_tris.c:114: intelStartInlinePrimitive: Assertion
`intel->batch->id == intel->last_state_batch_id' failed.
Aborted"

Perhaps, mesa library has problem.
I attach X.org.0.log .



Comment 15 MASAO TAKAHASHI 2008-01-09 00:48:05 UTC
Created attachment 291107 [details]
X.org.0.log

with linux-2.6.24-0.138.rc7.fc9
     xorg-x11-server-1.4.99.1-0.12.fc9
     xorg-x11-drv-i810-2.2.0-2.fc9

Comment 16 Kyle McMartin 2008-01-09 15:39:31 UTC
Please try the rpms at
http://koji.fedoraproject.org/koji/taskinfo?taskID=336149

they incorporate a possible fix.

cheers, Kyle

Comment 17 MASAO TAKAHASHI 2008-01-09 23:59:44 UTC
Dear Mr. Kyle.
I tried with the package that you recommended above.
   2.6.24-0.138.rc7.bz397631.fc9
But, glxgears is failed with same error message.
And there are no warning messages in X.org.0.log such as
  (WW) intel(0): PRB0_CTL (0x0000f001) indicates ring buffer enabled
 (WW) intel(0): Existing errors found in hardware state.

Please see an attached log.


Comment 18 MASAO TAKAHASHI 2008-01-10 00:01:05 UTC
Created attachment 291217 [details]
X.org.0.log with 2.6.24-0.138.rc7.bz397631.fc9

Comment 19 MASAO TAKAHASHI 2008-02-28 23:55:22 UTC
I have tested again.
!. environment
   linux-2.6.25-0.73.rc3.git9.fc9
   mesa-7.1-0.17.fc9
   libdrm-2.4.0-0.4.fc9
2. results
   Google worked well.
   The error message was gone.


Comment 20 MASAO TAKAHASHI 2008-02-29 08:46:48 UTC
I correct a mesa revision.
mesa-7.1-0.17.fc9 has a problem which can not enable dri.
mesa-7.1-0.16.fc9 is good.


Comment 21 MASAO TAKAHASHI 2008-03-01 05:00:41 UTC
It seems that the problem is gone away.
I close this report.
The another problem concerned with mesa package.
The gcc option "-fvisibility=hidden" is restored again in mesa-7.1-0.17.
This option causes an undefined symbol error while loading "i915_dri.so".
 undefined symbol are "_glthread_xxx".
After generating mesa without "-fvisibility=hidden" options, the above error is not
 displayed and "dri" is enabled.



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