mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Non-working serial console
Date: Sat, 4 Jun 2022 11:21:12 +0200	[thread overview]
Message-ID: <477007d7-e573-56dd-90de-877eeebd5c4c@molgen.mpg.de> (raw)
In-Reply-To: <YpsgHpRfz0JQcm9D@kroah.com>

Dear Greg,


Am 04.06.22 um 11:04 schrieb Greg KH:
> On Thu, Jun 02, 2022 at 11:09:15PM +0200, Paul Menzel wrote:

>> Am 02.06.22 um 18:50 schrieb Paul Menzel:
>>
>>> Since a while I noticed, output to the serial console with
>>> `console=ttyS0,115200n8` does not work with the attached configuration
>>> `defconfig-non-working-serial.txt` created by `make savedefconfig`.
>>> Only, when with `earlyprintk=ttyS0,115200,keep` the serial console
>>> starts working. I am able to reproduce it in QEMU. It’s reproducible
>>> with Linus’ latest master branch.
>>>
>>>       $ git log --oneline --no-decorate -1
>>>       8ab2afa23bd19 Merge tag 'for-5.19/fbdev-1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev
>>>       $ qemu-system-x86_64 --version
>>>       QEMU emulator version 5.1.0
>>>       Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
>>>       $ qemu-system-x86_64 -kernel arch/x86/boot/bzImage -append "console=ttyS0,115200n8" -serial file:/dev/shm/kernel.txt -curses
>>>
>>> With `earlyprintk=` it works:
>>>
>>>       $ qemu-system-x86_64 -kernel arch/x86/boot/bzImage -append "earlyprintk=serial console=ttyS0,115200n8" -serial file:/dev/shm/kernel.txt -curses
>>>
>>> Strangely, I found a different configuration, where it works, but I
>>> didn’t see what configuration option makes the difference.
>>>
>>> Can you reproduce the problem with `defconfig-no-working-serial.txt`?
>>
>> It turns out, the non-working configuration build the serial 8250 driver as
>> a module (`CONFIG_SERIAL_8250=m`) instead of building it into the Linux
>> kernel. Building it into the Linux kernel and using
>> `CONFIG_SERIAL_8250_CONSOLE=y` fixes my issue.
> 
> That makes sense, you need the console to be able to properly send data
> out to it :)

Indeed.

I am still confused, that `earlyprintk=ttyS0,115200,keep` works though 
despite `CONFIG_SERIAL_8250=m`. Doesn’t that mean, that Linux 
nevertheless contains some code to initialize the serial console, and 
send data to it?

> Was this a Kconfig change somewhere recently that we messed up the
> defaults for?  Any chance you can use 'git bisect' to track down the
> offending change?

No, I guess I made the change several months back to make the Linux 
kernel image smaller to decrease the boot time. (I have to do 
measurements again.)


Kind regards,

Paul

  reply	other threads:[~2022-06-04  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 16:50 Paul Menzel
2022-06-02 21:09 ` Paul Menzel
2022-06-04  9:04   ` Greg KH
2022-06-04  9:21     ` Paul Menzel [this message]
2022-06-06 14:31       ` Andy Shevchenko

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=477007d7-e573-56dd-90de-877eeebd5c4c@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®