[REGRESSION] nouveau: Resume hung after protecting against client races (MBA3,1)

Hi Ben, The new mutexes in nvc0/nv50 (fadb17190/b509656) break resume on my MBA3,1. A dead-lock somewhere, perhaps? Reverting fixes the problem. Thanks, Henrik

[REGRESSION] nouveau: Resume hung after protecting against client races (MBA3,1)

Hi Ben, The new mutexes in nvc0/nv50 (fadb17190/b509656) break resume on my MBA3,1. A dead-lock somewhere, perhaps? Reverting fixes the problem. Thanks, Henrik ___ dri-devel mailing list dri-devel@lists.freedesktop.org

Linux 3.7-rc6

> Yeah, the utter lack of a vbt fits very nicely, thanks for checking, > I've merged the patch into drm-intel-fixes and will forward it for > inclusion into 3.7 rsn. Great, thanks. One thing about that patch: if we would ever encounter a non-zero edp.bpp < 3, display_bpc would not be clamped. I

Linux 3.7-rc6

Hi Daniel, > >> My apologies for the long delay in answering, I've somehow mixed up > >> different bugreports and thought I've sent you a patch to test > >> already. Anyway, please test > >> > >> https://patchwork.kernel.org/patch/1728111/ > &

Linux 3.7-rc6

Hi Daniel, > My apologies for the long delay in answering, I've somehow mixed up > different bugreports and thought I've sent you a patch to test > already. Anyway, please test > > https://patchwork.kernel.org/patch/1728111/ Tested-by: Henrik Rydberg Thanks, Henrik

Re: Linux 3.7-rc6

Hi Daniel, My apologies for the long delay in answering, I've somehow mixed up different bugreports and thought I've sent you a patch to test already. Anyway, please test https://patchwork.kernel.org/patch/1728111/ Tested-by: Henrik Rydberg rydb...@euromail.se Can you please

Re: Linux 3.7-rc6

Yeah, the utter lack of a vbt fits very nicely, thanks for checking, I've merged the patch into drm-intel-fixes and will forward it for inclusion into 3.7 rsn. Great, thanks. One thing about that patch: if we would ever encounter a non-zero edp.bpp 3, display_bpc would not be clamped. I

Re: Linux 3.7-rc6

Hi Daniel, My apologies for the long delay in answering, I've somehow mixed up different bugreports and thought I've sent you a patch to test already. Anyway, please test https://patchwork.kernel.org/patch/1728111/ Tested-by: Henrik Rydberg rydb...@euromail.se Thanks, Henrik

Linux 3.7-rc6

Hi Daniel, > > As advertised, this patch breaks the Macbook Pro Retina, which seems > > unfair. The patch below is certainly not the best remedy, but it does > > work. Tested on a MacbookPro10,1. > > My apologies for the long delay in answering, I've somehow mixed up > different bugreports and

Re: Linux 3.7-rc6

Hi Daniel, As advertised, this patch breaks the Macbook Pro Retina, which seems unfair. The patch below is certainly not the best remedy, but it does work. Tested on a MacbookPro10,1. My apologies for the long delay in answering, I've somehow mixed up different bugreports and thought

Linux 3.7-rc6

> drm/i915: do not ignore eDP bpc settings from vbt As advertised, this patch breaks the Macbook Pro Retina, which seems unfair. The patch below is certainly not the best remedy, but it does work. Tested on a MacbookPro10,1. Thanks, Henrik --- From: Henrik Rydberg <rydb...@eurom

Re: Linux 3.7-rc6

drm/i915: do not ignore eDP bpc settings from vbt As advertised, this patch breaks the Macbook Pro Retina, which seems unfair. The patch below is certainly not the best remedy, but it does work. Tested on a MacbookPro10,1. Thanks, Henrik --- From: Henrik Rydberg rydb...@euromail.se Date

[REGRESSION] nouveau: Severe screen corruption on (0xaf, nv50)

On Sun, Oct 21, 2012 at 09:10:24AM +0200, Henrik Rydberg wrote: > On Thu, Oct 18, 2012 at 11:58:09AM +0200, Henrik Rydberg wrote: > > Hi Ben, > > > > 3.7-rc1 messed up the screen on my MacBookAir3,1 (nv50, 0xaf) pretty > > badly. Not su

