dri-devel February 2014

dri-devel@lists.freedesktop.org

154 participants
967 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 75136] New: Radeon HD
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75136 Priority: medium Bug ID: 75136 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD Severity: normal Classification: Unclassified OS: Linux (All) Reporter: tmciolek(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Radeon DRM fails on boot... this is observed with kernle 3.12.x and 3.13.x [ 92.918254] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed [ 92.918258] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed [ 92.932698] ------------[ cut here ]------------ [ 92.932712] WARNING: CPU: 5 PID: 3664 at drivers/gpu/drm/drm_crtc.c:2029 drm_mode_set_config_internal+0x62/0xac [drm]() [ 92.932713] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp tun bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables bnep rfcomm bluetooth parport_pc parport binfmt_misc ipv6 it87 hwmon_vid firewire_sbp2 loop fuse radeon ttm drm_kms_helper drm snd_hda_codec_hdmi snd_usb_audio snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_usbmidi_lib snd_hwdep snd_pcm_oss pwc snd_mixer_oss snd_pcm videobuf2_vmalloc joydev videobuf2_memops hid_apple v4l2_common hid_generic usbhid evdev snd_page_alloc hid videobuf2_core acpi_cpufreq snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq kvm_amd videodev cfbfillrect freq_table kvm processor k10temp pcspkr serio_raw cfbimgblt edac_core cfbcopyarea media sp5100_tco snd_seq_device snd_timer thermal_sys snd edac_mce_amd i2c_algo_bit i2c_piix4 i2c_core hwmon soundcore button ext3 jbd sg sr_mod sd_mod cdrom crc_t10dif crct10dif_common dm_mod xhci_hcd ata_generic ahci libahci pata_jmicron libata ehci_pci firewire_ohci microcode ohci_pci ohci_hcd firewire_core ehci_hcd r8169 usbcore crc_itu_t scsi_mod mii usb_common [ 92.932769] CPU: 5 PID: 3664 Comm: Xorg Not tainted 3.12.9 #1 [ 92.932771] Hardware name: Gigabyte Technology Co., Ltd. GA-870A-UD3/GA-870A-UD3, BIOS F5 08/01/2011 [ 92.932773] 0000000000000006 ffffffff8138712a 0000000000000000 ffffffff810348cb [ 92.932776] ffffffffa03c0b0f ffff88040bf26000 ffff88040c382240 0000000000000000 [ 92.932778] ffff88040bf26000 ffffffffa03c0b0f ffff8800cf89de20 ffff88040c382240 [ 92.932780] Call Trace: [ 92.932786] [<ffffffff8138712a>] ? dump_stack+0x4a/0x7e [ 92.932790] [<ffffffff810348cb>] ? warn_slowpath_common+0x74/0x89 [ 92.932797] [<ffffffffa03c0b0f>] ? drm_mode_set_config_internal+0x62/0xac [drm] [ 92.932803] [<ffffffffa03c0b0f>] ? drm_mode_set_config_internal+0x62/0xac [drm] [ 92.932810] [<ffffffffa03c2d0e>] ? drm_mode_setcrtc+0x41d/0x4c2 [drm] [ 92.932816] [<ffffffffa03b7a4b>] ? drm_ioctl+0x289/0x3bf [drm] [ 92.932822] [<ffffffffa03c28f1>] ? drm_mode_setplane+0x32e/0x32e [drm] [ 92.932825] [<ffffffff810e5c49>] ? do_mmap_pgoff+0x2d8/0x33d [ 92.932829] [<ffffffff81114655>] ? vfs_ioctl+0x1b/0x28 [ 92.932831] [<ffffffff81114d71>] ? do_vfs_ioctl+0x32d/0x3e8 [ 92.932833] [<ffffffff81114e7a>] ? SyS_ioctl+0x4e/0x7b [ 92.932836] [<ffffffff813902e6>] ? system_call_fastpath+0x1a/0x1f [ 92.932837] ---[ end trace d0bfb4b26dcd2b69 ]--- card is a Barts LE [Radeon HD 6790] with monitors plugged into two DVI ports Distro is Debian/Jesse xorg packages installed are:ii xorg-sgml-doctools 1:1.11-1 all Common tools for building X.Org SGML documentation ii xserver-xorg 1:7.7+6 amd64 X.Org X server ii xserver-xorg-core 2:1.14.5-1 amd64 Xorg X server - core server ii xserver-xorg-dev 2:1.14.5-1 amd64 Xorg X server - development files ii xserver-xorg-input-all 1:7.7+6 amd64 X.Org X server -- input driver metapackage ii xserver-xorg-input-evdev 1:2.8.2-1 amd64 X.Org X server -- evdev input driver ii xserver-xorg-input-mouse 1:1.9.0-1+b1 amd64 X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 1.7.3-1 amd64 Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-vmmouse 1:13.0.0-1+b1 amd64 X.Org X server -- VMMouse input driver to use with VMWare ii xserver-xorg-input-wacom 0.23.0+20131011-1 amd64 X.Org X server -- Wacom input driver ii xserver-xorg-video-ati 1:7.3.0-1 amd64 X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-mach64 6.9.4-1+b1 amd64 X.Org X server -- ATI Mach64 display driver ii xserver-xorg-video-r128 6.9.2-1 amd64 X.Org X server -- ATI r128 display driver ii xserver-xorg-video-radeon 1:7.3.0-1 amd64 X.Org X server -- AMD/ATI Radeon display driver Other questions: please ask Happy to apply and/or test patches -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 75134] New: UVD doesn't survive a GPU crash on a Radeon HD 6770
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75134 Priority: medium Bug ID: 75134 Assignee: dri-devel(a)lists.freedesktop.org Summary: UVD doesn't survive a GPU crash on a Radeon HD 6770 Severity: normal Classification: Unclassified OS: All Reporter: nmiell(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/DRI/Radeon Product: Mesa UVD isn't reinitialized after a GPU crash. GPU is a Radeon HD 6770, which is a Evergreen-based Juniper XT. Kernel is 3.13.3-201.fc20.x86_64 X is xorg-x11-server-Xorg-1.14.4-6.fc20.x86_64 Mesa is current master (adad8fb2e947e3ea9e9d84cb3722e46de91346e4). Reproducing: 1. vdpauinfo's output before the crash: Decoder capabilities: name level macbs width height ------------------------------------------- MPEG1 0 9216 2048 1152 MPEG2_SIMPLE 3 9216 2048 1152 MPEG2_MAIN 3 9216 2048 1152 H264_BASELINE 41 9216 2048 1152 H264_MAIN 41 9216 2048 1152 H264_HIGH 41 9216 2048 1152 VC1_SIMPLE 1 9216 2048 1152 VC1_MAIN 2 9216 2048 1152 VC1_ADVANCED 4 9216 2048 1152 2. Crash the GPU. DoubleFine's The Cave or Brütal Legend are good for this. 3. vdpauinfo's output after the crash: Decoder capabilities: name level macbs width height ------------------------------------------- MPEG1 0 1048576 16384 16384 MPEG2_SIMPLE 3 1048576 16384 16384 MPEG2_MAIN 3 1048576 16384 16384 4. Relevant kernel logs: radeon 0000:01:00.0: GPU lockup CP stall for more than 10104msec radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000012605f last fence id 0x0000000000126059 on ring 0) [drm] Disabling audio 0 support radeon 0000:01:00.0: Saved 311 dwords of commands on ring 0. radeon 0000:01:00.0: GPU softreset: 0x00000009 radeon 0000:01:00.0: GRBM_STATUS = 0xF0001828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x80000003 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40040000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048002 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268643 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88031ac2dc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88031ac2dc0c radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9001219c418 [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] Enabling audio 0 support ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD radeon 0000:01:00.0: GPU lockup CP stall for more than 10001msec radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000126064 last fence id 0x0000000000126060 on ring 0) [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). radeon 0000:01:00.0: ib ring test failed (-35). [drm] Disabling audio 0 support radeon 0000:01:00.0: GPU softreset: 0x00000009 radeon 0000:01:00.0: GRBM_STATUS = 0xF0001828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x80000003 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40040000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268643 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume CE: hpet increased min_delta_ns to 20115 nsec CE: hpet increased min_delta_ns to 30172 nsec [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88031ac2dc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88031ac2dc0c radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9001219c418 [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] Enabling audio 0 support [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 1 usecs ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD [drm:uvd_v1_0_ib_test] *ERROR* radeon: failed to get create msg (-22). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). switching from power state: ui class: none internal class: boot caps: video uvd vclk: 0 dclk: 0 power level 0 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 1 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: c b switching to power state: ui class: performance internal class: none caps: single_disp video uvd vclk: 0 dclk: 0 power level 0 sclk: 15700 mclk: 30000 vddc: 950 vddci: 0 power level 1 sclk: 50000 mclk: 110000 vddc: 1100 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: r ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD [drm] Disabling audio 0 support radeon 0000:01:00.0: Saved 247 dwords of commands on ring 0. radeon 0000:01:00.0: GPU softreset: 0x00000009 radeon 0000:01:00.0: GRBM_STATUS = 0xF0001828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x80000003 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40040000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048006 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88031ac2dc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88031ac2dc0c radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9001219c418 [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] Enabling audio 0 support ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 1 usecs [drm:uvd_v1_0_ib_test] *ERROR* radeon: failed to get create msg (-22). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). switching from power state: ui class: none internal class: boot caps: video uvd vclk: 0 dclk: 0 power level 0 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 1 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: c b switching to power state: ui class: performance internal class: none caps: single_disp video uvd vclk: 0 dclk: 0 power level 0 sclk: 15700 mclk: 30000 vddc: 950 vddci: 0 power level 1 sclk: 50000 mclk: 110000 vddc: 1100 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: r ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 75127] New: Radeon SUMO: atombios stuck executing
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75127 Priority: medium Bug ID: 75127 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon SUMO: atombios stuck executing Severity: major Classification: Unclassified OS: Linux (All) Reporter: sandy.8925(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 94246 --> https://bugs.freedesktop.org/attachment.cgi?id=94246&action=edit linux_kernel_3.14-rc2_dmesg I have a laptop with Radeon HD6520G GPU. I am running Arch Linux 64 bit with Linux 3.14-rc2 kernel and Mesa 10.0.3 During shutdown, suspend and resume, GPU hangs and I get error messages in the kernel that state: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D05E (len 62, WS 0, PS 0) @ 0xD07A Earlier, shutdown would work fine, and laptop would also suspend quickly. However now I find that suspend and shutdown take a long time and I see the above error messages. -- You are receiving this mail because: You are the assignee for the bug.

1 46

[Bug 75102] New: Radeon 4890 getting a blank screen and fans go up to 100% (kernel 3.13.3)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75102 Priority: medium Bug ID: 75102 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon 4890 getting a blank screen and fans go up to 100% (kernel 3.13.3) Severity: critical Classification: Unclassified OS: Linux (All) Reporter: peterasplund(a)gentoo.se Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI I've been fiddling around with the cooling on my Radeon 4890 and replaced it with an Arctic Cooling I had mounted on my old 4850 card. It worked for a while, but then the screens went black and the fan maxed out completely. BUT I noticed that the computer was still running, so it hadn't crashed. I could SSH in and reboot it manually. I figured the card had gotten to hot, so I switched the coolers again. But the problem was still there! I started monitoring the temperatures, and they really weren't any hotter than normal. Around 45 degrees C. The weird behavior still repeated itself, even when just browsing the web for a couple of minutes. One time it happened after only 2-3 minutes! I then booted into Windows to see if the problem was there, and nothing happened. I ran benchmarks (3D Mark) and played Left 4 Dead on highest settings for an hour, and no issues. I then booted into Linux, and it still happened. So I then realized I had updated the kernel to 3.13.3 from 3.12.3, and I booted into the old kernel instead. And now I've been running some "emerges" for an hour, and browsed the web, without any issues. Is it possible some weird bug has gotten into the 3.13 kernel? I googled the issue, and saw that there were several posts about the same behavior on the Catalyst drivers a year or so back. Even on Windows that is. -- You are receiving this mail because: You are the assignee for the bug.

1 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2014