dri-devel August 2013

dri-devel@lists.freedesktop.org

154 participants
881 discussions

[Bug 53391] New: nouveau: wrong display output order
by bugzilla-daemon＠bugzilla.kernel.org 08 Dec '21

08 Dec '21

https://bugzilla.kernel.org/show_bug.cgi?id=53391 Summary: nouveau: wrong display output order Product: Drivers Version: 2.5 Kernel Version: 3.8-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: stijn+bugs(a)linux-ipv6.be Regression: No My graphics card is a Gainward GTX480 (http://www.gainward.com/main/vgapro.php?id=238). It has 2 DVI outputs, and 1 mini HDMI output. The DVI outputs are numbered on the card, with DVI 1 being the closest to the PCIe slot, then DVI 2, and finally the mini HDMI. My primary (left) monitor, is connected to DVI 1, my secondary (right) monitor to DVI 2. When I boot the computer, the BIOS initializes and uses the monitor on DVI 1. Grub is displayed on the primary monitor, and the kernel initially outputs to the primary monitor as well. However, as soon as the nouveau module is loaded, the primary monitor goes to standby and the kernel now uses the secondary monitor (on DVI 2) as primary. When X starts (no Xorg.conf file), it is also displayed on the secondary monitor. When using either efifb, vesafb or uvesafb, the monitor on DVI 1 is always the primary monitor. X with nvidia.ko also uses DVI 1 as the primary display. Finally, when booting Windows, the startup screen is also displayed on the monitor connected to DVI 1. Here comes the weird part: when I am in X, and run xrandr, it does show 3 connected devices: DVI-I-1, DVI-I-2, and HDMI-1, with DVI-I-2 being the only active one. So it seems that in X, the output order is correct, but with nouveaufb the DVI connectors are swapped. I will attach the output of dmesg here. If anything else is needed, please let me know and I'll be happy to add it. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 13

[Bug 51381] New: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo
by bugzilla-daemon＠bugzilla.kernel.org 11 May '21

11 May '21

https://bugzilla.kernel.org/show_bug.cgi?id=51381 Summary: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo Product: Drivers Version: 2.5 Kernel Version: Linux version 3.6.9-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Tue Dec 4 08:04:10 CET 2012 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: a(a)anrd.net Regression: Yes Created an attachment (id=88591) --> (https://bugzilla.kernel.org/attachment.cgi?id=88591) journald log After updating from 3.6.6 to 3.6.9 my laptop with Intel graphics and ATI HD 5650 will not resume from suspend. I use vgaswitcheroo to disable the ATI card at boot. On resume the computer almost hangs (I can press power button and wait 5 minutes for a proper shutdown, but no other interaction is possible). It logs a lot of messages saying: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D098 (len 72, WS 0, PS 0) @ 0xD0C7 Steps to reproduce: echo "OFF" > /sys/kernel/debug/vgaswitcheroo/switch [suspend and resume] Actual results: Almost freeze. Expected results: Resume and work as normal. Log is attached, but if you need anything else just ask. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 62

[Bug 58981] New: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS
by bugzilla-daemon＠bugzilla.kernel.org 28 Jan '20

28 Jan '20

https://bugzilla.kernel.org/show_bug.cgi?id=58981 Summary: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS Product: Drivers Version: 2.5 Kernel Version: 2.6.35,3.2.45,3.10-rc2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: jdietrch(a)fastmail.fm Regression: Yes I have a Radeon 9250 PCI 256MB video card in my machine. I discovered that this machine would not boot with 3.2.45 when KMS was enabled by default in the kernel config. Immediately after the grub menu, the screen would go black and nothing more would happen. Or sometimes columns of character-sized "marks" would appear on the screen. In either case, though, the machine would not boot. So I went back to 2.6.33 and found that booting with KMS did work just fine there. So I used git bisect to find where the problem arose, and that pointed to this commit which was merged for 2.6.35: commit 6b8b1786a8c29ce6e32298b93ac8d4a18a2b11c4 Author: Jerome Glisse <jglisse(a)redhat.com> Date: Wed Apr 7 10:21:31 2010 +0000 drm/radeon/kms: enable use of unmappable VRAM V2 I confirmed this result of git bisect by checking out 2.6.35 final and reverting that one commit, and the resulting kernel booted fine with KMS enabled by default. I also tried 3.10-rc2 and that booted fine when I added radeon.modeset=0 to the kernel commandline. I will attach files with dmesg output and lspci. Please let me know if there is anything else I can do. I'll be happy to test a proposed fix if that would be helpful. Thank you, James Dietrich -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 6

