Bug 570604
| Summary: | X can't get signals with DRI | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Dave Airlie <airlied> |
| Component: | kernel | Assignee: | Dave Airlie <airlied> |
| Status: | CLOSED ERRATA | QA Contact: | desktop-bugs <desktop-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.5 | CC: | cmeadors, jkoten, vbenes |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-01-13 20:37:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dave Airlie
2010-03-04 20:37:56 UTC
Devel ack, request other acks. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Hi Dave, could you please be more specific of which HW you are using as I can send signals (like kill -1 $(pidof X)) and see it in gdb.. I have specified Section "Module" Load "dri" EndSection Section "DRI" Mode 0666 EndSection to xorg.conf I am using nvidia Quadro NVS 290 with nv driver. Am I missing something? Thanks for clarification, Vladimir With DRI means using a driver with DRI/3D support, nv doesn't have that. You need to be using radeon or intel on hardware we support DRI/3D on. I configured T61 w/ Intel Corporation Mobile GM965/GL960 to use dri, glxinfo showed direct rendering; gdb attach $(pidof X) and then kill -1 $(pidof X). gdb showed this: (gdb) continue Continuing. Program received signal SIGHUP, Hangup. 0x007cf402 in __kernel_vsyscall () (gdb) continue Continuing. Program received signal SIGTERM, Terminated. 0x007cf402 in __kernel_vsyscall () (gdb) continue Continuing. Program exited normally. so I still cannot reproduce the above mentioned lack of signals. Maybe it was fixed already. this has been upstream for a few years now with no problems so should be 0 risk. Also it makes life a lot easier for debugging any X server related issues. https://bugzilla.redhat.com/show_bug.cgi?id=507536 was the issue I t hink we were debugging when we really wanted this patch in for example. in kernel-2.6.18-237.el5 You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5 Detailed testing feedback is always welcomed. I was able to reproduce in kernel-2.6.18-236.el5 on T61 with intel graphic. When direct rendering is enabled, running gdb in VT and attaching it to Xorg result in gdb hangs and Xorg starts to eat 100% CPU. The system becomes unresponsive, but I was able to connect to it through ssh. This doesn't happen when direct rendering is off. Fix confirmed in kernel-2.6.18-237.el5 - With direct rendering enabled, I was able to attach gdb to Xorg from VT and send signals (SIGTSTP, SIGHUP, SIGUSR1) which were caught by gdb. I'll retest and verify in coming RC. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0017.html |