On 03/20/2013 07:29 PM, Borislav Petkov wrote:
> On Wed, Mar 20, 2013 at 07:23:19PM +0400, Lijo Antony wrote:
>> # bad: [fffddfd6c8e0c10c42c6e2cc54ba880fcc36ebbb] Merge branch
>> 'drm-next' of git://people.freedesktop.org/~airlied/linux
>> git bisect bad fffddfd6c
On 03/20/2013 07:29 PM, Borislav Petkov wrote:
On Wed, Mar 20, 2013 at 07:23:19PM +0400, Lijo Antony wrote:
# bad: [fffddfd6c8e0c10c42c6e2cc54ba880fcc36ebbb] Merge branch
'drm-next' of git://people.freedesktop.org/~airlied/linux
git bisect bad fffddfd6c8e0c10c42c6e2cc54ba880fcc36ebbb
On 03/20/2013 10:35 AM, Lijo Antony wrote:
I think this is same as https://lkml.org/lkml/2013/3/16/143 (btw, git
bisect in that mail is incorrect). While investigating, I found this
issue was introduced during 3.9 merge window. For me this comes when I
connect my TV via HDMI.
FWIW, git bisect
On 03/20/2013 12:40 AM, Peter Hurley wrote:
with the hope of having the right people on CC now (finally, thanks
Lucas :-)), here's the same splat on -rc3. Someone better take a look
soonish, please:
Also happens in next (on nv50 hardware).
I think this is same as https://lkml.org/lkml/2013/3
On 03/20/2013 10:35 AM, Lijo Antony wrote:
> I think this is same as https://lkml.org/lkml/2013/3/16/143 (btw, git
> bisect in that mail is incorrect). While investigating, I found this
> issue was introduced during 3.9 merge window. For me this comes when I
> connect my TV via HDMI
On 03/20/2013 12:40 AM, Peter Hurley wrote:
>>
>> with the hope of having the right people on CC now (finally, thanks
>> Lucas :-)), here's the same splat on -rc3. Someone better take a look
>> soonish, please:
>
> Also happens in next (on nv50 hardware).
I think this is same as https://lkml.org/l
On 03/16/2013 10:29 PM, Lijo Antony wrote:
But looking at 65b5f42e2a9eb9c8383fb67698bf8c27657f8c14, it looks I
might have done some mistake in bisecting.
My bisecting was indeed incorrect. Issue started even before 3.9.0-rc1.
Attempting a proper bisect this time...
-lijo
On 03/16/2013 10:29 PM, Lijo Antony wrote:
>
> But looking at 65b5f42e2a9eb9c8383fb67698bf8c27657f8c14, it looks I
> might have done some mistake in bisecting.
My bisecting was indeed incorrect. Issue started even before 3.9.0-rc1.
Attempting a proper bisect this time...
-lijo
Hi,
This is a Dell Inspiron N5110 laptop with Optimus mess.
Until 3.9.0-rc1, tv connected throuh HDMI was not getting detected. But
in 3.9.0-rc2, when I connect HDMI cable, I get this,
=
[ INFO: possible recursive locking detected ]
3.9.0-rc2 #22 Not
Signed-off-by: Lijo Antony
---
drivers/gpu/drm/nouveau/core/core/client.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/core/core/client.c
b/drivers/gpu/drm/nouveau/core/core/client.c
index 295c221..d0f6b9d 100644
--- a/drivers/gpu/drm/nouveau
Signed-off-by: Lijo Antony
---
drivers/gpu/drm/nouveau/core/core/client.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/core/core/client.c
b/drivers/gpu/drm/nouveau/core/core/client.c
index 295c221..d0f6b9d 100644
--- a/drivers/gpu/drm/nouveau
11 matches
Mail list logo