dri-devel July 2010

dri-devel@lists.freedesktop.org

65 participants
269 discussions

[Bug 25483] Neverwinter nights lacks ram when using the radeon driver
by bugzilla-daemon＠freedesktop.org 30 Jul '10

30 Jul '10

https://bugs.freedesktop.org/show_bug.cgi?id=25483 --- Comment #23 from Adam K Kirchhoff <akirchhoff135014(a)comcast.net> 2010-07-30 03:55:40 PDT --- I have seen these leaks as well. It gets to the point where the OOM killer kicks in and things start dying. Has anyone taken a stab at fixing these leaks? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[git pull] drm fixes
by Dave Airlie 30 Jul '10

30 Jul '10

Just two, one edid, the other a radeon pm info reporting fix. The following changes since commit fc0f5ac8fe693d1b05f5a928cc48135d1c8b7f2e: Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs (2010-07-27 14:32:59 -0700) are available in the git repository at: ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-fixes Adam Jackson (1): drm/edid: Fix the HDTV hack sync adjustment Daniel J Blueman (1): drm/radeon/kms: fix radeon mid power profile reporting drivers/gpu/drm/drm_edid.c | 4 ++-- drivers/gpu/drm/radeon/radeon_pm.c | 1 + 2 files changed, 3 insertions(+), 2 deletions(-)

1 0

[Bug 29297] New: [r300g] lightspark crash
by bugzilla-daemon＠freedesktop.org 29 Jul '10

29 Jul '10

https://bugs.freedesktop.org/show_bug.cgi?id=29297 Summary: [r300g] lightspark crash Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: d.okias(a)gmail.com Created an attachment (id=37438) --> (https://bugs.freedesktop.org/attachment.cgi?id=37438) gdb_output.txt Lightspark use for everything OpenGL rendering, so it crash almost every time. I will attach firefox gdb. Mesa with debug, lightspark with debug. -- 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

[Bug 24818] shadowtex demo doesn't work on rs780
by bugzilla-daemon＠freedesktop.org 29 Jul '10

29 Jul '10

https://bugs.freedesktop.org/show_bug.cgi?id=24818 --- Comment #8 from Török Edwin <edwintorok(a)gmail.com> 2010-07-29 09:49:40 PDT --- (In reply to comment #7) > (In reply to comment #4) > > I can confirm this using mesa master and RV620. > > > > I've noticed that corruption is random as I restart shadowtex demo until some > > time. After starting it for example 10th time, corruption stops changing. So it > > indeed looks like using some random data from VRAM or something. After having > > "stable" corruption I've to reboot to get random corruptions again (for a few > > shadowtex restarts). > > Seems like there's been a further regression - probably in mesa master during > the last few weeks. I now can't run this at all - > > shadowtex: r700_assembler.c:6355: Process_Export: Assertion > `starting_register_number >= pAsm->starting_export_register_number' failed. > > Anyone else getting this? The assert just got fixed by 9b3bf392e1af72d29afa0804260cac4d8ffe24e1. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 29263] New: shadowtex: r700_assembler.c:6355: Process_Export: Assertion `starting_register_number >= pAsm->starting_export_register_number' failed.
by bugzilla-daemon＠freedesktop.org 29 Jul '10

29 Jul '10

