From: Meelis Roos <mroos@ut.ee>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 4.18-rc* regression: x86-32 troubles (with timers?)
Date: Mon, 16 Jul 2018 22:00:41 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1807162200180.27791@math.ut.ee> (raw)
In-Reply-To: <alpine.LRH.2.21.1807161948380.27791@math.ut.ee>
> > Everything below here is is 'bad', which can be an indication that you
> > misclassified one of
> > the commits above as 'good' when it should have been 'bad'. The most likely
> > explanations are that you either typed the 'git bisect good' by accident, or
> > that the failure is not 100% reliable, and it sometimes works fine even on a
> > broken kernel.
> >
> > 0bc5fe857274133ca0 follows directly after 3a443bd6dd7c, "net/9p: correct the
> > variable name in v9fs_get_trans_by_name() comment", which is marked "good",
> > and can't really be good if 0bc5fe85727413 is bad and you are not using the
> > 'qed' driver.
> >
> > I'd retest 3a443bd6dd7c again to see if that should have been 'bad', and
> > if it was, test v4.17-rc4, which is what the net-next tree was based on.
>
> Yes, the same prebuilt 3a443bd6dd7c appeared to be bad when retesting
> it. Building v4.17-rc4 now.
v4.17-rc4 seems good after 2 reboots.
--
Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/
next prev parent reply other threads:[~2018-07-16 19:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 11:41 Meelis Roos
2018-07-04 21:02 ` Arnd Bergmann
2018-07-05 9:54 ` Meelis Roos
2018-07-05 11:04 ` Arnd Bergmann
2018-07-15 15:05 ` Meelis Roos
2018-07-15 20:51 ` Arnd Bergmann
2018-07-16 16:49 ` Meelis Roos
2018-07-16 19:00 ` Meelis Roos [this message]
2018-07-20 20:56 ` Meelis Roos
2018-07-20 23:01 ` bisected: " Meelis Roos
2018-07-23 16:03 ` Arnd Bergmann
2018-07-23 19:41 ` Daniel Borkmann
2018-07-23 20:34 ` Meelis Roos
2018-07-23 22:04 ` Daniel Borkmann
2018-07-24 4:47 ` Meelis Roos
2018-07-24 18:40 ` Daniel Borkmann
2018-07-24 6:11 ` Meelis Roos
2018-07-10 9:30 ` Pavel Machek
2018-07-10 9:32 ` Pavel Machek
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=alpine.LRH.2.21.1807162200180.27791@math.ut.ee \
--to=mroos@ut.ee \
--cc=arnd@arndb.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®