The reverse bisect from 4.3 to 4.4-rc1 shows the bug was "fixed" in
d55fc37, "Pull i2c updates from Wolfram Sang". That seems unrelated to
the bad commit identified in 4.2.6 (0691783, "NFSv4.1: Fix a protocol
issue with CLOSE stateids"), so either I botched the bisect or there
might be something m
Actually, I did both reverse and forward bisects (see comments 11 and 12
respectively), but by reverse bisect didn't find the fix because the
problem commit, 0691783, is a cherry pick of 4a1e2fe from the 4.3
branch.
After locating the original commit I tested all the 4.3 releases and
found they a
Stephen, to advise, what you did was a reverse (not forward) bisect.
Despite this, let this be marked Triaged for now, and the expectation
would be that the identified commit is reviewed for backporting.
** Tags removed: needs-reverse-bisect
** Tags added: cherry-pick reverse-bisect-done
** Chan
I went ahead and did the forward bisect, here's the final step:
$ git bisect good
0691783adb950a3839cc2bae5117c30e48c89539 is the first bad commit
commit 0691783adb950a3839cc2bae5117c30e48c89539
Author: Trond Myklebust
Date: Sun Aug 30 18:37:59 2015 -0700
NFSv4.1: Fix a protocol issue wit
Here are the results of the reverse bisect:
$ git bisect start
$ git bisect bad v4.4-rc6
$ git bisect good v4.2.6
Bisecting: a merge base must be tested
[64291f7db5bd8150a74ad2036f1037e6a0428df2] Linux 4.2
$ cp /boot/config-4.2.0-22-generic .config
$ make oldconfig
$ make clean
$ time make
I see. The lack of 4.2.x tags in Linus's repo combined with the Ubuntu
naming scheme (4.2.0-22) made me think it was still based on 4.2. I now
have the linux-stable repo, and 4.2.6 does reproduce the problem. I'll
start bisecting now, but at 90 minutes per build, it won't be fast...
>From a doc
Stephen, given the Ubuntu kernel first reported maps to upstream 4.2.6,
you would want to test that first to confirm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529266
Title:
[HP Spectre x360 -
Before starting the reverse bisect I built v4.2 from kernel.org, and it
does not reproduce the bug. I'm guessing I should try the Ubuntu kernel
repository next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Stephen, the next step is to fully reverse commit bisect from kernel 4.2
to 4.4-rc6 in order to identify the last bad commit, followed
immediately by the first good one. Once this commit has been identified,
then it may be reviewed as a candidate for backporting into your
release. Could you please
Ah, sorry about the out of date bios. Updating did not change the
behavior at all. Unfortunately dmidecode fails on my machine:
scbash@aveline:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for scbash:
/dev/mem: Operation not permitted
scbash@aveline:~
10 matches
Mail list logo
