All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [include/linux/string.h] 6974f0c455: kernel_BUG_at_lib/string.c
Date: Thu, 20 Jul 2017 22:50:52 +0800	[thread overview]
Message-ID: <20170720145052.GA18464@yexl-desktop> (raw)
In-Reply-To: <CA+55aFwuebKQ0-sAiRJWpMcaVJ8MjXvCg56DO5q8jMiPDXvc8A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

Hi, fengguang

On 07/19, Linus Torvalds wrote:
>Hmm. I wonder why the kernel test robot ends up having that annoying
>line doubling for the dmesg.
>

I found that the line doubling issue should be caused by setting
"earlyprintk=ttyS0,115200" and "console=ttyS0,115200" at the same time in
kernel parameter via debugging with `lkp qemu`, could I just omit one of them?
any side effect it may bring? or I can solve this issue by uniq the dmesg log
in report?

Thanks,
Xiaolong

  parent reply	other threads:[~2017-07-20 14:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  1:42 [lkp-robot] [include/linux/string.h] 6974f0c455: kernel_BUG_at_lib/string.c kernel test robot
2017-07-20  1:42 ` kernel test robot
2017-07-20  4:02 ` Daniel Micay
2017-07-20  4:04 ` Linus Torvalds
2017-07-20  4:04   ` Linus Torvalds
2017-07-20  4:41   ` Daniel Micay
2017-07-20 13:46   ` Masami Hiramatsu
2017-07-20 13:46     ` Masami Hiramatsu
2017-07-20 14:50   ` Ye Xiaolong [this message]
2017-07-21  1:30     ` Fengguang Wu
2017-07-21  1:52       ` Ye Xiaolong
2017-07-21  1:56         ` Fengguang Wu
2017-07-21  2:03           ` Ye Xiaolong
2017-07-20 15:51   ` Masami Hiramatsu
2017-07-20 15:51     ` Masami Hiramatsu
2017-07-20 18:41     ` Linus Torvalds
2017-07-20 18:41       ` Linus Torvalds
2017-07-20 22:20       ` Masami Hiramatsu
2017-07-20 22:20         ` Masami Hiramatsu
2017-07-21  3:29       ` Masami Hiramatsu
2017-07-21  3:29         ` Masami Hiramatsu
2017-07-21  3:29         ` Masami Hiramatsu
2017-07-21  1:59   ` Ye Xiaolong
2017-07-21  1:59     ` Ye Xiaolong
2017-07-21  5:48     ` Kees Cook
2017-07-21  5:48       ` Kees Cook
2017-07-21  9:15     ` Andy Shevchenko
2017-07-21  9:15       ` Andy Shevchenko
2017-07-21 10:03       ` Petr Mladek
2017-07-21 10:03         ` Petr Mladek
2017-07-25 23:35   ` Kees Cook
2017-07-25 23:35     ` Kees Cook
2017-07-26  0:11     ` Linus Torvalds
2017-07-26  0:11       ` Linus Torvalds
2017-07-26  0:38       ` Kees Cook
2017-07-26  0:38         ` Kees Cook
2017-07-26  2:37         ` Daniel Micay

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=20170720145052.GA18464@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.