From nobody Tue Nov 14 08:01:48 2023 X-Original-To: bugs@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 4STzK95cvDz50vcG for ; Tue, 14 Nov 2023 08:01:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4STzK90QWFz3bXd for ; Tue, 14 Nov 2023 08:01:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1699948909; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WkulgIDbCHe3T6HiNLEP70NfNg/Z89SXOzBGwtBdmWM=; b=rSLQjgTwUmItr4+ocX0Xv6xjAkQ2bF11em5K54IaZPvQjp5lWYhxWfBoZjvNEHcShtQXBD e5PF8KBPdO4wCjtSxc+TZqY0Iv35bx4NTqfkp9RLkjiCRBca0sAUVUR4uzQ7gVm6OzHItl BGWzLRfxbh/hDtuYy1raWmO10SGUYHj/Ke3QbvltAzZs6hU5x0wCYQWi8dpSJaUuYmgoOI o+pMkdgIyORMQL1guw6nxm6uvXWyPoMoCjOgVwBDPDGkt37SK9GrlqfG2clBJ9ihAWnUdt wCg4XhXhX188KLrcCVeS/FWrXp/LvZs2XSVLGE2DuuLRg0EmIAMXSa/Rpo4uHA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1699948909; a=rsa-sha256; cv=none; b=MKtAyWGFBEvlcL4vFpMTzvrtd1IS3DVWKLFTYe6+ska0J3hNvUtLOb2WofB/3vry2Bk2r3 TRl/iq613+8uwBGYQ2SeP+Lozj1KsEWZlN8ASAJh/EwVjCeEgaTq8o1u5BTjiAl2ObXZ/G DQbtEbLK31lByCQc02Ih3V+ekMlKDbqBsTG80+Jw88JbzEYJOAKczKKEf93mX19XkZul7d TU7w3kKisMltwL7F3ll/MAX2IvfxXjDAG0vixrAQrMMpa7EgwCBynrFkyT2jr/Axj+wSx0 4CDF2IaoOrQ4gVrBOWNIWt6Gx0q4CrOwZNWeDSNoaQrO3PHQXNwPVhAGcLLsuA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4STzK86YbNzh42 for ; Tue, 14 Nov 2023 08:01:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 3AE81m2a071938 for ; Tue, 14 Nov 2023 08:01:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3AE81mGr071937 for bugs@FreeBSD.org; Tue, 14 Nov 2023 08:01:48 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 266990] FreeBSD can not drive 16950 chip correctly Date: Tue, 14 Nov 2023 08:01:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: alster@vinterdalen.se X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266990 --- Comment #4 from Andrey Korobkov --- In 14.0-RELEASE it still works well, but new message appeared: "ns8250: UART FCR is broken". What does it mean? # dmesg.boot puc0: port 0x1000-0x103f,0x1040-0x104f mem 0xba000000-0xba000fff irq 27 at device 0.0 = on p ci7 ns8250: UART FCR is broken ns8250: UART FCR is broken uart2: <16950 or compatible> at port 1 on puc0 ns8250: UART FCR is broken ns8250: UART FCR is broken uart3: <16950 or compatible> at port 2 on puc0 ns8250: UART FCR is broken ns8250: UART FCR is broken uart4: <16950 or compatible> at port 3 on puc0 ns8250: UART FCR is broken ns8250: UART FCR is broken uart5: <16950 or compatible> at port 4 on puc0 --=20 You are receiving this mail because: You are the assignee for the bug.=