linux-kernel - linux-2.6.31 INIT: open(/dev/console): Input/output error (due to commit b50989dc444599c8b21edc23536fc305f4e9b7d5)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <b6a2187b0909240624u2821a312ub6d02df21d552248@mail.gmail.com>
Date:	Thu, 24 Sep 2009 21:24:45 +0800
From:	Jeff Chua <jeff.chua.linux@...il.com>
To:	lkml <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: linux-2.6.31 INIT: open(/dev/console): Input/output error (due to 
	commit b50989dc444599c8b21edc23536fc305f4e9b7d5)

Latest linux pull few days ago broke the console.

The error during boot up while switching from init S to M showed

INIT: open(/dev/console): Input/output error


Reverting this commit solves the problem. This is 100% repeatable on a
"real" machine, but does not show up on kvm or vmware guest console.


commit b50989dc444599c8b21edc23536fc305f4e9b7d5
Author: Alan Cox <alan@...ux.intel.com>
Date:   Sat Sep 19 13:13:22 2009 -0700

    tty: make the kref destructor occur asynchronously

    We want to be able to sleep in the destructor for USB at least. It isn't a
    hot path so just pushing it to a work queue doesn't really cause any
    difficulty.

    Signed-off-by: Alan Cox <alan@...ux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>



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