dri-devel April 2011

dri-devel@lists.freedesktop.org

93 participants
440 discussions

[git pull] drm fixes
by Dave Airlie 30 Apr '11

30 Apr '11

Nothing major, everyone must be on Easter holidays, the i915 one is actually a fix for dual-gpu laptops where i915 caused radeon to do something bad, the Kconfig one is because I see distros don't enable this and its really needed for dual-gpu functionality to work at all. Otherwise, just a couple of minor updates from Alex. Dave. The following changes since commit 8e10cd74342c7f5ce259cceca36f6eba084f5d58: Linux 2.6.39-rc5 (2011-04-26 20:48:50 -0700) are available in the git repository at: ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-fixes Alex Deucher (2): drm/radeon/kms: add missing safe regs for 6xx/7xx drm/radeon/kms: add info query for tile pipes Dave Airlie (2): drm: select FRAMEBUFFER_CONSOLE_PRIMARY if we have FRAMEBUFFER_CONSOLE drm/i915: restore only the mode of this driver on lastclose (v2) drivers/gpu/drm/Kconfig | 1 + drivers/gpu/drm/drm_fb_helper.c | 27 ++++++++++++++++++++------- drivers/gpu/drm/i915/i915_dma.c | 2 +- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_fb.c | 10 ++++++++++ drivers/gpu/drm/radeon/radeon_kms.c | 13 +++++++++++++ drivers/gpu/drm/radeon/reg_srcs/r600 | 1 + include/drm/drm_fb_helper.h | 1 + include/drm/radeon_drm.h | 1 + 9 files changed, 49 insertions(+), 8 deletions(-)

2 1

[Bug 36708] New: 32bit color flips and 64bit segfaults of glxgears when --enable-shared-glapi
by bugzilla-daemon＠freedesktop.org 30 Apr '11

30 Apr '11

https://bugs.freedesktop.org/show_bug.cgi?id=36708 Summary: 32bit color flips and 64bit segfaults of glxgears when --enable-shared-glapi Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: krzysztof.krakowiak(a)gmail.com 32bit misrendering(color flip and 64bit segfaults of glxgears when --enable-shared-glapi. Bug appears both with r300c and r300g. Talked with somebody before about exact reulsts with r600g, so maybe all drivers are affected? --disable-shared-glapi fixes problem Only some simple mesa demos,glxgears,teapot) and neverball are affected by this bug. Most of games like SuperTuxKart or Quake 3 Arena runs 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 1

[Bug 27314] displayport link training fails on certain panels (channel equalization fails)
by bugzilla-daemon＠freedesktop.org 30 Apr '11

30 Apr '11

https://bugs.freedesktop.org/show_bug.cgi?id=27314 --- Comment #38 from Ortwin Glück <odi(a)odi.ch> 2011-04-30 02:55:06 PDT --- Created an attachment (id=46185) --> (https://bugs.freedesktop.org/attachment.cgi?id=46185) dmesg with DP rewrite patches Still doesn't work unfortunately. dmesg attached. -- 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

[PATCH] fix mesa tarball creation again
by Thierry Vignaud 29 Apr '11

29 Apr '11

Hi The following patch fixes mesa tarball creation again

4 5

Re: linux-next: Tree for April 29 (gpu/drm)
by Randy Dunlap 29 Apr '11

29 Apr '11

On Fri, 29 Apr 2011 13:19:40 +1000 Stephen Rothwell wrote: > Hi all, > > Changes since 20110428: ERROR: "fb_mode_option" [drivers/gpu/drm/drm.ko] undefined! randconfig file is attached. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***

1 0

[Bug 31083] New: R600 misrenders irrlicht demo (01helloworld)
by bugzilla-daemon＠freedesktop.org 29 Apr '11

29 Apr '11

https://bugs.freedesktop.org/show_bug.cgi?id=31083 Summary: R600 misrenders irrlicht demo (01helloworld) Product: Mesa Version: 7.9 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: curaga(a)operamail.com Created an attachment (id=39738) --> (https://bugs.freedesktop.org/attachment.cgi?id=39738) Software renderer (correct output) The R600 driver misrenders the first demo of Irrlicht (irrlicht.sourceforge.net) when edited to use OpenGL instead of irrlicht's software renderer. The demo loads an animated md2 model with a bmp texture. Tested on Mesa 7.8.2 and 7.9, r600 fails on both, software renderer works on both. Screenshots attached. HW: Radeon HD4350 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

ApiTrace: OpenGL tracer, analyzer, debugger, replayer..
by Pasi Kärkkäinen 29 Apr '11

29 Apr '11

