From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org, LKP <lkp@01.org>
Subject: Re: [LKP] bea5b158ff BUG: kernel reboot-without-warning in boot-around-mounting-root stage
Date: Wed, 2 Jan 2019 10:58:44 +0100 [thread overview]
Message-ID: <20190102095844.GB14448@kroah.com> (raw)
In-Reply-To: <20190102011512.GF17624@shao2-debian>
On Wed, Jan 02, 2019 at 09:15:12AM +0800, kernel test robot 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/torvalds/linux.git master
>
> commit bea5b158ff0da9c7246ff391f754f5f38e34577a
> Author: Rob Herring <robh@kernel.org>
> AuthorDate: Thu Aug 11 10:20:58 2016 -0500
> Commit: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> CommitDate: Wed Aug 31 15:13:55 2016 +0200
>
> driver core: add test of driver remove calls during probe
>
> In recent discussions on ksummit-discuss[1], it was suggested to do a
> sequence of probe, remove, probe for testing driver remove paths. This
> adds a kconfig option for said test.
>
> [1] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-August/003459.html
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> cebf8fd169 driver core: fix race between creating/querying glue dir and its cleanup
> bea5b158ff driver core: add test of driver remove calls during probe
> e1ef035d27 Merge tag 'armsoc-defconfig' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
> 6a1d293238 Add linux-next specific files for 20181224
> +----------------------------------------------------------------------+------------+------------+------------+---------------+
> | | cebf8fd169 | bea5b158ff | e1ef035d27 | next-20181224 |
> +----------------------------------------------------------------------+------------+------------+------------+---------------+
> | boot_successes | 31 | 0 | 0 | 0 |
> | boot_failures | 0 | 11 | 11 | 7 |
> | BUG:kernel_reboot-without-warning_in_boot-around-mounting-root_stage | 0 | 11 | 11 | 7 |
> +----------------------------------------------------------------------+------------+------------+------------+---------------+
>
> [ 14.073515] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
> [ 14.095297] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> [ 14.177113] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
> [ 14.256672] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
> [ 14.278578] console [ttyS0] disabled
> BUG: kernel reboot-without-warning in boot-around-mounting-root stage
>
>
> # HH:MM RESULT GOOD BAD GOOD_BUT_DIRTY DIRTY_NOT_BAD
> git bisect start v4.9 v4.8 --
You are testing the 4.9 kernel release here?
A commit from 2016 is a "problem"? Are you sure this is still an issue?
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-02 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 1:15 kernel test robot
2019-01-02 9:58 ` Greg Kroah-Hartman [this message]
2019-01-03 0:44 ` Rong Chen
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=20190102095844.GB14448@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=robh@kernel.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®