Bug 133476 - dri with Intel 82815 CGC graphics locks machine
Summary: dri with Intel 82815 CGC graphics locks machine
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: FC3Target FC4Target
TreeView+ depends on / blocked
 
Reported: 2004-09-24 10:49 UTC by Russell Coker
Modified: 2015-01-04 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-10-03 00:44:21 UTC


Attachments (Terms of Use)

Description Russell Coker 2004-09-24 10:49:28 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
When I try to use dri with my i815 graphics the machine locks solid.  This occurs at GDM start time or from RHGB.

The below message is the last thing on the serial console before it locks up:

[drm:i810_unlock] *ERROR* Process 3259 using kernel context 0


Version-Release number of selected component (if applicable):
2.6.8-1.541

How reproducible:
Always

Steps to Reproduce:
Put machine in 1280x1024x16bpp mode so that DRI gets enabled and it locks up.

Additional info:

Comment 1 Dave Jones 2005-07-15 18:16:34 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 2 Dave Jones 2005-10-03 00:44:21 UTC
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.

There are a large number of inactive bugs in the database, and this is the only
way to purge them.

Thank you.


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