Hello, This might be an interesting tool for dri/driver developers.. from opengl.org: "New OpenGL tracer, analyzer and debugger: ApiTrace is a brand new project to trace, replay, analyze and debug graphics APIs. Using it you can inspect the OpenGL state frame by frame, call by call. You can analyze every shader, every texture, every buffer. You can also edit the trace itself and see the effects it would have on rendering in real-time." http://zrusin.blogspot.com/2011/04/apitrace.html "As a driver developer you no longer have to install all the games just to debug a problem, the report can simply include a short trace which you can use to immediately figure out what's wrong. As an application developer you can inspect every graphics call your app makes, you can analyze your api usage and you could automatically produce standalone testcases which you can send to driver developers." See the blog post for more info. -- Pasi

1 0

i915: irq nobody cared
by Jiri Slaby 28 Apr '11

28 Apr '11

Hi, while watching flash video in a browser I got: irq 42: nobody cared (try booting with the "irqpoll" option) Pid: 0, comm: swapper Tainted: G W 2.6.39-rc3-mm1_64+ #1423 Call Trace: <IRQ> [<ffffffff810bd671>] __report_bad_irq+0x31/0xc0 [<ffffffff810bd934>] note_interrupt+0x194/0x1d0 [<ffffffff810bbb58>] handle_irq_event_percpu+0xe8/0x160 [<ffffffff810bbc05>] handle_irq_event+0x35/0x60 [<ffffffff810be1af>] handle_edge_irq+0x6f/0x110 [<ffffffff81033a4d>] handle_irq+0x1d/0x30 [<ffffffff810336c8>] do_IRQ+0x58/0xe0 [<ffffffff815f9753>] common_interrupt+0x13/0x13 <EOI> [<ffffffff81030850>] ? __switch_to+0x260/0x2c0 [<ffffffff8109a46e>] ? tick_nohz_stop_sched_tick+0x28e/0x3d0 [<ffffffff81039be4>] ? default_idle+0x24/0x40 [<ffffffff81030236>] cpu_idle+0x36/0xb0 [<ffffffff815e3108>] rest_init+0x68/0x70 [<ffffffff81a7fb6a>] start_kernel+0x35c/0x367 [<ffffffff81a7f322>] x86_64_start_reservations+0x132/0x136 [<ffffffff81a7f417>] x86_64_start_kernel+0xf1/0xf8 handlers: [<ffffffff8132ee60>] (i915_driver_irq_handler+0x0/0x420) Disabling IRQ #42 Now the interrupt is polled, so that the graphics is obviously sluggish. I have also /sys/kernel/debug/dri contents if you want anything of that. Going to reboot now. # lspci -vvnnxxxs 00:02.0 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 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 Interrupt: pin A routed to IRQ 42 Region 0: Memory at feb80000 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at ec00 [size=8] Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M] Region 3: Memory at fea00000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4161 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 00: 86 80 c2 29 07 04 90 00 02 00 00 03 00 00 00 00 10: 00 00 b8 fe 01 ec 00 00 08 00 00 d0 00 00 a0 fe 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 c2 29 30: 00 00 00 00 90 00 00 00 00 00 00 00 05 01 00 00 40: 09 00 0b 01 00 00 00 00 01 00 00 00 00 00 00 00 50: 00 00 30 02 c9 03 00 00 00 00 00 00 00 00 80 af 60: 00 00 02 02 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 05 d0 01 00 0c 30 e0 fe 61 41 00 00 00 00 00 00 a0: 11 11 00 00 00 00 06 03 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 01 00 22 00 00 00 00 00 00 00 00 00 00 01 02 00 e0: 00 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00 f0: 10 00 00 00 00 00 00 00 90 0f 03 00 e4 e0 5b af regards, -- js

1 0

Re: [PATCH 2/3] drm: Warn if vblank state has become inconsistent.
by Mario Kleiner 28 Apr '11

28 Apr '11

