From nobody Tue Oct 25 02:11:28 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MxFmj72NHz4gGrX for ; Tue, 25 Oct 2022 02:11:33 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MxFmj1Z1zz3XRw for ; Tue, 25 Oct 2022 02:11:33 +0000 (UTC) (envelope-from void@f-m.fm) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 31C2E32008C3 for ; Mon, 24 Oct 2022 22:11:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 24 Oct 2022 22:11:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to; s=fm3; t= 1666663890; x=1666750290; bh=XqfzPqCb4IwNKc8lB5ufT3bdbU5aKo46u4y q2QFtMI0=; b=BjLhuMGfaooOlOZ6j530D8BVaw2aFgi5hGMj7r0gHJ4fvka0Yok C7ktKS0jV12r4Wa5Ji1wcG8FK/6yls8cND4Ur6HyyVV2YWXWJodS5NEaSLWleB0P ZCD7BG7GitqcqeVye52inyAGzfFqHSUOGBM3tzI3bRu+T+ADO6qzOJu7mWfdv44p k6YeGHs+Dzmr+CK0D3ljDyOxPGdqUhI4Ld/3EjCLTPbAhEB+/HhGm+Ke9ndnxPAp ywAmGtfqSwrJpuWt2DG/FXdtpQQVOo62WTUgebTJkBbLm/TiRLn9nFzN+wSCWyKs kh9S1i4lEY1D+qmV8QV0OqewqLED+U0Tz4Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1666663890; x= 1666750290; bh=XqfzPqCb4IwNKc8lB5ufT3bdbU5aKo46u4yq2QFtMI0=; b=R cX/nGoKe96wNR7mNtKv6MSICclpGCV4rvLPk5Ht7qAnd38vlQwPUXpYlp69kTBTt xkA29cCz0PqWQ+zprSQkhQq41XCYiHjIDaa+9p2k3vepSDqDltOd7kTRM/9i7U7M TKnLTdkt8bSU+Q9CI45V9if3DRCFChJ4cimjijyX+YHJgAfd7z3c+OhsSzkimN/1 xZ27l0rfBRr8RbgI8kzuDarjCRWLPAZONGK4H1ctpAJB7O1JkkD/A3G0azhC8cI+ 8RK4VPk8OZnbCxhUjfCOJZFmQOpFFnw63rQIZ13peMYML277IHk7gTail2C5dbMn 0v4q8ONXu/lhtq82gfJXA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrgedthedgheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepveduffeivdfffffghfegfeejfefftdeiteehteekfefhvdefgfettdeuheegff eunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhho ihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 24 Oct 2022 22:11:30 -0400 (EDT) Date: Tue, 25 Oct 2022 03:11:28 +0100 From: void To: freebsd-current@freebsd.org Subject: ns8250: UART FCR is broken Message-ID: Mail-Followup-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Rspamd-Queue-Id: 4MxFmj1Z1zz3XRw X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=BjLhuMGf; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="R cX/nGo"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.25 as permitted sender) smtp.mailfrom=void@f-m.fm X-Spamd-Result: default: False [-4.75 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.65)[-0.648]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.25:from]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.25:from] X-ThisMailContainsUnwantedMimeParts: N hello freebsd-current@, this started appearing in dmesg ns8250: UART FCR is broken ns8250: UART FCR is broken uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ns8250: UART FCR is broken uart0: console (9600,n,8,1) ns8250: UART FCR is broken ns8250: UART FCR is broken uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 ns8250: UART FCR is broken ns8250: UART FCR is broken ns8250: UART FCR is broken uart2: <16550 or compatible> port 0x3e8-0x3ef irq 4 on acpi0 ns8250: UART FCR is broken The system is a bhyve guest running main-n258723-e0c3f66b4d5f on amd64 with a lightly modified generic-nodebug. There's no physical hardware attached to any com port on the host. Do I need to be concerned with this or is it a known issue? is it a real hardware problem? The host runs many bhyve guests. TIA,