From nobody Fri Aug 23 02:49:52 2024 X-Original-To: freebsd-stable@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 4Wql0s0sBmz5V6kR for ; Fri, 23 Aug 2024 02:50:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wql0r40MZz54LB for ; Fri, 23 Aug 2024 02:50:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-7b8884631c4so661157a12.2 for ; Thu, 22 Aug 2024 19:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1724381403; x=1724986203; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GO7GO7A/eGaCccdh5VODheZVT7vNjF9ZLOt2JwrlCUo=; b=Y3bVmBwyJrAbkYVQFe43LwccQ8rjpWW3ns1/nIuzjRirznvGTTu3aTLfyAtQh2u/G5 4EVdz02p1lvyHHpKEOwyEb2ySCbrOqRri5O+EMItrHBtvQkj4xCnXzZgflOEnYMzcVCw 0alkkBfVEUYS5fxX+KpDPwzJDn4Lf/GaMx1IgNu1O88HC/e7v9wT1aNRxDQ0+P4bjd08 rn21N18/8nbFZ4EXt7eBg76nJZCjL1jKOBnVPwxQ8f4nsAeMkIhSSxQxV7/bmFZ+OPpN foUgO4extYR/sXxYYDx0o7MMHuJGsMm1z/MZrnaZ/df37LYgSD2NOZpatASRUOvM8mNa CdaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724381403; x=1724986203; h=cc: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=GO7GO7A/eGaCccdh5VODheZVT7vNjF9ZLOt2JwrlCUo=; b=u9BzdlTFya3Owr5OXaduzrq477xjS+z1TO3LvyoWGdEByd/WWehe6bb4kJhKKqaVDt Vr3VzsKtsiaGPPoLvM/d1nQhyIoyozshaO7G8aCGOZRuHqB5H7mmen+qMBFpJD8edtpj S0891PjMODtNFDwanPWW1RAbt0mLeCz69DiWbvD0qmAa55O66R6TPW1xGYP6t/Eyp5ur gzzT9rSrpt21WWFNTewg4L13KlypHYEP8m/mCLJcPFjOCK9Zd/74ch6NWL2/LcmGKb8T qxciDeW9txcoFZYlgNELxivFRoO8hKa2fc6xeMi+C2GOuEuG3C0ML/combgEJcWXrHov ddoA== X-Gm-Message-State: AOJu0Yycd1utyARRQHtkLfcWvSeYS79JLCl6RsY+TM6e07AXOHvQjpyP ooKhWEY4ts1UAAnBIFZRvvlF0bQylhCTR0TJTLJB/jf2Ak4XrEwmhEGxsdSCr/D83ExPMhO6Fdz klRsA/kbMzyL7dS1j2SaVnMvL8nfc5XKZQH/0OBj3evkoHTFU X-Google-Smtp-Source: AGHT+IGppM78YRf768E/eCE52qkBIevd/qCQuAFyqrhoyZjdq13nTuoqnOrE3ufpbN/yyo3kv7FItF9R8gQ2HGBcQKw= X-Received: by 2002:a17:90a:9314:b0:2c8:ac1:d8c3 with SMTP id 98e67ed59e1d1-2d646d4bb42mr753105a91.29.1724381403251; Thu, 22 Aug 2024 19:50:03 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Thu, 22 Aug 2024 20:49:52 -0600 Message-ID: Subject: Re: uart device lost after upgrading 14.1 d56a912f2 to b99852587 To: KOT MATPOCKuH Cc: freebsd-stable List Content-Type: multipart/alternative; boundary="000000000000ffa1ea062050d4e0" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Wql0r40MZz54LB --000000000000ffa1ea062050d4e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 22, 2024 at 3:54=E2=80=AFAM KOT MATPOCKuH = wrote: > Hello all! > > After upgrading FreeBSD 14.1 from d56a912f2 to b99852587 system lost uart > device on my SunFire X2270 system. > Entries from dmesg.boot file BEFORE update: > uart0: at port 0x3f8 irq 4 > flags 0x1 > 0 on isa0 > uart0: console (9600,n,8,1) > > What happened? How can I return my serial console to working state? > I believe that kib@ is correct. on isa0 is a good hint that we're attaching with the old hints. I think we should add an entry about this to the release notes for the next 14.x release. > On the updated system I do not have these entries, also I have NO ttyu0 > devices that were used as console. > I'm using stable/14 git's branch. > There were no changes in the kernel configuration file. > I do not have this problem on other systems, including different Sun's > servers, but this servers using different chipset. For example log entrie= s > from SunFire X4200: > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > ns8250: UART FCR is broken > uart0: console (9600,n,8,1) > Yea, ACPI on the newer system has these uarts listed. On the other systems not so much. The X2270 was released 2009 or 2010, which is new enough I'd expect it to have ACPI and have the serial ports in its AML.... Warner --000000000000ffa1ea062050d4e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Aug 22, 2024 at 3:54=E2=80=AF= AM KOT MATPOCKuH <matpockuh@gmail= .com> wrote:
Hello all!

After upgrading Free= BSD 14.1 from d56a912f2 to b99852587 system lost uart device on my SunFire = X2270 system.
Entries from dmesg.boot file BEFORE update:
=
uart0: <Non-standard ns8250 class UART with FIFOs> at port= 0x3f8 irq 4 flags 0x1
0 on isa0
uart0: console (9600,n,8,1)

What happened? How can I return my serial console= to working state?

I beli= eve that kib@ is correct. on isa0 is a good hint that we're attaching w= ith the old hints.

I think we should add an entry = about this to the release notes for the next 14.x release.
=C2=A0=
On the updated system I do not have these entries, also I have NO t= tyu0 devices that were used as console.
I'm using stable/14 g= it's branch.
There were no changes in the kernel configuratio= n file.
I do not have this problem on other systems, including di= fferent Sun's servers, but this servers using different chipset. For ex= ample log entries from SunFire X4200:
uart0: <16550 or com= patible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ns8250: UART FCR = is broken
uart0: console (9600,n,8,1)

Yea, ACPI on the newer system has these uarts listed. On th= e other systems not so much.

The=C2=A0X2270 was=C2= =A0released 2009 or 2010, which is new enough I'd expect it to have ACP= I and have the serial ports in its AML....

Warner<= /div>
--000000000000ffa1ea062050d4e0--