On Apr 27, 2011, at 10:58 AM, dri-devel-request(a)lists.freedesktop.org wrote: > Message: 5 > Date: Wed, 27 Apr 2011 10:38:14 +0200 > From: Michel D?nzer <michel(a)daenzer.net> > Subject: Re: [PATCH 2/3] drm: Warn if vblank state has become > inconsistent. > To: christopher.halse.rogers(a)canonical.com > Cc: dri-devel(a)lists.freedesktop.org > Message-ID: <1303893494.5633.129.camel(a)thor.local> > Content-Type: text/plain; charset="UTF-8" > > On Mit, 2011-04-27 at 16:10 +1000, > christopher.halse.rogers(a)canonical.com wrote: >> From: Christopher James Halse Rogers >> <christopher.halse.rogers(a)canonical.com> >> >> After emitting all the waiting vblank events no-one should hold >> a vblank reference. Emit a warning if this is not the case. >> >> Signed-off-by: Christopher James Halse Rogers >> <christopher.halse.rogers(a)canonical.com> >> --- >> drivers/gpu/drm/drm_irq.c | 1 + >> 1 files changed, 1 insertions(+), 0 deletions(-) >> >> diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c >> index a1f12cb..72407fa 100644 >> --- a/drivers/gpu/drm/drm_irq.c >> +++ b/drivers/gpu/drm/drm_irq.c >> @@ -960,6 +960,7 @@ void drm_vblank_off(struct drm_device *dev, >> int crtc) >> e->event.sequence); >> } >> >> + WARN_ON(atomic_read(&dev->vblank_refcount[crtc]) != 0); >> spin_unlock_irqrestore(&dev->vbl_lock, irqflags); >> } >> EXPORT_SYMBOL(drm_vblank_off); > > Reviewed-by: Michel D?nzer <michel(a)daenzer.net> > Any pending kms pageflip will also hold a reference on the vblank of a crtc, so having the refcount non-zero there is not really a sign of inconsistency, so i'm not sure if a warning is appropriate there. -mario ********************************************************************* Mario Kleiner Max Planck Institute for Biological Cybernetics Spemannstr. 38 72076 Tuebingen Germany e-mail: mario.kleiner(a)tuebingen.mpg.de office: +49 (0)7071/601-1623 fax: +49 (0)7071/601-616 www: http://www.kyb.tuebingen.mpg.de/~kleinerm ********************************************************************* "For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." (Richard Feynman)

2 2

[PATCH] drm/nouveau: Remove interrupt handler around suspend/resume
by Alex Williamson 28 Apr '11

28 Apr '11

We're often using a shared interrupt line for nouveau, so we have to be prepared that it could be called at any point in time. If we've suspended the device via vga switcheroo and get a stray interrupt on the line from another device, we'll read back -1 from the device and head down all sorts of strange paths, most of which eventually lock the system. On my system (Asus UL30VT) the interrupt line is shared with USB. Attempting to disable the USB bluetooth device seems to trigger a stray interrupt that ends up in nv04_fifo_isr() where we eventually hit the "PFIFO still angry after 100 spins, halt", which kills the system. Using free_irq/request_irq around the suspend seems to be a reliable fix. Attempting to flag the device state in nouvea_irq_handler(), similar to the intel_lid_notify() fix is too racy since we can power off the device as an interrupt is being processed. Signed-off-by: Alex Williamson <alex.williamson(a)redhat.com> --- drivers/gpu/drm/nouveau/nouveau_drv.c | 22 ++++++++++++++++++++++ 1 files changed, 22 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_drv.c b/drivers/gpu/drm/nouveau/nouveau_drv.c index 155ebdc..91f2aca 100644 --- a/drivers/gpu/drm/nouveau/nouveau_drv.c +++ b/drivers/gpu/drm/nouveau/nouveau_drv.c @@ -229,6 +229,10 @@ nouveau_pci_suspend(struct pci_dev *pdev, pm_message_t pm_state) NV_INFO(dev, "And we're gone!\n"); pci_save_state(pdev); + + pci_intx(pdev, 0); + free_irq(drm_dev_to_irq(dev), dev); + if (pm_state.event == PM_EVENT_SUSPEND) { pci_disable_device(pdev); pci_set_power_state(pdev, PCI_D3hot); @@ -255,6 +259,8 @@ nouveau_pci_resume(struct pci_dev *pdev) struct drm_nouveau_private *dev_priv = dev->dev_private; struct nouveau_engine *engine = &dev_priv->engine; struct drm_crtc *crtc; + char *irqname; + unsigned long sh_flags = 0; int ret, i; if (dev->switch_power_state == DRM_SWITCH_POWER_OFF) @@ -265,6 +271,22 @@ nouveau_pci_resume(struct pci_dev *pdev) NV_INFO(dev, "We're back, enabling device...\n"); pci_set_power_state(pdev, PCI_D0); pci_restore_state(pdev); + + if (drm_core_check_feature(dev, DRIVER_IRQ_SHARED)) + sh_flags = IRQF_SHARED; + + if (dev->devname) + irqname = dev->devname; + else + irqname = dev->driver->name; + + ret = request_irq(drm_dev_to_irq(dev), dev->driver->irq_handler, + sh_flags, irqname, dev); + if (ret < 0) { + NV_ERROR(dev, "error re-requesting irq: %d\n", ret); + return ret; + } + if (pci_enable_device(pdev)) return -1; pci_set_master(dev->pdev);

2 2

← Newer
1
...
25
26
27
28
29
30
31
...
44
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2011