amd issueshttps://gitlab.freedesktop.org/drm/amd/-/issues2019-11-19T16:35:30Zhttps://gitlab.freedesktop.org/drm/amd/-/issues/287Radeon HD6450 KMS garbled screen on boot.2019-11-19T16:35:30ZBugzilla Migration UserRadeon HD6450 KMS garbled screen on boot.## Submitted by sow..@..st.edu
Assigned to **Default DRI bug account**
**[Link to original bug (#52467)](https://bugs.freedesktop.org/show_bug.cgi?id=52467)**
## Description
Just recently upgraded to a Radeon HD6450. Upon boot, as...## Submitted by sow..@..st.edu
Assigned to **Default DRI bug account**
**[Link to original bug (#52467)](https://bugs.freedesktop.org/show_bug.cgi?id=52467)**
## Description
Just recently upgraded to a Radeon HD6450. Upon boot, as soon as fbcon takes over, the screen gets corrupted. (note X is not started on boot). SSHing into the box and starting and restarting X a couple time sometimes fixes the issue, sometimes locks of the machine.https://gitlab.freedesktop.org/drm/amd/-/issues/291X lockups /2019-11-19T16:35:33ZBugzilla Migration UserX lockups /## Submitted by #Paul
Assigned to **Default DRI bug account**
**[Link to original bug (#53122)](https://bugs.freedesktop.org/show_bug.cgi?id=53122)**
## Description
Created attachment 65122<br>
X log file<br>
<br>
Upon swapping vi...## Submitted by #Paul
Assigned to **Default DRI bug account**
**[Link to original bug (#53122)](https://bugs.freedesktop.org/show_bug.cgi?id=53122)**
## Description
Created attachment 65122<br>
X log file<br>
<br>
Upon swapping video cards, I have started getting intermittent freezes of X<br>
on my Slackware65 13.37 AMD Opteron box (kernel 3.4.4)<br>
<br>
The display freezes up totally, including mouse pointer; occasionally there are short (eg ~10s) freezes which might be related, and usually it happens when<br>
web browsing (mostly when there is embedded flash on the bbc.co.uk olympics pages) <br>
<br>
I hope the below is sufficient info; I need to swap video cards back because I can't afford such lockups ATM.<br>
<br>
<br>
Here's the lspci lines:<br>
0a:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4550] (prog-if 00 [VGA controller])<br>
Subsystem: Giga-byte Technology Device 21ae<br>
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+<br>
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- `<MAbort- >`SERR- <PERR- INTx-<br>
Latency: 0, Cache Line Size: 64 bytes<br>
Interrupt: pin A routed to IRQ 74<br>
Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M]<br>
Region 2: Memory at f0500000 (64-bit, non-prefetchable) [size=64K]<br>
Region 4: I/O ports at 4000 [size=256]<br>
[virtual] Expansion ROM at f0520000 [disabled] [size=128K]<br>
Capabilities: `<access denied>`<br>
Kernel driver in use: radeon<br>
Kernel modules: radeon<br>
<br>
<br>
This appears in /var/log/messages (if I wait 20+mins, it seems to unfreeze fairly reliably)<br>
<br>
Aug 3 17:28:11 fishpond acpid: client 2126[0:0] has disconnected<br>
Aug 3 17:28:11 fishpond acpid: client connected from 2126[0:0]<br>
Aug 3 17:28:11 fishpond acpid: 1 client rule loaded<br>
Aug 3 17:48:19 fishpond kernel: [68040.346054] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 17:50:19 fishpond kernel: [68160.346048] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 17:52:19 fishpond kernel: [68280.346054] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 17:54:19 fishpond kernel: [68400.346054] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 17:56:19 fishpond kernel: [68520.346048] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 17:58:19 fishpond kernel: [68640.346053] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 18:00:19 fishpond kernel: [68760.346054] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 18:02:19 fishpond kernel: [68880.346047] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 18:04:19 fishpond kernel: [69000.346052] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
Aug 3 18:06:19 fishpond kernel: [69120.346052] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
<br>
And instances of this in /var/log/syslog<br>
<br>
[69120.346044] INFO: task X:2111 blocked for more than 120 seconds.<br>
[69120.346049] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br>
[69120.346052] X D ffffffff816065c0 0 2111 2098 0x00400004<br>
[69120.346058] ffff8801743d9b58 0000000000000082 ffff8801743d9ae8 0000000000011dc0<br>
[69120.346062] 0000000000011dc0 ffff880179dd06d0 0000000000011dc0 ffff8801743d9fd8<br>
[69120.346066] ffff8801743d8000 0000000000011dc0 ffff8801743d9fd8 0000000000011dc0<br>
[69120.346071] Call Trace:<br>
[69120.346083] [`<ffffffff81562859>`] schedule+0x29/0x70<br>
[69120.346087] [`<ffffffff81562ade>`] schedule_preempt_disabled+0xe/0x10<br>
[69120.346091] [`<ffffffff815613b9>`] __mutex_lock_slowpath+0xd9/0x150<br>
[69120.346095] [`<ffffffff815610fb>`] mutex_lock+0x2b/0x50<br>
[69120.346125] [`<ffffffffa0222820>`] radeon_bo_create+0x150/0x2a0 [radeon]<br>
[69120.346141] [`<ffffffffa0233e6a>`] radeon_gem_object_create+0x5a/0x100 [radeon]<br>
[69120.346155] [`<ffffffffa0234254>`] radeon_gem_create_ioctl+0x54/0xe0 [radeon]<br>
[69120.346160] [`<ffffffff815610ee>`] ? mutex_lock+0x1e/0x50<br>
[69120.346174] [`<ffffffffa023470c>`] ? radeon_gem_get_tiling_ioctl+0xbc/0xf0 [radeon]<br>
[69120.346189] [`<ffffffffa013405f>`] drm_ioctl+0x2cf/0x520 [drm]<br>
[69120.346204] [`<ffffffffa0234200>`] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]<br>
[69120.346210] [`<ffffffff81142ad7>`] do_vfs_ioctl+0x97/0x540<br>
[69120.346213] [`<ffffffff81143011>`] sys_ioctl+0x91/0xa0<br>
[69120.346217] [`<ffffffff815640d2>`] system_call_fastpath+0x16/0x1b<br>
<br>
<br>
There is no error logged by X, but here its (but note that I run 6 simultaneaous X's on vt7-vt12). I've attached a log file<br>
<br>
**Attachment 65122**, "X log file": <br>
[Xorg.0.log.old](/uploads/5cf1c1f575c03f0c3287268b480ef244/Xorg.0.log.old)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/295[radeon][RV620] Resuming from suspend/hibernation randomly fails since kernel...2019-11-19T16:35:41ZBugzilla Migration User[radeon][RV620] Resuming from suspend/hibernation randomly fails since kernel 3.5.0## Submitted by Loïc Yhuel `@hwti`
Assigned to **Default DRI bug account**
**[Link to original bug (#54133)](https://bugs.freedesktop.org/show_bug.cgi?id=54133)**
## Description
Since 3.5.0 kernel (currently 3.5.2-3.fc17.x86_64), ...## Submitted by Loïc Yhuel `@hwti`
Assigned to **Default DRI bug account**
**[Link to original bug (#54133)](https://bugs.freedesktop.org/show_bug.cgi?id=54133)**
## Description
Since 3.5.0 kernel (currently 3.5.2-3.fc17.x86_64), resuming from suspend or hibernation randomly fails. There is no display, and the screen flashes every few seconds (probably due to the backlight).<br>
<br>
Hardware:<br>
Toshiba Satellite Pro A300 laptop<br>
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series<br>
<br>
Here are the relevant kernel messages :<br>
[drm] PCIE GART of 512M enabled (table at 0x0000000000040000).<br>
radeon 0000:01:00.0: WB enabled<br>
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0xffff880134cc6c00<br>
[drm] ring test on 0 succeeded in 0 usecs<br>
[drm] ib test on ring 0 succeeded in 0 usecs<br>
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!<br>
radeon 0000:01:00.0: GPU reset succeed<br>
[drm] PCIE GART of 512M enabled (table at 0x0000000000040000).<br>
...https://gitlab.freedesktop.org/drm/amd/-/issues/299[RADEON:KMS:RV730XT:HDMI:AUDIO] Screaming audio IRQ with 3.5.3 kernel2019-11-19T16:35:56ZBugzilla Migration User[RADEON:KMS:RV730XT:HDMI:AUDIO] Screaming audio IRQ with 3.5.3 kernel## Submitted by Chris Rankin
Assigned to **Default DRI bug account**
**[Link to original bug (#54675)](https://bugs.freedesktop.org/show_bug.cgi?id=54675)**
## Description
Created attachment 66851<br>
dmesg output when radeon.audi...## Submitted by Chris Rankin
Assigned to **Default DRI bug account**
**[Link to original bug (#54675)](https://bugs.freedesktop.org/show_bug.cgi?id=54675)**
## Description
Created attachment 66851<br>
dmesg output when radeon.audio=1<br>
<br>
I have recently added a HD4670 AGP to one of my older machines, and I am noticing problems with the HDMI audio device. Specifically:<br>
<br>
irq 17: nobody cared (try booting with the "irqpoll" option)<br>
Pid: 0, comm: swapper/0 Not tainted 3.5.3 #2<br>
Call Trace:<br>
[`<c1063806>`] ? __report_bad_irq+0x11/0x94<br>
[`<c1063a2d>`] ? note_interrupt+0x120/0x19b<br>
[`<c1062325>`] ? handle_irq_event_percpu+0xe8/0xfb<br>
[`<c1062361>`] ? handle_irq_event+0x29/0x40<br>
[`<c10640fc>`] ? handle_level_irq+0x93/0x93<br>
[`<c1064163>`] ? handle_fasteoi_irq+0x67/0x90<br>
`<IRQ>` [`<c1003625>`] ? do_IRQ+0x2e/0x83<br>
[`<c1229829>`] ? common_interrupt+0x29/0x30<br>
[`<c106007b>`] ? audit_update_watch+0x59/0x285<br>
[`<c1007479>`] ? default_idle+0x23/0x3b<br>
[`<c1007b38>`] ? cpu_idle+0x4b/0x7e<br>
[`<c1314877>`] ? start_kernel+0x2a4/0x2a7<br>
handlers:<br>
[`<f8575b75>`] azx_interrupt [snd_hda_intel]<br>
Disabling IRQ #17<br>
<br>
This is with radeon.audio=0. With radeon.audio=1, the KMS IRQ has similar problem and is also disabled.<br>
<br>
**Attachment 66851**, "dmesg output when radeon.audio=1": <br>
[HD4670-AUDIO.log](/uploads/19696883ad130a79de1903e75ba2ca63/HD4670-AUDIO.log)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/301video playback causes total freeze on RV3502019-11-19T16:36:01ZBugzilla Migration Uservideo playback causes total freeze on RV350## Submitted by spa..@..hoo.de
Assigned to **Default DRI bug account**
**[Link to original bug (#55006)](https://bugs.freedesktop.org/show_bug.cgi?id=55006)**
## Description
Video playback and switching between tabs while browsing...## Submitted by spa..@..hoo.de
Assigned to **Default DRI bug account**
**[Link to original bug (#55006)](https://bugs.freedesktop.org/show_bug.cgi?id=55006)**
## Description
Video playback and switching between tabs while browsing often leads to total freeze of my system. Even the magic SysRQ keys wont work then.<br>
<br>
steps to reproduce:<br>
Watching movies with vlc, or switching between tabs is often enough to freeze the system.<br>
<br>
It all started with introducing KernelModeSetting to Linux. This bug has been affecting me since i upgraded from Debian Lenny to Squeeze and thus to Kernel 2.6.32. I could avoid that bug however by adding "radeon.modeset=0" at the boot prompt from 2.6.32.<br>
<br>
Now with Linux 3.2 even passing "radeon.modeset=0" at the boot prompt does not work any more for me. <br>
<br>
I reported the bug to Debian and they told me to try Linux 3.5, which also freezes often. For reference here is the link to my bug report:<br>
<br>
http://bugs.debian.org/680097 <br>
<br>
This is a very serious regression for my RV350 and causes file system corruption & data loss (for my work progress)<br>
<br>
I cannot add a log from the freeze, since nothing gets logged then. If you know a way i could give you one, let me know.https://gitlab.freedesktop.org/drm/amd/-/issues/3033650HD card stalls while playing urbanterror2019-11-19T16:36:05ZBugzilla Migration User3650HD card stalls while playing urbanterror## Submitted by dagg
Assigned to **Default DRI bug account**
**[Link to original bug (#55688)](https://bugs.freedesktop.org/show_bug.cgi?id=55688)**
## Description
Created attachment 68149<br>
relevant log part<br>
<br>
I have a m...## Submitted by dagg
Assigned to **Default DRI bug account**
**[Link to original bug (#55688)](https://bugs.freedesktop.org/show_bug.cgi?id=55688)**
## Description
Created attachment 68149<br>
relevant log part<br>
<br>
I have a multiseat setup with two radeon cards, 5450HD and 3650HD, I was playing urbanterror on the seat that uses 3650HD and the gpu stalled.<br>
<br>
my kernel version is 3.6.0, libdrm, mesa and xf86-video-ati are from git where the last update was yesterday.<br>
<br>
I'm attaching the relevant part from /var/log/messages.<br>
<br>
yesterday I've played the same game on the same setup and it didn't stalled.<br>
<br>
**Attachment 68149**, "relevant log part": <br>
[radeon_stale](/uploads/9b921d4da763e13520d32b6393d0db6e/radeon_stale)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/304Mouse cursor corruption when moving between monitors2019-11-19T16:36:08ZBugzilla Migration UserMouse cursor corruption when moving between monitors## Submitted by Nikolaus Rath
Assigned to **Default DRI bug account**
**[Link to original bug (#55819)](https://bugs.freedesktop.org/show_bug.cgi?id=55819)**
## Description
Created attachment 68357<br>
Picture of corrupted cursor<...## Submitted by Nikolaus Rath
Assigned to **Default DRI bug account**
**[Link to original bug (#55819)](https://bugs.freedesktop.org/show_bug.cgi?id=55819)**
## Description
Created attachment 68357<br>
Picture of corrupted cursor<br>
<br>
I'm using a ATI Radeon HD 4350 with x.org 1.12.3.902 (1.12.4 RC 2) on Debian testing. I'm running a configuration with two monitors.<br>
<br>
Every once in a while, I experience mouse cursor corruption when moving the cursor from one screen to the other. The cursor then looks like in the attached photo. I order to get it back to normal, I have to move the cursor several times from one monitor to the other. There seems to be a specific path that I need to take, but I cannot find out which one it is exactly. <br>
<br>
The problem does not appear when specifying 'Option "SWcursor"' in xorg.conf.<br>
<br>
~~**Attachment 68357**~~, "Picture of corrupted cursor": <br>
![mouse_cursor_corruption](/uploads/34424dabfa38861ba46fc2b1f7e2d84d/mouse_cursor_corruption.jpg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/307(SUMO2) Black screen on X Launch, corrupted VTs when using KMS2019-11-19T16:36:12ZBugzilla Migration User(SUMO2) Black screen on X Launch, corrupted VTs when using KMS## Submitted by Tony Thomas
Assigned to **Default DRI bug account**
**[Link to original bug (#56081)](https://bugs.freedesktop.org/show_bug.cgi?id=56081)**
## Description
Created attachment 68683<br>
Xorg.0.log<br>
<br>
Using AMD ...## Submitted by Tony Thomas
Assigned to **Default DRI bug account**
**[Link to original bug (#56081)](https://bugs.freedesktop.org/show_bug.cgi?id=56081)**
## Description
Created attachment 68683<br>
Xorg.0.log<br>
<br>
Using AMD A4-3420M APU, have NOT been able to use the R600 driver on either Suse (12.x, factory), Arch Linux (latest built, or git xorg/mesa/dri build), or Ubuntu (12.04, 12.10b2). ALL various combinations of xorg 1.12/1.13, xorg-video-ati, mesa, and kernel 3.5-3.6 give the same black screen after startup, transition to Xorg corrupts all VT's. <br>
<br>
KMS for Single user or non-X sessions works fine. Grub boot with "radeon.audio=0" does alleviate some corruption on VT7 (but not enough to be usable). Changing accel options or even disabling accel has no effect.<br>
<br>
Appears there is something specific to the A4-3420M(6410D, chipID 0x9644, identified by system as a Sumo2) that is affected by this.<br>
<br>
~~**Attachment 68683**~~, "Xorg.0.log": <br>
[Xorg.0.log](/uploads/11d23900842f74709bbf471ef0751df5/Xorg.0.log)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/309kernel > 3.4.7 breaks KMS on rv515 (r300)2019-11-19T16:37:01ZBugzilla Migration Userkernel > 3.4.7 breaks KMS on rv515 (r300)## Submitted by dmotd
Assigned to **Default DRI bug account**
**[Link to original bug (#56561)](https://bugs.freedesktop.org/show_bug.cgi?id=56561)**
## Description
I performed a system update (arch linux) but have experienced iss...## Submitted by dmotd
Assigned to **Default DRI bug account**
**[Link to original bug (#56561)](https://bugs.freedesktop.org/show_bug.cgi?id=56561)**
## Description
I performed a system update (arch linux) but have experienced issues with KMS on any kernel past 3.4.7 (all of 3.5 up till the current 3.6.3). The boot sequence stalls at the point where the KMS hooks usually kick in and referesh the screen. I can make the kernel boot with 'nomodeset' option.<br>
<br>
https://bugs.freedesktop.org/show_bug.cgi?id=54662 looks similar, but the none of the 3.6 kernels i've tried resove this issue.https://gitlab.freedesktop.org/drm/amd/-/issues/312Invalid command stream (bad START_3D) on DIS gpu2019-11-19T16:37:08ZBugzilla Migration UserInvalid command stream (bad START_3D) on DIS gpu## Submitted by Igor Murzov
Assigned to **Default DRI bug account**
**[Link to original bug (#56743)](https://bugs.freedesktop.org/show_bug.cgi?id=56743)**
## Description
Created attachment 69522<br>
dmesg output<br>
<br>
On my mu...## Submitted by Igor Murzov
Assigned to **Default DRI bug account**
**[Link to original bug (#56743)](https://bugs.freedesktop.org/show_bug.cgi?id=56743)**
## Description
Created attachment 69522<br>
dmesg output<br>
<br>
On my muxed hybrid system (Lenovo IdeaPad U455) X works fine with IGD gpu (RS780M), but screen gets garbled when DIS gpu (RV710) is active. In dmesg output there are lots of following messages:<br>
[drm:r600_packet3_check] *ERROR* bad START_3D<br>
[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !<br>
<br>
My system is:<br>
Lenovo IdeaPad U455 with RS780M and RV710 gpus.<br>
linux-3.7.0-rc3+<br>
libdrm-2.4.39<br>
xf86-video-ati-6.14.6<br>
mesa-9.0<br>
glu-9.0<br>
xorg-server-1.12.3<br>
<br>
**Attachment 69522**, "dmesg output": <br>
[dmesg-laptop-20121104-bad_START_3D](/uploads/89b465da54def28022374b3f79332207/dmesg-laptop-20121104-bad_START_3D)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/313FireGL Mobility T2: WebGL under firefox16 freezes system2019-11-19T16:37:12ZBugzilla Migration UserFireGL Mobility T2: WebGL under firefox16 freezes system## Submitted by mir..@..sin.de
Assigned to **Default DRI bug account**
**[Link to original bug (#56878)](https://bugs.freedesktop.org/show_bug.cgi?id=56878)**
## Description
Created attachment 69702<br>
kernel messages of the cras...## Submitted by mir..@..sin.de
Assigned to **Default DRI bug account**
**[Link to original bug (#56878)](https://bugs.freedesktop.org/show_bug.cgi?id=56878)**
## Description
Created attachment 69702<br>
kernel messages of the crash<br>
<br>
When opening http://lwn.net/Articles/522127/ with firefox16 the screen goes black for a moment and then reappears for a few seconds after which it goes black again. This cycle goes on a few times after which the system completely locks up (even Magic Sysrq seems to have no effect).<br>
<br>
I don't know if it is related but sometimes opening huge images in firefox causes X to crash, too. This, however, doesn't freeze the kernel and beside the crash itself everything works normally afterwards.<br>
<br>
kernel: 3.6.6<br>
xorg-server: 1.13.0<br>
xf86-video-ati: 7.0.0<br>
mesa: 9.0<br>
<br>
**Attachment 69702**, "kernel messages of the crash": <br>
[kernel-log](/uploads/671e609a2ce735e6ec5d7376021e29b1/kernel-log)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/3143.7 radeonfb broken on efivga screens2019-11-19T16:37:17ZBugzilla Migration User3.7 radeonfb broken on efivga screens## Submitted by Vladimir
Assigned to **Default DRI bug account**
**[Link to original bug (#57567)](https://bugs.freedesktop.org/show_bug.cgi?id=57567)**
## Description
Ubuntu 12.10<br>
MacPro3,1<br>
<br>
stock 3.5 kernel and 3.7-r...## Submitted by Vladimir
Assigned to **Default DRI bug account**
**[Link to original bug (#57567)](https://bugs.freedesktop.org/show_bug.cgi?id=57567)**
## Description
Ubuntu 12.10<br>
MacPro3,1<br>
<br>
stock 3.5 kernel and 3.7-rcX ppa kernel<br>
<br>
booting via efi with grub2<br>
<br>
ati cards have broken framebuffer on 3.7 (all is fine on 3.5)<br>
<br>
tried 2600xt, 6870, 6970 (all have efi part in rom, showing efi boot screen)<br>
<br>
on 3.7, when radeonfb activates, I see for a moment two sides of screen (left and right) swapped (not mirrored), then(when X start) only very few lines on top of screen is actualy showing something(I can see part of mouse pointer there), rest is filled with one color.<br>
<br>
Same result with all cards I mentioned.
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=56139
* https://bugs.freedesktop.org/show_bug.cgi?id=43655https://gitlab.freedesktop.org/drm/amd/-/issues/315One pixel column that belongs in one monitor shows up in the other instead2019-11-19T16:37:20ZBugzilla Migration UserOne pixel column that belongs in one monitor shows up in the other instead## Submitted by shankao
Assigned to **Default DRI bug account**
**[Link to original bug (#58652)](https://bugs.freedesktop.org/show_bug.cgi?id=58652)**
## Description
I have configured the laptop screen in the left and a external ...## Submitted by shankao
Assigned to **Default DRI bug account**
**[Link to original bug (#58652)](https://bugs.freedesktop.org/show_bug.cgi?id=58652)**
## Description
I have configured the laptop screen in the left and a external monitor in the right. On the left most part of the monitor, I can see 1 column of pixels that belong to the content that is in the right most part of the laptop.<br>
<br>
Strangely, it does not show up when I try to do a screenshot, but is quite evident when watching a fullscreen movie in the monitor, for example.<br>
<br>
Original bug report at Ubuntu's launchpad: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1085338https://gitlab.freedesktop.org/drm/amd/-/issues/316[RS780] Backtrace if firmware is not available on kernel-3.72019-11-19T16:37:24ZBugzilla Migration User[RS780] Backtrace if firmware is not available on kernel-3.7## Submitted by ojab `@ojab`
Assigned to **Default DRI bug account**
**[Link to original bug (#58747)](https://bugs.freedesktop.org/show_bug.cgi?id=58747)**
## Description
Created attachment 72109<br>
Related dmesg output<br>
<br>...## Submitted by ojab `@ojab`
Assigned to **Default DRI bug account**
**[Link to original bug (#58747)](https://bugs.freedesktop.org/show_bug.cgi?id=58747)**
## Description
Created attachment 72109<br>
Related dmesg output<br>
<br>
After updating to kernel 3.7 I get backtrace if booting without firmware available (related dmesg part in the attached file).<br>
Also reproducible with kernel 3.7.1.<br>
<br>
**Attachment 72109**, "Related dmesg output": <br>
[rs780.txt](/uploads/be3d1df1781141b5c6bb47d052dd9068/rs780.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/317Cannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID2019-11-19T16:37:28ZBugzilla Migration UserCannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID## Submitted by David Hagood
Assigned to **Default DRI bug account**
**[Link to original bug (#58914)](https://bugs.freedesktop.org/show_bug.cgi?id=58914)**
## Description
Created attachment 72358<br>
X Start up log messages<br>
<...## Submitted by David Hagood
Assigned to **Default DRI bug account**
**[Link to original bug (#58914)](https://bugs.freedesktop.org/show_bug.cgi?id=58914)**
## Description
Created attachment 72358<br>
X Start up log messages<br>
<br>
The Radeon driver will not load with the Radeon kernel drivers in Linux 3.8.0<br>
<br>
The following is an excerpt from the startup:<br>
<br>
[ 109.112] (II) Loading extension DRI2<br>
[ 109.112] (II) LoadModule: "radeon"<br>
[ 109.112] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so<br>
[ 109.112] (II) Module radeon: vendor="X.Org Foundation"<br>
[ 109.112] compiled for 1.12.3, module version = 7.0.99<br>
[ 109.112] Module class: X.Org Video Driver<br>
[ 109.112] ABI class: X.Org Video Driver, version 12.0<br>
[ 109.112] (II) RADEON: Driver for ATI Radeon chipsets:<br>
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),<br>
(many cards snipped)<br>
[ 109.114] (--) using VT number 8<br>
<br>
[ 109.119] (II) [KMS] Kernel modesetting enabled.<br>
[ 109.120] (II) RADEON(0): Creating default Display subsection in Screen section<br>
"Default Screen Section" for depth/fbbpp 24/32<br>
[ 109.120] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32<br>
[ 109.120] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)<br>
[ 109.120] (==) RADEON(0): Default visual is TrueColor<br>
[ 109.120] (==) RADEON(0): RGB weight 888<br>
[ 109.120] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)<br>
[ 109.120] (--) RADEON(0): Chipset: "ATI Radeon HD 4350" (ChipID = 0x954f)<br>
[ 109.120] drmOpenDevice: node name is /dev/dri/card0<br>
[ 109.120] drmOpenDevice: open result is 9, (OK)<br>
[ 109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0<br>
[ 109.120] drmOpenDevice: node name is /dev/dri/card0<br>
[ 109.120] drmOpenDevice: open result is 9, (OK)<br>
[ 109.120] drmOpenByBusid: drmOpenMinor returns 9<br>
[ 109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0<br>
[ 109.120] drmOpenDevice: node name is /dev/dri/card0<br>
[ 109.120] drmOpenDevice: open result is 9, (OK)<br>
[ 109.120] drmOpenByBusid: drmOpenMinor returns 9<br>
[ 109.120] drmOpenByBusid: Interface 1.4 failed, trying 1.1<br>
[ 109.120] drmOpenByBusid: drmGetBusid reports <br>
<br>
That last line is not a copy/paste issue - it literally is<br>
"[ 109.120] drmOpenByBusid: drmGetBusid reports "<br>
<br>
(as in, there is no bus ID given)<br>
<br>
Then the X Radeon driver looks for any other DRI node, fails, and dies.<br>
<br>
[ 109.120] drmOpenDevice: node name is /dev/dri/card1<br>
[ 109.125] drmOpenByBusid: drmOpenMinor returns -1<br>
(snip many other searches)<br>
[ 109.170] drmOpenDevice: node name is /dev/dri/card14<br>
[ 109.174] drmOpenByBusid: drmOpenMinor returns -1<br>
[ 109.174] drmOpenDevice: node name is /dev/dri/card15<br>
[ 109.178] drmOpenByBusid: drmOpenMinor returns -1<br>
[ 109.178] drmOpenDevice: node name is /dev/dri/card0<br>
[ 109.178] drmOpenDevice: open result is 9, (OK)<br>
[ 109.178] drmOpenDevice: node name is /dev/dri/card0<br>
[ 109.178] drmOpenDevice: open result is 9, (OK)<br>
[ 109.178] drmGetBusid returned ''<br>
[ 109.178] (EE) RADEON(0): [drm] failed to set drm interface version.<br>
[ 109.178] (EE) RADEON(0): Kernel modesetting setup failed<br>
[ 109.178] (II) UnloadModule: "radeon"<br>
[ 109.178] (EE) Screen(s) found, but none have a usable configuration.<br>
<br>
I have tried the following:<br>
1) adding the following parameters in /etc/modprobe.d/radeon.conf<br>
options radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1<br>
2) Adding the following to /etc/initramfs-tools/modules<br>
radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1<br>
and rebuilding the ramdisk.<br>
<br>
The kernel has the following configuration with respect to the Radeon drivers:<br>
CONFIG_DRM_RADEON=m<br>
CONFIG_DRM_RADEON_KMS=y<br>
# CONFIG_FB_RADEON is not set<br>
<br>
**Attachment 72358**, "X Start up log messages": <br>
[Xorg.0.log](/uploads/24bb40a1dc2caaddcea94fa2dc97c1f5/Xorg.0.log)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/318[radeon BUG] Sleeping function called from invalid context2019-11-19T16:37:32ZBugzilla Migration User[radeon BUG] Sleeping function called from invalid context## Submitted by ebi..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#59219)](https://bugs.freedesktop.org/show_bug.cgi?id=59219)**
## Description
Created attachment 72816<br>
dmesg output showing 2 inst...## Submitted by ebi..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#59219)](https://bugs.freedesktop.org/show_bug.cgi?id=59219)**
## Description
Created attachment 72816<br>
dmesg output showing 2 instances of radeon BUG during resume<br>
<br>
I am running linux-3.8-rc3 on AMD64 with various debugging options enabled, including CONFIG_DEBUG_SLAB. When resuming the system from suspend-to-memory, I run into a warning and stacktrace regarding kmem_cache_alloc() being called from an invalid context in ttm_bo_move_accel_cleanup(). dmesg output attached. Marked as minor because suspend still works properly (at least the times I've tried it).<br>
<br>
Based on the source code and object file it appears that the memory allocation is actually the kzalloc() at the beginning of ttm_buffer_object_transfer().<br>
<br>
Graphics card is:<br>
<br>
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series]<br>
<br>
**Attachment 72816**, "dmesg output showing 2 instances of radeon BUG during resume": <br>
[dmesg.gz](/uploads/aa6748dc37e4d745bdf3ce1558f5bf8e/dmesg.gz)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/321[snb efi gmux] imac 12,1 blank screen upon booting2019-11-19T16:37:53ZBugzilla Migration User[snb efi gmux] imac 12,1 blank screen upon booting## Submitted by William
Assigned to **Default DRI bug account**
**[Link to original bug (#59431)](https://bugs.freedesktop.org/show_bug.cgi?id=59431)**
## Description
Created attachment 73107<br>
kernel error message<br>
<br>
Hi,<...## Submitted by William
Assigned to **Default DRI bug account**
**[Link to original bug (#59431)](https://bugs.freedesktop.org/show_bug.cgi?id=59431)**
## Description
Created attachment 73107<br>
kernel error message<br>
<br>
Hi,<br>
<br>
i have been waiting a while for new kernels to come up and see if this problem got fixed, but that has not happened yet.<br>
<br>
I'm trying to boot an x86 kernel with a 64 bit efi firmware using grub. This is supported since kernel 3.4 but i cannot start the imac without disabling the i915 driver. I can start the system with i915.disable=1 but without this option it gives me the attached kernel message (picture).<br>
<br>
When using the same kernel version but 64 bit, the system boots without problems.<br>
<br>
I'm not sure how I should report this bug so if more information is needed, I'm happy to give that.<br>
I have tested this with an ubuntu install using kernel version 3.5.0 till the latest kernel 3.8 rc3.<br>
<br>
**Attachment 73107**, "kernel error message": <br>
![IMG_20130115_181242](/uploads/3adcff213f4562c7f90dcd482ed4eec5/IMG_20130115_181242.jpg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/325[RS880] Xorg.0.log: flip queue failed: Device or resource busy2019-11-19T16:38:00ZBugzilla Migration User[RS880] Xorg.0.log: flip queue failed: Device or resource busy## Submitted by Michael Lange
Assigned to **Default DRI bug account**
**[Link to original bug (#59903)](https://bugs.freedesktop.org/show_bug.cgi?id=59903)**
## Description
Created attachment 73686<br>
dmesg<br>
<br>
/var/log/Xorg...## Submitted by Michael Lange
Assigned to **Default DRI bug account**
**[Link to original bug (#59903)](https://bugs.freedesktop.org/show_bug.cgi?id=59903)**
## Description
Created attachment 73686<br>
dmesg<br>
<br>
/var/log/Xorg.0.log is full with:<br>
[ 1599.434] (WW) RADEON(0): flip queue failed: Device or resource busy<br>
[ 1599.434] (WW) RADEON(0): Page flip failed: Device or resource busy<br>
<br>
running up-to-date gentoo-system, with the following (unstable) packages<br>
linux-3.8.0-rc5 compiled a few minutes ago<br>
xorg-server-1.13.1 compiled a few minutes ago<br>
libdrm from git compiled a few minutes ago<br>
mesa from git compiled a few minutes ago<br>
xf86-video-ati from git compiled a few minutes ago<br>
<br>
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4290]<br>
<br>
my system is working as an htpc and is running fine, no crashes or oops<br>
slim is login my user and starts xbmc automatic <br>
xbmc in fullscreen is the only graphical application<br>
the system is connected to my tv through hdmi<br>
<br>
if i switch with my remote through the xbmc-menu or watch a video the xorg-log is spam the whole time with page filp errors<br>
if i leave xbmc alone, so the log is spam every few seconds with page flip errors<br>
<br>
is this related to this bug?<br>
https://bugs.freedesktop.org/show_bug.cgi?id=58659<br>
<br>
my system is working fine, no crashes or oops so far<br>
<br>
**Attachment 73686**, "dmesg": <br>
[file_59903.txt](/uploads/3bdd58131b9a638fb6cbab05e27f9683/file_59903.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/326SNA causes problems with DRI_PRIME2019-11-19T16:38:03ZBugzilla Migration UserSNA causes problems with DRI_PRIME## Submitted by Aleksandr Mezin `@amezin`
Assigned to **Default DRI bug account**
**[Link to original bug (#61678)](https://bugs.freedesktop.org/show_bug.cgi?id=61678)**
## Description
When I run Xonotic on discrete gpu (DRI_PRIME...## Submitted by Aleksandr Mezin `@amezin`
Assigned to **Default DRI bug account**
**[Link to original bug (#61678)](https://bugs.freedesktop.org/show_bug.cgi?id=61678)**
## Description
When I run Xonotic on discrete gpu (DRI_PRIME=1), sometimes I see only black<br>
screen, and dmesg is full of these messages:<br>
[ 5172.729073] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed<br>
0xa<br>
[ 5172.729078] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!<br>
<br>
Radeon starts working again only after reboot.<br>
This doesn't happen with UXA, so I think the problem is related to SNA.<br>
Tested on versions 2.20.13 and 2.21.3 - no difference.https://gitlab.freedesktop.org/drm/amd/-/issues/328LVDS screen mode switching fails2019-11-19T16:38:06ZBugzilla Migration UserLVDS screen mode switching fails## Submitted by Felix von Leitner
Assigned to **Default DRI bug account**
**[Link to original bug (#62246)](https://bugs.freedesktop.org/show_bug.cgi?id=62246)**
## Description
I have a HP Envy 14 laptop, which has switchable grap...## Submitted by Felix von Leitner
Assigned to **Default DRI bug account**
**[Link to original bug (#62246)](https://bugs.freedesktop.org/show_bug.cgi?id=62246)**
## Description
I have a HP Envy 14 laptop, which has switchable graphics between:<br>
<br>
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)<br>
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Madison [Radeon HD 5000M Series] (rev ff)<br>
<br>
This used to work (I'm not using it very often, so I don't know which kernel<br>
version broke it), and I think it caused total kernel hang in 3.0 till 3.3 or<br>
so. Not it "works" in the sense that when a HDMI cable is connected, I get a<br>
picture on the connected monitor. But the primary display output, LVDS-2, stays black.<br>
<br>
Here's the relevant dmesg parts:<br>
<br>
agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset<br>
agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable<br>
agpgart-intel 0000:00:00.0: detected 32768K stolen memory<br>
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xb0000000<br>
[drm] Initialized drm 1.1.0 20060810<br>
i915 0000:00:02.0: setting latency timer to 64<br>
i915 0000:00:02.0: irq 40 for MSI/MSI-X<br>
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).<br>
[drm] Driver supports precise vblank timestamp query.<br>
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem<br>
vgaarb: transferring owner from PCI:0000:00:02.0 to PCI:0000:01:00.0<br>
ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared<br>
ACPI: Battery Slot [BAT0] (battery present)<br>
ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared<br>
ACPI: Battery Slot [BAT1] (battery absent)<br>
[drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2<br>
fbcon: inteldrmfb (fb0) is primary device<br>
Console: switching to colour frame buffer device 200x56<br>
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device<br>
i915 0000:00:02.0: registered panic notifier<br>
[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness<br>
acpi device:01: registered as cooling_device5<br>
ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)<br>
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3<br>
[Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS<br>
acpi device:0a: registered as cooling_device6<br>
ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no)<br>
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:08/LNXVIDEO:01/input/input4<br>
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0<br>
<br>
[drm] radeon defaulting to kernel modesetting.<br>
[drm] radeon kernel modesetting enabled.<br>
VGA switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle<br>
radeon 0000:01:00.0: enabling device (0000 -> 0003)<br>
[drm] initializing kernel modesetting (REDWOOD 0x1002:0x68C1 0x103C:0x1436).<br>
[drm] register mmio base: 0xC4400000<br>
[drm] register mmio size: 131072<br>
vga_switcheroo: enabled<br>
ATPX version 1<br>
ATOM BIOS: MADISON<br>
radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)<br>
radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF<br>
mtrr: no more MTRRs available<br>
[drm] Detected VRAM RAM=1024M, BAR=256M<br>
[drm] RAM width 128bits DDR<br>
[TTM] Zone kernel: Available graphics memory: 3980934 kiB<br>
[TTM] Zone dma32: Available graphics memory: 2097152 kiB<br>
[TTM] Initializing pool allocator<br>
[TTM] Initializing DMA pool allocator<br>
[drm] radeon: 1024M of VRAM memory ready<br>
[drm] radeon: 512M of GTT memory ready.<br>
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).<br>
[drm] Driver supports precise vblank timestamp query.<br>
radeon 0000:01:00.0: irq 45 for MSI/MSI-X<br>
radeon 0000:01:00.0: radeon: using MSI.<br>
[drm] radeon: irq initialized.<br>
[drm] GART: num cpu pages 131072, num gpu pages 131072<br>
[drm] probing gen 2 caps for device 8086:45 = 1/0<br>
[drm] Loading REDWOOD Microcode<br>
[drm] PCIE GART of 512M enabled (table at 0x0000000000040000).<br>
radeon 0000:01:00.0: WB enabled<br>
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880251324c00<br>
radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff880251324c0c<br>
radeon 0000:01:00.0: enabling bus mastering<br>
[drm] ring test on 0 succeeded in 1 usecs<br>
[drm] ring test on 3 succeeded in 1 usecs<br>
[drm] ib test on ring 0 succeeded in 0 usecs<br>
[drm] ib test on ring 3 succeeded in 0 usecs<br>
[drm] radeon atom DIG backlight initialized<br>
[drm] Radeon Display Connectors<br>
[drm] Connector 0:<br>
[drm] LVDS-2<br>
[drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c<br>
[drm] Encoders:<br>
[drm] LCD1: INTERNAL_UNIPHY<br>
[drm] Connector 1:<br>
[drm] DP-1<br>
[drm] HPD2<br>
[drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c<br>
[drm] Encoders:<br>
[drm] DFP1: INTERNAL_UNIPHY1<br>
[drm] Connector 2:<br>
[drm] HDMI-A-1<br>
[drm] HPD1<br>
[drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c<br>
[drm] Encoders:<br>
[drm] DFP2: INTERNAL_UNIPHY1<br>
[drm] Internal thermal controller with fan control<br>
[drm] radeon: power management initialized<br>
[drm] fb mappable at 0xA0142000<br>
[drm] vram apper at 0xA0000000<br>
[drm] size 5787648<br>
[drm] fb depth is 24<br>
[drm] pitch is 6400<br>
radeon 0000:01:00.0: fb1: radeondrmfb frame buffer device<br>
[drm] Initialized radeon 2.29.0 20080528 for 0000:01:00.0 on minor 1<br>
<br>
When I start the intel framebuffer, the display is also black, but I<br>
found out that that is just the brightness set to 0, so I wrote a little<br>
too that writes to /sys/class/backlight/acpi_video0/brightness to set a<br>
sensible brightness.<br>
<br>
When the radeon screen stayed black, I assumed the same problem, so I<br>
changed my tool to also write to<br>
/sys/class/backlight/acpi_video1/brightness, but this does not help.<br>
<br>
To check whether this was related to VGA switcheroo interactions, I compiled a kernel with no Intel driver in it and insmod'ed the radeon module. This time the LVDS display stayed in text mode and "hung" in the sense that the text did not continue scrolling.<br>
<br>
I something is attacked on the HDMI output, that display gets a text console when I insmod radeon.<br>
<br>
When I start X, the LVDS screen still stays broken, but the console disappears from the HDMI screen, and the laptop appears to hang. My default setup within X is to have an xterm, so I moved my mouse into that xterm (without seeing any of it) and started a shell script that uses xrandr to set up the second display, but nothing happened. It felt as if the Intel driver still felt responsible for LVDS.<br>
<br>
Since I'm using X in non-radeon mode all the time, I have no Xorg.log left from my radeon testing. I can tell you though what was in it. No (EE) lines. I originally used X.org 1.12.3, then switched to 1.14 to see if that would make the problem disappear. I tried the latest release versions of libdrm and xf86-intel-radeon but when that did not work, I upgraded to the git versions of both. No improvement.<br>
<br>
I can try again tonight at home and produce an Xorg.0.log for you.