From nobody Wed Oct 26 20:48:11 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 4MyLW06gGcz4g1g9 for ; Wed, 26 Oct 2022 20:48:28 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MyLW01nR8z45fH; Wed, 26 Oct 2022 20:48:28 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-ej1-f51.google.com with SMTP id k2so24854537ejr.2; Wed, 26 Oct 2022 13:48:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=5dTggOeEo8gcVqrFdVinElabDbbPFej6hzzA59bBK2I=; b=v+tUvM+u4bzfHy8qT9OLrOd6GFZX9Om+a+39BuMeY9+YXqvMiNNZMmaOR0nPvMB+ZM DEvu9SH/wPgJzIoiamd7oEGtVcV69144u7a7rI3fOvLLnVGKdViIJ+zRscPdQ7TV+lvw RILwF/Dnj/0iVih81aBz3br1GNNes//LTguL8W68T5WpOEPyTV2KxRuNpOtCpOq+ElvP Ewn28Af2tiNY9IiFuLuH8lkY9vDxCmzhom5N+lTZlJo5AQLQpye/FoPtMC9m8C4h0V6h yo44UL6rpSMf2NmwSX7p/98F/OqD0WmNU+I7VfW3+l62JrF5lBd1cYYeHQnDQswcYtBt FZbw== X-Gm-Message-State: ACrzQf0fNcnKbhb9zpcdNWsrx7YiZfugQVZtU8qal4Yfg0tRCPAyjA5g L6b3l9UBklovTwDbTsLdRT70h3IdjFHsxMxz+QHdCy7ueZo= X-Google-Smtp-Source: AMsMyM5cHJFmWa9qaY2ev8aeY7kVQodho5FbMEnS4Yp5wlvkJySJY+Pc+3b1yDbZaGoXvv+EDbmrN0dkFJwjthJdkQY= X-Received: by 2002:a17:906:ee81:b0:77e:829a:76e9 with SMTP id wt1-20020a170906ee8100b0077e829a76e9mr40683010ejb.207.1666817305860; Wed, 26 Oct 2022 13:48:25 -0700 (PDT) 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 References: In-Reply-To: From: Ed Maste Date: Wed, 26 Oct 2022 16:48:11 -0400 Message-ID: Subject: Re: ns8250: UART FCR is broken To: freebsd-current@freebsd.org, Colin Percival Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4MyLW01nR8z45fH X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.218.51 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-3.10 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[209.85.218.51:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.218.51:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; DMARC_NA(0.00)[freebsd.org]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Mon, 24 Oct 2022 at 22:11, void wrote: > > hello freebsd-current@, > > this started appearing in dmesg > > ns8250: UART FCR is broken > ns8250: UART FCR is broken This message was added as part of Colin's work to support FreeBSD in the Firecracker VMM https://cgit.freebsd.org/src/commit/?id=c4b68e7e53bb352be3fa16995b99764c03097e66 In this case it indicates that bhyve has the same bug/missing functionality as Firecracker -- it doesn't implement the FCR_XMT_RST or FCR_RCV_RST bits. You can safely ignore the message, and it will disappear once someone adds the required support to bhyve. We should probably also have the kernel emit the message only once. I've CC'd Colin for comment.