Re: [REGRESSION] nouveau: Severe screen corruption on (0xaf, nv50)

On Sun, Oct 21, 2012 at 09:10:24AM +0200, Henrik Rydberg wrote: On Thu, Oct 18, 2012 at 11:58:09AM +0200, Henrik Rydberg wrote: Hi Ben, 3.7-rc1 messed up the screen on my MacBookAir3,1 (nv50, 0xaf) pretty badly. Not surprisingly, commit 3863c9bc887e9638a9d905d55f6038641ece78d6

[REGRESSION] nouveau: Severe screen corruption on (0xaf, nv50)

On Thu, Oct 18, 2012 at 11:58:09AM +0200, Henrik Rydberg wrote: > Hi Ben, > > 3.7-rc1 messed up the screen on my MacBookAir3,1 (nv50, 0xaf) pretty > badly. Not surprisingly, > > commit 3863c9bc887e9638a9d905d55f6038641ece78d6 > Author: Ben Skeggs > Date: Sat Ju

Re: [REGRESSION] nouveau: Severe screen corruption on (0xaf, nv50)

On Thu, Oct 18, 2012 at 11:58:09AM +0200, Henrik Rydberg wrote: Hi Ben, 3.7-rc1 messed up the screen on my MacBookAir3,1 (nv50, 0xaf) pretty badly. Not surprisingly, commit 3863c9bc887e9638a9d905d55f6038641ece78d6 Author: Ben Skeggs bske...@redhat.com Date: Sat Jul 14 19:09:17 2012

[REGRESSION] nouveau: Severe screen corruption on (0xaf, nv50)

Hi Ben, 3.7-rc1 messed up the screen on my MacBookAir3,1 (nv50, 0xaf) pretty badly. Not surprisingly, commit 3863c9bc887e9638a9d905d55f6038641ece78d6 Author: Ben Skeggs Date: Sat Jul 14 19:09:17 2012 +1000 drm/nouveau/instmem: completely new implementation, as a subdev module is the

[REGRESSION] nouveau: Severe screen corruption on (0xaf, nv50)

Hi Ben, 3.7-rc1 messed up the screen on my MacBookAir3,1 (nv50, 0xaf) pretty badly. Not surprisingly, commit 3863c9bc887e9638a9d905d55f6038641ece78d6 Author: Ben Skeggs bske...@redhat.com Date: Sat Jul 14 19:09:17 2012 +1000 drm/nouveau/instmem: completely new implementation, as a subdev

[PATCH] nouveau: Do not use nva3 engine for 0xaf chipset

The nva3 copy engine exhibits random memory corruption in at least one case, the GeForce 320M (nv50, 0xaf) in the MacBookAir3,1. This patch omits creating the engine for the specific chipset, falling back to M2MF, which kills the symptoms. Signed-off-by: Henrik Rydberg --- Hi Ben, this patch

[PATCH] nouveau: Do not use nva3 engine for 0xaf chipset

The nva3 copy engine exhibits random memory corruption in at least one case, the GeForce 320M (nv50, 0xaf) in the MacBookAir3,1. This patch omits creating the engine for the specific chipset, falling back to M2MF, which kills the symptoms. Signed-off-by: Henrik Rydberg rydb...@euromail.se --- Hi

