From: Stephen Rothwell <sfr@canb.auug.org.au>
To: kernel test robot <rong.a.chen@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, LKP <lkp@01.org>
Subject: Re: [LKP] b179f0826c BUG: kernel hang in boot stage
Date: Thu, 1 Nov 2018 14:54:04 +1100 [thread overview]
Message-ID: <20181101145404.396c0973@canb.auug.org.au> (raw)
In-Reply-To: <20181101011307.GW24195@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
Hi all,
On Thu, 1 Nov 2018 09:13:07 +0800 kernel test robot <rong.a.chen@intel.com> wrote:
>
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit b179f0826c6a13563c5ce0554c6da6748a1fa699
> Author: Stephen Rothwell <sfr@canb.auug.org.au>
> AuthorDate: Mon Oct 29 16:55:21 2018 +1100
> Commit: Stephen Rothwell <sfr@canb.auug.org.au>
> CommitDate: Mon Oct 29 16:55:21 2018 +1100
>
> Add linux-next specific files for 20181029
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> a3bbfc79c4 Merge branch 'akpm/master'
> b179f0826c Add linux-next specific files for 20181029
> +------------------------------------------------+------------+---------------+
> | | a3bbfc79c4 | next-20181029 |
> +------------------------------------------------+------------+---------------+
> | boot_successes | 33 | 0 |
> | boot_failures | 2 | 30 |
> | BUG:kernel_hang_in_boot_stage | 1 | 30 |
> | IP-Config:Auto-configuration_of_network_failed | 1 | |
> +------------------------------------------------+------------+---------------+
That is really hard to believe given that the commit above only adds
documentation to the tree :-)
$ git log --stat -1 next-20181029
commit b179f0826c6a13563c5ce0554c6da6748a1fa699 (tag: next-20181029)
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon Oct 29 16:55:21 2018 +1100
Add linux-next specific files for 20181029
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Next/SHA1s | 292 +
Next/Trees | 294 +
Next/merge.log | 14253 ++++++++++++++++++++++++++++++++++++++++++++++++
Next/quilt-import.log | 2 +
localversion-next | 1 +
5 files changed, 14842 insertions(+)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-11-01 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 1:13 kernel test robot
2018-11-01 3:54 ` Stephen Rothwell [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=20181101145404.396c0973@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@01.org \
--cc=rong.a.chen@intel.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
all inboxes | Powered by JetHome®