https://bugs.freedesktop.org/show_bug.cgi?id=29263 Summary: shadowtex: r700_assembler.c:6355: Process_Export: Assertion `starting_register_number >= pAsm->starting_export_register_number' failed. Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: edwintorok(a)gmail.com CC: brianp(a)vmware.com Created an attachment (id=37398) --> (https://bugs.freedesktop.org/attachment.cgi?id=37398) glxinfo, Xorg.0.log, dmesg I just started shadowtex today and got this assertion failure. ./shadowtex Using GL_ARB_depth_texture and GL_ARB_shadow and GL_ARB_fragment_program and GL_ARB_shadow_ambient Using GL_EXT_framebuffer_object Keys: a = toggle animation i = show depth texture image m = show depth texture mapping d = show fragment distance from light source n = show normal, shadowed image f = toggle nearest/bilinear texture filtering b/B = decrease/increase shadow map Z bias p = toggle use of packed depth/stencil M = cycle through fragment program modes v = toggle vertex program modes cursor keys = rotate scene <shift> + cursor keys = rotate light source o = cycle through comparison modes Rendering 256 x 256 depth texture shadowtex: r700_assembler.c:6355: Process_Export: Assertion `starting_register_number >= pAsm->starting_export_register_number' failed. Aborted Steps to reproduce: 1 Build mesa for r600: $ ./configure --prefix=/opt/xorg --with-dri-drivers=r600,swrast --disable-gallium --with-dri-driverdir=/opt/xorg/lib/dri --enable-glx-tls PKG_CONFIG_PATH=/opt/xorg/lib/pkgconfig/ $ make clean $ make -j8 $ make install 2 Run shadowtex demo $ cd /path/to/mesa/demos $ ./shadowtex I remember shadowtex working at some point (and works with 7.8.x). "Works" in the sense that it renders something, the shadow texture itself is random (see bug #26735). But it was certainly not aborting. So I did a git bisect and it came up with this: b6b9b17d27c570cc99ae339e595cf2f63ca5e8d7 is the first bad commit commit b6b9b17d27c570cc99ae339e595cf2f63ca5e8d7 Author: Brian Paul <brianp(a)vmware.com> Date: Fri Jul 2 08:14:54 2010 -0600 mesa: make the number of draw buffers part of the texenv program key state All the state that effects the program should be in the key. This didn't help with bug 28169 but is a good fix anyway. NOTE: this is a low-priority candidate for the 7.8 branch. In practice, this issue might never be hit. :040000 040000 c9f1d363565e225cdf17e57993b6a773a46107c5 3e22c4d9a51ba9b569ee72ba2fa2a1186f41a30d M src Reverting that patch makes it work again. I don't know if there a bug in that patch, or it exposed another bug (maybe even the bug that caused the random texture in the first place?) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 24041] [KMS] KMS fails to initalize, in a rs690
by bugzilla-daemon＠freedesktop.org 28 Jul '10

28 Jul '10

https://bugs.freedesktop.org/show_bug.cgi?id=24041 Manuel Braga <mul.braga(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Manuel Braga <mul.braga(a)gmail.com> 2010-07-28 12:08:46 PDT --- Just now tried 2.6.35-rc6 without any problem. The fix were added at 2.6.32, commit 18a4cd2e9147dd41234dade56edb62c6222832eb and is working fine. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[2.6.35-rc6 patch] fix radeon mid power profile reporting
by Daniel J Blueman 28 Jul '10

28 Jul '10

Hi Dave, This one-liner may be a suitable late-fix for 2.6.35-final: Fix incorrectly reporting 'default' power profile, when it is set to 'mid'. Signed-off-by: Daniel J Blueman <daniel.blueman(a)gmail.com> diff --git a/drivers/gpu/drm/radeon/radeon_pm.c b/drivers/gpu/drm/radeon/radeon_pm.c index 115d26b..3fa6984 100644 --- a/drivers/gpu/drm/radeon/radeon_pm.c +++ b/drivers/gpu/drm/radeon/radeon_pm.c @@ -333,6 +333,7 @@ static ssize_t radeon_get_pm_profile(struct device *dev, return snprintf(buf, PAGE_SIZE, "%s\n", (cp == PM_PROFILE_AUTO) ? "auto" : (cp == PM_PROFILE_LOW) ? "low" : + (cp == PM_PROFILE_MID) ? "mid" : (cp == PM_PROFILE_HIGH) ? "high" : "default"); } -- Daniel J Blueman

2 1

