dri-devel December 2010

dri-devel@lists.freedesktop.org

94 participants
405 discussions

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 13 Dec '10

13 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #18 from Holger Lenz <holger.lenz(a)onlinehome.de> 2010-12-13 21:52:09 --- (In reply to comment #17) > (In reply to comment #16) > > Holger, your issue may not be the same as Duncan's. I'd suggest changing the > > AGP mode in your bios or adjusting it or disabling it via the kernel command > > line (radeon.agpmode=-1 to disable, 1,2,4,8 to force the agp mode). It might > > also be related to the latency setting on the host bridge. VIA boards tend to > > set them pretty aggressively. > You may be right: Still using the patched driver I set radeon.agpmode=-1 and > the system came up with X using radeon and swrast. Seems like radeon.agpmode=-1 > switches off dri / the r600 classic driver. A few switches to the fb console > broke the vt session, but I was always able to switch back to X. > Unfortunately I cannot get AGP to work with the radeon driver. Using really > conservative settings in the AGP bridge, the driver still doesn't boot without > radeon.agpmode=-1. I used the following BIOS settings to get moderate timings > AGP Mode=4x > VLINK 8x disable > AGP 3.0 calibration cycle enabled > DBI output for AGP transactions disable > > The hardware itself should be pretty stable - I ran a heavy Furmark stress test New info before getting some sleep: The system was using swrast above because it didnt use kms. If I force KMS by using radeon.modeset=0 on the kcl, radeon and r600 will be loaded even if i set radeon.agpmode=-1. The system will then freeze after loading X and showing a few windows. So the improvement w/o AGP is not freezing immediately. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 13 Dec '10

13 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #17 from Holger Lenz <holger.lenz(a)onlinehome.de> 2010-12-13 21:00:06 --- (In reply to comment #16) > Holger, your issue may not be the same as Duncan's. I'd suggest changing the > AGP mode in your bios or adjusting it or disabling it via the kernel command > line (radeon.agpmode=-1 to disable, 1,2,4,8 to force the agp mode). It might > also be related to the latency setting on the host bridge. VIA boards tend to > set them pretty aggressively. You may be right: Still using the patched driver I set radeon.agpmode=-1 and the system came up with X using radeon and swrast. Seems like radeon.agpmode=-1 switches off dri / the r600 classic driver. A few switches to the fb console broke the vt session, but I was always able to switch back to X. Unfortunately I cannot get AGP to work with the radeon driver. Using really conservative settings in the AGP bridge, the driver still doesn't boot without radeon.agpmode=-1. I used the following BIOS settings to get moderate timings AGP Mode=4x VLINK 8x disable AGP 3.0 calibration cycle enabled DBI output for AGP transactions disable The hardware itself should be pretty stable - I ran a heavy Furmark stress test under windows to check for robustness. Any ideas how to debug the AGP issue? BR Holger -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 13 Dec '10

13 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #16 from Alex Deucher <alexdeucher(a)gmail.com> 2010-12-13 20:13:12 --- Holger, your issue may not be the same as Duncan's. I'd suggest changing the AGP mode in your bios or adjusting it or disabling it via the kernel command line (radeon.agpmode=-1 to disable, 1,2,4,8 to force the agp mode). It might also be related to the latency setting on the host bridge. VIA boards tend to set them pretty aggressively. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 13 Dec '10

13 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #15 from Holger Lenz <holger.lenz(a)onlinehome.de> 2010-12-13 19:56:36 --- Did some more homework: Compiled kernel 2.6.37 rc5, taking care to enable KMS (new driver) by setting DRM_MODESET_KMS=ON. Unpatched and patched drivers show the same behavior: 1. Boot without nomodeset in the kernel cmd line: Blank screen before X is fully loaded. 2. Boot with nomodeset in the kernel cmd line: X loads with radeon/R600 classic driver is is reasonably quick in 2D, but a lockup occurs sooner or later. Switching from X to fb terminal usually does the trick quickly. The patched driver seems to lock up more quickly. Any ideas what I could do to help you fix the bug? Hardware is similar to Duncans: AMD K8, VIA K8T800 chipset, Radeon HD 4650 AGP (RV730) Cheers Holger -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[PATCH] drm/radeon/kms: disable the r600 cb offset checker for linear surfaces
by Alex Deucher 13 Dec '10

13 Dec '10

