From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lithops.sigma-star.at ([195.201.40.130]) by casper.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gK4mS-0004NE-KL for linux-um@lists.infradead.org; Tue, 06 Nov 2018 17:04:46 +0000 From: Richard Weinberger Subject: Re: 4.20-rc1 looks broken for UML Date: Tue, 06 Nov 2018 18:04:25 +0100 Message-ID: <1819644.8DN5KTyJeP@blindfold> In-Reply-To: References: <4a096c4f-6552-dbcb-676b-a87306dde07a@kot-begemot.co.uk> <11176055.DIHjKAC0ao@blindfold> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-um" Errors-To: linux-um-bounces+geert=linux-m68k.org@lists.infradead.org To: Anton Ivanov Cc: gregkh@linuxfoundation.org, linux-um@lists.infradead.org Am Dienstag, 6. November 2018, 16:00:59 CET schrieb Anton Ivanov: > > On 11/5/18 10:07 PM, Richard Weinberger wrote: > > Anton, > > > > Am Montag, 5. November 2018, 16:22:36 CET schrieb Anton Ivanov: > >> This looks like something specific to ttys - the io there gets > >> corruption and/or hangs. > >> > >> I cannot reproduce it when I ssh in. > >> > >> It does not look like it is the new write IRQ bugfix - that works fine > >> over 4.19. > >> > >> Still debugging... > > Hmm, I don't see this with my Debian userspace. > > What exactly is your setup/config? > > > Gotcha. > > 8ebfe885c65ec82a0b1e955cf99ed62664e84414 is the guilty party. > > With it, I get tty corruption on UML. Any attempt to push a large amount > of data via the console results in spurious echoes or even a hang. > > Reverting it fixes things. Really?! This is "TTY: sn_console: Replace spin_is_locked() with spin_trylock()". sn_console is "SGI Altix L1 serial console"... Thanks, //richard _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um