[Bug 32556] New: screen flickers all the time with desktop image appearing only briefly
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32556 Summary: screen flickers all the time with desktop image appearing only briefly Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 3ntr0p13(a)gmail.com Created an attachment (id=41344) --> (https://bugs.freedesktop.org/attachment.cgi?id=41344) dmesg 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 4000+, this time running a 64 bits debian squeeze. The machine is a small factor desktop machine designed around laptop components, so the graphic card is an integrated radeon x1200. When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the time 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. While booting with radeon.modeset=0 the problem doesn't exhibits itself The following packages version from debian squeeze are installed: xserver-xorg 1:7.5+8 xserver-xorg-core 2:1.7.7-10 xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that machine (when booted on 2.6.37-rc6). Regards, Gildas -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 38

[Bug 32422] New: Large images displayed in Firefox appear corrupted
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32422 Summary: Large images displayed in Firefox appear corrupted Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: da_fox(a)mad.scientist.com Created an attachment (id=41150) --> (https://bugs.freedesktop.org/attachment.cgi?id=41150) Picture describing a thousand words. "A picture says more than a thousand words" (aka see attachment) 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. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 21

[Bug 68178] New: evergreen: hard lockup on suspend and resume with current firmware
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=68178 Priority: medium Bug ID: 68178 Assignee: dri-devel(a)lists.freedesktop.org Summary: evergreen: hard lockup on suspend and resume with current firmware Severity: major Classification: Unclassified OS: Linux (All) Reporter: nine(a)detonation.org Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 84133 --> https://bugs.freedesktop.org/attachment.cgi?id=84133&action=edit dmesg of my system for information As soon as the up to date firmware package is installed, my system hangs on suspend and again on resume with the screen turned off and the system not reacting to anything. Tested it on various kernels with the earliest being 3.7.10 (current openSUSE kernel) and the latest being 3.11-rc5. I tried to get more information, but there are no logs, the screen is turned off and even netconsole did not show more. Do you have suggestions about how to debug this or things that I can try to narrow it down? My GPU is a: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Redwood [Radeon HD 5670] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device e151 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f4420000 (64-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=256] Expansion ROM at f4400000 [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 <?> Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon Attaching dmesg of a running system just for info. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 68059] New: with radeon.dpm=1, Xorg crashed a while after resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=68059 Priority: medium Bug ID: 68059 Assignee: dri-devel(a)lists.freedesktop.org Summary: with radeon.dpm=1, Xorg crashed a while after resume Severity: critical Classification: Unclassified OS: Linux (All) Reporter: wrxzzj(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 84008 --> https://bugs.freedesktop.org/attachment.cgi?id=84008&action=edit dmesg I test with kernel 3.11rc5, mesa 9.2git, xorg 1.14.2, Radeon HD6310. with radeon.dpm enabled, after resume from RAM, Xorg crashed a while. attachment is my dmesg log. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 67994] New: System freezes when playing video on open source AMD drivers with VDPAU
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67994 Priority: medium Bug ID: 67994 Assignee: dri-devel(a)lists.freedesktop.org Summary: System freezes when playing video on open source AMD drivers with VDPAU Severity: normal Classification: Unclassified OS: Linux (All) Reporter: scorp.exe(a)yandex.ua Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Kernel - Linux 3.11rc4 Version mesa-common-dev - 9.2.0~git20130729+9.2.9b8ad643-0ubuntu0sarvatt~raring Version libg3dvl-mesa - 9.3~git1308091520.e8d897~gd~r Driver - Gallium 0.4 To repeat the freezing - start the video on player with support for VDPAU (mplayer or XBMC), stop it, and then run another video. -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 67970] New: Kernel bugs related to the powersaving features of mobility radeon x1400
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67970 Priority: medium Bug ID: 67970 Assignee: dri-devel(a)lists.freedesktop.org Summary: Kernel bugs related to the powersaving features of mobility radeon x1400 Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: shayanmansuri(a)yahoo.com Hardware: All Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I have a Mobility Radeon X1400 (RV500 Family) on my dell inspiron 6400 (or it's called inspiron 1501 or 1505 elsewhere). I use Open-source drivers and they work for me and I have no problem with anything except the powermanagement at kernel level. When I want to activate powersaving feature I use these commands: 1. when I use this command: echo dynpm > /sys/class/drm/card0/device/power_method nothing happens. I mean GPU frequency remain high. I even do not use a GUI. I'm in the shell. 2. when I use these commands echo profile > /sys/class/drm/card0/device/power_method echo low > /sys/class/drm/card0/device/power_profile I receive these error: kernel:[ 192.253008] NMI: PCI system error (SERR) for reason b1 on CPU 0. kernel:[ 192.253016] Dazed and confused, but trying to continue I have noticed that the kernel do not changes the GPU and Vram frequencies correctly in the profile mode. This is what I get when I set it to mid: # echo mid > /sys/class/drm/card0/device/power_profile # cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 432000 kHz current engine clock: 209250 kHz default memory clock: 396000 kHz current memory clock: 135000 kHz PCIE lanes: 1 This is what I get when I set it to low: # echo low > /sys/class/drm/card0/device/power_profile # cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 432000 kHz current engine clock: 324000 kHz default memory clock: 396000 kHz current memory clock: 135000 kHz PCIE lanes: 1 This is what I get when I set it to high: # echo high > /sys/class/drm/card0/device/power_profile # cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 432000 kHz current engine clock: 432000 kHz default memory clock: 396000 kHz current memory clock: 396000 kHz PCIE lanes: 0 If you look at the above values, it is obvious that the current clock of mid and low profiles should be replaced with each other. I've tested this in different distribution of GNU/Linux with different kernel versions: Including Ubuntu, LMDE, Archlinux and Chakra. with these kernel versions: 2.6.38, 2.6.39, 3.0.0 RC5, 3.0.0-1-amd64 in LMDE, and lately with 3.4.55 LTS in ubuntu 12.04.2. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 67946] New: Switching to Integrated card to vgaswitcheroo with radeon.audio=1 makes kernel to hang
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67946 Priority: medium Bug ID: 67946 Assignee: dri-devel(a)lists.freedesktop.org Summary: Switching to Integrated card to vgaswitcheroo with radeon.audio=1 makes kernel to hang Severity: normal Classification: Unclassified OS: All Reporter: mail(a)3v1n0.net Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I've a Mobility Radeon HD 5650 muxed with an intel card. If I boot with radeon.audio=1 and I switch the radeon card off when pulseaudio is running, then the kernel hangs as soon as I close X: [ 489.177732] hda-intel 0000:01:00.1: Disabling via VGA-switcheroo [ 489.297129] hda-intel 0000:01:00.1: Cannot lock devices! [ 489.297139] radeon: switched off [ 489.300356] [drm] Disabling audio support [ 489.319552] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000015e418 and cpu addr 0xffffc90009df0418 [ 489.973886] ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event: unsupported [ 489.973903] _handle_hotplug_event_root: Bus check notify on \_SB_.PCI0 [ 678.992375] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 678.992453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996303] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 683.996377] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C3DC (len 871, WS 0, PS 0) @ 0xC439 [ 689.000275] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 689.000349] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 694.004285] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 694.004363] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.008330] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 699.008414] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.514458] init: tty1 main process (2460) killed by QUIT signal [ 699.514489] init: tty1 main process ended, respawning [ 704.012405] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 704.012492] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 709.016515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 709.016596] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 These errors doesn't happen instead if I close X and kill pulseaudio before switching cards. Not sure if this is a pulseaudio issue or a kernel one (that should notify pulseaudio about the unplugged HDMI audio card). -- You are receiving this mail because: You are the assignee for the bug.

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2013