dri-devel November 2013

dri-devel@lists.freedesktop.org

134 participants
940 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 64721] New: Radeon HD6450 fails on all distro's out of box.
by bugzilla-daemon＠bugzilla.kernel.org 02 Dec '19

02 Dec '19

https://bugzilla.kernel.org/show_bug.cgi?id=64721 Bug ID: 64721 Summary: Radeon HD6450 fails on all distro's out of box. Product: Drivers Version: 2.5 Kernel Version: Linux 3.2.04-amd64 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: ichapman(a)videotron.ca Regression: No I think I'm at the right place to report video card frustrations. Radeon HD450 fails to work out of the box with any Linux. With Debian Wheezy I need to edit the grub line starting with linux and add vga=791 to do anything. vga=771 fails With Knoppix 7.0 I need vga=771 and that's okay, but vga=791 the left half of screen is on right and right on left. The cursor moves to right falls off the screen and re-appears on left side. Very strange. With DebianMint I need vga=771 or 791 to get it to work. On my Acer Aspire laptop with a Radeon HD6310 I do not need any of this vga= stuff. I am sure that this is not a driver problem. All the vga=xxx does is kick it somewhere so that I loads the driver. My Motherboard is M2V-Mx from Asus and once the /etc/default/grub is fixed with GRUB_CMDLINE_LINUX="vga=791" or 771 it's okay. (sudo update-grub of course) I recently junked my Nvidia 8500GT video because the driver for that became sick, the worst feature was not being able to display the layout of the pcb tool unless I disabled the driver and used cpu sw rendering on the video but that's an other story. Ian. -- You are receiving this mail because: You are watching the assignee of the bug.

1 5

