From: Dave Jones <davej@redhat.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: 3.9+ tty lockdep trace.
Date: Tue, 7 May 2013 11:04:23 -0400 [thread overview]
Message-ID: <20130507150423.GA13062@redhat.com> (raw)
In-Reply-To: <51890C31.3000203@hurleysoftware.com>
On Tue, May 07, 2013 at 10:14:09AM -0400, Peter Hurley wrote:
> >> Just hit this again, by switching tty's during bootup.
> >> The previous time was switching from X to console iirc, so that seems to be
> >> the key to triggering this.
> >
> > Sorry for not getting back to this sooner, merge window fun...
> >
> > Anyway, Peter, could this be something that your ldisc patches are
> > triggering?
>
> Yes, although early analysis also suggests the lockdep splat is possible
> regardless, just much less likely.
>
> I looked at this over the weekend, but I wasn't able to determine (in
> the limited time I had available) if the splat was valid; ie., if the
> cpu states could actually be concurrent and result in deadlock.
>
> I need to study the VT_DISALLOCATE ioctl in more detail which I plan
> to do this week.
I don't know if it proves/disproves anything, but shortly before the dump
gets printed, everything is kind of locked up. I can switch tty's, but
the gettys on them are dead to the world until after the dump.
ISTR a pause for a while when I hit this switching from X too.
Dave
next prev parent reply other threads:[~2013-05-07 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 15:47 3.9+ tty lockdep trace Dave Jones
2013-05-06 18:00 ` Dave Jones
2013-05-06 18:40 ` Greg Kroah-Hartman
2013-05-07 14:14 ` Peter Hurley
2013-05-07 15:04 ` Dave Jones [this message]
2013-05-07 17:35 ` Peter Hurley
2013-05-07 18:00 ` Dave Jones
2013-05-08 21:18 ` Peter Hurley
2013-05-17 16:41 ` [PATCH] tty/vt: Fix vc_deallocate() lock order Peter Hurley
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=20130507150423.GA13062@redhat.com \
--to=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.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.