dri-devel March 2014

dri-devel@lists.freedesktop.org

144 participants
926 discussions

[Bug 73530] New: Asus U38N: Black screen with Radeon driver in Linux 3.10, 3.11 and 3.12
by bugzilla-daemon＠freedesktop.org 12 Aug '15

12 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=73530 Priority: medium Bug ID: 73530 Assignee: dri-devel(a)lists.freedesktop.org Summary: Asus U38N: Black screen with Radeon driver in Linux 3.10, 3.11 and 3.12 Severity: major Classification: Unclassified OS: All Reporter: paulepanter(a)users.sourceforge.net Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Copying my message to list dri-devel [1]. As reported in the channel #radeon on <irc.freenode.net>, with the laptop Asus U38N-C4010H with an AMD Radeon HD 7600G (Trinity A8-4555M) I am unable to get something displayed on the screen with modesetting enabled. The backlight of the screen is on, but nothing is shown on the screen. Booting with `radeon.modeset=0` on the Linux kernel command line works. I was able to reproduce this problem with Grml with Linux 3.10 and 3.11 and Debian Sid/unstable with Linux 3.12.6. Attaching a VGA monitor to the mini VGA connector using an adapter, nothing was shown on the monitor either. The following is the output I get when starting with `radeon.modeset=0` and then doing `sudo modprobe -r radeon` and `sudo modprobe radeon modeset=1`. Jan 11 06:42:24 myhostname kernel: [ 1060.871165] [drm] radeon kernel modesetting enabled. Jan 11 06:42:24 myhostname kernel: [ 1060.871244] checking generic (d0000000 1f0000) vs hw (d0000000 10000000) Jan 11 06:42:24 myhostname kernel: [ 1060.871247] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Jan 11 06:42:24 myhostname kernel: [ 1060.871322] Console: switching to colour dummy device 80x25 Jan 11 06:42:24 myhostname kernel: [ 1060.871836] [drm] initializing kernel modesetting (ARUBA 0x1002:0x9908 0x1043:0x1557). Jan 11 06:42:24 myhostname kernel: [ 1060.871882] [drm] register mmio base: 0xFEB00000 Jan 11 06:42:24 myhostname kernel: [ 1060.871884] [drm] register mmio size: 262144 Jan 11 06:42:24 myhostname kernel: [ 1060.871913] [drm] ACPI VFCT contains a BIOS for 00:01.0 1002:9908, size 19968 Jan 11 06:42:24 myhostname kernel: [ 1060.871925] ATOM BIOS: 113 Jan 11 06:42:24 myhostname kernel: [ 1060.871997] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 - 0x000000002FFFFFFF (768M used) Jan 11 06:42:24 myhostname kernel: [ 1060.872000] radeon 0000:00:01.0: GTT: 1024M 0x0000000030000000 - 0x000000006FFFFFFF Jan 11 06:42:24 myhostname kernel: [ 1060.872003] [drm] Detected VRAM RAM=768M, BAR=256M Jan 11 06:42:24 myhostname kernel: [ 1060.872005] [drm] RAM width 64bits DDR Jan 11 06:42:24 myhostname kernel: [ 1060.872088] [TTM] Zone kernel: Available graphics memory: 1581256 kiB Jan 11 06:42:24 myhostname kernel: [ 1060.872091] [TTM] Initializing pool allocator Jan 11 06:42:24 myhostname kernel: [ 1060.872101] [TTM] Initializing DMA pool allocator Jan 11 06:42:24 myhostname kernel: [ 1060.872129] [drm] radeon: 768M of VRAM memory ready Jan 11 06:42:24 myhostname kernel: [ 1060.872133] [drm] radeon: 1024M of GTT memory ready. Jan 11 06:42:24 myhostname kernel: [ 1060.874660] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/TAHITI_uvd.bin Jan 11 06:42:24 myhostname kernel: [ 1060.874989] [drm] GART: num cpu pages 262144, num gpu pages 262144 Jan 11 06:42:24 myhostname kernel: [ 1060.882325] [drm] Loading ARUBA Microcode Jan 11 06:42:24 myhostname kernel: [ 1060.882749] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_pfp.bin Jan 11 06:42:24 myhostname kernel: [ 1060.883100] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_me.bin Jan 11 06:42:24 myhostname kernel: [ 1060.883456] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_rlc.bin Jan 11 06:42:24 myhostname kernel: [ 1060.884967] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). Jan 11 06:42:24 myhostname kernel: [ 1060.885159] radeon 0000:00:01.0: WB enabled Jan 11 06:42:24 myhostname kernel: [ 1060.885166] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00 and cpu addr 0xffff880129f11c00 Jan 11 06:42:24 myhostname kernel: [ 1060.885905] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011db5a18 Jan 11 06:42:24 myhostname kernel: [ 1060.885910] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04 and cpu addr 0xffff880129f11c04 Jan 11 06:42:24 myhostname kernel: [ 1060.885914] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08 and cpu addr 0xffff880129f11c08 Jan 11 06:42:24 myhostname kernel: [ 1060.885918] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c and cpu addr 0xffff880129f11c0c Jan 11 06:42:24 myhostname kernel: [ 1060.885922] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10 and cpu addr 0xffff880129f11c10 Jan 11 06:42:24 myhostname kernel: [ 1060.885929] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Jan 11 06:42:24 myhostname kernel: [ 1060.885931] [drm] Driver supports precise vblank timestamp query. Jan 11 06:42:24 myhostname kernel: [ 1060.885958] radeon 0000:00:01.0: irq 52 for MSI/MSI-X Jan 11 06:42:24 myhostname kernel: [ 1060.885982] radeon 0000:00:01.0: radeon: using MSI. Jan 11 06:42:24 myhostname kernel: [ 1060.886266] [drm] radeon: irq initialized. Jan 11 06:42:24 myhostname kernel: [ 1060.905813] [drm] ring test on 0 succeeded in 2 usecs Jan 11 06:42:24 myhostname kernel: [ 1060.905876] [drm] ring test on 3 succeeded in 2 usecs Jan 11 06:42:24 myhostname kernel: [ 1060.905885] [drm] ring test on 4 succeeded in 1 usecs Jan 11 06:42:24 myhostname kernel: [ 1060.961514] [drm] ring test on 5 succeeded in 1 usecs Jan 11 06:42:24 myhostname kernel: [ 1060.981502] [drm] UVD initialized successfully. Jan 11 06:42:24 myhostname kernel: [ 1060.985538] [drm] Enabling audio 0 support Jan 11 06:42:24 myhostname kernel: [ 1060.985544] [drm] Enabling audio 1 support Jan 11 06:42:24 myhostname kernel: [ 1060.985549] [drm] Enabling audio 2 support Jan 11 06:42:24 myhostname kernel: [ 1060.985553] [drm] Enabling audio 3 support Jan 11 06:42:24 myhostname kernel: [ 1060.985557] [drm] Enabling audio 4 support Jan 11 06:42:24 myhostname kernel: [ 1060.985560] [drm] Enabling audio 5 support Jan 11 06:42:24 myhostname kernel: [ 1060.986106] [drm] ib test on ring 0 succeeded in 0 usecs Jan 11 06:42:24 myhostname kernel: [ 1060.986644] [drm] ib test on ring 3 succeeded in 0 usecs Jan 11 06:42:24 myhostname kernel: [ 1060.987175] [drm] ib test on ring 4 succeeded in 1 usecs Jan 11 06:42:24 myhostname kernel: [ 1061.007977] [drm] ib test on ring 5 succeeded Jan 11 06:42:24 myhostname kernel: [ 1061.032890] [drm] radeon atom DIG backlight initialized Jan 11 06:42:24 myhostname kernel: [ 1061.032894] [drm] Radeon Display Connectors Jan 11 06:42:24 myhostname kernel: [ 1061.032897] [drm] Connector 0: Jan 11 06:42:24 myhostname kernel: [ 1061.032899] [drm] eDP-1 Jan 11 06:42:24 myhostname kernel: [ 1061.032901] [drm] HPD1 Jan 11 06:42:24 myhostname kernel: [ 1061.032904] [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c Jan 11 06:42:24 myhostname kernel: [ 1061.032906] [drm] Encoders: Jan 11 06:42:24 myhostname kernel: [ 1061.032908] [drm] LCD1: INTERNAL_UNIPHY2 Jan 11 06:42:24 myhostname kernel: [ 1061.032909] [drm] Connector 1: Jan 11 06:42:24 myhostname kernel: [ 1061.032911] [drm] VGA-1 Jan 11 06:42:24 myhostname kernel: [ 1061.032912] [drm] HPD2 Jan 11 06:42:24 myhostname kernel: [ 1061.032915] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c Jan 11 06:42:24 myhostname kernel: [ 1061.032916] [drm] Encoders: Jan 11 06:42:24 myhostname kernel: [ 1061.032917] [drm] CRT1: INTERNAL_UNIPHY2 Jan 11 06:42:24 myhostname kernel: [ 1061.032919] [drm] CRT1: NUTMEG Jan 11 06:42:24 myhostname kernel: [ 1061.032920] [drm] Connector 2: Jan 11 06:42:24 myhostname kernel: [ 1061.032922] [drm] HDMI-A-1 Jan 11 06:42:24 myhostname kernel: [ 1061.032923] [drm] HPD3 Jan 11 06:42:24 myhostname kernel: [ 1061.032925] [drm] DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c Jan 11 06:42:24 myhostname kernel: [ 1061.032926] [drm] Encoders: Jan 11 06:42:24 myhostname kernel: [ 1061.032928] [drm] DFP1: INTERNAL_UNIPHY Jan 11 06:42:25 myhostname kernel: [ 1061.082355] [drm] Internal thermal controller without fan control Jan 11 06:42:25 myhostname kernel: [ 1061.082493] [drm] radeon: power management initialized Jan 11 06:42:26 myhostname kernel: [ 1062.360915] [drm] fb mappable at 0xD1488000 Jan 11 06:42:26 myhostname kernel: [ 1062.360922] [drm] vram apper at 0xD0000000 Jan 11 06:42:26 myhostname kernel: [ 1062.360926] [drm] size 8294400 Jan 11 06:42:26 myhostname kernel: [ 1062.360928] [drm] fb depth is 24 Jan 11 06:42:26 myhostname kernel: [ 1062.360931] [drm] pitch is 7680 Jan 11 06:42:26 myhostname kernel: [ 1062.361231] fbcon: radeondrmfb (fb0) is primary device Jan 11 06:42:28 myhostname kernel: [ 1064.675993] Console: switching to colour frame buffer device 240x67 Jan 11 06:42:28 myhostname kernel: [ 1064.681973] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device Jan 11 06:42:28 myhostname kernel: [ 1064.681976] radeon 0000:00:01.0: registered panic notifier Jan 11 06:42:28 myhostname kernel: [ 1064.682222] [drm] Initialized radeon 2.34.0 20080528 for 0000:00:01.0 on minor 0 The screen turns off shortly (backlight too) and then only the backlight comes back up. As requested by Alex [2] I am going to attach the two files. [1] http://lists.freedesktop.org/archives/dri-devel/2014-January/051737.html [2] http://lists.freedesktop.org/archives/dri-devel/2014-January/051791.html -- You are receiving this mail because: You are the assignee for the bug.

