dri-devel March 2014

dri-devel@lists.freedesktop.org

144 participants
926 discussions

3.14 radeon regression: radeon is broken (pci bug?)
by Andy Lutomirski 16 Sep '14

16 Sep '14

My system works on a 3.13 Fedora kernel. It does not work on a more-or-less identically configured 3.14-rc7+ kernel. The symptom is that the Plymouth password prompt flashes and them the screen goes blank. Hitting escape brings back the text console, and all is well until X tries to start. Then I get a blank screen. killall -9 Xorg from ssh causes these errors to be logged: [ 226.239747] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 226.239751] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD34 (len 55, WS 0, PS 0) @ 0xCD57 [ 231.241492] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 231.241496] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD6C (len 62, WS 0, PS 0) @ 0xCD88 [ 236.243111] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 236.243115] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD6C (len 62, WS 0, PS 0) @ 0xCD88 [ 241.244625] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 241.244628] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD6C (len 62, WS 0, PS 0) @ 0xCD88 lspci -vvvxxxnn on 3.14-rc7+ says: 09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: radeon 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 09:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] [1002:aa98] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: snd_hda_intel 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff (oops!) On 3.13, it says: 09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB DDR3 [174b:e164] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 92 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at f4a20000 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at c000 [size=256] Expansion ROM at f4a00000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon 00: 02 10 79 67 07 04 10 00 00 00 00 03 10 00 80 00 10: 0c 00 00 e0 00 00 00 00 04 00 a2 f4 00 00 00 00 20: 01 c0 00 00 00 00 00 00 00 00 00 00 4b 17 64 e1 30: 00 00 a0 f4 50 00 00 00 00 00 00 00 0a 01 00 00 09:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] [1002:aa98] Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1GB DDR3 [174b:aa98] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 96 Region 0: Memory at f4a40000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel 00: 02 10 98 aa 06 04 10 00 00 00 03 04 10 00 80 00 10: 04 00 a4 f4 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 4b 17 98 aa 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 02 00 00 Logs attached. Unfortunately, I'll be away from this computer until Wednesday.

3 8

[Bug 34462] New: 180 second hang on boot, DRM doesn't seem to initialize (firmware issue?)
by bugzilla-daemon＠freedesktop.org 14 Sep '14

14 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=34462 Summary: 180 second hang on boot, DRM doesn't seem to initialize (firmware issue?) 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: owen.riddy(a)gmail.com Created an attachment (id=43540) --> (https://bugs.freedesktop.org/attachment.cgi?id=43540) dmesg from Debian Unstable, fails to load I have a Radeon 3450 graphics card and have been using Debian Squeeze (linux 2.6.32). The card was/is very well supported by the radeon graphics driver, and firmware was being properly loaded (Debian splits the firmware into a separate package from the kernel). Whenever I compiled a newer vanilla kernel KMS didn't work (starting with 2.6.33, I believe. It was a while ago) and X wouldn't load. Every so often I tried a different kernel, and the problem remained. On X, the system would completely hang with a blank screen (I couldn't access any virtual terminals). I assumed I'd mis-configured my kernel and gave up. Debian has now upgraded to linux 2.6.37-1 and this image seems to have the same problem. After upgrading, I get a suspicious 180 second pause when the kernel "populates /dev", which I now attribute to a bug. I'm getting an error message about modprobe blocking (in dmesg). I suspect firmware loading problems: Wheezy (fails, 2.6.37): dmesg | grep -C 4 icroc [ 4.325551] [drm] radeon: 256M of VRAM memory ready [ 4.325554] [drm] radeon: 512M of GTT memory ready. [ 4.325619] [drm] radeon: irq initialized. [ 4.325622] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 4.326544] [drm] Loading RS780 Microcode [ 4.329997] input: HDA ATI SB Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input7 [ 4.414321] radeon 0000:01:05.0: WB enabled [ 4.446469] [drm] ring test succeeded in 1 usecs [ 4.446595] [drm] radeon: ib pool ready. Squeeze (works, 2.6.32): dmesg | grep -C 4 icroc [ 4.616162] [drm] radeon: 256M of VRAM memory ready [ 4.616163] [drm] radeon: 512M of GTT memory ready. [ 4.616204] [drm] radeon: irq initialized. [ 4.616206] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 4.616624] [drm] Loading RS780 Microcode [ 4.616627] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 4.714728] hda_codec: ALC1200: BIOS auto-probing. [ 4.716081] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/input/input6 [ 4.809447] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin -- [ 4.941941] radeon 0000:02:00.0: irq 30 for MSI/MSI-X [ 4.941946] radeon 0000:02:00.0: radeon: using MSI. [ 4.941978] [drm] radeon: irq initialized. [ 4.941980] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 4.942370] [drm] Loading RV620 Microcode [ 4.942372] platform radeon_cp.0: firmware: requesting radeon/RV620_pfp.bin [ 4.982496] platform radeon_cp.0: firmware: requesting radeon/RV620_me.bin [ 4.988086] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 5.025570] [drm] ring test succeeded in 0 usecs To be sure I haven't tainted the configuration, the method to get a test platform was: * Installed the Squeeze release base system * Upgrade to Wheezy, rebooted to test KMS (virtual terminal screen resolution was large, suggesting it worked) * Upgraded to unstable and reboot, at which point I get the 180 second hang and modprobe errors, as well as a rather low resolution VT. lspci and other info can be found on this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613922 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[PATCH] drm/exynos: use a new anon file for exynos gem mmaper
by Inki Dae 11 Sep '14

