From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751917Ab2GUWiH (ORCPT <rfc822;w@1wt.eu>);
	Sat, 21 Jul 2012 18:38:07 -0400
Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:43145 "EHLO
	lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751255Ab2GUWiG (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 21 Jul 2012 18:38:06 -0400
Date: Sat, 21 Jul 2012 23:41:45 +0100
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, Alan Cox <alan@linux.intel.com>,
        Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Oops after merge of tty-next
Message-ID: <20120721234145.354e6ee9@pyramind.ukuu.org.uk>
In-Reply-To: <5009D68A.3050301@mev.co.uk>
References: <5009D68A.3050301@mev.co.uk>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu)
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII=
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, 20 Jul 2012 23:07:06 +0100
Ian Abbott <abbotti@mev.co.uk> wrote:

> I'm getting an Oops in the linux-next tree today after the merge of the 
> remote-tracking branch 'tty/tty-next'.  I bisected it down to commit 
> 36b3c070d2346c890d690d71f6eab02f8c511137 in 
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git :
> 
>    tty: Move the handling of the tty release logic

Ok that's not improbable, I thought I had them all nailed.

> Sorry, I don't have a copy of the Oops right now, but it's failing 
> somewhere in tty_open() or check_tty_count() during system boot, 
> probably when getty opens one of the vc tty devices.

That would be more surprising as its a path I tested a lot but strange
things occur. What may also be very important is to know what distro you
are using.

Alan