public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fushuai Wang <fushuai.wang@linux.dev>
To: andy.shevchenko@gmail.com
Cc: fushuai.wang@linux.dev, gregkh@linuxfoundation.org,
	ilpo.jarvinen@linux.intel.com, jirislaby@kernel.org,
	kees@kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, osama.abdelkader@gmail.com,
	wangfushuai@baidu.com
Subject: Re: [PATCH] serial: 8250: Clear CON_PRINTBUFFER on port re-registration
Date: Thu, 16 Apr 2026 19:32:00 +0800	[thread overview]
Message-ID: <20260416113200.38244-1-fushuai.wang@linux.dev> (raw)
In-Reply-To: <CAHp75Vc7sdDT+nWZX7u7aSsUhUquYNAiYo9HrxHhjXnGz5g55Q@mail.gmail.com>

>> >> When two PnP devices map to the same physical port, the serial8250 driver
>> >> removes and re-registers the console structure for the same port.
>> >
>> > Is it a real device out of there? Can you share what that is?
>>
>> Yes, it's a real device.
>> In my Intel(R) Xeon(R) 6971P-C machine, the boot log shows:
>>         [   17.242984] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
>>         [   17.251352] printk: console [ttyS0] disabled
>
>>         [   17.257934] serial 00:04: Runtime PM usage count underflow!
>
> This is strange, what kernel version is this?

Please ingore this. I just test the patch in kernel 6.6. And this log
has nothing to do with this problem. It was fixed in patch ed2761958ad7
("tty: serial: 8250: Fix another runtime PM usage counter underflow").

>
>>         [   17.258360] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
>>         [   17.258516] printk: console [ttyS0] enabled
>>         [   29.643013] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
>>
>> The issue occurs when BIOS "Serial Device" option is set to BMC:
>>           Setup Question  = Serial Device
>>           Help String     = Sets the Serial Device used to output bios serial log
>>           Token   = 9003   // Do NOT change this line
>>           Offset  = 2F8
>
> Is it an IO port?

No, Offset = 2F8 is the offset in BIOS configuration space, not the I/O port.

>>           Width   = 01
>>           BIOS Default =[01]BMC
>>           Options = *[01]BMC       // Move "*" to desired Option
>>                     [02]S3M
>>
>> So 00:05 may be the BMC serial port device. From ACPI paths:
>>         /sys/bus/pnp/devices/00:04/firmware_node/path: \_SB_.LPC0.UAR1
>>         /sys/bus/pnp/devices/00:05/firmware_node/path: \_SB_.UAR1
>
> Do I understand correctly that both devices refer to the same physical
> device?! How on earth is it supposed to work?

Not exactly the same physical device, but they map to the same I/O port (0x3f8).
They are different PnP devices with different ACPI paths:

  00:04: \_SB_.LPC0.UAR1  (LPC COM1)
  00:05: \_SB_.UAR1       (BMC serial port)

When BIOS "Serial Device" option is set to BMC, both 00:04 and 00:05 are mapped to
the same physical I/O port 0x3f8. And then:

  1.00:04 is probed first and registers the console for port 0x3f8
  2.00:05 is detected and also needs to use port 0x3f8
  3.Since port 0x3f8 is already in use, the driver must remove 00:04 first before
    adding 00:05
  4.This process involves console re-registration, which causes the entire 
    log buffer to be reprinted

Sorry if my explanation is not clear - I don't work with serial subsystem often. :-)

-- 
Regards,
WANG

  reply	other threads:[~2026-04-16 11:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16  9:29 [PATCH] serial: 8250: Clear CON_PRINTBUFFER on port re-registration Fushuai Wang
2026-04-16  9:40 ` Andy Shevchenko
2026-04-16 10:02   ` Fushuai Wang
2026-04-16 10:15     ` Andy Shevchenko
2026-04-16 11:32       ` Fushuai Wang [this message]
2026-04-16 18:30         ` Andy Shevchenko
2026-04-17  4:00           ` Fushuai Wang

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=20260416113200.38244-1-fushuai.wang@linux.dev \
    --to=fushuai.wang@linux.dev \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=osama.abdelkader@gmail.com \
    --cc=wangfushuai@baidu.com \
    /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