11 Sep '14

This patch resolves potential deadlock issue that can be incurred by changing file->f_op and filp->private_data to exynos specific mapper ops and gem object temporarily. To resolve this issue, this patch creates a new anon file dedicated to exynos specific mmaper, and making it used instead of existing one. Signed-off-by: Inki Dae <inki.dae(a)samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park(a)samsung.com> --- drivers/gpu/drm/exynos/exynos_drm_drv.c | 21 +++++++++ drivers/gpu/drm/exynos/exynos_drm_drv.h | 1 + drivers/gpu/drm/exynos/exynos_drm_gem.c | 74 ++++++------------------------- drivers/gpu/drm/exynos/exynos_drm_gem.h | 3 ++ 4 files changed, 38 insertions(+), 61 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c b/drivers/gpu/drm/exynos/exynos_drm_drv.c index 22b8f5e..b5e5957 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_drv.c +++ b/drivers/gpu/drm/exynos/exynos_drm_drv.c @@ -14,6 +14,8 @@ #include <drm/drmP.h> #include <drm/drm_crtc_helper.h> +#include <linux/anon_inodes.h> + #include <drm/exynos_drm.h> #include "exynos_drm_drv.h" @@ -150,9 +152,14 @@ static int exynos_drm_unload(struct drm_device *dev) return 0; } +static const struct file_operations exynos_drm_gem_fops = { + .mmap = exynos_drm_gem_mmap_buffer, +}; + static int exynos_drm_open(struct drm_device *dev, struct drm_file *file) { struct drm_exynos_file_private *file_priv; + struct file *anon_filp; int ret; file_priv = kzalloc(sizeof(*file_priv), GFP_KERNEL); @@ -167,6 +174,16 @@ static int exynos_drm_open(struct drm_device *dev, struct drm_file *file) file->driver_priv = NULL; } + anon_filp = anon_inode_getfile("exynos_gem", &exynos_drm_gem_fops, + NULL, 0); + if (IS_ERR(anon_filp)) { + kfree(file_priv); + return PTR_ERR(anon_filp); + } + + anon_filp->f_mode = FMODE_READ | FMODE_WRITE; + file_priv->anon_filp = anon_filp; + return ret; } @@ -179,6 +196,7 @@ static void exynos_drm_preclose(struct drm_device *dev, static void exynos_drm_postclose(struct drm_device *dev, struct drm_file *file) { struct exynos_drm_private *private = dev->dev_private; + struct drm_exynos_file_private *file_priv; struct drm_pending_vblank_event *v, *vt; struct drm_pending_event *e, *et; unsigned long flags; @@ -204,6 +222,9 @@ static void exynos_drm_postclose(struct drm_device *dev, struct drm_file *file) } spin_unlock_irqrestore(&dev->event_lock, flags); + file_priv = file->driver_priv; + if (file_priv->anon_filp) + fput(file_priv->anon_filp); kfree(file->driver_priv); file->driver_priv = NULL; diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.h b/drivers/gpu/drm/exynos/exynos_drm_drv.h index eaa1966..0eaf5a2 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_drv.h +++ b/drivers/gpu/drm/exynos/exynos_drm_drv.h @@ -226,6 +226,7 @@ struct exynos_drm_ipp_private { struct drm_exynos_file_private { struct exynos_drm_g2d_private *g2d_priv; struct exynos_drm_ipp_private *ipp_priv; + struct file *anon_filp; }; /* diff --git a/drivers/gpu/drm/exynos/exynos_drm_gem.c b/drivers/gpu/drm/exynos/exynos_drm_gem.c index 1ade191..49b8c9b 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_gem.c +++ b/drivers/gpu/drm/exynos/exynos_drm_gem.c @@ -338,46 +338,22 @@ int exynos_drm_gem_map_offset_ioctl(struct drm_device *dev, void *data, &args->offset); } -static struct drm_file *exynos_drm_find_drm_file(struct drm_device *drm_dev, - struct file *filp) -{ - struct drm_file *file_priv; - - /* find current process's drm_file from filelist. */ - list_for_each_entry(file_priv, &drm_dev->filelist, lhead) - if (file_priv->filp == filp) - return file_priv; - - WARN_ON(1); - - return ERR_PTR(-EFAULT); -} - -static int exynos_drm_gem_mmap_buffer(struct file *filp, +int exynos_drm_gem_mmap_buffer(struct file *filp, struct vm_area_struct *vma) { struct drm_gem_object *obj = filp->private_data; struct exynos_drm_gem_obj *exynos_gem_obj = to_exynos_gem_obj(obj); struct drm_device *drm_dev = obj->dev; struct exynos_drm_gem_buf *buffer; - struct drm_file *file_priv; unsigned long vm_size; int ret; + WARN_ON(!mutex_is_locked(&obj->dev->struct_mutex)); + vma->vm_flags |= VM_IO | VM_DONTEXPAND | VM_DONTDUMP; vma->vm_private_data = obj; vma->vm_ops = drm_dev->driver->gem_vm_ops; - /* restore it to driver's fops. */ - filp->f_op = fops_get(drm_dev->driver->fops); - - file_priv = exynos_drm_find_drm_file(drm_dev, filp); - if (IS_ERR(file_priv)) - return PTR_ERR(file_priv); - - /* restore it to drm_file. */ - filp->private_data = file_priv; - update_vm_cache_attr(exynos_gem_obj, vma); vm_size = vma->vm_end - vma->vm_start; @@ -411,15 +387,13 @@ static int exynos_drm_gem_mmap_buffer(struct file *filp, return 0; } -static const struct file_operations exynos_drm_gem_fops = { - .mmap = exynos_drm_gem_mmap_buffer, -}; - int exynos_drm_gem_mmap_ioctl(struct drm_device *dev, void *data, struct drm_file *file_priv) { + struct drm_exynos_file_private *exynos_file_priv; struct drm_exynos_gem_mmap *args = data; struct drm_gem_object *obj; + struct file *anon_filp; unsigned long addr; if (!(dev->driver->driver_features & DRIVER_GEM)) { @@ -427,47 +401,25 @@ int exynos_drm_gem_mmap_ioctl(struct drm_device *dev, void *data, return -ENODEV; } + mutex_lock(&dev->struct_mutex); + obj = drm_gem_object_lookup(dev, file_priv, args->handle); if (!obj) { DRM_ERROR("failed to lookup gem object.\n"); + mutex_unlock(&dev->struct_mutex); return -EINVAL; } - /* - * We have to use gem object and its fops for specific mmaper, - * but vm_mmap() can deliver only filp. So we have to change - * filp->f_op and filp->private_data temporarily, then restore - * again. So it is important to keep lock until restoration the - * settings to prevent others from misuse of filp->f_op or - * filp->private_data. - */ - mutex_lock(&dev->struct_mutex); - - /* - * Set specific mmper's fops. And it will be restored by - * exynos_drm_gem_mmap_buffer to dev->driver->fops. - * This is used to call specific mapper temporarily. - */ - file_priv->filp->f_op = &exynos_drm_gem_fops; - - /* - * Set gem object to private_data so that specific mmaper - * can get the gem object. And it will be restored by - * exynos_drm_gem_mmap_buffer to drm_file. - */ - file_priv->filp->private_data = obj; + exynos_file_priv = file_priv->driver_priv; + anon_filp = exynos_file_priv->anon_filp; + anon_filp->private_data = obj; - addr = vm_mmap(file_priv->filp, 0, args->size, - PROT_READ | PROT_WRITE, MAP_SHARED, 0); + addr = vm_mmap(anon_filp, 0, args->size, PROT_READ | PROT_WRITE, + MAP_SHARED, 0); drm_gem_object_unreference(obj); if (IS_ERR_VALUE(addr)) { - /* check filp->f_op, filp->private_data are restored */ - if (file_priv->filp->f_op == &exynos_drm_gem_fops) { - file_priv->filp->f_op = fops_get(dev->driver->fops); - file_priv->filp->private_data = file_priv; - } mutex_unlock(&dev->struct_mutex); return (int)addr; } diff --git a/drivers/gpu/drm/exynos/exynos_drm_gem.h b/drivers/gpu/drm/exynos/exynos_drm_gem.h index 702ec3a..fde860c 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_gem.h +++ b/drivers/gpu/drm/exynos/exynos_drm_gem.h @@ -122,6 +122,9 @@ int exynos_drm_gem_map_offset_ioctl(struct drm_device *dev, void *data, int exynos_drm_gem_mmap_ioctl(struct drm_device *dev, void *data, struct drm_file *file_priv); +int exynos_drm_gem_mmap_buffer(struct file *filp, + struct vm_area_struct *vma); + /* map user space allocated by malloc to pages. */ int exynos_drm_gem_userptr_ioctl(struct drm_device *dev, void *data, struct drm_file *file_priv); -- 1.7.9.5

