From owner-freebsd-bugs@freebsd.org Wed Jun 20 18:13:12 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC37B1002025 for ; Wed, 20 Jun 2018 18:13:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 57A766B85D for ; Wed, 20 Jun 2018 18:13:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 188341002024; Wed, 20 Jun 2018 18:13:12 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E524C1002023 for ; Wed, 20 Jun 2018 18:13:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 745366B85C for ; Wed, 20 Jun 2018 18:13:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B9E7D1DC6B for ; Wed, 20 Jun 2018 18:13:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5KIDA3R020443 for ; Wed, 20 Jun 2018 18:13:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5KIDA1q020433 for bugs@FreeBSD.org; Wed, 20 Jun 2018 18:13:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229188] Bhyve console hang on serial, works on stdio Date: Wed, 20 Jun 2018 18:13:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: dgilbert@eicat.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 18:13:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229188 Bug ID: 229188 Summary: Bhyve console hang on serial, works on stdio Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: dgilbert@eicat.ca I have a bulldozer (AMD 9590) running -CURRENT (a few days ago) that exhibi= ts some strange behavior lighting up a linux VM that we have transferred over = from Digital Ocean. If it boots with console as stdio (-f argument), it runs. If it boots with= out -f (console is a null-modem serial), then I get the following on the console (and the boot never finishes) [ 54.548000] serial8250: too much work for irq4 [ 57.412000] serial8250: too much work for irq4 [ 61.040000] [sched_delayed] sched: RT throttling activated [ 61.044000] serial8250: too much work for irq4 [ 63.892000] serial8250: too much work for irq4 [ 66.760000] serial8250: too much work for irq4 [ 69.656000] serial8250: too much work for irq4 Now I've done some research on this message. According to old posts (2009-2012-ish) Other virtual machines got this message from linux when they were either delivering interrupts on the serial when the serial was empty _= or_ they were emptying the serial buffer too quickly and interrupting for more output. On that latter point, apparently this is a legitimate failure mode of some physical chips, so the was much pushback on the linux side that the VMs nee= d be fixed. I don't see any published work arounds and I'd rather not leave screens run= ning the console of machines ... so ... --=20 You are receiving this mail because: You are the assignee for the bug.=