There are too many strange corner cases triggered in old userspace drivers out there to that it's nearly impossible to not break some obscure app. Cc: Jean Delvare <khali(a)linux-fr.org> Signed-off-by: Alex Deucher <alexdeucher(a)gmail.com> --- drivers/gpu/drm/radeon/r600_cs.c | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/radeon/r600_cs.c b/drivers/gpu/drm/radeon/r600_cs.c index 0f90fc3..7831e08 100644 --- a/drivers/gpu/drm/radeon/r600_cs.c +++ b/drivers/gpu/drm/radeon/r600_cs.c @@ -315,11 +315,10 @@ static inline int r600_cs_track_validate_cb(struct radeon_cs_parser *p, int i) if (array_mode == V_0280A0_ARRAY_LINEAR_GENERAL) { /* the initial DDX does bad things with the CB size occasionally */ /* it rounds up height too far for slice tile max but the BO is smaller */ - tmp = (height - 7) * 8 * bpe; - if ((tmp + track->cb_color_bo_offset[i]) > radeon_bo_size(track->cb_color_bo[i])) { - dev_warn(p->dev, "%s offset[%d] %d %d %lu too big\n", __func__, i, track->cb_color_bo_offset[i], tmp, radeon_bo_size(track->cb_color_bo[i])); - return -EINVAL; - } + /* r600c,g also seem to flush at bad times in some apps resulting in + * bogus values here. So for linear just allow anything to avoid breaking + * broken userspace. + */ } else { dev_warn(p->dev, "%s offset[%d] %d %d %lu too big\n", __func__, i, track->cb_color_bo_offset[i], tmp, radeon_bo_size(track->cb_color_bo[i])); return -EINVAL; -- 1.7.1.1

1 0

[PATCH] drm-vblank: Always return true vblank count of scheduled vblank event.
by Mario Kleiner 13 Dec '10

13 Dec '10

-------- Original Message -------- Subject: [PATCH] drm-vblank: Always return true vblank count of scheduled vblank event. Date: Fri, 10 Dec 2010 15:58:10 +0100 From: Mario Kleiner <mario.kleiner(a)tuebingen.mpg.de> To: airlied(a)gmail.com CC: jbarnes(a)virtuousgeek.org, krh(a)bitplanet.net, Mario Kleiner <mario.kleiner(a)tuebingen.mpg.de> This patch tries to make sure that the vbl.reply.sequence vblank count for a queued or emitted vblank event always corresponds to the true vblank count of queueing/emission, so the ddx can rely on the returned target_msc for consistency checks and implementation of swap_intervals in glXSwapBuffers(). Without this there is a small race-condition between the userspace ddx queueing a vblank event and the vblank counter incrementing before the event gets queued in the kernel. Signed-off-by: Mario Kleiner <mario.kleiner(a)tuebingen.mpg.de> --- drivers/gpu/drm/drm_irq.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c index 4e82d0d..55160d7 100644 --- a/drivers/gpu/drm/drm_irq.c +++ b/drivers/gpu/drm/drm_irq.c @@ -1086,15 +1086,18 @@ static int drm_queue_vblank_event(struct drm_device *dev, int pipe, e->event.sequence = vblwait->request.sequence; if ((seq - vblwait->request.sequence) <= (1 << 23)) { + e->event.sequence = seq; e->event.tv_sec = now.tv_sec; e->event.tv_usec = now.tv_usec; drm_vblank_put(dev, e->pipe); list_add_tail(&e->base.link, &e->base.file_priv->event_list); wake_up_interruptible(&e->base.file_priv->event_wait); + vblwait->reply.sequence = seq; trace_drm_vblank_event_delivered(current->pid, pipe, vblwait->request.sequence); } else { list_add_tail(&e->base.link, &dev->vblank_event_list); + vblwait->reply.sequence = vblwait->request.sequence; } spin_unlock_irqrestore(&dev->event_lock, flags); -- 1.7.0.4

2 3

[Bug 32188] segfault caused by Komodo Edit, r600c
by bugzilla-daemon＠freedesktop.org 13 Dec '10

13 Dec '10

https://bugs.freedesktop.org/show_bug.cgi?id=32188 Alex Deucher <agd5f(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|DRI |xorg Version|DRI CVS |unspecified Component|DRM/Radeon |Driver/Radeon AssignedTo|dri-devel(a)lists.freedesktop |xorg-driver-ati(a)lists.x.org |.org | QAContact| |xorg-team(a)lists.x.org --- Comment #4 from Alex Deucher <agd5f(a)yahoo.com> 2010-12-13 08:27:04 PST --- This is a bug in the ddx. -- 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 31943] drm EDID checking is too strict
by bugzilla-daemon＠freedesktop.org 13 Dec '10

13 Dec '10

https://bugs.freedesktop.org/show_bug.cgi?id=31943 Alex Deucher <agd5f(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[drm:radeon_dvi_detect] |drm EDID checking is too |*ERROR* HDMI Type A-1: |strict |probed a monitor but | |no|invalid EDID | -- 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 32188] segfault caused by Komodo Edit, r600c
by bugzilla-daemon＠freedesktop.org 13 Dec '10

13 Dec '10

1 0

2.6.37-rc2-git7 regression: wine fails to start
by Jean Delvare 13 Dec '10

13 Dec '10

Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs: radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730 X.org version is 7.5. With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection. I can also provide any additional data you need for investigation. -- Jean Delvare

3 10

← Newer
1
...
27
28
29
30
31
32
33
...
41
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel December 2010