From: Hugh Dickins <hughd@google.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Sasha Levin <sasha.levin@oracle.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Sasha Levin <levinsasha928@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
linux-fbdev@vger.kernel.org, florianSchandinat@gmx.de
Subject: Re: tty, vt: lockdep warnings
Date: Wed, 07 Nov 2012 06:26:41 +0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1211062219470.1077@eggly.anvils> (raw)
In-Reply-To: <alpine.LNX.2.00.1211061950020.1712@eggly.anvils>
On Tue, 6 Nov 2012, Hugh Dickins wrote:
>
> Ah, now I actually scan through it, I see references to blank screen:
> I'll try taking off your patch and seeing if it came up at screen
> blanking time, then put on your patch back on and try again.
> I'll report back in an hour or two.
Yes, that was it. When the console screen blanked on 3.7.0-rc3-mm1,
it generated that lockdep splat, visible once I unblanked. But once I
applied your patch to the kernel, lockdep kept quiet across blank/unblank.
Thanks!
Hugh
prev parent reply other threads:[~2012-11-07 6:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50899507.1040900@oracle.com>
2012-10-26 13:37 ` tty, vt: lockdep warnings Alan Cox
2012-11-05 17:26 ` Sasha Levin
2012-11-05 17:59 ` Alan Cox
2012-11-05 18:00 ` Sasha Levin
2012-11-05 19:17 ` Hugh Dickins
2012-11-05 20:15 ` Alan Cox
2012-11-05 20:34 ` Hugh Dickins
2012-11-06 16:11 ` Alan Cox
2012-11-06 16:42 ` Dave Jones
2012-11-06 17:38 ` Alan Cox
2012-11-07 13:47 ` Sasha Levin
2012-11-07 15:57 ` Alan Cox
2012-11-07 16:15 ` Bjørn Mork
2012-11-07 16:56 ` Alan Cox
2012-11-08 14:34 ` tty, vt: lockdep warnings (Patch v3) Alan Cox
2012-11-09 19:34 ` Hugh Dickins
2012-11-09 19:42 ` Sasha Levin
2012-11-13 16:24 ` Sasha Levin
2012-11-07 4:29 ` tty, vt: lockdep warnings Hugh Dickins
2012-11-07 6:26 ` Hugh Dickins [this message]
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=alpine.LNX.2.00.1211062219470.1077@eggly.anvils \
--to=hughd@google.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=davej@redhat.com \
--cc=florianSchandinat@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=levinsasha928@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox