public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Forest <forestix@gaga.casa>
Cc: linux-serial@vger.kernel.org
Subject: Re: Seeking help diagnosing serial port failure to transmit (while receive works)
Date: Tue, 24 Feb 2026 01:39:06 +0100	[thread overview]
Message-ID: <2026022418-stellar-overwrite-bf17@gregkh> (raw)
In-Reply-To: <7imppktb51fdnlm8jaovts1tkhr6r1751c@sonic.net>

On Mon, Feb 23, 2026 at 03:19:03PM -0800, Forest wrote:
> Hi, folks.
> 
> I'm seeing puzzling behavior from a recent AMD motherboard serial port:
> It receives data, but doesn't appear to send, and doesn't report any
> errors. Does this problem ring a bell for anyone here?
> 
> dmesg reports this:
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
> 
> The /proc/tty/driver/serial tx count rises as I type in picocom, but the
> terminal at the other end of a null-modem cable (a laptop with a
> USB/serial adapter) doesn't see the typed characters. The other
> direction of the same connection works just fine.
> 
> Things that have not helped:
> - Replacing the motherboard's cables and connectors
> - Replacing the null modem adapter with a different model
> - Replacing the remote USB/serial adapter with a different model
> - Switching picocom's flow control between RTS/CTS, xon/xoff, none
> - Changing the serial port's IRQ and address in the BIOS
> - Changing between 9600 and 115200 bps
> 
> I'm approaching my wit's end. Could this be a known problem with the
> kernel's serial driver and the B650 chipset (socket AM5), or with recent
> AGESA versions?

Based on experience, it's always flow control being set somewhere (on
one side or the other), so watch out for that.

good luck!

greg k-h

      reply	other threads:[~2026-02-24  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 23:19 Seeking help diagnosing serial port failure to transmit (while receive works) Forest
2026-02-24  0:39 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026022418-stellar-overwrite-bf17@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=forestix@gaga.casa \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox