amd issueshttps://gitlab.freedesktop.org/drm/amd/-/issues2019-11-19T16:22:53Zhttps://gitlab.freedesktop.org/drm/amd/-/issues/173[switchable] Xorg usually hangs up system on start2019-11-19T16:22:53ZBugzilla Migration User[switchable] Xorg usually hangs up system on start## Submitted by Nikolay Amiantov
Assigned to **Default DRI bug account**
**[Link to original bug (#32970)](https://bugs.freedesktop.org/show_bug.cgi?id=32970)**
## Description
Created attachment 41846<br>
lspci -v<br>
<br>
Overvie...## Submitted by Nikolay Amiantov
Assigned to **Default DRI bug account**
**[Link to original bug (#32970)](https://bugs.freedesktop.org/show_bug.cgi?id=32970)**
## Description
Created attachment 41846<br>
lspci -v<br>
<br>
Overview: On notebook with switchable graphics (Acer Aspire 4820TG-5454G50Miks) when switching to the integrated graphics card before starting Xorg server, system usually shows non-blanking cursor and hangs up.<br>
<br>
Steps to reproduce:<br>
1. Switch to the integrated graphics card with vgaswitcheroo (with or without switching off unused card)<br>
2. Start Xorg<br>
<br>
Actial results:<br>
System hangs up.<br>
<br>
Expected results:<br>
Xorg starts properly, login screen is shown.<br>
<br>
Build:<br>
xf86-video-intel: fd9235ebe03a01982238cdd6e8b55f613e14b6af<br>
Repeats with current stable version (2.14.0) and with older commits, also with older driver and Xorg versions on Gentoo Linux (~amd64 + x11 overlay)<br>
<br>
**Attachment 41846**, "lspci -v": <br>
[lspci](/uploads/c3b591151e8c0652b338e0ca60ce997d/lspci)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/172[RADEON:KMS:PLL] screen flickers all the time with desktop image appearing on...2019-11-19T16:22:45ZBugzilla Migration User[RADEON:KMS:PLL] screen flickers all the time with desktop image appearing only briefly## Submitted by Gildas Le Nadan
Assigned to **Default DRI bug account**
**[Link to original bug (#32556)](https://bugs.freedesktop.org/show_bug.cgi?id=32556)**
## Description
Created attachment 41344<br>
dmesg<br>
<br>
Machine is ...## Submitted by Gildas Le Nadan
Assigned to **Default DRI bug account**
**[Link to original bug (#32556)](https://bugs.freedesktop.org/show_bug.cgi?id=32556)**
## Description
Created attachment 41344<br>
dmesg<br>
<br>
Machine is the same as in bug report 28331 although with different software components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor<br>
4000+, this time running a 64 bits debian squeeze.<br>
<br>
The machine is a small factor desktop machine designed around laptop<br>
components, so the graphic card is an integrated radeon x1200.<br>
<br>
When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the time<br>
making the machine unusable, while with debian kernel 2.6.32-5 such "flick to black" event occur from time to time, making it annoying but usable.<br>
<br>
While booting with radeon.modeset=0 the problem doesn't exhibits itself<br>
<br>
The following packages version from debian squeeze are installed:<br>
xserver-xorg 1:7.5+8<br>
xserver-xorg-core 2:1.7.7-10<br>
xserver-xorg-video-radeon 1:6.13.1-2+squeeze1<br>
<br>
Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that machine (when booted on 2.6.37-rc6).<br>
<br>
Regards,<br>
Gildas<br>
<br>
**Patch 41344**, "dmesg": <br>
[dmesg](/uploads/63806f5c1b6b99f986b28ee38b8a3ff2/dmesg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/171[RADEON:KMS:TTM] large images displayed in Firefox appear corrupted2019-11-19T16:22:05ZBugzilla Migration User[RADEON:KMS:TTM] large images displayed in Firefox appear corrupted## Submitted by Da Fox
Assigned to **Default DRI bug account**
**[Link to original bug (#32422)](https://bugs.freedesktop.org/show_bug.cgi?id=32422)**
## Description
Created attachment 41150<br>
Picture describing a thousand words...## Submitted by Da Fox
Assigned to **Default DRI bug account**
**[Link to original bug (#32422)](https://bugs.freedesktop.org/show_bug.cgi?id=32422)**
## Description
Created attachment 41150<br>
Picture describing a thousand words.<br>
<br>
"A picture says more than a thousand words" (aka see attachment)<br>
<br>
This is what happens when I try to view the XKCD "Online Communities 2" map (http://xkcd.com/802_large/) or other large images in firefox.<br>
<br>
**Attachment 41150**, "Picture describing a thousand words.": <br>
![Screenshot_-_12152010_-_07_16_00_PM](/uploads/85925f4888dd5ecc321a37f8e019742e/Screenshot_-_12152010_-_07_16_00_PM.png)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/170KMS:RS480:X200M LCD Monitor on VGA-0 shows wavy picture2019-11-19T16:21:54ZBugzilla Migration UserKMS:RS480:X200M LCD Monitor on VGA-0 shows wavy picture## Submitted by Edgar Villanueva
Assigned to **Default DRI bug account**
**[Link to original bug (#32399)](https://bugs.freedesktop.org/show_bug.cgi?id=32399)**
## Description
When second LCD monitor is connected to VGA-0 picture ...## Submitted by Edgar Villanueva
Assigned to **Default DRI bug account**
**[Link to original bug (#32399)](https://bugs.freedesktop.org/show_bug.cgi?id=32399)**
## Description
When second LCD monitor is connected to VGA-0 picture is wavy.<br>
The text on the screen flutters.
### Depends on
* [Bug 32350](https://bugs.freedesktop.org/show_bug.cgi?id=32350)https://gitlab.freedesktop.org/drm/amd/-/issues/166Display fades to white screen instead of blanking out in DPMS mode on a Sony ...2019-11-19T16:21:46ZBugzilla Migration UserDisplay fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E## Submitted by boris64
Assigned to **Default DRI bug account**
**[Link to original bug (#32319)](https://bugs.freedesktop.org/show_bug.cgi?id=32319)**
## Description
Created attachment 41011<br>
Fade-to-white-picture No.1<br>
<br...## Submitted by boris64
Assigned to **Default DRI bug account**
**[Link to original bug (#32319)](https://bugs.freedesktop.org/show_bug.cgi?id=32319)**
## Description
Created attachment 41011<br>
Fade-to-white-picture No.1<br>
<br>
On my new Sony Vaio laptop (VPCEC3L1E) the screen fades to white<br>
(with backlights on, i think) instead of simply blanking out.<br>
This can be reproduced by running "xset dpms force off" or<br>
by simply waiting until powermanagement kicks in.<br>
<br>
The graphics card used is a radeon 5xxx(?)<br>
(01:00.0 VGA compatible controller: ATI Technologies Inc Device 68e0).<br>
<br>
This happens on console and in X.<br>
I'll attach some pictures showing the issue.<br>
<br>
<br>
Thanks for any help!<br>
<br>
<br>
PS: I hope i did choose the correct product/component for<br>
this type of bug.<br>
<br>
**Attachment 41011**, "Fade-to-white-picture No.1": <br>
![1](/uploads/2560b9cd56e3877c9655adb02902a218/1.JPG)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/164[RADEON:KMS:RV250:RESUME] corrupted screen after resume2019-11-19T16:21:24ZBugzilla Migration User[RADEON:KMS:RV250:RESUME] corrupted screen after resume## Submitted by Johannes Obermayr
Assigned to **Default DRI bug account**
**[Link to original bug (#31230)](https://bugs.freedesktop.org/show_bug.cgi?id=31230)**
## Description
Created attachment 39897<br>
specific part of /var/lo...## Submitted by Johannes Obermayr
Assigned to **Default DRI bug account**
**[Link to original bug (#31230)](https://bugs.freedesktop.org/show_bug.cgi?id=31230)**
## Description
Created attachment 39897<br>
specific part of /var/log/messages (~13 MiB, "drm.debug=255")<br>
<br>
After resume the screen is totally corrupted.<br>
<br>
**Attachment 39897**, "specific part of /var/log/messages (~13 MiB, "drm.debug=255")": <br>
[kernel.log.bz2](/uploads/500931fc3e346b947dde42f4840f3fd0/kernel.log.bz2)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/162[RADEON:KMS:RV370:INIT] [drm] cp init fail (any kernels 2.6.3x.x)2019-11-19T16:21:16ZBugzilla Migration User[RADEON:KMS:RV370:INIT] [drm] cp init fail (any kernels 2.6.3x.x)## Submitted by djn..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#31213)](https://bugs.freedesktop.org/show_bug.cgi?id=31213)**
## Description
when loading the 'radeon' driver with modeset=1 (KMS ena...## Submitted by djn..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#31213)](https://bugs.freedesktop.org/show_bug.cgi?id=31213)**
## Description
when loading the 'radeon' driver with modeset=1 (KMS enabled) <br>
the following error appears in dmesg | grep drm<br>
<br>
[drm:r100_ring_test] *ERROR* radeon: ring test failed (sracth(0x15E4)=0xCAFEDEAD)<br>
[drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).<br>
<br>
the result is that OpenGL renderer with be the 'software rasterizer'. and performance is obviously crippled.<br>
<br>
glxinfo returns:<br>
<br>
OpenGL vendor string: Mesa Project<br>
OpenGL renderer string: Software Rasterizer<br>
OpenGL version string: 2.1 Mesa 7.8.1<br>
<br>
The error occurs with kernels 2.6.33.4, 2.6.35.7 and even the latest at the time 2.6.36. The pc is a toshiba satellite m40-185 laptop with ati mobility radeon X300 (rv370) gpu.<br>
<br>
Additionally, I have tried installing the git versions of libdrm, mesa, and xf86-video-ati to this date (29/10/2010) with Gallium support (enabled in turn --enable-gallium, --enable-gallium-radeon and even both, using llvm (version 2.8) compiler. The problem persists.<br>
<br>
The only way to get 3d accelaration is to disable KMS. then dmesg | grep drm seems to load up fine (see here: http://pastebin.com/vNfyeq7P). But then I have problems with 3d applications 'competing' to stay on top - they don't seem to be able to work well with KDE4 compositing effects. To avoid that I have to disable the compositing effects ( see here for in depth explanation and some Xorg.0.log and dmesg outputs http://www.linuxquestions.org/questions/slackware-14/3d-applications-compete-to-stay-on-top-with-the-radeon-driver-840392/ )https://gitlab.freedesktop.org/drm/amd/-/issues/160[RADEON:KMS:RS100:MODESET] no display on VGA2019-11-19T16:21:08ZBugzilla Migration User[RADEON:KMS:RS100:MODESET] no display on VGA## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#30620)](https://bugs.freedesktop.org/show_bug.cgi?id=30620)**
## Description
I've bug report from user with old notebook with ATI 320M...## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#30620)](https://bugs.freedesktop.org/show_bug.cgi?id=30620)**
## Description
I've bug report from user with old notebook with ATI 320M (RS100). She installed openSUSE 11.3 which comes with 2.6.34 and can not get driver display anything.<br>
<br>
The important part is that notebook's PANEL is broken and she uses VGA for external monitor.<br>
<br>
There are two KMS cases I got tested by her:<br>
1) "vga=0x31a" ─ black VGA screen right after booting start<br>
2) "" (no vga) ─ black VGA screen right after booting start<br>
<br>
So I asked to experiment with UMS a little:<br>
3) "vga=0x31a radeon.modeset=0 3" ─ radeonfb loads, VGA works!<br>
4) "vga=0x31a radeon.modeset=0" ─ radeonfb works, black VGA screen on X start<br>
<br>
Without radeonfb:<br>
5) "radeon.modeset=0 3" ─ pure console works on VGA, no radeonfb<br>
6) "radeon.modeset=0" ─ pure console works on VGA, black VGA on X start<br>
<br>
<br>
My conclusions:<br>
1) KMS can not initialize VGA<br>
2) UMS can not initialize VGA<br>
3) radeonfb *can* initialize VGA<br>
4) There is no conflict with radeonfb, as dropping "vga=0x31a" does not help<br>
<br>
What else can I ask for to make it debuggable?<br>
<br>
I thought of Xorg.0.log but it may be hard to get for her as she had to mount some USB storage in console and copy file to it.<br>
Taking "dmesg | grep drm" could be easier. Would it be useful?https://gitlab.freedesktop.org/drm/amd/-/issues/159[RADEON:KMS:RS780:MODESET] video=1280x720@50 no longer works2019-11-19T16:21:00ZBugzilla Migration User[RADEON:KMS:RS780:MODESET] video=1280x720@50 no longer works## Submitted by Marius Groeger
Assigned to **Default DRI bug account**
**[Link to original bug (#30325)](https://bugs.freedesktop.org/show_bug.cgi?id=30325)**
## Description
With the current drm-radeon-testing my grub cmdline opti...## Submitted by Marius Groeger
Assigned to **Default DRI bug account**
**[Link to original bug (#30325)](https://bugs.freedesktop.org/show_bug.cgi?id=30325)**
## Description
With the current drm-radeon-testing my grub cmdline option video=1280x720@50 no longer works (RS780, output to LCD TV via HDMI). The fbcon apparently is enabled, but the TV doen't get a displayable picture anymore. Booting with d-r-t from 6 weeks ago works and correctly uses the EDID reported 1280x720@50 mode.<br>
<br>
I did ask the same thing on the dri-devel mailing list and received no answer so I'm filing this bug both as another humble nudge to the authors of the drm video= code, and as a more persistent reminder of the issue.<br>
<br>
Thanks<br>
Mariushttps://gitlab.freedesktop.org/drm/amd/-/issues/156[RADEON:KMS:AGP:R300:PPC] random X freeze by a GPU lockup2019-11-19T16:18:13ZBugzilla Migration User[RADEON:KMS:AGP:R300:PPC] random X freeze by a GPU lockup## Submitted by DaNiMoTh
Assigned to **Default DRI bug account**
**[Link to original bug (#30227)](https://bugs.freedesktop.org/show_bug.cgi?id=30227)**
## Description
Created attachment 38743<br>
dmesg after the fail<br>
<br>
App...## Submitted by DaNiMoTh
Assigned to **Default DRI bug account**
**[Link to original bug (#30227)](https://bugs.freedesktop.org/show_bug.cgi?id=30227)**
## Description
Created attachment 38743<br>
dmesg after the fail<br>
<br>
Apparently random GPU lockup (ati r300), with X.org freeze.<br>
<br>
It happens more frequently if I compile and I switch over many applications (firefox, terminal, opera). Attached there is the dmesg after the fail (I could continue to work on others console - ctrl+alt+f1,2,3..).<br>
<br>
**Attachment 38743**, "dmesg after the fail": <br>
[dmesg_after_fail](/uploads/8956874b0884122774cf5b97ba40e476/dmesg_after_fail)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/155radeon/KMS: Screen hotplugging does not work2019-11-19T16:18:03ZBugzilla Migration Userradeon/KMS: Screen hotplugging does not work## Submitted by Daniel Klaffenbach
Assigned to **Default DRI bug account**
**[Link to original bug (#29941)](https://bugs.freedesktop.org/show_bug.cgi?id=29941)**
## Description
I noticed that in recent kernel versions the runtime...## Submitted by Daniel Klaffenbach
Assigned to **Default DRI bug account**
**[Link to original bug (#29941)](https://bugs.freedesktop.org/show_bug.cgi?id=29941)**
## Description
I noticed that in recent kernel versions the runtime detection of newly added monitors does not work properly.<br>
<br>
When I plug in my TV (DVI2HDMI) after booting I cannot enable it. xrandr correctly shows a new screen and I can even enable the output, but the TV screen stays black. Restarting X does not help.<br>
<br>
The driver also seems to recognize the port status after plugging it in (/sys/class/drm/card0-DVI-I-2/status) changes from "disconnected" to "connected".<br>
<br>
When I plug the HDMI cable in _before_ booting my computer the TV works just fine.<br>
<br>
GFX: Radeon HD 3870<br>
Linux: 2.6-git (issue appeared in 2.6.35) with KMS<br>
Mesa: git<br>
libdrm: git<br>
xf86-video-ati: githttps://gitlab.freedesktop.org/drm/amd/-/issues/153[RADEON:KMS::EDID] i2c bit banging + preempt kernel -> i2c failure (random XR...2019-11-19T16:17:54ZBugzilla Migration User[RADEON:KMS::EDID] i2c bit banging + preempt kernel -> i2c failure (random XRandR failures)## Submitted by Arno Schuring
Assigned to **Default DRI bug account**
**[Link to original bug (#29787)](https://bugs.freedesktop.org/show_bug.cgi?id=29787)**
## Description
A few weeks ago, X started displaying weird errors during...## Submitted by Arno Schuring
Assigned to **Default DRI bug account**
**[Link to original bug (#29787)](https://bugs.freedesktop.org/show_bug.cgi?id=29787)**
## Description
A few weeks ago, X started displaying weird errors during normal use. These range from simple output resets to application crashes due to X BadAlloc responses. In detail, this is what I see happening:<br>
<br>
- output blink. Usually the screen goes dark for about a second. When the screen returns, I see either:<br>
- display position getting cancelled (xrandr --pos 0x0) on my left screen<br>
when this happens I can usually get it back to the correct position via the xrandr command line tool, but sometimes that triggers a WM crash<br>
- display rotation getting cancelled (xrandr --rotate normal) on the right screen. When this happens:<br>
- quodlibet (python-gtk app) crashing with BadAlloc (serial 255 error_code 11 request_code 53 minor_code 0). It will keep crashing like this until I restart X<br>
- whatever other app I had running on the right screen has disappeared as well<br>
- window manager (e17) crashing. It can recover succesfully, though<br>
- when I re-enable screen rotation, the display gets completely garbled<br>
<br>
I have started seeing this happen with 2.6.35-rc3 (was running 2.6.34-rc6 before that), and with 2.6.35.1 this happens a lot less frequently (from once a day to twice in a week).<br>
<br>
From the latest crash, I can give the following info from xsession-errors:<br>
(E17 init)<br>
E17 INIT: XINERAMA CHOSEN: [1], 1080x1920+1280+0<br>
E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+896<br>
(output blinking starts)<br>
E17 INIT: XINERAMA SCREEN: [0], 1280x1024+0+0<br>
E17 INIT: XINERAMA CHOSEN: [153045780], 0x153045764+0+153046580<br>
(e17 crash, try to recover)<br>
E17 INIT: XINERAMA CHOSEN: [1], 1920x1080+1280+0<br>
E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+0<br>
(rotation lost on [1], position lost on [0])<br>
E17 INIT: XINERAMA CHOSEN: [1], 1080x1920+1280+0<br>
E17 INIT: XINERAMA CHOSEN: [141138596], 0x141138580+0+141139396<br>
E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+896<br>
(restoring rotation confuses E17)<br>
###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation);<br>
6 requests ago: file nsX11ErrorHandler.cpp, line 182<br>
UNKNOWN [/usr/lib/xulrunner-1.9.2/libxul.so +0x001CA781]<br>
(firefox crashing)<br>
<br>
Now, the reason for the E17 crash looks like a use-after-free bug. Question is: who is freeing the Xinerama structures, and why are they freed at all? I never had these problems before, and when using stock 2.6.32 (from Debian) I don't have these problems either, so I'm ruling out hardware failure.<br>
<br>
<br>
I can see the following lines logged by the kernel (KMS enabled on radeon 9550):<br>
[12045.280155] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID<br>
[13500.386132] [drm:radeon_vga_detect] *ERROR* VGA-1: probed a monitor but no|invalid EDID<br>
[13797.568760] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID<br>
And I believe these are harmless (and reported in #27708). I can see these messages being reported for as long my kernel logs go back. But when the crashes occur, they are followed by these lines:<br>
[35753.097508] i2c i2c-1: sendbytes: NAK bailout.<br>
[35762.752866] i2c i2c-1: sendbytes: NAK bailout.<br>
[35772.912023] i2c i2c-1: readbytes: ack/nak timeout<br>
Which I believe are not so harmless. Or they could be a red herring, I'm not qualified to tell.<br>
<br>
Since the same time, I've been seeing a lot of lines logged by g-s-d, like<br>
gdk_pixbuf_format_get_name: assertion `format != NULL' failed<br>
But I do not believe these are relevant.https://gitlab.freedesktop.org/drm/amd/-/issues/1482.6.35 with RV630 AGP does not enable KMS/DRM2019-11-19T16:17:46ZBugzilla Migration User2.6.35 with RV630 AGP does not enable KMS/DRM## Submitted by Juho-Mikko Pellinen
Assigned to **Default DRI bug account**
**[Link to original bug (#29579)](https://bugs.freedesktop.org/show_bug.cgi?id=29579)**
## Description
Created attachment 37860<br>
2.6.35 Xorg.0.log with...## Submitted by Juho-Mikko Pellinen
Assigned to **Default DRI bug account**
**[Link to original bug (#29579)](https://bugs.freedesktop.org/show_bug.cgi?id=29579)**
## Description
Created attachment 37860<br>
2.6.35 Xorg.0.log with radeon.modeset=0<br>
<br>
I'm having problems with getting KMS to work with 2.6.35.<br>
I have earlier configuration with 2.6.34 and KMS works as it should. When booting up I get framebuffer console and X starts without errors.<br>
<br>
Steps to reproduce:<br>
1. copy working config from 2.6.34 to 2.6.35<br>
2. make oldconfig and double check the differing options, none related to drm/radeon<br>
3. compile kernel, boot it with different configurations<br>
4. drm does not initialize, framebuffer console does not came up, X can't open dri<br>
<br>
6. If I boot with radeon.modeset=0 drm initializes.<br>
<br>
I have tried number of kernel configs without any success. Prior to this I consulted #radeon, but it couldn't find any problems with my configuration. Normally I compile things as modules and it works quite well.<br>
AGP-drivers are compiled as modules/in kernel and load before radeon/drm.<br>
I have tried 2.6.35 vanilla, -rc2, -rc4, -rc6, -rc6, -gentoo-r1 . They all fail the same way.<br>
<br>
Any ideas how to get KMS working again?<br>
<br>
My hardware:<br>
RV630 AGP (HD2600 Pro AGP)<br>
nForce3 chipset<br>
CPU Athlon64 3xxx+<br>
<br>
lscpi:<br>
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)<br>
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)<br>
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)<br>
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)<br>
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)<br>
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2)<br>
00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)<br>
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)<br>
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)<br>
00:0a.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller (rev a2)<br>
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2)<br>
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)<br>
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration<br>
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map<br>
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller<br>
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control<br>
01:00.0 VGA compatible controller: ATI Technologies Inc RV630 PRO AGP [Radeon HD 2600 PRO AGP]<br>
02:06.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86)<br>
02:07.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)<br>
02:07.1 Input device controller: Creative Labs SB Audigy Game Port (rev 03)<br>
02:07.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port<br>
02:08.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)<br>
<br>
**Attachment 37860**, "2.6.35 Xorg.0.log with radeon.modeset=0": <br>
[Xorg.0.log](/uploads/4cda4af3a072ac20771ec8a9b1635655/Xorg.0.log)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/146Linux 2.6.34 kernel Radeon KMS driver freezes my computer sometimes2019-11-19T16:17:39ZBugzilla Migration UserLinux 2.6.34 kernel Radeon KMS driver freezes my computer sometimes## Submitted by 045..@..tti.fi
Assigned to **Default DRI bug account**
**[Link to original bug (#29445)](https://bugs.freedesktop.org/show_bug.cgi?id=29445)**
## Description
Created attachment 37682<br>
/var/log/dmesg<br>
<br>
I u...## Submitted by 045..@..tti.fi
Assigned to **Default DRI bug account**
**[Link to original bug (#29445)](https://bugs.freedesktop.org/show_bug.cgi?id=29445)**
## Description
Created attachment 37682<br>
/var/log/dmesg<br>
<br>
I use the kernel radeon driver with a Radeon Mobility R300 on a Toshiba laptop. The driver in 2.6.32 works fine and also the non-KMS driver in 2.6.34. However, when I enable the KMS driver (and disable the framebuffer drivers) in the 2.6.34 kernel, my computer freezes after a while of using X. If I don't start X the new KMS driver works fine.<br>
<br>
The outputs of dmesg, Xorg.0.log, and glxinfo are attached separately.<br>
<br>
In the case when I collected the above output, the bug manifested when I changed back to the virtual desktop of a running audio application (foobar2000 under wine). Access to the USB port with an external hard disk died at that moment. Usually the entire computer freezes (including keyboard, mouse, etc), but sometimes the bug seems to just disable the USB system. It only happens when the KMS driver is active so I file the bug here and not at the USB system or elsewhere.<br>
<br>
**Attachment 37682**, "/var/log/dmesg": <br>
[dmesg](/uploads/36f1805bfde75cd6212512ba09d0205a/dmesg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/144After pm-suspend the second monitor shows garbled output on evergreen card (kms)2019-11-19T16:17:31ZBugzilla Migration UserAfter pm-suspend the second monitor shows garbled output on evergreen card (kms)## Submitted by boris64
Assigned to **Default DRI bug account**
**[Link to original bug (#29217)](https://bugs.freedesktop.org/show_bug.cgi?id=29217)**
## Description
Created attachment 37311<br>
digicam picture of both monitors<b...## Submitted by boris64
Assigned to **Default DRI bug account**
**[Link to original bug (#29217)](https://bugs.freedesktop.org/show_bug.cgi?id=29217)**
## Description
Created attachment 37311<br>
digicam picture of both monitors<br>
<br>
After resuming a previous (via pm-suspend) suspended system <br>
the second monitor only shows a garbled picture.<br>
Running xrandr to switch resolution seems to work, but<br>
the picture still ist truncated.<br>
This is a kms/multihead configuration.<br>
<br>
Used software:<br>
Kernel-2.6.35-rc5<br>
latest xf86-video-ati from git<br>
latest libdrm from git<br>
latest mesa from git<br>
<br>
**Attachment 37311**, "digicam picture of both monitors": <br>
![evergreen_multihead_after_resume](/uploads/62401a778cd31e4e65fcbb896b4884f0/evergreen_multihead_after_resume.jpg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/143RC410: 3D apps do not run after upgrade to 2.6.35-rc52019-11-19T16:17:22ZBugzilla Migration UserRC410: 3D apps do not run after upgrade to 2.6.35-rc5## Submitted by Tom Stellard `@tstellar`
Assigned to **Default DRI bug account**
**[Link to original bug (#29095)](https://bugs.freedesktop.org/show_bug.cgi?id=29095)**
## Description
Created attachment 37103<br>
Output from glxge...## Submitted by Tom Stellard `@tstellar`
Assigned to **Default DRI bug account**
**[Link to original bug (#29095)](https://bugs.freedesktop.org/show_bug.cgi?id=29095)**
## Description
Created attachment 37103<br>
Output from glxgears with RADEON_DEBUG=all<br>
<br>
I just upgraded from 2.6.33 to 2.6.35-rc5, and whenever I try to run glxgears or any of the mesa demos only a black window is displayed. There is nothing interesting in my dmesg log. I am using the latest git versions of libdrm, mesa, xf86-video-ati, and X server 1.8.1.902. My card is a Radeon Xpress 200M IGP (RC410) I can give bisecting the kernel a try, but first I wanted to see if anyone had any ideas about what might be wrong. Previously, I was running a patched version of 2.6.33 to work around this bug: https://bugzilla.kernel.org/show_bug.cgi?id=15626 . The fix for this bug made it into one of the 2.6.35-rc* releases.<br>
<br>
**Attachment 37103**, "Output from glxgears with RADEON_DEBUG=all": <br>
[glxgears.all](/uploads/3db934d7022bbfff0f165b0572a696aa/glxgears.all)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/140[RADEON:KMS:RV670:MODESET] garbled screen after resuming from suspend2019-11-19T16:17:13ZBugzilla Migration User[RADEON:KMS:RV670:MODESET] garbled screen after resuming from suspend## Submitted by Daniel Klaffenbach
Assigned to **Default DRI bug account**
**[Link to original bug (#29026)](https://bugs.freedesktop.org/show_bug.cgi?id=29026)**
## Description
Created attachment 36970<br>
system log<br>
<br>
Usi...## Submitted by Daniel Klaffenbach
Assigned to **Default DRI bug account**
**[Link to original bug (#29026)](https://bugs.freedesktop.org/show_bug.cgi?id=29026)**
## Description
Created attachment 36970<br>
system log<br>
<br>
Using mesa-git, libdrm-git and xf86-video-ati-git I always get a garbled screen (including framebuffer console) after resume. I took a screenshot, but obviously it looks normal.<br>
<br>
Video card: Radeon HD3870<br>
Kernel: Linux-git (2.6.35-rc4+), KMS enabled by default<br>
<br>
There is no crash or lockup, it's just sort of impossible to read anything on the screen after resuming.<br>
<br>
**Attachment 36970**, "system log": <br>
[dmesg.txt](/uploads/e44496eb896b4560250c5377cb3ca857/dmesg.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/139latest d-r-t has regular X crashes2019-11-19T16:17:03ZBugzilla Migration Userlatest d-r-t has regular X crashes## Submitted by Aidan Marks
Assigned to **Default DRI bug account**
**[Link to original bug (#29001)](https://bugs.freedesktop.org/show_bug.cgi?id=29001)**
## Description
after updating to latest d-r-t, X crashes regularly, often ...## Submitted by Aidan Marks
Assigned to **Default DRI bug account**
**[Link to original bug (#29001)](https://bugs.freedesktop.org/show_bug.cgi?id=29001)**
## Description
after updating to latest d-r-t, X crashes regularly, often just by starting firefox and waiting for it to restore all the previous open tabs.<br>
<br>
xorg-server 1.8.1.902<br>
git libdrm/mesa/ddx<br>
kde 4.4.5 on rv790.<br>
<br>
Backtrace:<br>
[ 33638.299] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a1358]<br>
[ 33638.299] 1: /usr/bin/X (0x400000+0x636f9) [0x4636f9]<br>
[ 33638.299] 2: /lib/libpthread.so.0 (0x7fc9ad310000+0xf120) [0x7fc9ad31f120]<br>
[ 33638.299] 3: /usr/lib/libpixman-1.so.0 (0x7fc9ac3a6000+0x3ce53) [0x7fc9ac3e2e53]<br>
[ 33638.299] 4: /usr/lib/libpixman-1.so.0 (0x7fc9ac3a6000+0x31091) [0x7fc9ac3d7091]<br>
[ 33638.299] 5: /usr/lib/libpixman-1.so.0 (pixman_image_composite32+0xfe3) [0x7fc9ac3d91c3]<br>
[ 33638.299] 6: /usr/lib64/xorg/modules/libfb.so (fbComposite+0x225) [0x7fc9a99ad8b5]<br>
[ 33638.299] 7: /usr/lib64/xorg/modules/libexa.so (0x7fc9a9780000+0x10701) [0x7fc9a9790701]<br>
[ 33638.299] 8: /usr/lib64/xorg/modules/libexa.so (0x7fc9a9780000+0xe15e) [0x7fc9a978e15e]<br>
[ 33638.299] 9: /usr/bin/X (0x400000+0xd4b80) [0x4d4b80]<br>
[ 33638.299] 10: /usr/bin/X (0x400000+0xce2ad) [0x4ce2ad]<br>
[ 33638.300] 11: /usr/bin/X (0x400000+0x2f5ec) [0x42f5ec]<br>
[ 33638.300] 12: /usr/bin/X (0x400000+0x24de5) [0x424de5]<br>
[ 33638.300] 13: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7fc9ab9dbbbd]<br>
[ 33638.300] 14: /usr/bin/X (0x400000+0x24999) [0x424999]<br>
[ 33638.300] Bus error at address 0x7fc99fb86b04<br>
[ 33638.300] <br>
Fatal server error:<br>
[ 33638.300] Caught signal 7 (Bus error). Server aborting<br>
[ 33638.300] <br>
[ 33638.300]https://gitlab.freedesktop.org/drm/amd/-/issues/138rv515 (Mobility x1400) Display corruption after some time2019-11-19T16:16:54ZBugzilla Migration Userrv515 (Mobility x1400) Display corruption after some time## Submitted by Nicos Gollan
Assigned to **Default DRI bug account**
**[Link to original bug (#28940)](https://bugs.freedesktop.org/show_bug.cgi?id=28940)**
## Description
Created attachment 36799<br>
lspci output (graphics only)<...## Submitted by Nicos Gollan
Assigned to **Default DRI bug account**
**[Link to original bug (#28940)](https://bugs.freedesktop.org/show_bug.cgi?id=28940)**
## Description
Created attachment 36799<br>
lspci output (graphics only)<br>
<br>
After some uptime (upwards of an hour so far), I get different kinds of display corruption on a laptop with a Radeon x1400.<br>
<br>
Currently, I'm looking at a somewhat grainy picture which looks like a badly dithered low-colour version of the screen content. There are noticeable vertical stripes, and the whole image is shimmering. The system is working fine otherwise.<br>
<br>
In an earlier instance, I had a pulsating green gradient covering the bottom of the screen. In addition, screen response was slow, like the proper content was only updating evers second or so.<br>
<br>
The effect does not show in screenshots.<br>
<br>
This is on a Debian-built 2.6.34 686 kernel, running X.org 1.7.7 and the "radeon" driver 6.13.0, libdrm2 2.4.21 from Debian packages.<br>
<br>
I'm attaching lspci output for the card, as well as dmesg and the Xorg.log from the currently "broken" running system.<br>
<br>
**Attachment 36799**, "lspci output (graphics only)": <br>
[lspci-mobility-x1400.txt](/uploads/52974d445d91a362d8a5eeb2a4d56fe6/lspci-mobility-x1400.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/137[ati-dri] R100 OpenGL Crash buffer overflow2019-11-19T16:16:46ZBugzilla Migration User[ati-dri] R100 OpenGL Crash buffer overflow## Submitted by Tuxality
Assigned to **Default DRI bug account**
**[Link to original bug (#28928)](https://bugs.freedesktop.org/show_bug.cgi?id=28928)**
## Description
DRI is working with direct rendering and hardware acceleration...## Submitted by Tuxality
Assigned to **Default DRI bug account**
**[Link to original bug (#28928)](https://bugs.freedesktop.org/show_bug.cgi?id=28928)**
## Description
DRI is working with direct rendering and hardware acceleration, but only working OpenGL application is glxgears and small example written by me using gtkglext. When I try to run yabause or any application that uses OpenGL then I've got this:<br>
<br>
*********************************WARN_ONCE*********************************<br>
File radeon_swtcl.c function r100_swtcl_flush line 322<br>
Rendering was 13 commands larger than predicted size. We might overflow command buffer.<br>
***************************************************************************<br>
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info.<br>
<br>
And then crash.<br>
<br>
When I write dmesg I got this:<br>
<br>
[drm:r100_cs_track_texture_check] *ERROR* No texture bound to unit 0<br>
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !<br>
<br>
I'm using module radeon under ATI Radeon M6 (R100) and packages version under Archlinux i686:<br>
<br>
ati-dri 7.8.2-1<br>
xf86-video-ati 6.13.0-1<br>
mesa 7.8.2-1<br>
libgl 7.8.2-1<br>
<br>
The DRI module is from 20090101, but was working ok with version from 20061018, so with Mesa 7.2 (2008).<br>
<br>
I've tried to compile Mesa 7.2, but the DRI was not working (only swrast).<br>
<br>
Please help me, I can't even watch youtube with proper speed. Only alternative for me is Debian Lenny that has everything (DRI) working ok, because it has the old version.