dri-devel October 2013

dri-devel@lists.freedesktop.org

171 participants
926 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 71067] New: [drm:r600] UVD not responding OR failed testing IB on GFX ring
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71067 Priority: medium Bug ID: 71067 Assignee: dri-devel(a)lists.freedesktop.org Summary: [drm:r600] UVD not responding OR failed testing IB on GFX ring Severity: normal Classification: Unclassified OS: All Reporter: timothee.romain.ravier(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI When I boot 3.10 or 3.11 kernels, I get either one of those errors, apparently at random : * UVD not responding, trying to reset the VCPU -> Full log attached: *freeze-boot-then-yellow.log The display turns yellow when the X server starts. I can still use VT and there is no corruption there. I made sure that I got the latest firmware and I also checked my initrd (following instructions in 65270); * GPU lockup CP stall for more than 10000msec GPU lockup (waiting for 0x000000000000020e last fence id 0x00000000000001ec) r600_ib_test] *ERROR* radeon: fence wait failed (-35) radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35) -> Full log attached: *freeze-cursor.log I can log into my graphical session, but quickly after that, everything freeze and I can only move the cursor which displays as a "corrupted" square. Again VT are fine. I filed only one bug report as I get both issue using the same software and boot command line. At the beginning I had bug 67994, which turned into this one. I tried downgrading the kernel without much success for now. Booting with nomodeset works perfectly (with no accel/KMS obviously) and booting under Windows 7 too. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 70543] New: [r600g] HD5450 + uvd + hdmi flickers
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=70543 Priority: medium Bug ID: 70543 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] HD5450 + uvd + hdmi flickers Severity: normal Classification: Unclassified OS: All Reporter: stompdagger1(a)yahoo.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 87753 --> https://bugs.freedesktop.org/attachment.cgi?id=87753&action=edit X's session log I have a HD5450 hooked up to my lcd tv as part of a multiseat setup. every few seconds the feed flickers. usually I use xbmc to view content but it happens with VBox too. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 70542] New: [r600g] HD5450 + uvd + hdmi flickers
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=70542 Priority: medium Bug ID: 70542 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] HD5450 + uvd + hdmi flickers Severity: normal Classification: Unclassified OS: All Reporter: stompdagger1(a)yahoo.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 87752 --> https://bugs.freedesktop.org/attachment.cgi?id=87752&action=edit seat greetings, I have a HD5450 hooked up to my lcd tv as part of a multiseat setup. every few seconds the feed flickers. usually I use xbmc to view content but it happens with VBox too. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 70514] New: Unresponsive system on boot with radeon + FireGL v7700
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=70514 Priority: medium Bug ID: 70514 Assignee: dri-devel(a)lists.freedesktop.org Summary: Unresponsive system on boot with radeon + FireGL v7700 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: noryb009(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: 9.2 Component: Drivers/Gallium/r600 Product: Mesa I'm using a FireGL V7700 with Arch Linux x64. When booting to a command line, when drivers are loaded, the screen goes into power saving mode, and the system becomes unresponsive. Booting with `nomodeset' works OK. If I run "$ modprobe radeon modeset=1", the screen goes power saving mode, the system stops responding to open ssh session(s), and the caps lock key no longer works (kernel panic?). I've also tested with a Puppy Linux Live-CD, with the same results (unresponsive on driver load). I've tested a HD 4650 in the same system, and everything works fine. $ lspci -v | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV670 GL [FireGL V7700] (prog-if 00 [VGA controller]) -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 70286] New: X crashes when using Firefox with logout loop
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=70286 Priority: medium Bug ID: 70286 Assignee: dri-devel(a)lists.freedesktop.org Summary: X crashes when using Firefox with logout loop Severity: major Classification: Unclassified OS: Linux (All) Reporter: xgt008(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 87293 --> https://bugs.freedesktop.org/attachment.cgi?id=87293&action=edit syslog during crash Firefox 24, with hardware acceleration on, X crashes and the whole desktop enters a logout loop. Restarting is the only way out :(. I am running Ubunut 13.04 (linux mint 15) with Linux Kernel 3.11.4 with radeon.dpm=1 and oibaf ppa (mesa-9.3-git) and Xorg 1.13.4 Attached are my syslog and Xorg.0.log during the crash. Please let me know if I need to attach any further logs. Here are some error messages that I found in these logs : syslog : [ 1807.720765] [drm:radeon_crtc_page_flip] *ERROR* failed to pin new rbo buffer before flip [ 1810.600061] radeon 0000:01:00.0: ffff88008c51ac00 pin failed from Xorg.0.log : [ 1839.182] (WW) RADEON(0): flip queue failed: Invalid argument [ 1839.182] (WW) RADEON(0): Page flip failed: Invalid argument -- You are receiving this mail because: You are the assignee for the bug.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2013