All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:23:19 +0400	[thread overview]
Message-ID: <5149D467.7030908@gmail.com> (raw)
In-Reply-To: <5149589D.6090403@gmail.com>

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 gave this log,

git bisect start 'drivers/gpu/'
# good: [e450fcc6669705ef49784080ac6dd8513df37763] drm/tegra: Add list 
of framebuffers to debugfs
git bisect good e450fcc6669705ef49784080ac6dd8513df37763
# bad: [6dbe51c251a327e012439c4772097a13df43c5b8] Linux 3.9-rc1
git bisect bad 6dbe51c251a327e012439c4772097a13df43c5b8
# good: [bab588fcfb6335c767d811a8955979f5440328e0] Merge tag 'soc' of 
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect good bab588fcfb6335c767d811a8955979f5440328e0
# good: [be88298b0a3f771a4802f20c5e66af74bfd1dff1] drm/tilcdc: only 
build on arm
git bisect good be88298b0a3f771a4802f20c5e66af74bfd1dff1
# bad: [4d53233a36fdda567cd4d080e27e1ee4b669ddd1] drm: don't use 
idr_remove_all()
git bisect bad 4d53233a36fdda567cd4d080e27e1ee4b669ddd1
# good: [9afa3195b96da7d2320ec44d19fbfbded7a15571] Merge branch 
'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial
git bisect good 9afa3195b96da7d2320ec44d19fbfbded7a15571
# good: [496ad9aa8ef448058e36ca7a787c61f2e63f0f54] new helper: 
file_inode(file)
git bisect good 496ad9aa8ef448058e36ca7a787c61f2e63f0f54
# bad: [d895cb1af15c04c522a25c79cc429076987c089b] Merge branch 
'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
git bisect bad d895cb1af15c04c522a25c79cc429076987c089b
# bad: [fffddfd6c8e0c10c42c6e2cc54ba880fcc36ebbb] Merge branch 
'drm-next' of git://people.freedesktop.org/~airlied/linux
git bisect bad fffddfd6c8e0c10c42c6e2cc54ba880fcc36ebbb

-lijo

  reply	other threads:[~2013-03-20 15:23 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
2013-03-20 15:23         ` Lijo Antony [this message]
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=5149D467.7030908@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.