Re: [REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

On Mon, Jul 09, 2012 at 03:13:25PM +0200, Henrik Rydberg wrote: On Thu, Jul 05, 2012 at 10:34:10AM +0200, Henrik Rydberg wrote: On Thu, Jul 05, 2012 at 08:54:46AM +0200, Henrik Rydberg wrote: Thanks for tracking down the source of this corruption. I don't have any such hardware, so

[REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

On Mon, Jul 09, 2012 at 03:13:25PM +0200, Henrik Rydberg wrote: > On Thu, Jul 05, 2012 at 10:34:10AM +0200, Henrik Rydberg wrote: > > On Thu, Jul 05, 2012 at 08:54:46AM +0200, Henrik Rydberg wrote: > > > > Thanks for tracking down the source of this corruption. I d

[REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

On Thu, Jul 05, 2012 at 10:34:10AM +0200, Henrik Rydberg wrote: > On Thu, Jul 05, 2012 at 08:54:46AM +0200, Henrik Rydberg wrote: > > > Thanks for tracking down the source of this corruption. I don't have > > > any such hardware, so until someone can figure it out, I think

Re: [REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

On Thu, Jul 05, 2012 at 10:34:10AM +0200, Henrik Rydberg wrote: On Thu, Jul 05, 2012 at 08:54:46AM +0200, Henrik Rydberg wrote: Thanks for tracking down the source of this corruption. I don't have any such hardware, so until someone can figure it out, I think we should apply this patch

[REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

On Thu, Jul 05, 2012 at 08:54:46AM +0200, Henrik Rydberg wrote: > > Thanks for tracking down the source of this corruption. I don't have > > any such hardware, so until someone can figure it out, I think we > > should apply this patch. > > In that case, I would have to

[REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

> Thanks for tracking down the source of this corruption. I don't have > any such hardware, so until someone can figure it out, I think we > should apply this patch. In that case, I would have to massage the patch a bit first; it creates a problem with suspend/resume. Might be something with

[REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

Hi Ben, Dave, Since 3.5-rc0, I have been experiencing occasional screen corruption on my MacBookAir3,1, using a GeForce 320M (nv50, 0xaf). The X driver version is xf86-video-nouvea-1.0.1-1 (arch). I do not know what the root problem is, but I have been able to isolate the symptoms to the usage

[REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

Hi Ben, Dave, Since 3.5-rc0, I have been experiencing occasional screen corruption on my MacBookAir3,1, using a GeForce 320M (nv50, 0xaf). The X driver version is xf86-video-nouvea-1.0.1-1 (arch). I do not know what the root problem is, but I have been able to isolate the symptoms to the usage

Re: [REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

Thanks for tracking down the source of this corruption. I don't have any such hardware, so until someone can figure it out, I think we should apply this patch. In that case, I would have to massage the patch a bit first; it creates a problem with suspend/resume. Might be something with

Re: [REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf

On Thu, Jul 05, 2012 at 08:54:46AM +0200, Henrik Rydberg wrote: Thanks for tracking down the source of this corruption. I don't have any such hardware, so until someone can figure it out, I think we should apply this patch. In that case, I would have to massage the patch a bit first

[git pull] drm fixes

Hi Dave, > just two changes, one udl endian fix, one nouveau memory corruption on > some GPUs. I have been tracking an elusive memory corruption bug appearing on my MacBookAir3,1 (nv50) since -rc0, but unfortunately it seems to be different from the one fixed here. The problem is of the random

Re: [git pull] drm fixes

Hi Dave, just two changes, one udl endian fix, one nouveau memory corruption on some GPUs. I have been tracking an elusive memory corruption bug appearing on my MacBookAir3,1 (nv50) since -rc0, but unfortunately it seems to be different from the one fixed here. The problem is of the random

[PATCH] nouveau: Set special lane map for the right chipset

-off-by: Henrik Rydberg --- Hi Dave, This patch fixes a regression in 3.4, tested against -rc2. Resending for your convenience, in case it got lost. Thanks, Henrik drivers/gpu/drm/nouveau/nv50_sor.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau

[PATCH] nouveau: Set special lane map for the right chipset

-off-by: Henrik Rydberg rydb...@euromail.se --- Hi Dave, This patch fixes a regression in 3.4, tested against -rc2. Resending for your convenience, in case it got lost. Thanks, Henrik drivers/gpu/drm/nouveau/nv50_sor.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers

[PATCH] nouveau: Set special lane map for the right chipset

-off-by: Henrik Rydberg --- drivers/gpu/drm/nouveau/nv50_sor.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nv50_sor.c b/drivers/gpu/drm/nouveau/nv50_sor.c index a7844ab..2746402 100644 --- a/drivers/gpu/drm/nouveau/nv50_sor.c +++ b/drivers/gpu/drm

[PATCH] nouveau: Set special lane map for the right chipset

-off-by: Henrik Rydberg rydb...@euromail.se --- drivers/gpu/drm/nouveau/nv50_sor.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nv50_sor.c b/drivers/gpu/drm/nouveau/nv50_sor.c index a7844ab..2746402 100644 --- a/drivers/gpu/drm/nouveau/nv50_sor.c