Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When running piglit (quick driver test) X become unresponsive. I think the test causing this is /spec/glsl-1.10/execution/variable-indexing/fs-temp-mat4-row-wr
In messages I can see:
radeon 0000:18:00.0: couldn't scheduling ib
[drm: radeon_cs_ib_chunk] *ERROR* Failed to schedule IB!
Version-Release number of selected component (if applicable):
kernel-2.6.32-339.el6
xorg-x11-server-Xorg-1.13.0-7.el6
xorg-x11-drv-ati-6.99.99-1.el6
How reproducible:
100%
Steps to Reproduce:
1. run piglit-run /usr/lib64/piglit/tests/quick-driver.tests /tmp/piglit
2.
3.
Actual results:
X hung up
Expected results:
Additional info:
18:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV620 [ATI FireGL V3700] [1002:95cc] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:1b03]
Physical Slot: 4
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f0100000 (64-bit, non-prefetchable) [size=64K]
I/O ports at 1100 [size=256]
[virtual] Expansion ROM at f0120000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Kernel driver in use: radeon
Kernel modules: radeon
You need to use the r600.tests rather than quickdriver new test in piglit are known to lockup r6xx.
Comment 6RHEL Program Management
2012-12-14 08:31:30 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
I just have a lock-up with spills of
Feb 12 21:17:01 localhost kernel: [114728.981180] radeon 0000:01:05.0: couldn't schedule ib
Feb 12 21:17:01 localhost kernel: [114728.981188] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
for 4 minutes; had to reboot in a virtual console.
Since I am on fedora, I'll just put the info under the other bug (bug 1054756).
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/