From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: Build failures and crashes in stable queues (3.19, 4.19, 5.0)
Date: Thu, 21 Mar 2019 11:20:55 -0700 [thread overview]
Message-ID: <20190321182055.GA20453@roeck-us.net> (raw)
In-Reply-To: <20190321173245.GA5882@kroah.com>
On Thu, Mar 21, 2019 at 06:32:45PM +0100, Greg Kroah-Hartman wrote:
> > Want me to bisect ?
>
> That would be great, and save me a lot of time if you can do that,
> thanks!
>
See below. The problem is fixed with upstream commit 86a86804e4f18
("s390/setup: fix boot crash for machine without EDAT-1").
Note that 4.14.y is also affected.
Guenter
---
# bad: [4107be0fa04a568e3b3651726a4d7c4c82616ac7] Linux 4.19.31-rc1
# good: [7794d352260604f02e7d446e632af2ca7fe8dda6] Linux 4.19.30
git bisect start 'HEAD' 'v4.19.30'
# good: [49c97d9d99af8e5dcead8d5efb954c53d400c908] net: thunderx: add nicvf_send_msg_to_pf result check for set_rx_mode_task
git bisect good 49c97d9d99af8e5dcead8d5efb954c53d400c908
# bad: [39e29428ac0926122fcfe1e09a738587b6f7b5be] s390/virtio: handle find on invalid queue gracefully
git bisect bad 39e29428ac0926122fcfe1e09a738587b6f7b5be
# good: [a6300398ee44af9372c2568671fa1c34620df84a] crypto: skcipher - set CRYPTO_TFM_NEED_KEY if ->setkey() fails
git bisect good a6300398ee44af9372c2568671fa1c34620df84a
# good: [f003b3e4226914799108471ec497bbd7c27637bd] xen: fix dom0 boot on huge systems
git bisect good f003b3e4226914799108471ec497bbd7c27637bd
# good: [5b0eb946afb2233cc320cb28b50f9dbb64fd1593] regulator: s2mps11: Fix steps for buck7, buck8 and LDO35
git bisect good 5b0eb946afb2233cc320cb28b50f9dbb64fd1593
# good: [fb46b8117ab8ca280eafd754cafe98a5977cb831] clocksource/drivers/exynos_mct: Move one-shot check from tick clear to ISR
git bisect good fb46b8117ab8ca280eafd754cafe98a5977cb831
# good: [fc191b16f180cd2f05113102c97fc03a4ce98018] clocksource/drivers/arch_timer: Workaround for Allwinner A64 timer instability
git bisect good fc191b16f180cd2f05113102c97fc03a4ce98018
# bad: [66dd19a676b2d2c0679a45d6745561bc11edf9f2] s390/setup: fix early warning messages
git bisect bad 66dd19a676b2d2c0679a45d6745561bc11edf9f2
# first bad commit: [66dd19a676b2d2c0679a45d6745561bc11edf9f2] s390/setup: fix early warning messages
next prev parent reply other threads:[~2019-03-21 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 16:16 Build failures and crashes in stable queues (3.19, 4.19, 5.0) Guenter Roeck
2019-03-21 16:47 ` Greg Kroah-Hartman
2019-03-21 16:49 ` Greg Kroah-Hartman
2019-03-21 17:38 ` Guenter Roeck
2019-03-21 18:32 ` Greg Kroah-Hartman
2019-03-21 16:50 ` Greg Kroah-Hartman
2019-03-21 17:28 ` Guenter Roeck
2019-03-21 17:32 ` Greg Kroah-Hartman
2019-03-21 17:52 ` Guenter Roeck
2019-03-21 18:20 ` Guenter Roeck [this message]
2019-03-22 11:08 ` Greg Kroah-Hartman
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=20190321182055.GA20453@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).