From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shile Zhang <shile.zhang@linux.alibaba.com>
Subject: Re: linux-next: Tree for Oct 25
Date: Thu, 28 Oct 2021 20:54:40 +0800 [thread overview]
Message-ID: <cef396ef-373d-6a02-62f2-191c440cec14@linux.alibaba.com> (raw)
In-Reply-To: <20211028234846.78e715df@canb.auug.org.au>
在 2021/10/28 下午8:48, Stephen Rothwell 写道:
> Hi Xianting,
>
> On Thu, 28 Oct 2021 15:59:02 +0800 Xianting Tian <xianting.tian@linux.alibaba.com> wrote:
>> 在 2021/10/28 下午12:51, Stephen Rothwell 写道:
>>> Hi Xianting,
>>>
>>> On Thu, 28 Oct 2021 09:51:00 +0800 Xianting Tian <xianting.tian@linux.alibaba.com> wrote:
>>>> 在 2021/10/27 下午7:42, Stephen Rothwell 写道:
>>>>> Hi all,
>>>>>
>>>>> On Mon, 25 Oct 2021 20:49:21 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>>>> There seems to be something amiss with cnosole output in today's release
>>>>>> (at least on my ppc qemu boot tests).
>>>>> The console output seems to be back today. I assume its repair had
>>>>> something to do with commit
>>>>>
>>>>> 60f41e848492 ("Revert "tty: hvc: pass DMA capable memory to put_chars()"")
>>>>> >> hi Stephen，
>>>> Thanks for the info, Could you share more details about the issue you met? is it about early console print issue?
>>>>
>>> Here is the diff between my boot logs:
>> thanks, I checked the log, Can I understand it as you missed some early bootup log when use new release?
> yes, the console messages stopped for a while when we switched from the
> bootconsole to the final hvc0 console.
thanks, it makes sense, this commit broken the early console mechanism,
I will submit the fix patch for reviewing soon.
>
>>> @@ -124,81 +124,9 @@
>>> clocksource: timebase mult[1f40000] shift[24] registered
>>> Console: colour dummy device 80x25
>>> printk: console [hvc0] enabled
>>> - printk: console [hvc0] enabled
>>> - printk: bootconsole [udbg0] disabled
>>> printk: bootconsole [udbg0] disabled
>>> - pid_max: default: 32768 minimum: 301
>>> - Mount-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
>>> - Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
> .
> .
> .
next prev parent reply other threads:[~2021-10-28 12:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 9:49 linux-next: Tree for Oct 25 Stephen Rothwell
2021-10-25 20:50 ` linux-next: Tree for Oct 25 (drivers/platform/x86/amd-pmc.c) Randy Dunlap
2021-10-25 21:29 ` Hans de Goede
2021-10-25 21:32 ` Limonciello, Mario
2021-10-26 7:55 ` Hans de Goede
2021-10-25 22:11 ` linux-next: Tree for Oct 25 Dmitry Osipenko
2021-10-26 1:28 ` Ming Lei
2021-10-26 8:40 ` Dmitry Osipenko
2021-10-26 3:20 ` linux-next: Tree for Oct 25 (bootconfig: xbc_alloc_mem()) Randy Dunlap
2021-10-26 5:11 ` Stephen Rothwell
2021-10-27 11:42 ` linux-next: Tree for Oct 25 Stephen Rothwell
2021-10-27 12:54 ` Greg Kroah-Hartman
2021-10-28 1:51 ` Xianting Tian
2021-10-28 4:51 ` Stephen Rothwell
2021-10-28 7:59 ` Xianting Tian
2021-10-28 12:48 ` Stephen Rothwell
2021-10-28 12:54 ` Xianting Tian [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-25 4:20 Stephen Rothwell
2019-10-25 5:45 Stephen Rothwell
2016-10-25 3:31 Stephen Rothwell
2016-10-26 1:09 ` Paul Gortmaker
2016-10-27 6:21 ` Daniel Vetter
2013-10-25 15:03 Thierry Reding
2013-10-25 21:01 ` Guenter Roeck
2013-10-25 22:31 ` Randy Dunlap
2013-10-26 16:59 ` Mark Brown
2013-10-28 8:01 ` Thierry Reding
2013-10-28 16:53 ` Mark Brown
2012-10-25 4:01 Stephen Rothwell
2011-10-25 9:36 Stephen Rothwell
2011-10-25 9:43 ` Stephen Rothwell
2011-10-25 10:42 ` Stephen Rothwell
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=cef396ef-373d-6a02-62f2-191c440cec14@linux.alibaba.com \
--to=xianting.tian@linux.alibaba.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shile.zhang@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).