1 119

[Bug 73792] New: UVD usage with HD makes X11 quite unstable on Samsung ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics))
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=73792 Priority: medium Bug ID: 73792 Assignee: dri-devel(a)lists.freedesktop.org Summary: UVD usage with HD makes X11 quite unstable on Samsung ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics)) Severity: normal Classification: Unclassified OS: All Reporter: rvdb(a)cryptolab.net Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 92387 --> https://bugs.freedesktop.org/attachment.cgi?id=92387&action=edit Dmesg output I have a Smasung ATIV Bool Lite 9 notebook on which I installed a Slackware-current system which works roughly well except suspend and UVD playback. About the later, I run a Kernel 3.12.8 with less-than-a-week-ago git pulls of libdrm, glamor, mesa, mesa-glu and xfree-video-ati. Desktop graphic and compositing work well without glitch and no specific lag. I use libvdpau 0.7 and less-than-a-week-ago git pulls of ffmpeg, x264 and vlc. vlc is configured to use VDPAU and this the UVD chip in the processor. When running SD h264 videos, everything works fine and the CPU usage is low (less than 75% of total W11/KWin/vlc on a GHz core, that's fine with me). I get issues when trying to run HD h264 videos. The CPU usage is still fine, the video starts but after some time, the video hangs, the system becomes unresponsive then the screen turns black, as displaying a black image, it's a bit less black then when the screen is turned of. At this point, either I need to reboot or at some point, the screen seems to turn of, then light up again and resume where I was, though sometimes the video remains black and I have to move the VLC slider to get some images. Then the film can play several seconds then the whole pattern occurs again. And so on until the system does not resume and I must reboot. I've attached dmesg, syslog, glxinfo et vdpauinfo outputs. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 69196] New: gpu lockup and full crash when starting some games in wine
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=69196 Priority: medium Bug ID: 69196 Assignee: dri-devel(a)lists.freedesktop.org Summary: gpu lockup and full crash when starting some games in wine Severity: normal Classification: Unclassified OS: Linux (All) Reporter: maxmusterm(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 85587 --> https://bugs.freedesktop.org/attachment.cgi?id=85587&action=edit kernel log from the crash First of I searched the bugs and found some similar looking bugs but none which stroke me as the same bug. lspci tells me my graphics card is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770 GHz Edition] I always use everything mesa and kernel vanilla from git. My kernel has the version 3.11.0-1-08716-g26b0332-dirty.The mesa checkout is 4 days old. glxinfo tells me Mesa 9.3.0-devel (git-0f6fce1) (if this is relevant) I tested it with hyperz enabled and disabled both time it failed the same way. First the display turns dark (no signal) and then after being responsive for a few seconds the pc crashes completly. If I kill the process in time it doesn't die completly on me. I don't know if this is of any relevance but the firmware for the card was missing and I grabbed the file from here: http://people.freedesktop.org/~agd5f/radeon_ucode/VERDE_smc.bin I'll refrain from parsin anything specific from the kernel log since I don't know which lines are relevant -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 32312] New: openvg "lion" demo freezes the system & lockup GPU with r600g
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=32312 Summary: openvg "lion" demo freezes the system & lockup GPU with r600g Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: virtuousfox(a)gmail.com in time of bug #30684 r600g were giving poor performance with "lion" demo (about ~30 fps on my system) but not long ago i've noticed big, x10 time speedup (up to ~350 fps). however, it was not for long: with 783e7caadf945f176cb297b8791769e2855fc9ef revision launching "lion" demo on my system results in 1) video system freeze 2) 100% CPU time usage on all cores and total system freeze up if i not act quickly and not kill demo process via ssh fast if killed in time - all goes back to normal, in exception of launching gles1gears demo right after which results in same behaviour. however, repeated launch of gles1gears results in working demo but with some artefacts. third launch is all ok. i'm pretty sure that regression was introduced in r600g in last 48 ~hours (same revision but with r300g work ok) but i haven't done bisect. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 60254] New: agd5f wip kernel Oops when provoking GPU lock.
by bugzilla-daemon＠freedesktop.org 30 Jul '15

30 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=60254 Priority: medium Bug ID: 60254 Assignee: dri-devel(a)lists.freedesktop.org Summary: agd5f wip kernel Oops when provoking GPU lock. Severity: normal Classification: Unclassified OS: All Reporter: lists(a)andyfurniss.entadsl.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI The GPU lock with Rv670 and openarena is nothing new - it seems to have been a feature for almost a year (I haven't used rv670 for most of that time). On noticing the new gpu reset code in drm-next-3.9-wip I decided to provoke it on my AGP box and got - Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup (waiting for 0x00000000000111c8 last fence id 0x00000000000111c6) Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: f51df600 unpin not necessary Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: Saved 217 dwords of commands on ring 0. Feb 3 20:46:56 nf7 kernel: BUG: unable to handle kernel paging request at f87aec0c Feb 3 20:46:56 nf7 kernel: IP: [<fa033a3e>] radeon_fence_process+0x7e/0x160 [radeon] Feb 3 20:46:56 nf7 kernel: *pde = 3702f067 *pte = 00000000 Feb 3 20:46:56 nf7 kernel: Oops: 0000 [#1] PREEMPT Feb 3 20:46:56 nf7 kernel: Modules linked in: radeon fbcon font bitblit ttm softcursor drm_kms_helper drm fb fbdev i2c_algo_bit i2c_core cfbcopyarea cfbimgblt cfbfillrect ehci_pci ehci_hcd nvidia_agp agpgart ohci_hcd usbhid usbcore usb_common snd_intel8x0 snd_ac97_codec ac97_bus forcedeth Feb 3 20:46:56 nf7 kernel: Pid: 2511, comm: openarena.i386 Not tainted 3.8.0-rc3-gc7fb5ff #1 /NF7-S/NF7 (nVidia-nForce2) Feb 3 20:46:56 nf7 kernel: EIP: 0060:[<fa033a3e>] EFLAGS: 00210246 CPU: 0 Feb 3 20:46:56 nf7 kernel: EIP is at radeon_fence_process+0x7e/0x160 [radeon] Feb 3 20:46:56 nf7 kernel: EAX: f87aec0c EBX: f73b2848 ECX: f73b2848 EDX: 00000000 Feb 3 20:46:56 nf7 kernel: ESI: 00000000 EDI: f73b2000 EBP: e4765d8c ESP: e4765d58 Feb 3 20:46:56 nf7 kernel: DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 Feb 3 20:46:56 nf7 kernel: CR0: 8005003b CR2: f87aec0c CR3: 1e75f000 CR4: 000007d0 Feb 3 20:46:56 nf7 kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 Feb 3 20:46:56 nf7 kernel: DR6: ffff0ff0 DR7: 00000400 Feb 3 20:46:56 nf7 kernel: Process openarena.i386 (pid: 2511, ti=e4764000 task=f70ad2b0 task.ti=e4764000) Feb 3 20:46:56 nf7 kernel: Stack: Feb 3 20:46:56 nf7 kernel: c13d4e58 00765d7c 00000018 f73b2848 f73b2888 00000872 00000003 00000872 Feb 3 20:46:56 nf7 kernel: 00000000 0000000c 00000003 f73b2a5c e4765e0c e4765da4 fa034850 f73b2000 Feb 3 20:46:56 nf7 kernel: f73b2000 f73b2a5c e4765e0c e4765dc4 fa049bb8 f73b28e8 00000000 c12b06cd Feb 3 20:46:56 nf7 kernel: Call Trace: Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80 Feb 3 20:46:56 nf7 kernel: [<fa034850>] radeon_fence_count_emitted+0x20/0x90 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa049bb8>] radeon_ring_backup+0x38/0x100 [radeon] Feb 3 20:46:56 nf7 kernel: [<c12b06cd>] ? _dev_info+0x2d/0x30 Feb 3 20:46:56 nf7 kernel: [<fa020b22>] radeon_gpu_reset+0x62/0x1d0 [radeon] Feb 3 20:46:56 nf7 kernel: [<f8be99c6>] ? ttm_bo_unreserve+0x26/0x50 [ttm] Feb 3 20:46:56 nf7 kernel: [<fa04821d>] radeon_gem_handle_lockup.part.2+0xd/0x20 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa048b13>] radeon_gem_wait_idle_ioctl+0xb3/0xd0 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0 [radeon] Feb 3 20:46:56 nf7 kernel: [<f8af9e82>] drm_ioctl+0x402/0x460 [drm] Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0 [radeon] Feb 3 20:46:56 nf7 kernel: [<c104f469>] ? ktime_add_safe+0x9/0x60 Feb 3 20:46:56 nf7 kernel: [<c104fe80>] ? hrtimer_forward+0xa0/0x190 Feb 3 20:46:56 nf7 kernel: [<f8af9a80>] ? drm_copy_field+0x80/0x80 [drm] Feb 3 20:46:56 nf7 kernel: [<c10eb65a>] do_vfs_ioctl+0x7a/0x590 Feb 3 20:46:56 nf7 kernel: [<c101ef0b>] ? lapic_next_event+0x1b/0x20 Feb 3 20:46:56 nf7 kernel: [<c106978d>] ? clockevents_program_event+0x9d/0x150 Feb 3 20:46:56 nf7 kernel: [<c106ab18>] ? tick_program_event+0x28/0x30 Feb 3 20:46:56 nf7 kernel: [<c1050612>] ? hrtimer_interrupt+0x182/0x2f0 Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80 Feb 3 20:46:56 nf7 kernel: [<c1048cf9>] ? __rcu_read_unlock+0x9/0x60 Feb 3 20:46:56 nf7 kernel: [<c10f4bc7>] ? fget_light+0x77/0xd0 Feb 3 20:46:56 nf7 kernel: [<c10ebbac>] sys_ioctl+0x3c/0x70 Feb 3 20:46:56 nf7 kernel: [<c13d7ffa>] sysenter_do_call+0x12/0x22 Feb 3 20:46:56 nf7 kernel: Code: 8b 4d d4 8d 84 51 f0 00 00 00 8b 74 c7 08 89 75 e0 8b 74 c7 0c 8b 45 d8 83 c0 08 80 bf ec 0d 00 00 00 0f 84 bf 00 00 00 8b 40 0c <8b> 00 39 45 e8 8b 4d ec 89 c3 ba 01 00 00 00 0f 47 ce 39 f1 77 Feb 3 20:46:56 nf7 kernel: EIP: [<fa033a3e>] radeon_fence_process+0x7e/0x160 [radeon] SS:ESP 0068:e4765d58 Feb 3 20:46:56 nf7 kernel: CR2: 00000000f87aec0c Feb 3 20:46:56 nf7 kernel: ---[ end trace 457588a7cbc40235 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 70227] New: OpenCL reaper-prime app crashes due to atomic_or unimplemented
by bugzilla-daemon＠freedesktop.org 29 Jul '15

29 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=70227 Priority: medium Bug ID: 70227 Assignee: dri-devel(a)lists.freedesktop.org Summary: OpenCL reaper-prime app crashes due to atomic_or unimplemented Severity: normal Classification: Unclassified OS: All Reporter: alexxy(a)gentoo.org Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Miner app https://github.com/arnuschky/primecoin-reaper.git crashes with ./reaper \|||||||||||||||||||||/ - Reaper v13 64-bit - - PRIME BETA 2 - - coded by mtrlt - /|||||||||||||||||||||\ Warning: unknown property "use_gpu" in configuration file. I'm now mining primecoin! Share thread started GeneratePrimeTable() : setting nSievePercentage = 1, nSieveSize = 100000 GeneratePrimeTable() : prime table [1, 100000] generated with 9592 primes Available CPU mining algorithms: hp7 Using default: hp7 Creating 1 CPU thread. 1...Warning: can't set thread priority done List of platforms: 0 Default Using platform number 0 Using device 0 OpenCL device 0........ Compiling kernel... this could take up to 2 minutes. 2 warnings generated. Building kernel CalculateMultipliers Building kernel Sieve Building kernel Combine Building kernel Fermat done Compiling kernel... this could take up to 2 minutes. 2 warnings generated. Building kernel CalculateMultipliers Building kernel Sieve Building kernel Combine Building kernel Fermat 0x7f735cdadd00: i32 = GlobalAddress<i32 (...)* @atomic_or> 0 [ORD=104] Stack dump: 0. Running pass 'Function Pass Manager' on module 'radeon'. 1. Running pass 'AMDGPU DAG->DAG Pattern Instruction Selection' on function '@Sieve' Segmentation fault -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 33399] New: No HDMI PCM mutichannel audio
by bugzilla-daemon＠freedesktop.org 14 Jul '15

14 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=33399 Summary: No HDMI PCM mutichannel audio Product: DRI Version: XOrg CVS Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: xavier.bestel(a)free.fr Hi, using a HD 2600, audio over HDMI is stereo-only. The only mean to have multichannel (e.g. 5.1) is to use passthrough, but true multichannel (e.g. 8 channels PCM) isn't supported by the driver, although it should be supported by the HDMI standard. Here's the excerpt from alsa-info.sh concerning the card: Codec: ATI R6xx HDMI Address: 0 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x1002aa01 Subsystem Id: 0x00aa0100 Revision Id: 0x100000 No Modem Function Group found Default PCM: rates [0x40]: 48000 bits [0x2]: 16 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A GPIO: io=0, o=0, i=0, unsolicited=0, wake=0 Node 0x02 [Audio Output] wcaps 0x201: Stereo Digital Control: name="IEC958 Playback Con Mask", index=0, device=0 Control: name="IEC958 Playback Pro Mask", index=0, device=0 Control: name="IEC958 Playback Default", index=0, device=0 Control: name="IEC958 Playback Switch", index=0, device=0 Device: name="HDMI 0", type="HDMI", device=3 Converter: stream=1, channel=0 Digital: Enabled GenLevel Digital category: 0x2 Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x00000094: OUT Detect HDMI Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x02 Full data is at http://www.alsa-project.org/db/?f=b3f67a0890f9878b7b3f345578e24eda0aaa59ac Thanks, Xav -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 65730] New: no sound via HDMI for Radeon 6850 mesa driver
by bugzilla-daemon＠freedesktop.org 13 Jul '15

13 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=65730 Priority: medium Bug ID: 65730 Assignee: dri-devel(a)lists.freedesktop.org Summary: no sound via HDMI for Radeon 6850 mesa driver Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jasontheparamedic(a)hotmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Drivers/DRI/R600 Product: Mesa Greetings, this is my first bug report so I apologize if it is placed in the wrong section. I am unable to get sound via HDMI cable using the open source driver for my Radeon 6850. I have (X)ubuntu 13.04 32bit system, using mesa 9.2, as provided by the xorg-edgers ppa, using all appropriate updates as passed downstream by the ppa. Using the FGLRX driver does fix the sound issue along with providing a high level of hardware acceleration, but it does cripple me being able to play on some emulators due to the well-known buggy nature of the FGLRX driver. I already made a report on the askubuntu.com forums, but so far there has been no response. My motherboard's native sound card is broken, so currently I have my computer speakers plugged into the HD monitor, hence HDMI sound is my only choice at this time. Here is a link to my askubuntu question (so as to avoid duplication of effort with providing info). http://askubuntu.com/questions/306196/no-sound-via-hdmi-using-xubuntu-13-04… Thanks in advance for any assistance. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 70689] New: Periodic system freezes on Linux 3.11-rc4 and later
by bugzilla-daemon＠freedesktop.org 13 Jul '15

13 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=70689 Priority: medium Bug ID: 70689 Assignee: dri-devel(a)lists.freedesktop.org Summary: Periodic system freezes on Linux 3.11-rc4 and later Severity: normal Classification: Unclassified OS: All Reporter: krejzi(a)email.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Ever since Linux 3.11-rc4 (still present in 3.12-rc6), when both Radeon and Intel GPUs are enabled on a hybrid graphics laptop, system freezes (well, the picture freezes) every minute or two, then unfreezes and so on, making system unusable. When I disable radeon graphics card via vgaswitcheroo, freezes stop. I have, however, discovered that when radeon driver gets loaded before i915 one, freezes happen. If i915 manages to get loaded before radeon, freezes don't happen. When both are built into kernel, radeon driver gets always loaded before i915. This behaviour wasn't present in 3.11-rc3 kernel. Discrete card is Radeon HD 6450M and integrated one is Intel HD 3000. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 71226] New: Colors occasionally broken on DCE5 Barts (HD69xx)
by bugzilla-daemon＠freedesktop.org 13 Jul '15

13 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=71226 Priority: medium Bug ID: 71226 Assignee: dri-devel(a)lists.freedesktop.org Summary: Colors occasionally broken on DCE5 Barts (HD69xx) Severity: normal Classification: Unclassified OS: All Reporter: zajec5(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI >From time to time colors on my displays appear broken. It happens randomly and is pretty hard to reproduce. -- You are receiving this mail because: You are the assignee for the bug.

1 11

← Newer
1
...
43
44
45
46
47
48
49
...
93
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2014