Date: Thu, 25 Nov 2010 10:14:36 -0500
From: Kyle McMartin <kyle@mcmartin.ca>
To: Valdis.Kletnieks@vt.edu
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
        linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>
Subject: Re: mmotm 2010-11-23 - WARNING: at drivers/tty/tty_io.c:1331
Message-ID: <20101125151436.GG22651@bombadil.infradead.org>
References: <201011240045.oAO0jYQ5016010@imap1.linux-foundation.org>
 <5747.1290574539@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5747.1290574539@localhost>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1304
Lines: 31

On Tue, Nov 23, 2010 at 11:55:39PM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 23 Nov 2010 16:13:06 PST, akpm@linux-foundation.org said:
> > The mm-of-the-moment snapshot 2010-11-23-16-12 has been uploaded to
> > 
> >    http://userweb.kernel.org/~akpm/mmotm/
> 
> Seen during boot:
> 
> [   23.015448] Modules linked in:
> [   23.015453] Pid: 1207, comm: plymouthd Not tainted 2.6.37-rc3-mmotm1123 #3
> [   23.015455] Call Trace:

I've been trying to figure this one out for a while, without much luck.
(Users are seeing it in 2.6.36 as well.)

I *think* (I added a rawhide debugging patch to print the tty->name)
that plymouth is always opening tty7 to cause this. My guess is the BKL
removal has exposed some kind of race, but it's not obvious to me (and
there's many other bugs to sort through too. :(

CC-ing Jiri since he seems to be the poor guy who's been poking this
recently (there's a good few threads about this (though the others look
like an ldisc attach race...)) I wouldn't think that's the case here
since N_TTY is the default...

--Kyle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/