[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 72051] New: [JUNIPER] with kernel 3.12 some HDMI screens are not recognized
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=72051 Priority: medium Bug ID: 72051 Assignee: dri-devel(a)lists.freedesktop.org Summary: [JUNIPER] with kernel 3.12 some HDMI screens are not recognized Severity: normal Classification: Unclassified OS: Linux (All) Reporter: eugene.shalygin+bugzilla.FDO(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 89860 --> https://bugs.freedesktop.org/attachment.cgi?id=89860&action=edit xrandr -q --verbose with screen 1 connected I have two external screens, say screen 1 and 2. Screen 1 have HDMI input and screens 2 is connected via HDMI-to-DVI adapter. With kernel 3.12 screen 1 is not recognized on connect anymore. Booting kernel 3.11.9 makes it work again. When I connect screen 1 nothing appears not in Xorg.0.log nor in dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 71864] New: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71864 Priority: medium Bug ID: 71864 Assignee: dri-devel(a)lists.freedesktop.org Summary: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0) Severity: critical Classification: Unclassified OS: Linux (All) Reporter: reimth(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI [Problem] Since upgrade from kernel 2.6.35 to kernel 3.2.0 (Ubuntu 12.04) we experience numerous kernel freezes (no keyboard/mouse, no kernel logging, no num key change, stop of server applications, e. g. dhcpd, postfix, bind9, magic keys not working, no serial console), that can only be resolved by switching power off (hard reset). There is no clear way to reproduce this bug. The likelihood of the kernel crash increases, if mail GUIs like Evolution or Thunderbird are open or Firefox is open and when switching between these windows. The kernel freezes latest within 6 h. Whereas if just the desktop and xterm is running, the system seems to be stable (48 h and more). The bug can be confirmed under lightdm/unity as desktop, as well as when using mdm/cinnamon. Log information can only be retrieved using netconsole. They show a GPU lockup and CP stall, from which the radeon driver cannot recover. [Configuration Specifics] We run two X Servers: one controlled by the display manager (on vt7 or vt8) and one controlled by xinit (on vt9). See attached process list. We use the DVI port of the integrated Radeon X1200 (RS690) display controller on an ASUS MSA mainboard. One monitor (Samsung) is connected. Radeon driver with KMS enabled is used. [Netconsole Output] The last kernel log messages that reach the netconsole receiver vary: a) The shortest log [212173.596044] radeon 0000:01:05.0: GPU lockup CP stall for more than 10000msec [212175.370234] radeon 0000:01:05.0: failed to reset GPU [212175.406899] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3). [212175.406912] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! b) A longer one [286295.708052] radeon 0000:01:05.0: GPU lockup CP stall for more than 10020msec [286297.455900] radeon 0000:01:05.0: failed to reset GPU [286297.929150] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(14). [286297.929174] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.937321] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(15). [286297.937349] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.943050] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). [286297.943074] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.947188] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). [286297.947213] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.949490] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2). [286297.949509] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! c) GPU reset attempt [179005.128038] radeon 0000:01:05.0: GPU lockup CP stall for more than 10032msec [179005.128068] GPU lockup (waiting for 0x0004E1FF last fence id 0x0004E1F4) [179005.268649] radeon: wait for empty RBBM fifo failed ! Bad things might happen. [179005.409044] Failed to wait GUI idle while programming pipes. Bad things might happen. [179005.410064] radeon 0000:01:05.0: (rs600_asic_reset:348) RBBM_STATUS=0x9401C100 [179005.908155] radeon 0000:01:05.0: (rs600_asic_reset:367) RBBM_STATUS=0x9401C100 [179006.405224] radeon 0000:01:05.0: (rs600_asic_reset:375) RBBM_STATUS=0x9400C100 [179006.902280] radeon 0000:01:05.0: (rs600_asic_reset:383) RBBM_STATUS=0x9400C100 [179006.902315] radeon 0000:01:05.0: restoring config space at offset 0x1 (was 0x100403, writing 0x100407) [179006.902346] radeon 0000:01:05.0: failed to reset GPU [179006.903346] radeon 0000:01:05.0: GPU reset failed d) Successful GPU reset but inaccessible CP [ 1775.356043] radeon 0000:01:05.0: GPU lockup CP stall for more than 10008msec [ 1775.356067] GPU lockup (waiting for 0x000124ED last fence id 0x000124EA) [ 1775.919383] radeon: wait for empty RBBM fifo failed ! Bad things might happen. [ 1776.059845] Failed to wait GUI idle while programming pipes. Bad things might happen. [ 1776.060872] radeon 0000:01:05.0: (rs600_asic_reset:348) RBBM_STATUS=0xB001C100 [ 1776.559021] radeon 0000:01:05.0: (rs600_asic_reset:367) RBBM_STATUS=0x90010140 [ 1777.056092] radeon 0000:01:05.0: (rs600_asic_reset:375) RBBM_STATUS=0x10000140 [ 1777.553160] radeon 0000:01:05.0: (rs600_asic_reset:383) RBBM_STATUS=0x10000140 [ 1777.553197] radeon 0000:01:05.0: restoring config space at offset 0x1 (was 0x100403, writing 0x100407) [ 1777.553232] radeon 0000:01:05.0: GPU reset succeed [ 1777.554232] radeon 0000:01:05.0: GPU reset succeed [ 1777.554263] sched: RT throttling activated [ 1777.749090] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [ 1777.754590] [drm] PCIE GART of 512M enabled (table at 0x0000000036700000). [ 1777.754958] radeon 0000:01:05.0: WB enabled [ 1777.754991] [drm] radeon: ring at 0x0000000080001000 [ 1777.892767] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD) [ 1777.892774] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). [ 1777.892783] radeon 0000:01:05.0: failed initializing CP (-22). [ 1786.390793] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11). [ 1786.390818] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! A really verbose log with drm.debug set to 0xf has been attached. As well as the usually required information. -- You are receiving this mail because: You are the assignee for the bug.

1 22

[Bug 71753] New: Radeon Audio clock running wrong speed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71753 Priority: medium Bug ID: 71753 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon Audio clock running wrong speed Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fritsch(a)xbmc.org Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI When syncing radeon audio to a systemclock one realizes that it goes wrong approximately 10ms per 6 seconds. For example with 60hz and 50hz the audio clock is 10ms / 6 seconds too fast, which causes great issues, when watching e.g. LiveTV. When displaying at 24hz the audio clock is approximately 10ms / 6 seconds too slow, which can be workarounded by doubling packages. You can only realize this problem, if you don't use any resample algorithms to make audio fit. Some output from an xbmc.log: Configuration: 50hz no sync playback to display. Kernel 3.12 (Pierre Ossmann patch applied) with mesa git 19:46:13 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62710358734.243919, should be:62710332298.764549, error:-26435.479370 19:46:16 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62712528103.582550, should be:62712508710.849106, error:-19392.733447 19:46:17 T:139718566078208 DEBUG: CPullupCorrection: detected pattern of length 1: 40000.00, frameduration: 40000.000000 19:46:22 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62718996472.639107, should be:62719007584.295349, error:11111.656243 19:46:28 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62725295876.976349, should be:62725306470.191048, error:10593.214698 19:46:35 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62731698477.715050, should be:62731709235.032417, error:10757.317365 19:46:38 T:139719056176896 DEBUG: Thread JobWorker 139719056176896 terminating (autodelete) 19:46:41 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62738297284.064415, should be:62738308465.384331, error:11181.319916 19:46:48 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62744796455.484329, should be:62744807397.750954, error:10942.266624 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 71697] New: [radeonsi] gtkperf hangs the system
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71697 Priority: medium Bug ID: 71697 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] gtkperf hangs the system Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI HD 7950 drm-next-3.13 (agd5f tree) libdrm git mesa git xf86-video-ati git xorg-server-1.14.4 + DRI-loader-entrypoint glamor git llvm 3.4 git The system hangs about a minute after gtkperf started, there is nothing in /var/log/messages. -- You are receiving this mail because: You are the assignee for the bug.

1 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel November 2013