From: Lijo Antony <lijo.kernel@gmail.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Borislav Petkov <bp@alien8.de>, Ben Skeggs <bskeggs@redhat.com>,
Lucas Stach <dev@lynxeye.de>,
nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Dave Airlie <airlied@linux.ie>
Subject: Re: [Nouveau] nouveau lockdep splat
Date: Wed, 20 Mar 2013 10:35:09 +0400 [thread overview]
Message-ID: <5149589D.6090403@gmail.com> (raw)
In-Reply-To: <1363725620.3413.29.camel@thor.lan>
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/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. But for a couple of tags during bisecting, I
have seen the same during boot also.
-lijo
next prev parent reply other threads:[~2013-03-20 6:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 21:16 nouveau lockdep splat Borislav Petkov
2013-03-04 21:16 ` Borislav Petkov
2013-03-05 16:30 ` Lucas Stach
2013-03-06 0:04 ` Borislav Petkov
2013-03-06 0:04 ` Borislav Petkov
2013-03-06 19:14 ` Marcin Slusarz
2013-03-06 19:31 ` Stephen Warren
2013-03-06 19:31 ` Stephen Warren
2013-03-06 19:53 ` Borislav Petkov
2013-03-06 20:02 ` Joe Perches
2013-03-06 19:42 ` Borislav Petkov
2013-03-19 20:24 ` Borislav Petkov
2013-03-19 20:40 ` [Nouveau] " Peter Hurley
2013-03-20 6:35 ` Lijo Antony [this message]
2013-03-20 15:23 ` Lijo Antony
2013-03-20 15:29 ` Borislav Petkov
2013-03-24 18:00 ` Lijo Antony
2013-03-24 19:49 ` Borislav Petkov
2013-03-07 11:20 ` Arend van Spriel
2013-03-11 14:20 ` Arend van Spriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5149589D.6090403@gmail.com \
--to=lijo.kernel@gmail.com \
--cc=airlied@linux.ie \
--cc=bp@alien8.de \
--cc=bskeggs@redhat.com \
--cc=dev@lynxeye.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=peter@hurleysoftware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.