Suspend lockup: How to bisect d-r-t specific commits?
by Rafał Miłecki 28 Jul '10

28 Jul '10

I've installed openSUSE 11.3 which comes with 2.6.34 kernel and added 2.6.35-rc5 from package. In both cases suspending and resuming works fine. Then I downloaded 2.6.35-rc5 and compiled it myself. Suspending and resuming works fine. When trying d-r-t with the same config my machine locks up on suspending, just before machine is expected to turn off. How can I use "git bisect" command to bisect d-r-t specific commits? -- Rafał

4 25

mmotm 2010-07-27 - nouveau lockdep issues.
by Valdis.Kletnieks＠vt.edu 28 Jul '10

28 Jul '10

On Tue, 27 Jul 2010 14:56:50 PDT, akpm(a)linux-foundation.org said: > The mm-of-the-moment snapshot 2010-07-27-14-56 has been uploaded to > > http://userweb.kernel.org/~akpm/mmotm/ Hit this while the X server was on its way down during a 'shutdown -r now'. Worked fine in -rc5-mmotm0719. 'e16' is the Enlightenment window manager, if that matters. [ 93.181787] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1 [ 99.802836] [drm] nouveau 0000:01:00.0: Allocating FIFO number 4 [ 99.808875] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4 [ 103.262226] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1 [ 113.341948] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1 [ 123.421836] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1 [ 123.550520] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4 [ 123.551253] [ 123.551253] ====================================================== [ 123.551253] [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ] [ 123.551253] 2.6.35-rc6-mmotm0727 #1 [ 123.551253] ------------------------------------------------------ [ 123.551253] e16/3822 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: [ 123.551253] (&(&mm->unused_lock)->rlock){+.+...}, at: [<ffffffff812a94bc>] drm_mm_put_block+0x10e/0x142 [ 123.551253] [ 123.551253] and this task is already holding: [ 123.551253] (&(&dev_priv->context_switch_lock)->rlock){-.....}, at: [<ffffffff812bdbab>] nouveau_channel_free+0x10f/0x233 [ 123.551253] which would create a new lock dependency: [ 123.551253] (&(&dev_priv->context_switch_lock)->rlock){-.....} -> (&(&mm->unused_lock)->rlock){+.+...} [ 123.551253] [ 123.551253] but this new dependency connects a HARDIRQ-irq-safe lock: [ 123.551253] (&(&dev_priv->context_switch_lock)->rlock){-.....} [ 123.551253] ... which became HARDIRQ-irq-safe at: [ 123.551253] [<ffffffff81065043>] __lock_acquire+0x301/0xd6a [ 123.551253] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.551253] [<ffffffff81594dda>] _raw_spin_lock_irqsave+0x44/0x57 [ 123.551253] [<ffffffff812c264b>] nouveau_irq_handler+0x63/0x1920 [ 123.551253] [<ffffffff810817bb>] handle_IRQ_event+0xad/0x213 [ 123.551253] [<ffffffff81083bd2>] handle_fasteoi_irq+0xd1/0x115 [ 123.551253] [<ffffffff81004b6e>] handle_irq+0x122/0x133 [ 123.551253] [<ffffffff8100499f>] do_IRQ+0x57/0xaf [ 123.551253] [ 123.604031] [drm] nouveau 0000:01:00.0: GPU lockup - switching to software fbcon [ 123.604031] [<ffffffff81595cd3>] ret_from_intr+0x0/0xf [ 123.604031] [<ffffffff81000c73>] cpu_idle+0x85/0x169 [ 123.604031] [<ffffffff81b62061>] start_secondary+0x1b1/0x1b5 [ 123.604031] [ 123.604031] to a HARDIRQ-irq-unsafe lock: [ 123.604031] (&(&mm->unused_lock)->rlock){+.+...} [ 123.604031] ... which became HARDIRQ-irq-unsafe at: [ 123.604031] ... [<ffffffff810650c4>] __lock_acquire+0x382/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594ce1>] _raw_spin_lock+0x36/0x45 [ 123.604031] [<ffffffff812a9669>] drm_mm_pre_get+0x24/0xb2 [ 123.604031] [<ffffffff812b748b>] ttm_bo_init+0x1fe/0x3c0 [ 123.604031] [<ffffffff812c5dce>] nouveau_bo_new+0x3ae/0x423 [ 123.604031] [<ffffffff812bf2c8>] nouveau_mem_init+0x293/0x487 [ 123.604031] [<ffffffff812bce55>] nouveau_card_init+0xa5e/0xd52 [ 123.604031] [<ffffffff812bd675>] nouveau_load+0x519/0x528 [ 123.604031] [<ffffffff812a74af>] drm_get_pci_dev+0x174/0x26a [ 123.604031] [<ffffffff8158a14e>] nouveau_pci_probe+0x10/0x12 [ 123.604031] [<ffffffff812228ce>] local_pci_probe+0x3f/0x70 [ 123.604031] [<ffffffff81222c4c>] pci_device_probe+0x65/0x96 [ 123.604031] [<ffffffff8130a840>] driver_probe_device+0xe8/0x182 [ 123.604031] [<ffffffff8130a924>] __driver_attach+0x4a/0x6b [ 123.604031] [<ffffffff81309a2f>] bus_for_each_dev+0x57/0x83 [ 123.604031] [<ffffffff8130a505>] driver_attach+0x19/0x1b [ 123.604031] [<ffffffff8130a147>] bus_add_driver+0xae/0x205 [ 123.604031] [<ffffffff8130ab80>] driver_register+0xb5/0x122 [ 123.604031] [<ffffffff81222e82>] __pci_register_driver+0x61/0xcd [ 123.604031] [<ffffffff812a7839>] drm_pci_init+0x31/0x98 [ 123.604031] [<ffffffff812a003f>] drm_init+0x5d/0x61 [ 123.604031] [<ffffffff81b4e59a>] nouveau_init+0x48/0x4a [ 123.604031] [<ffffffff810002ff>] do_one_initcall+0x7a/0x12f [ 123.604031] [<ffffffff81b2ccae>] kernel_init+0x138/0x1c2 [ 123.604031] [<ffffffff81003554>] kernel_thread_helper+0x4/0x10 [ 123.604031] [ 123.604031] other info that might help us debug this: [ 123.604031] [ 123.604031] 1 lock held by e16/3822: [ 123.604031] #0: (&(&dev_priv->context_switch_lock)->rlock){-.....}, at: [<ffffffff812bdbab>] nouveau_channel_free+0x10f/0x233 [ 123.604031] [ 123.604031] the dependencies between HARDIRQ-irq-safe lock and the holding lock: [ 123.604031] -> (&(&dev_priv->context_switch_lock)->rlock){-.....} ops: 15 { [ 123.604031] IN-HARDIRQ-W at: [ 123.604031] [<ffffffff81065043>] __lock_acquire+0x301/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594dda>] _raw_spin_lock_irqsave+0x44/0x57 [ 123.604031] [<ffffffff812c264b>] nouveau_irq_handler+0x63/0x1920 [ 123.604031] [<ffffffff810817bb>] handle_IRQ_event+0xad/0x213 [ 123.604031] [<ffffffff81083bd2>] handle_fasteoi_irq+0xd1/0x115 [ 123.604031] [<ffffffff81004b6e>] handle_irq+0x122/0x133 [ 123.604031] [<ffffffff8100499f>] do_IRQ+0x57/0xaf [ 123.604031] [<ffffffff81595cd3>] ret_from_intr+0x0/0xf [ 123.604031] [<ffffffff81000c73>] cpu_idle+0x85/0x169 [ 123.604031] [<ffffffff81b62061>] start_secondary+0x1b1/0x1b5 [ 123.604031] INITIAL USE at: [ 123.604031] [<ffffffff81065145>] __lock_acquire+0x403/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594dda>] _raw_spin_lock_irqsave+0x44/0x57 [ 123.604031] [<ffffffff812c264b>] nouveau_irq_handler+0x63/0x1920 [ 123.604031] [<ffffffff810817bb>] handle_IRQ_event+0xad/0x213 [ 123.604031] [<ffffffff81083bd2>] handle_fasteoi_irq+0xd1/0x115 [ 123.604031] [<ffffffff81004b6e>] handle_irq+0x122/0x133 [ 123.604031] [<ffffffff8100499f>] do_IRQ+0x57/0xaf [ 123.604031] [<ffffffff81595cd3>] ret_from_intr+0x0/0xf [ 123.604031] [<ffffffff81000c73>] cpu_idle+0x85/0x169 [ 123.604031] [<ffffffff81b62061>] start_secondary+0x1b1/0x1b5 [ 123.604031] } [ 123.604031] ... key at: [<ffffffff8243b758>] __key.32520+0x0/0x8 [ 123.604031] ... acquired at: [ 123.604031] [<ffffffff810648cd>] check_irq_usage+0x42/0x89 [ 123.604031] [<ffffffff810657d6>] __lock_acquire+0xa94/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594ce1>] _raw_spin_lock+0x36/0x45 [ 123.604031] [<ffffffff812a94bc>] drm_mm_put_block+0x10e/0x142 [ 123.604031] [<ffffffff812bf7e2>] nouveau_gpuobj_del+0x14c/0x179 [ 123.604031] [<ffffffff812c02ad>] nouveau_gpuobj_ref_del+0x25d/0x284 [ 123.604031] [<ffffffff812e3fb2>] nv50_graph_destroy_context+0xd0/0xdc [ 123.604031] [<ffffffff812bdbdd>] nouveau_channel_free+0x141/0x233 [ 123.604031] [<ffffffff812be5bf>] nouveau_ioctl_fifo_free+0x79/0x86 [ 123.604031] [<ffffffff8129fdab>] drm_ioctl+0x2b3/0x36b [ 123.604031] [<ffffffff810ec6fc>] vfs_ioctl+0x31/0xa2 [ 123.604031] [<ffffffff810ed07b>] do_vfs_ioctl+0x496/0x4c9 [ 123.604031] [<ffffffff810ed105>] sys_ioctl+0x57/0x96 [ 123.604031] [<ffffffff8100272b>] system_call_fastpath+0x16/0x1b [ 123.604031] [ 123.604031] [ 123.604031] the dependencies between the lock to be acquired and HARDIRQ-irq-unsafe lock: [ 123.604031] -> (&(&mm->unused_lock)->rlock){+.+...} ops: 10338 { [ 123.604031] HARDIRQ-ON-W at: [ 123.604031] [<ffffffff810650c4>] __lock_acquire+0x382/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594ce1>] _raw_spin_lock+0x36/0x45 [ 123.604031] [<ffffffff812a9669>] drm_mm_pre_get+0x24/0xb2 [ 123.604031] [<ffffffff812b748b>] ttm_bo_init+0x1fe/0x3c0 [ 123.604031] [<ffffffff812c5dce>] nouveau_bo_new+0x3ae/0x423 [ 123.604031] [<ffffffff812bf2c8>] nouveau_mem_init+0x293/0x487 [ 123.604031] [<ffffffff812bce55>] nouveau_card_init+0xa5e/0xd52 [ 123.604031] [<ffffffff812bd675>] nouveau_load+0x519/0x528 [ 123.604031] [<ffffffff812a74af>] drm_get_pci_dev+0x174/0x26a [ 123.604031] [<ffffffff8158a14e>] nouveau_pci_probe+0x10/0x12 [ 123.604031] [<ffffffff812228ce>] local_pci_probe+0x3f/0x70 [ 123.604031] [<ffffffff81222c4c>] pci_device_probe+0x65/0x96 [ 123.604031] [<ffffffff8130a840>] driver_probe_device+0xe8/0x182 [ 123.604031] [<ffffffff8130a924>] __driver_attach+0x4a/0x6b [ 123.604031] [<ffffffff81309a2f>] bus_for_each_dev+0x57/0x83 [ 123.604031] [<ffffffff8130a505>] driver_attach+0x19/0x1b [ 123.604031] [<ffffffff8130a147>] bus_add_driver+0xae/0x205 [ 123.604031] [<ffffffff8130ab80>] driver_register+0xb5/0x122 [ 123.604031] [<ffffffff81222e82>] __pci_register_driver+0x61/0xcd [ 123.604031] [<ffffffff812a7839>] drm_pci_init+0x31/0x98 [ 123.604031] [<ffffffff812a003f>] drm_init+0x5d/0x61 [ 123.604031] [<ffffffff81b4e59a>] nouveau_init+0x48/0x4a [ 123.604031] [<ffffffff810002ff>] do_one_initcall+0x7a/0x12f [ 123.604031] [<ffffffff81b2ccae>] kernel_init+0x138/0x1c2 [ 123.604031] [<ffffffff81003554>] kernel_thread_helper+0x4/0x10 [ 123.604031] SOFTIRQ-ON-W at: [ 123.604031] [<ffffffff810650e5>] __lock_acquire+0x3a3/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594ce1>] _raw_spin_lock+0x36/0x45 [ 123.604031] [<ffffffff812a9669>] drm_mm_pre_get+0x24/0xb2 [ 123.604031] [<ffffffff812b748b>] ttm_bo_init+0x1fe/0x3c0 [ 123.604031] [<ffffffff812c5dce>] nouveau_bo_new+0x3ae/0x423 [ 123.604031] [<ffffffff812bf2c8>] nouveau_mem_init+0x293/0x487 [ 123.604031] [<ffffffff812bce55>] nouveau_card_init+0xa5e/0xd52 [ 123.604031] [<ffffffff812bd675>] nouveau_load+0x519/0x528 [ 123.604031] [<ffffffff812a74af>] drm_get_pci_dev+0x174/0x26a [ 123.604031] [<ffffffff8158a14e>] nouveau_pci_probe+0x10/0x12 [ 123.604031] [<ffffffff812228ce>] local_pci_probe+0x3f/0x70 [ 123.604031] [<ffffffff81222c4c>] pci_device_probe+0x65/0x96 [ 123.604031] [<ffffffff8130a840>] driver_probe_device+0xe8/0x182 [ 123.604031] [<ffffffff8130a924>] __driver_attach+0x4a/0x6b [ 123.604031] [<ffffffff81309a2f>] bus_for_each_dev+0x57/0x83 [ 123.604031] [<ffffffff8130a505>] driver_attach+0x19/0x1b [ 123.604031] [<ffffffff8130a147>] bus_add_driver+0xae/0x205 [ 123.604031] [<ffffffff8130ab80>] driver_register+0xb5/0x122 [ 123.604031] [<ffffffff81222e82>] __pci_register_driver+0x61/0xcd [ 123.604031] [<ffffffff812a7839>] drm_pci_init+0x31/0x98 [ 123.604031] [<ffffffff812a003f>] drm_init+0x5d/0x61 [ 123.604031] [<ffffffff81b4e59a>] nouveau_init+0x48/0x4a [ 123.604031] [<ffffffff810002ff>] do_one_initcall+0x7a/0x12f [ 123.604031] [<ffffffff81b2ccae>] kernel_init+0x138/0x1c2 [ 123.604031] [<ffffffff81003554>] kernel_thread_helper+0x4/0x10 [ 123.604031] INITIAL USE at: [ 123.604031] [<ffffffff81065145>] __lock_acquire+0x403/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594ce1>] _raw_spin_lock+0x36/0x45 [ 123.604031] [<ffffffff812a9669>] drm_mm_pre_get+0x24/0xb2 [ 123.604031] [<ffffffff812b748b>] ttm_bo_init+0x1fe/0x3c0 [ 123.604031] [<ffffffff812c5dce>] nouveau_bo_new+0x3ae/0x423 [ 123.604031] [<ffffffff812bf2c8>] nouveau_mem_init+0x293/0x487 [ 123.604031] [<ffffffff812bce55>] nouveau_card_init+0xa5e/0xd52 [ 123.604031] [<ffffffff812bd675>] nouveau_load+0x519/0x528 [ 123.604031] [<ffffffff812a74af>] drm_get_pci_dev+0x174/0x26a [ 123.604031] [<ffffffff8158a14e>] nouveau_pci_probe+0x10/0x12 [ 123.604031] [<ffffffff812228ce>] local_pci_probe+0x3f/0x70 [ 123.604031] [<ffffffff81222c4c>] pci_device_probe+0x65/0x96 [ 123.604031] [<ffffffff8130a840>] driver_probe_device+0xe8/0x182 [ 123.604031] [<ffffffff8130a924>] __driver_attach+0x4a/0x6b [ 123.604031] [<ffffffff81309a2f>] bus_for_each_dev+0x57/0x83 [ 123.604031] [<ffffffff8130a505>] driver_attach+0x19/0x1b [ 123.604031] [<ffffffff8130a147>] bus_add_driver+0xae/0x205 [ 123.604031] [<ffffffff8130ab80>] driver_register+0xb5/0x122 [ 123.604031] [<ffffffff81222e82>] __pci_register_driver+0x61/0xcd [ 123.604031] [<ffffffff812a7839>] drm_pci_init+0x31/0x98 [ 123.604031] [<ffffffff812a003f>] drm_init+0x5d/0x61 [ 123.604031] [<ffffffff81b4e59a>] nouveau_init+0x48/0x4a [ 123.604031] [<ffffffff810002ff>] do_one_initcall+0x7a/0x12f [ 123.604031] [<ffffffff81b2ccae>] kernel_init+0x138/0x1c2 [ 123.604031] [<ffffffff81003554>] kernel_thread_helper+0x4/0x10 [ 123.604031] } [ 123.604031] ... key at: [<ffffffff8243b408>] __key.30042+0x0/0x8 [ 123.604031] ... acquired at: [ 123.604031] [<ffffffff810648cd>] check_irq_usage+0x42/0x89 [ 123.604031] [<ffffffff810657d6>] __lock_acquire+0xa94/0xd6a [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff81594ce1>] _raw_spin_lock+0x36/0x45 [ 123.604031] [<ffffffff812a94bc>] drm_mm_put_block+0x10e/0x142 [ 123.604031] [<ffffffff812bf7e2>] nouveau_gpuobj_del+0x14c/0x179 [ 123.604031] [<ffffffff812c02ad>] nouveau_gpuobj_ref_del+0x25d/0x284 [ 123.604031] [<ffffffff812e3fb2>] nv50_graph_destroy_context+0xd0/0xdc [ 123.604031] [<ffffffff812bdbdd>] nouveau_channel_free+0x141/0x233 [ 123.604031] [<ffffffff812be5bf>] nouveau_ioctl_fifo_free+0x79/0x86 [ 123.604031] [<ffffffff8129fdab>] drm_ioctl+0x2b3/0x36b [ 123.604031] [<ffffffff810ec6fc>] vfs_ioctl+0x31/0xa2 [ 123.604031] [<ffffffff810ed07b>] do_vfs_ioctl+0x496/0x4c9 [ 123.604031] [<ffffffff810ed105>] sys_ioctl+0x57/0x96 [ 123.604031] [<ffffffff8100272b>] system_call_fastpath+0x16/0x1b [ 123.604031] [ 123.604031] [ 123.604031] stack backtrace: [ 123.604031] Pid: 3822, comm: e16 Tainted: G W 2.6.35-rc6-mmotm0727 #1 [ 123.604031] Call Trace: [ 123.604031] [<ffffffff81064876>] check_usage+0x351/0x366 [ 123.604031] [<ffffffff8106313b>] ? register_lock_class+0x1e/0x2c7 [ 123.604031] [<ffffffff810648cd>] check_irq_usage+0x42/0x89 [ 123.604031] [<ffffffff810657d6>] __lock_acquire+0xa94/0xd6a [ 123.604031] [<ffffffff810652ba>] ? __lock_acquire+0x578/0xd6a [ 123.604031] [<ffffffff812a94bc>] ? drm_mm_put_block+0x10e/0x142 [ 123.604031] [<ffffffff81065fca>] lock_acquire+0x10a/0x130 [ 123.604031] [<ffffffff812a94bc>] ? drm_mm_put_block+0x10e/0x142 [ 123.604031] [<ffffffff81594ce1>] _raw_spin_lock+0x36/0x45 [ 123.604031] [<ffffffff812a94bc>] ? drm_mm_put_block+0x10e/0x142 [ 123.604031] [<ffffffff812a94bc>] drm_mm_put_block+0x10e/0x142 [ 123.604031] [<ffffffff812bf7e2>] nouveau_gpuobj_del+0x14c/0x179 [ 123.604031] [<ffffffff812c02ad>] nouveau_gpuobj_ref_del+0x25d/0x284 [ 123.604031] [<ffffffff812e3fb2>] nv50_graph_destroy_context+0xd0/0xdc [ 123.604031] [<ffffffff812bdbdd>] nouveau_channel_free+0x141/0x233 [ 123.604031] [<ffffffff8109a0f9>] ? trace_preempt_off+0x15/0x28 [ 123.604031] [<ffffffff8129fd9c>] ? drm_ioctl+0x2a4/0x36b [ 123.604031] [<ffffffff812be5bf>] nouveau_ioctl_fifo_free+0x79/0x86 [ 123.604031] [<ffffffff8129fdab>] drm_ioctl+0x2b3/0x36b [ 123.604031] [<ffffffff812be546>] ? nouveau_ioctl_fifo_free+0x0/0x86 [ 123.604031] [<ffffffff81064b97>] ? mark_lock+0x2d/0x1d8 [ 123.604031] [<ffffffff810ec6fc>] vfs_ioctl+0x31/0xa2 [ 123.604031] [<ffffffff810ed07b>] do_vfs_ioctl+0x496/0x4c9 [ 123.604031] [<ffffffff810ed105>] sys_ioctl+0x57/0x96 [ 123.604031] [<ffffffff8100272b>] system_call_fastpath+0x16/0x1b

2 1

[PATCH] drm/edid: Fix the HDTV hack sync adjustment
by Adam Jackson 27 Jul '10

27 Jul '10

We're adjusting horizontal timings only here, moving vsync was just a slavish translation of a typo in the X server. Signed-off-by: Adam Jackson <ajax(a)redhat.com> --- drivers/gpu/drm/drm_edid.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c index 83d8072..ea1d572 100644 --- a/drivers/gpu/drm/drm_edid.c +++ b/drivers/gpu/drm/drm_edid.c @@ -864,8 +864,8 @@ drm_mode_std(struct drm_connector *connector, struct edid *edid, mode = drm_cvt_mode(dev, 1366, 768, vrefresh_rate, 0, 0, false); mode->hdisplay = 1366; - mode->vsync_start = mode->vsync_start - 1; - mode->vsync_end = mode->vsync_end - 1; + mode->hsync_start = mode->hsync_start - 1; + mode->hsync_end = mode->hsync_end - 1; return mode; } -- 1.7.1.1

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
27
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2010