Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751975AbbKJA3r (ORCPT ); Mon, 9 Nov 2015 19:29:47 -0500 Received: from one.firstfloor.org ([193.170.194.197]:34335 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751252AbbKJA3m (ORCPT ); Mon, 9 Nov 2015 19:29:42 -0500 Date: Tue, 10 Nov 2015 01:29:39 +0100 From: Andi Kleen To: gregkh@linuxfoundation.org, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, peter@hurleysoftware.com Subject: 4.3 serial driver crashes with console shortly after boot Message-ID: <20151110002939.GG3533@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1100 Lines: 32 Hi, With 4.3 an x86 server is always crashing roughly a minute after boot in __uart_start/uart_tx_stopped. This is repeatable over multiple boots. The back trace is flush_to_ldisc->n_tty_receive_buf2->n_tty_receive_buf_common-> commit_echoes-> uart_flush_chars->uart_start It seems to follow a bad pointer here ffffffff813bbdfa: f6 80 f4 01 00 00 01 testb $0x1,0x1f4(%rax) <--- ffffffff813bbe01: 74 01 je ffffffff813bbe04 <__uart_start.isra.1+0x24> Unfortunately I don't have the contents of RAX which scrolled away, but since CR2 is 1f4 I suspect it's NUL. It seems to depend on the order of the console=... arguments on the kernel command line. With console=tty0 console=ttyS0,115200n8 it crashes, but when reversing the options it does not crash. -Andi -- ak@linux.intel.com -- Speaking for myself only. -- 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/