3 7

[Bug 72921] New: DPM Power Cycle with AMD A8-6600K & MSI FM2-A55M-E33
by bugzilla-daemon＠freedesktop.org 09 Sep '14

09 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=72921 Priority: medium Bug ID: 72921 Assignee: dri-devel(a)lists.freedesktop.org Summary: DPM Power Cycle with AMD A8-6600K & MSI FM2-A55M-E33 Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: mmstickman(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa As Linux kernel 3.13 has DPM now enabled by default, it is unbootable due to an issue with DPM and this set of hardware. Soon after the display is initiated, such as when it gets to the login screen, the system will simply power off and reboot if DPM is enabled. -- You are receiving this mail because: You are the assignee for the bug.

3 44

[Bug 44126] New: [r300g] 0ad: carpet textures "flash" and get hidden by ground texture.
by bugzilla-daemon＠freedesktop.org 05 Sep '14

05 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=44126 Bug #: 44126 Summary: [r300g] 0ad: carpet textures "flash" and get hidden by ground texture. Classification: Unclassified Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: fabio.ped(a)libero.it Created attachment 54794 --> https://bugs.freedesktop.org/attachment.cgi?id=54794 example of carpets partially hidden by ground texture Since 0ad alpha 8 there is a new faction: Persians. Their civic center has a couple of carpets on it (just start a map with Persians and see the main building). When you zoom (using mouse wheel) or rotate (using Q and E keys) the screen, the carpets on the civic center "flash" and get partially hidden by the ground texture. An example screenshot is attached. Llvmpipe doesn't have this problem, as well other videos and screenshots found on the net. -- 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 74863] New: [r600g] HyperZ broken on RV770 and CYPRESS (Left 4 Dead 2 trees corruption) bisected!
by bugzilla-daemon＠freedesktop.org 03 Sep '14

03 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=74863 Priority: medium Bug ID: 74863 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] HyperZ broken on RV770 and CYPRESS (Left 4 Dead 2 trees corruption) bisected! Severity: normal Classification: Unclassified OS: Linux (All) Reporter: b.bellec(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 93888 --> https://bugs.freedesktop.org/attachment.cgi?id=93888&action=edit tree correctly rendered Probably the same issue than: https://bugs.freedesktop.org/show_bug.cgi?id=74803 Trees in Left 4 Dead 2 have some rendering issue when you move, so in fact they looks like to blink. See the screenshots attached. This hits my RV770 (HD4850) and CYPRESS (HD5850). When R600_DEBUG=nohyperz is set, there is no problem. R600_DEBUG=nosb doesn't fix. First bad commit is: r600g: defer shader variant selection and depending state updates commit a144bc29b5bb8322a54308603c5d0a8467448164 Signed-off-by: Vadim Girlin <vadimgirlin(a)gmail.com> Signed-off-by: Dave Airlie <airlied(a)redhat.com> Reviewed-by: Alex Deucher <alexander.deucher(a)amd.com> Note that the bug happens in L4D2 only when the option "Effects details" in the graphic options of the game is set to Medium or High, but not when set to Low. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 74784] New: Strange artifacts when rendering tees in Dota 2
by bugzilla-daemon＠freedesktop.org 03 Sep '14

03 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=74784 Priority: medium Bug ID: 74784 Assignee: dri-devel(a)lists.freedesktop.org Summary: Strange artifacts when rendering tees in Dota 2 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: brunojimen(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 93753 --> https://bugs.freedesktop.org/attachment.cgi?id=93753&action=edit Strange artifacts in trees Hi, When playing Dota 2, randomly and depending on the ligh and the perspective, some random artifacts appear in trees. They also appear in other places, but the trees are the most visible ones. My graphics card is an AMD HD5470M (AMD Cedar) and I am using Arch linux 64 bits and mesa compiled from git at commit 356aff3. I thought this problem could be related to this other bug report: https://bugs.freedesktop.org/show_bug.cgi?id=72895 but applying that patch doesn't help. The attached screenshot shows the problem with the trees. If you need anything else, just ask. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 30102] New: Radeon : ring test failed
by bugzilla-daemon＠bugzilla.kernel.org 03 Sep '14

03 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=30102 Summary: Radeon : ring test failed Product: Drivers Version: 2.5 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: b747xx(a)gmail.com Regression: No Created an attachment (id=49622) --> (https://bugzilla.kernel.org/attachment.cgi?id=49622) dmesg On the radoen module load, I got this error: [ 9.874444] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD) [ 9.874447] radeon 0000:01:05.0: disabling GPU acceleration [ 9.875771] radeon 0000:01:05.0: ffff88043c78dc00 unpin not necessary This is intermittent. I got theses error two weeks ago and it vanish after a reboot about 1 week ago. The video acceleration was working perfectly until yesterday reboot (adding an option in the kernel) and now the problem is back. After the problem came back, I tried booting on the 3 others kernels I used this week (when it was working correctly) and the problem is still there with them. I have attached the dmesg and my .config if this can help find the problem. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 15

[Bug 74892] New: HyperZ GPU lockup with radeonsi 7970M PITCAIRN and Distance Alpha game
by bugzilla-daemon＠freedesktop.org 01 Sep '14

01 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=74892 Priority: medium Bug ID: 74892 Assignee: dri-devel(a)lists.freedesktop.org Summary: HyperZ GPU lockup with radeonsi 7970M PITCAIRN and Distance Alpha game Severity: normal Classification: Unclassified OS: All Reporter: haagch.christoph(a)googlemail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa The kernel people at https://bugzilla.kernel.org/show_bug.cgi?id=70411 told me this needs to be fixed in mesa, so here it is. The interesting part: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] Latest mesa git, but has probably been happening since HyperZ was enabled by default. dmesg is attached there: https://bugzilla.kernel.org/attachment.cgi?id=125651 It's reproducible every time so I can later get more detail. For now there's the dmesg: Starting the game and showing some intro works, but shortly before displaying the menu X freezes for a few seconds and after it is usable again, I see the stuff starting at 82688.801309 in dmesg. HyperZ seems to work fine for everything else I have tried so far. It only happens in the Distance Alpha that's only (officially) available to kickstarter backers. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 58660] New: Radeon HD 6950 completely broken.
by bugzilla-daemon＠freedesktop.org 01 Sep '14

01 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=58660 Priority: medium Bug ID: 58660 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD 6950 completely broken. Severity: normal Classification: Unclassified OS: All Reporter: v10lator(a)myway.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI I own a Sapphire Radeon HD 6950. This card has a dual-bios where one of them has unlocked shaders (Radeon HD 6970). This is not a modded BIOS, it's made by Sapphire and fully supported by them. Now my problem is that with the Radeon HD 6950 BIOS (locked shaders) the GPU seems to hang as soon as compiz starts. With the unlocked BIOS it starts just fine. -- You are receiving this mail because: You are the assignee for the bug.

1 12

← Newer
1
...
49
50
51
52
53
54
55
...
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