* [linux-3.18 bisection] complete test-amd64-amd64-xl
@ 2019-05-19 19:24 ` osstest service owner
0 siblings, 0 replies; 19+ messages in thread
From: osstest service owner @ 2019-05-19 19:24 UTC (permalink / raw)
To: xen-devel, osstest-admin
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
(Revision log too long, omitted.)
For bisection revision-tuple graph see:
http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.html
Revision IDs in each graph node refer, respectively, to the Trees above.
----------------------------------------
Running cs-bisection-step --graph-out=/home/logs/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot --summary-out=tmp/136574.bisection-summary --basis-template=128858 --blessings=real,real-bisect linux-3.18 test-amd64-amd64-xl xen-boot
Searching for failure / basis pass:
136390 fail [host=debina1] / 132456 [host=godello1] 131535 [host=godello0] 131512 [host=rimava1] 131479 [host=godello1] 131442 [host=huxelrebe0] 131420 [host=baroque1] 131370 [host=italia0] 131336 [host=fiano0] 131307 [host=albana0] 131279 [host=huxelrebe1] 131231 [host=joubertin0] 131192 [host=godello0] 131149 [host=rimava1] 131095 [host=godello1] 131035 [host=baroque1] 130939 [host=italia0] 130876 [host=albana0] 130843 [host=chardonnay0] 130367 [host=fiano0] 130203 [host=elbling0] 130067 [hos\
t=godello1] 129845 [host=albana1] 129760 [host=joubertin0] 128858 [host=godello1] 128841 [host=baroque1] 128807 [host=chardonnay1] 128691 [host=chardonnay0] 128258 [host=baroque0] 128232 [host=albana0] 128177 [host=pinot1] 128096 [host=elbling1] 127486 [host=godello0] 127472 [host=joubertin0] 127455 [host=joubertin1] 127296 ok.
Failure / basis pass flights: 136390 / 127296
(tree with no url: minios)
(tree with no url: seabios)
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
Basis pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
Generating revisions with ./adhoc-revtuple-generator git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git#ba6984fc0162f24a510ebc34e881b546b69c553b-6b1ae527b1fdee86e81da0cb26ced75731c6c0fa git://xenbits.xen.org/osstest/linux-firmware.git#c530a75c1e6a472b0eb9558310b518f0dfcd8860-c530a75c1e6a472b0eb9558310b518f0dfcd8860 git://xenbits.xen.org/osstest/ovmf.git#ef529e6ab7c31290a33045bb1f1837447cc0eb56-96ef5a8e30a8da33eaab09f13cc8d752342717a5 git://xenbits.xen.org/qemu-xen-traditional\
.git#9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149-d0d8ad39ecb51cd7497cd524484fe09f50876798 git://xenbits.xen.org/qemu-xen.git#de5b678ca4dcdfa83e322491d478d66df56c1986-9cca02d8ffc23e9688a971d858e4ffdff5389b11 git://xenbits.xen.org/xen.git#9f3fd3d339b42a632ccc1c5fff218d1d19a69f01-e83077a3d11072708a5c38fa09fa9d011914e2a1
adhoc-revtuple-generator: tree discontiguous: linux-stable
adhoc-revtuple-generator: tree discontiguous: ovmf
adhoc-revtuple-generator: tree discontiguous: qemu-xen
adhoc-revtuple-generator: tree discontiguous: xen
Loaded 1008 nodes in revision graph
Searching for test results:
126472 [host=joubertin1]
126583 [host=joubertin1]
126711 [host=joubertin1]
126813 [host=joubertin1]
126926 [host=fiano0]
127001 [host=fiano0]
127296 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
127486 [host=godello0]
127472 [host=joubertin0]
127455 [host=joubertin1]
128096 [host=elbling1]
128177 [host=pinot1]
128232 [host=albana0]
128258 [host=baroque0]
128691 [host=chardonnay0]
128807 [host=chardonnay1]
128858 [host=godello1]
128841 [host=baroque1]
129760 [host=joubertin0]
129845 [host=albana1]
130067 [host=godello1]
130203 [host=elbling0]
130367 [host=fiano0]
130843 [host=chardonnay0]
130876 [host=albana0]
130939 [host=italia0]
131095 [host=godello1]
131035 [host=baroque1]
131149 [host=rimava1]
131192 [host=godello0]
131279 [host=huxelrebe1]
131231 [host=joubertin0]
131307 [host=albana0]
131336 [host=fiano0]
131420 [host=baroque1]
131370 [host=italia0]
131442 [host=huxelrebe0]
131479 [host=godello1]
131512 [host=rimava1]
131535 [host=godello0]
131563 fail irrelevant
131580 fail irrelevant
131593 fail irrelevant
131641 fail irrelevant
131619 fail irrelevant
131666 fail irrelevant
131673 fail irrelevant
131705 fail irrelevant
131749 fail irrelevant
131729 fail irrelevant
131769 fail irrelevant
131990 fail irrelevant
131969 fail irrelevant
132066 fail irrelevant
132179 fail irrelevant
132290 fail irrelevant
132408 fail irrelevant
132456 [host=godello1]
132579 fail irrelevant
132652 fail irrelevant
132741 fail irrelevant
132798 fail irrelevant
132984 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
132991 blocked irrelevant
132989 fail irrelevant
132969 fail irrelevant
132985 fail irrelevant
132988 pass irrelevant
132993 blocked irrelevant
132994 blocked irrelevant
132996 fail irrelevant
132998 pass irrelevant
133000 fail irrelevant
133001 fail irrelevant
133002 pass irrelevant
133003 fail irrelevant
133004 fail irrelevant
133006 fail irrelevant
133007 pass irrelevant
133008 pass irrelevant
133009 pass irrelevant
133275 fail irrelevant
133288 fail irrelevant
133464 fail irrelevant
133499 fail irrelevant
133565 fail irrelevant
133539 fail irrelevant
133630 fail irrelevant
133577 fail irrelevant
133671 fail irrelevant
133693 fail irrelevant
133774 fail irrelevant
133736 fail irrelevant
133819 fail irrelevant
133856 fail irrelevant
133891 fail irrelevant
133918 fail irrelevant
133953 fail irrelevant
134758 fail irrelevant
134917 fail irrelevant
135000 fail irrelevant
135113 fail irrelevant
135441 fail irrelevant
135538 fail irrelevant
135739 fail irrelevant
135872 fail irrelevant
135981 fail irrelevant
136089 fail irrelevant
136220 fail irrelevant
136390 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136560 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136574 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136549 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
136551 fail irrelevant
136563 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136569 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136554 fail irrelevant
136570 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136556 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 d0d8ad39ecb51cd7497cd524484fe09f50876798 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
136558 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136571 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136572 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
Searching for interesting versions
Result found: flight 127296 (pass), for basis pass
Result found: flight 136390 (fail), for basis failure
Repro found: flight 136549 (pass), for basis pass
Repro found: flight 136558 (fail), for basis failure
0 revisions at ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
No revisions left to test, checking graph state.
Result found: flight 136563 (pass), for last pass
Result found: flight 136569 (fail), for first failure
Repro found: flight 136570 (pass), for last pass
Repro found: flight 136571 (fail), for first failure
Repro found: flight 136572 (pass), for last pass
Repro found: flight 136574 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
(Revision log too long, omitted.)
Revision graph left in /home/logs/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.{dot,ps,png,html,svg}.
----------------------------------------
136574: tolerable ALL FAIL
flight 136574 linux-3.18 real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/136574/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
test-amd64-amd64-xl 7 xen-boot fail baseline untested
jobs:
test-amd64-amd64-xl fail
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* [Xen-devel] [linux-3.18 bisection] complete test-amd64-amd64-xl
@ 2019-05-19 19:24 ` osstest service owner
0 siblings, 0 replies; 19+ messages in thread
From: osstest service owner @ 2019-05-19 19:24 UTC (permalink / raw)
To: xen-devel, osstest-admin
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
(Revision log too long, omitted.)
For bisection revision-tuple graph see:
http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.html
Revision IDs in each graph node refer, respectively, to the Trees above.
----------------------------------------
Running cs-bisection-step --graph-out=/home/logs/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot --summary-out=tmp/136574.bisection-summary --basis-template=128858 --blessings=real,real-bisect linux-3.18 test-amd64-amd64-xl xen-boot
Searching for failure / basis pass:
136390 fail [host=debina1] / 132456 [host=godello1] 131535 [host=godello0] 131512 [host=rimava1] 131479 [host=godello1] 131442 [host=huxelrebe0] 131420 [host=baroque1] 131370 [host=italia0] 131336 [host=fiano0] 131307 [host=albana0] 131279 [host=huxelrebe1] 131231 [host=joubertin0] 131192 [host=godello0] 131149 [host=rimava1] 131095 [host=godello1] 131035 [host=baroque1] 130939 [host=italia0] 130876 [host=albana0] 130843 [host=chardonnay0] 130367 [host=fiano0] 130203 [host=elbling0] 130067 [hos\
t=godello1] 129845 [host=albana1] 129760 [host=joubertin0] 128858 [host=godello1] 128841 [host=baroque1] 128807 [host=chardonnay1] 128691 [host=chardonnay0] 128258 [host=baroque0] 128232 [host=albana0] 128177 [host=pinot1] 128096 [host=elbling1] 127486 [host=godello0] 127472 [host=joubertin0] 127455 [host=joubertin1] 127296 ok.
Failure / basis pass flights: 136390 / 127296
(tree with no url: minios)
(tree with no url: seabios)
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
Basis pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
Generating revisions with ./adhoc-revtuple-generator git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git#ba6984fc0162f24a510ebc34e881b546b69c553b-6b1ae527b1fdee86e81da0cb26ced75731c6c0fa git://xenbits.xen.org/osstest/linux-firmware.git#c530a75c1e6a472b0eb9558310b518f0dfcd8860-c530a75c1e6a472b0eb9558310b518f0dfcd8860 git://xenbits.xen.org/osstest/ovmf.git#ef529e6ab7c31290a33045bb1f1837447cc0eb56-96ef5a8e30a8da33eaab09f13cc8d752342717a5 git://xenbits.xen.org/qemu-xen-traditional\
.git#9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149-d0d8ad39ecb51cd7497cd524484fe09f50876798 git://xenbits.xen.org/qemu-xen.git#de5b678ca4dcdfa83e322491d478d66df56c1986-9cca02d8ffc23e9688a971d858e4ffdff5389b11 git://xenbits.xen.org/xen.git#9f3fd3d339b42a632ccc1c5fff218d1d19a69f01-e83077a3d11072708a5c38fa09fa9d011914e2a1
adhoc-revtuple-generator: tree discontiguous: linux-stable
adhoc-revtuple-generator: tree discontiguous: ovmf
adhoc-revtuple-generator: tree discontiguous: qemu-xen
adhoc-revtuple-generator: tree discontiguous: xen
Loaded 1008 nodes in revision graph
Searching for test results:
126472 [host=joubertin1]
126583 [host=joubertin1]
126711 [host=joubertin1]
126813 [host=joubertin1]
126926 [host=fiano0]
127001 [host=fiano0]
127296 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
127486 [host=godello0]
127472 [host=joubertin0]
127455 [host=joubertin1]
128096 [host=elbling1]
128177 [host=pinot1]
128232 [host=albana0]
128258 [host=baroque0]
128691 [host=chardonnay0]
128807 [host=chardonnay1]
128858 [host=godello1]
128841 [host=baroque1]
129760 [host=joubertin0]
129845 [host=albana1]
130067 [host=godello1]
130203 [host=elbling0]
130367 [host=fiano0]
130843 [host=chardonnay0]
130876 [host=albana0]
130939 [host=italia0]
131095 [host=godello1]
131035 [host=baroque1]
131149 [host=rimava1]
131192 [host=godello0]
131279 [host=huxelrebe1]
131231 [host=joubertin0]
131307 [host=albana0]
131336 [host=fiano0]
131420 [host=baroque1]
131370 [host=italia0]
131442 [host=huxelrebe0]
131479 [host=godello1]
131512 [host=rimava1]
131535 [host=godello0]
131563 fail irrelevant
131580 fail irrelevant
131593 fail irrelevant
131641 fail irrelevant
131619 fail irrelevant
131666 fail irrelevant
131673 fail irrelevant
131705 fail irrelevant
131749 fail irrelevant
131729 fail irrelevant
131769 fail irrelevant
131990 fail irrelevant
131969 fail irrelevant
132066 fail irrelevant
132179 fail irrelevant
132290 fail irrelevant
132408 fail irrelevant
132456 [host=godello1]
132579 fail irrelevant
132652 fail irrelevant
132741 fail irrelevant
132798 fail irrelevant
132984 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
132991 blocked irrelevant
132989 fail irrelevant
132969 fail irrelevant
132985 fail irrelevant
132988 pass irrelevant
132993 blocked irrelevant
132994 blocked irrelevant
132996 fail irrelevant
132998 pass irrelevant
133000 fail irrelevant
133001 fail irrelevant
133002 pass irrelevant
133003 fail irrelevant
133004 fail irrelevant
133006 fail irrelevant
133007 pass irrelevant
133008 pass irrelevant
133009 pass irrelevant
133275 fail irrelevant
133288 fail irrelevant
133464 fail irrelevant
133499 fail irrelevant
133565 fail irrelevant
133539 fail irrelevant
133630 fail irrelevant
133577 fail irrelevant
133671 fail irrelevant
133693 fail irrelevant
133774 fail irrelevant
133736 fail irrelevant
133819 fail irrelevant
133856 fail irrelevant
133891 fail irrelevant
133918 fail irrelevant
133953 fail irrelevant
134758 fail irrelevant
134917 fail irrelevant
135000 fail irrelevant
135113 fail irrelevant
135441 fail irrelevant
135538 fail irrelevant
135739 fail irrelevant
135872 fail irrelevant
135981 fail irrelevant
136089 fail irrelevant
136220 fail irrelevant
136390 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136560 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136574 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136549 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 9c0eed618f37dd5b4a57c8b3fbc48ef8913e3149 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
136551 fail irrelevant
136563 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136569 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136554 fail irrelevant
136570 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136556 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 ef529e6ab7c31290a33045bb1f1837447cc0eb56 d0d8ad39ecb51cd7497cd524484fe09f50876798 de5b678ca4dcdfa83e322491d478d66df56c1986 9f3fd3d339b42a632ccc1c5fff218d1d19a69f01
136558 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136571 fail 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
136572 pass ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
Searching for interesting versions
Result found: flight 127296 (pass), for basis pass
Result found: flight 136390 (fail), for basis failure
Repro found: flight 136549 (pass), for basis pass
Repro found: flight 136558 (fail), for basis failure
0 revisions at ba6984fc0162f24a510ebc34e881b546b69c553b c530a75c1e6a472b0eb9558310b518f0dfcd8860 96ef5a8e30a8da33eaab09f13cc8d752342717a5 d0d8ad39ecb51cd7497cd524484fe09f50876798 9cca02d8ffc23e9688a971d858e4ffdff5389b11 e83077a3d11072708a5c38fa09fa9d011914e2a1
No revisions left to test, checking graph state.
Result found: flight 136563 (pass), for last pass
Result found: flight 136569 (fail), for first failure
Repro found: flight 136570 (pass), for last pass
Repro found: flight 136571 (fail), for first failure
Repro found: flight 136572 (pass), for last pass
Repro found: flight 136574 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
(Revision log too long, omitted.)
Revision graph left in /home/logs/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.{dot,ps,png,html,svg}.
----------------------------------------
136574: tolerable ALL FAIL
flight 136574 linux-3.18 real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/136574/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
test-amd64-amd64-xl 7 xen-boot fail baseline untested
jobs:
test-amd64-amd64-xl fail
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 10:46 ` Ian Jackson
0 siblings, 0 replies; 19+ messages in thread
From: Ian Jackson @ 2019-05-20 10:46 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, Stefano Stabellini, Boris Ostrovsky,
Juergen Gross, Wei Liu, Paul Durrant
Cc: xen-devel, Lars Kurth
This has been true for some time. osstest has been sending automatic
mails including bisection reports like the one below, for about a
month.
osstest's "tested and good" branch of linux-3.18 is 190 days behind
the upstream tip.
Do we care about this at all ?
Note that the Xen Project does not have a dedicated team of QA
engineers who do triage of test reports. It is up to every maintainer
of every Xen-related component to keep an eye on these test reports
and investigate failures.
For the avoidance of any doubt, osstest's "bisection complete" reports
can always be relied on to accurately identify a real, repeatable,
regression. osstest will only make such a report if it has reproduced
several times both the failure at the commit it blames, and the
success at the commit it says is OK. (In trees with a lot of merging,
the commit that is blamed is sadly often a merge, but one of its
parents will be identified as good.)
In this case osstest has sent a significant number of functionally
identical reports saying it has identified a regression in lots of
different tests. But this has not resulted in any action AFAIAA.
Please would someone involved with the Linux kernel end of things pick
this up.
Thanks,
Ian.
osstest service owner writes ("[linux-3.18 bisection] complete test-amd64-amd64-xl"):
> branch xen-unstable
> xenbranch xen-unstable
> job test-amd64-amd64-xl
> testid xen-boot
>
> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> Tree: xen git://xenbits.xen.org/xen.git
>
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
> Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
>
>
> (Revision log too long, omitted.)
>
>
> For bisection revision-tuple graph see:
> http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.html
> Revision IDs in each graph node refer, respectively, to the Trees above.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* [Xen-devel] Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 10:46 ` Ian Jackson
0 siblings, 0 replies; 19+ messages in thread
From: Ian Jackson @ 2019-05-20 10:46 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, Stefano Stabellini, Boris Ostrovsky,
Juergen Gross, Wei Liu, Paul Durrant
Cc: xen-devel, Lars Kurth
This has been true for some time. osstest has been sending automatic
mails including bisection reports like the one below, for about a
month.
osstest's "tested and good" branch of linux-3.18 is 190 days behind
the upstream tip.
Do we care about this at all ?
Note that the Xen Project does not have a dedicated team of QA
engineers who do triage of test reports. It is up to every maintainer
of every Xen-related component to keep an eye on these test reports
and investigate failures.
For the avoidance of any doubt, osstest's "bisection complete" reports
can always be relied on to accurately identify a real, repeatable,
regression. osstest will only make such a report if it has reproduced
several times both the failure at the commit it blames, and the
success at the commit it says is OK. (In trees with a lot of merging,
the commit that is blamed is sadly often a merge, but one of its
parents will be identified as good.)
In this case osstest has sent a significant number of functionally
identical reports saying it has identified a regression in lots of
different tests. But this has not resulted in any action AFAIAA.
Please would someone involved with the Linux kernel end of things pick
this up.
Thanks,
Ian.
osstest service owner writes ("[linux-3.18 bisection] complete test-amd64-amd64-xl"):
> branch xen-unstable
> xenbranch xen-unstable
> job test-amd64-amd64-xl
> testid xen-boot
>
> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> Tree: xen git://xenbits.xen.org/xen.git
>
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
> Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
>
>
> (Revision log too long, omitted.)
>
>
> For bisection revision-tuple graph see:
> http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.html
> Revision IDs in each graph node refer, respectively, to the Trees above.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 11:17 ` Juergen Gross
0 siblings, 0 replies; 19+ messages in thread
From: Juergen Gross @ 2019-05-20 11:17 UTC (permalink / raw)
To: Ian Jackson, Konrad Rzeszutek Wilk, Stefano Stabellini,
Boris Ostrovsky, Wei Liu, Paul Durrant
Cc: xen-devel, Lars Kurth
On 20/05/2019 12:46, Ian Jackson wrote:
> This has been true for some time. osstest has been sending automatic
> mails including bisection reports like the one below, for about a
> month.
>
> osstest's "tested and good" branch of linux-3.18 is 190 days behind
> the upstream tip.
>
> Do we care about this at all ?
>
> Note that the Xen Project does not have a dedicated team of QA
> engineers who do triage of test reports. It is up to every maintainer
> of every Xen-related component to keep an eye on these test reports
> and investigate failures.
>
> For the avoidance of any doubt, osstest's "bisection complete" reports
> can always be relied on to accurately identify a real, repeatable,
> regression. osstest will only make such a report if it has reproduced
> several times both the failure at the commit it blames, and the
> success at the commit it says is OK. (In trees with a lot of merging,
> the commit that is blamed is sadly often a merge, but one of its
> parents will be identified as good.)
>
> In this case osstest has sent a significant number of functionally
> identical reports saying it has identified a regression in lots of
> different tests. But this has not resulted in any action AFAIAA.
>
> Please would someone involved with the Linux kernel end of things pick
> this up.
>
> Thanks,
> Ian.
>
> osstest service owner writes ("[linux-3.18 bisection] complete test-amd64-amd64-xl"):
>> branch xen-unstable
>> xenbranch xen-unstable
>> job test-amd64-amd64-xl
>> testid xen-boot
>>
>> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>> Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
>> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
>> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
>> Tree: xen git://xenbits.xen.org/xen.git
>>
>> *** Found and reproduced problem changeset ***
>>
>> Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
That was the commit for 3.18.140
>> Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
and that the one for 3.18.121
There are 1352 commits between the two commits. A bisector telling me
such a result is next to useless.
Not sure when I'll be able to pick it up.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Xen-devel] Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 11:17 ` Juergen Gross
0 siblings, 0 replies; 19+ messages in thread
From: Juergen Gross @ 2019-05-20 11:17 UTC (permalink / raw)
To: Ian Jackson, Konrad Rzeszutek Wilk, Stefano Stabellini,
Boris Ostrovsky, Wei Liu, Paul Durrant
Cc: xen-devel, Lars Kurth
On 20/05/2019 12:46, Ian Jackson wrote:
> This has been true for some time. osstest has been sending automatic
> mails including bisection reports like the one below, for about a
> month.
>
> osstest's "tested and good" branch of linux-3.18 is 190 days behind
> the upstream tip.
>
> Do we care about this at all ?
>
> Note that the Xen Project does not have a dedicated team of QA
> engineers who do triage of test reports. It is up to every maintainer
> of every Xen-related component to keep an eye on these test reports
> and investigate failures.
>
> For the avoidance of any doubt, osstest's "bisection complete" reports
> can always be relied on to accurately identify a real, repeatable,
> regression. osstest will only make such a report if it has reproduced
> several times both the failure at the commit it blames, and the
> success at the commit it says is OK. (In trees with a lot of merging,
> the commit that is blamed is sadly often a merge, but one of its
> parents will be identified as good.)
>
> In this case osstest has sent a significant number of functionally
> identical reports saying it has identified a regression in lots of
> different tests. But this has not resulted in any action AFAIAA.
>
> Please would someone involved with the Linux kernel end of things pick
> this up.
>
> Thanks,
> Ian.
>
> osstest service owner writes ("[linux-3.18 bisection] complete test-amd64-amd64-xl"):
>> branch xen-unstable
>> xenbranch xen-unstable
>> job test-amd64-amd64-xl
>> testid xen-boot
>>
>> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>> Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
>> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
>> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
>> Tree: xen git://xenbits.xen.org/xen.git
>>
>> *** Found and reproduced problem changeset ***
>>
>> Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
That was the commit for 3.18.140
>> Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
and that the one for 3.18.121
There are 1352 commits between the two commits. A bisector telling me
such a result is next to useless.
Not sure when I'll be able to pick it up.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 11:41 ` Wei Liu
0 siblings, 0 replies; 19+ messages in thread
From: Wei Liu @ 2019-05-20 11:41 UTC (permalink / raw)
To: Ian Jackson
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, Paul Durrant, xen-devel, Boris Ostrovsky
On Mon, May 20, 2019 at 11:46:16AM +0100, Ian Jackson wrote:
> This has been true for some time. osstest has been sending automatic
> mails including bisection reports like the one below, for about a
> month.
>
> osstest's "tested and good" branch of linux-3.18 is 190 days behind
> the upstream tip.
>
> Do we care about this at all ?
>
> Note that the Xen Project does not have a dedicated team of QA
> engineers who do triage of test reports. It is up to every maintainer
> of every Xen-related component to keep an eye on these test reports
> and investigate failures.
>
> For the avoidance of any doubt, osstest's "bisection complete" reports
> can always be relied on to accurately identify a real, repeatable,
> regression. osstest will only make such a report if it has reproduced
> several times both the failure at the commit it blames, and the
> success at the commit it says is OK. (In trees with a lot of merging,
> the commit that is blamed is sadly often a merge, but one of its
> parents will be identified as good.)
>
> In this case osstest has sent a significant number of functionally
> identical reports saying it has identified a regression in lots of
> different tests. But this has not resulted in any action AFAIAA.
>
> Please would someone involved with the Linux kernel end of things pick
> this up.
>
> Thanks,
> Ian.
>
> osstest service owner writes ("[linux-3.18 bisection] complete test-amd64-amd64-xl"):
> > branch xen-unstable
> > xenbranch xen-unstable
> > job test-amd64-amd64-xl
> > testid xen-boot
> >
> > Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> > Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
> > Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> > Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> > Tree: xen git://xenbits.xen.org/xen.git
> >
> > *** Found and reproduced problem changeset ***
> >
> > Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
> > Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
> > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
> >
It seems that there is something wrong with the IGB driver.
Seen in one of the normal flight:
http://logs.test-lab.xenproject.org/osstest/logs/136390/test-amd64-amd64-xl/serial-debina1.log
May 19 00:12:40.076089 [ 12.671451] ------------[ cut here ]------------
May 19 00:12:40.076107 [ 12.671463] WARNING: CPU: 7 PID: 1519 at drivers/pci/msi.c:975 pci_enable_msix+0x364/0x3b0()
May 19 00:12:40.088095 [ 12.671470] Modules linked in: igb(+) i2c_algo_bit
May 19 00:12:40.088115 [ 12.671481] CPU: 7 PID: 1519 Comm: systemd-udevd Not tainted 3.18.140 #1
May 19 00:12:40.100092 [ 12.671487] Hardware name: Supermicro SYS-5018D-FN8T/X10SDV-TP8F, BIOS 1.0b 11/21/2016
May 19 00:12:40.112083 [ 12.671493] 0000000000000000 ffff880005147a78 ffffffff817f4db9 0000000000000000
May 19 00:12:40.112108 [ 12.671502] 0000000000000009 ffff880005147ab8 ffffffff810b740c ffff8800196d3000
May 19 00:12:40.124110 [ 12.671511] ffff8800196d3000 000000000000000a ffff88000409e998 0000000000000009
May 19 00:12:40.124132 [ 12.671521] Call Trace:
May 19 00:12:40.136087 [ 12.671528] [<ffffffff817f4db9>] dump_stack+0x7a/0x96
May 19 00:12:40.136108 [ 12.671534] [<ffffffff810b740c>] warn_slowpath_common+0x7c/0xa0
May 19 00:12:40.148084 [ 12.671540] [<ffffffff810b74d5>] warn_slowpath_null+0x15/0x20
May 19 00:12:40.148107 [ 12.671547] [<ffffffff81364344>] pci_enable_msix+0x364/0x3b0
May 19 00:12:40.148121 [ 12.671563] [<ffffffffa0005b88>] ? igb_alloc_q_vector.isra.57+0x98/0x280 [igb]
May 19 00:12:40.160098 [ 12.671570] [<ffffffff813643bd>] pci_enable_msix_range+0x2d/0x70
May 19 00:12:40.172086 [ 12.671580] [<ffffffffa0005e76>] igb_set_interrupt_capability+0x86/0x1b0 [igb]
May 19 00:12:40.172111 [ 12.671591] [<ffffffffa0009d63>] igb_probe+0x4d3/0x1270 [igb]
May 19 00:12:40.184090 [ 12.671600] [<ffffffff813530e9>] pci_device_probe+0x69/0xc0
May 19 00:12:40.184111 [ 12.671608] [<ffffffff81414eec>] really_probe+0x6c/0x240
May 19 00:12:40.196087 [ 12.671613] [<ffffffff814151a9>] __driver_attach+0x99/0xa0
May 19 00:12:40.196108 [ 12.671619] [<ffffffff81415110>] ? __device_attach+0x50/0x50
May 19 00:12:40.208087 [ 12.671625] [<ffffffff81413273>] bus_for_each_dev+0x63/0xa0
May 19 00:12:40.208109 [ 12.671631] [<ffffffff81414a89>] driver_attach+0x19/0x20
May 19 00:12:40.220087 [ 12.671637] [<ffffffff8141469c>] bus_add_driver+0x10c/0x210
May 19 00:12:40.220109 [ 12.671643] [<ffffffffa0029000>] ? 0xffffffffa0029000
May 19 00:12:40.220123 [ 12.671648] [<ffffffff81415a8f>] driver_register+0x5f/0xf0
May 19 00:12:40.232095 [ 12.671655] [<ffffffff81351aa6>] __pci_register_driver+0x46/0x50
May 19 00:12:40.232123 [ 12.671665] [<ffffffffa002904f>] igb_init_module+0x4f/0x51 [igb]
May 19 00:12:40.244091 [ 12.671671] [<ffffffff81002128>] do_one_initcall+0x88/0x1e0
May 19 00:12:40.244112 [ 12.671678] [<ffffffff811c0412>] ? __vunmap+0xa2/0x100
May 19 00:12:40.256090 [ 12.671685] [<ffffffff8112d145>] load_module+0x1bd5/0x2320
May 19 00:12:40.256111 [ 12.671692] [<ffffffff8112da16>] SYSC_finit_module+0x96/0xa0
May 19 00:12:40.268093 [ 12.671699] [<ffffffff8112da39>] SyS_finit_module+0x9/0x10
May 19 00:12:40.268113 [ 12.671705] [<ffffffff817fd789>] system_call_fastpath+0x12/0x17
May 19 00:12:40.280089 [ 12.671710] ---[ end trace 723a474d0c2ed165 ]---
May 19 00:12:40.280109 (XEN) d0: Forcing read-only access to MFN fb18c
May 19 00:12:40.292086 [ 12.672504] BUG: unable to handle kernel paging request at ffffc900000fc00c
May 19 00:12:40.292110 [ 12.672511] IP: [<ffffffff81364105>] pci_enable_msix+0x125/0x3b0
May 19 00:12:40.304086 [ 12.672519] PGD 1a833067 PUD 1a834067 PMD 1a835067 PTE 0
May 19 00:12:40.304106 [ 12.672527] Oops: 0000 [#1] SMP
May 19 00:12:40.304118 [ 12.672532] Modules linked in: igb(+) i2c_algo_bit
May 19 00:12:40.316091 [ 12.672540] CPU: 7 PID: 1519 Comm: systemd-udevd Tainted: G W 3.18.140 #1
May 19 00:12:40.316116 [ 12.672546] Hardware name: Supermicro SYS-5018D-FN8T/X10SDV-TP8F, BIOS 1.0b 11/21/2016
May 19 00:12:40.328096 [ 12.672552] task: ffff88001abf0000 ti: ffff880005144000 task.ti: ffff880005144000
May 19 00:12:40.340096 [ 12.672558] RIP: e030:[<ffffffff81364105>] [<ffffffff81364105>] pci_enable_msix+0x125/0x3b0
May 19 00:12:40.340122 [ 12.672566] RSP: e02b:ffff880005147ad8 EFLAGS: 00010286
May 19 00:12:40.352090 [ 12.672570] RAX: ffffc900000fc00c RBX: ffff8800196d3000 RCX: 00000000fffffffa
May 19 00:12:40.352112 [ 12.672576] RDX: 0000000000000000 RSI: ffff880004fb0200 RDI: ffff880004fb0200
May 19 00:12:40.364097 [ 12.672582] RBP: ffff880005147b38 R08: ffff880004fb0200 R09: ffff88001a400658
May 19 00:12:40.376087 [ 12.672587] R10: 0000000000000000 R11: 000000000001a0f1 R12: 000000000000000d
May 19 00:12:40.376108 [ 12.672593] R13: ffff880005344480 R14: 000000000008800c R15: ffff88000409e998
May 19 00:12:40.388029 [ 12.672607] FS: 00007fc8fb4ed8c0(0000) GS:ffff88001fdc0000(0000) knlGS:0000000000000000
May 19 00:12:40.400084 [ 12.672613] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
May 19 00:12:40.400104 [ 12.672618] CR2: ffffc900000fc00c CR3: 0000000000027000 CR4: 0000000000040660
May 19 00:12:40.412088 [ 12.672627] Stack:
May 19 00:12:40.412105 [ 12.672629] ffff880005147b28 ffff8800196d37a0 0000000000000009 ffff8800196d37a0
May 19 00:12:40.412122 [ 12.672638] ffff88000409e780 0000000000090007 0000000000000007 0000000000000009
May 19 00:12:40.424096 [ 12.672646] ffff8800196d3000 ffff88000409e998 0000000000000009 ffff8800196d3000
May 19 00:12:40.436098 [ 12.672655] Call Trace:
May 19 00:12:40.436114 [ 12.672659] [<ffffffff813643bd>] pci_enable_msix_range+0x2d/0x70
May 19 00:12:40.436130 [ 12.672670] [<ffffffffa0005e76>] igb_set_interrupt_capability+0x86/0x1b0 [igb]
May 19 00:12:40.448097 [ 12.672680] [<ffffffffa0009d63>] igb_probe+0x4d3/0x1270 [igb]
May 19 00:12:40.448117 [ 12.672688] [<ffffffff813530e9>] pci_device_probe+0x69/0xc0
May 19 00:12:40.460094 [ 12.672694] [<ffffffff81414eec>] really_probe+0x6c/0x240
May 19 00:12:40.460114 [ 12.672700] [<ffffffff814151a9>] __driver_attach+0x99/0xa0
May 19 00:12:40.472093 [ 12.672705] [<ffffffff81415110>] ? __device_attach+0x50/0x50
May 19 00:12:40.472114 [ 12.672711] [<ffffffff81413273>] bus_for_each_dev+0x63/0xa0
May 19 00:12:40.484090 [ 12.672717] [<ffffffff81414a89>] driver_attach+0x19/0x20
May 19 00:12:40.484110 [ 12.672722] [<ffffffff8141469c>] bus_add_driver+0x10c/0x210
May 19 00:12:40.496091 [ 12.672727] [<ffffffffa0029000>] ? 0xffffffffa0029000
May 19 00:12:40.496110 [ 12.672733] [<ffffffff81415a8f>] driver_register+0x5f/0xf0
May 19 00:12:40.508095 [ 12.672739] [<ffffffff81351aa6>] __pci_register_driver+0x46/0x50
May 19 00:12:40.508117 [ 12.672748] [<ffffffffa002904f>] igb_init_module+0x4f/0x51 [igb]
May 19 00:12:40.520089 [ 12.672754] [<ffffffff81002128>] do_one_initcall+0x88/0x1e0
May 19 00:12:40.520111 [ 12.672763] [<ffffffff811c0412>] ? __vunmap+0xa2/0x100
May 19 00:12:40.532086 [ 12.672769] [<ffffffff8112d145>] load_module+0x1bd5/0x2320
May 19 00:12:40.532107 [ 12.672775] [<ffffffff8112da16>] SYSC_finit_module+0x96/0xa0
May 19 00:12:40.544087 [ 12.672782] [<ffffffff8112da39>] SyS_finit_module+0x9/0x10
May 19 00:12:40.544108 [ 12.672787] [<ffffffff817fd789>] system_call_fastpath+0x12/0x17
May 19 00:12:40.556083 [ 12.672792] Code: 0c 4c 89 ee 49 8d 04 c7 48 89 55 b8 44 0f b7 70 04 89 08 41 8b 7d 0c 41 c1 e6 04 41 83 c6 0c e8 d2 19 da ff 49 63 c6 49 03 45 28 <8b> 00 be 01 00 00 00 41 89 45 08 4c 89 ef e8 58 83 d0 ff 48 8b
May 19 00:12:40.568096 [ 12.672858] RIP [<ffffffff81364105>] pci_enable_msix+0x125/0x3b0
May 19 00:12:40.580087 [ 12.672865] RSP <ffff880005147ad8>
May 19 00:12:40.580106 [ 12.672868] CR2: ffffc900000fc00c
May 19 00:12:40.580117 [ 12.672873] ---[ end trace 723a474d0c2ed166 ]---
> >
> > (Revision log too long, omitted.)
> >
> >
> > For bisection revision-tuple graph see:
> > http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.html
> > Revision IDs in each graph node refer, respectively, to the Trees above.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Xen-devel] Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 11:41 ` Wei Liu
0 siblings, 0 replies; 19+ messages in thread
From: Wei Liu @ 2019-05-20 11:41 UTC (permalink / raw)
To: Ian Jackson
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, Paul Durrant, xen-devel, Boris Ostrovsky
On Mon, May 20, 2019 at 11:46:16AM +0100, Ian Jackson wrote:
> This has been true for some time. osstest has been sending automatic
> mails including bisection reports like the one below, for about a
> month.
>
> osstest's "tested and good" branch of linux-3.18 is 190 days behind
> the upstream tip.
>
> Do we care about this at all ?
>
> Note that the Xen Project does not have a dedicated team of QA
> engineers who do triage of test reports. It is up to every maintainer
> of every Xen-related component to keep an eye on these test reports
> and investigate failures.
>
> For the avoidance of any doubt, osstest's "bisection complete" reports
> can always be relied on to accurately identify a real, repeatable,
> regression. osstest will only make such a report if it has reproduced
> several times both the failure at the commit it blames, and the
> success at the commit it says is OK. (In trees with a lot of merging,
> the commit that is blamed is sadly often a merge, but one of its
> parents will be identified as good.)
>
> In this case osstest has sent a significant number of functionally
> identical reports saying it has identified a regression in lots of
> different tests. But this has not resulted in any action AFAIAA.
>
> Please would someone involved with the Linux kernel end of things pick
> this up.
>
> Thanks,
> Ian.
>
> osstest service owner writes ("[linux-3.18 bisection] complete test-amd64-amd64-xl"):
> > branch xen-unstable
> > xenbranch xen-unstable
> > job test-amd64-amd64-xl
> > testid xen-boot
> >
> > Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> > Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
> > Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> > Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> > Tree: xen git://xenbits.xen.org/xen.git
> >
> > *** Found and reproduced problem changeset ***
> >
> > Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
> > Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
> > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
> >
It seems that there is something wrong with the IGB driver.
Seen in one of the normal flight:
http://logs.test-lab.xenproject.org/osstest/logs/136390/test-amd64-amd64-xl/serial-debina1.log
May 19 00:12:40.076089 [ 12.671451] ------------[ cut here ]------------
May 19 00:12:40.076107 [ 12.671463] WARNING: CPU: 7 PID: 1519 at drivers/pci/msi.c:975 pci_enable_msix+0x364/0x3b0()
May 19 00:12:40.088095 [ 12.671470] Modules linked in: igb(+) i2c_algo_bit
May 19 00:12:40.088115 [ 12.671481] CPU: 7 PID: 1519 Comm: systemd-udevd Not tainted 3.18.140 #1
May 19 00:12:40.100092 [ 12.671487] Hardware name: Supermicro SYS-5018D-FN8T/X10SDV-TP8F, BIOS 1.0b 11/21/2016
May 19 00:12:40.112083 [ 12.671493] 0000000000000000 ffff880005147a78 ffffffff817f4db9 0000000000000000
May 19 00:12:40.112108 [ 12.671502] 0000000000000009 ffff880005147ab8 ffffffff810b740c ffff8800196d3000
May 19 00:12:40.124110 [ 12.671511] ffff8800196d3000 000000000000000a ffff88000409e998 0000000000000009
May 19 00:12:40.124132 [ 12.671521] Call Trace:
May 19 00:12:40.136087 [ 12.671528] [<ffffffff817f4db9>] dump_stack+0x7a/0x96
May 19 00:12:40.136108 [ 12.671534] [<ffffffff810b740c>] warn_slowpath_common+0x7c/0xa0
May 19 00:12:40.148084 [ 12.671540] [<ffffffff810b74d5>] warn_slowpath_null+0x15/0x20
May 19 00:12:40.148107 [ 12.671547] [<ffffffff81364344>] pci_enable_msix+0x364/0x3b0
May 19 00:12:40.148121 [ 12.671563] [<ffffffffa0005b88>] ? igb_alloc_q_vector.isra.57+0x98/0x280 [igb]
May 19 00:12:40.160098 [ 12.671570] [<ffffffff813643bd>] pci_enable_msix_range+0x2d/0x70
May 19 00:12:40.172086 [ 12.671580] [<ffffffffa0005e76>] igb_set_interrupt_capability+0x86/0x1b0 [igb]
May 19 00:12:40.172111 [ 12.671591] [<ffffffffa0009d63>] igb_probe+0x4d3/0x1270 [igb]
May 19 00:12:40.184090 [ 12.671600] [<ffffffff813530e9>] pci_device_probe+0x69/0xc0
May 19 00:12:40.184111 [ 12.671608] [<ffffffff81414eec>] really_probe+0x6c/0x240
May 19 00:12:40.196087 [ 12.671613] [<ffffffff814151a9>] __driver_attach+0x99/0xa0
May 19 00:12:40.196108 [ 12.671619] [<ffffffff81415110>] ? __device_attach+0x50/0x50
May 19 00:12:40.208087 [ 12.671625] [<ffffffff81413273>] bus_for_each_dev+0x63/0xa0
May 19 00:12:40.208109 [ 12.671631] [<ffffffff81414a89>] driver_attach+0x19/0x20
May 19 00:12:40.220087 [ 12.671637] [<ffffffff8141469c>] bus_add_driver+0x10c/0x210
May 19 00:12:40.220109 [ 12.671643] [<ffffffffa0029000>] ? 0xffffffffa0029000
May 19 00:12:40.220123 [ 12.671648] [<ffffffff81415a8f>] driver_register+0x5f/0xf0
May 19 00:12:40.232095 [ 12.671655] [<ffffffff81351aa6>] __pci_register_driver+0x46/0x50
May 19 00:12:40.232123 [ 12.671665] [<ffffffffa002904f>] igb_init_module+0x4f/0x51 [igb]
May 19 00:12:40.244091 [ 12.671671] [<ffffffff81002128>] do_one_initcall+0x88/0x1e0
May 19 00:12:40.244112 [ 12.671678] [<ffffffff811c0412>] ? __vunmap+0xa2/0x100
May 19 00:12:40.256090 [ 12.671685] [<ffffffff8112d145>] load_module+0x1bd5/0x2320
May 19 00:12:40.256111 [ 12.671692] [<ffffffff8112da16>] SYSC_finit_module+0x96/0xa0
May 19 00:12:40.268093 [ 12.671699] [<ffffffff8112da39>] SyS_finit_module+0x9/0x10
May 19 00:12:40.268113 [ 12.671705] [<ffffffff817fd789>] system_call_fastpath+0x12/0x17
May 19 00:12:40.280089 [ 12.671710] ---[ end trace 723a474d0c2ed165 ]---
May 19 00:12:40.280109 (XEN) d0: Forcing read-only access to MFN fb18c
May 19 00:12:40.292086 [ 12.672504] BUG: unable to handle kernel paging request at ffffc900000fc00c
May 19 00:12:40.292110 [ 12.672511] IP: [<ffffffff81364105>] pci_enable_msix+0x125/0x3b0
May 19 00:12:40.304086 [ 12.672519] PGD 1a833067 PUD 1a834067 PMD 1a835067 PTE 0
May 19 00:12:40.304106 [ 12.672527] Oops: 0000 [#1] SMP
May 19 00:12:40.304118 [ 12.672532] Modules linked in: igb(+) i2c_algo_bit
May 19 00:12:40.316091 [ 12.672540] CPU: 7 PID: 1519 Comm: systemd-udevd Tainted: G W 3.18.140 #1
May 19 00:12:40.316116 [ 12.672546] Hardware name: Supermicro SYS-5018D-FN8T/X10SDV-TP8F, BIOS 1.0b 11/21/2016
May 19 00:12:40.328096 [ 12.672552] task: ffff88001abf0000 ti: ffff880005144000 task.ti: ffff880005144000
May 19 00:12:40.340096 [ 12.672558] RIP: e030:[<ffffffff81364105>] [<ffffffff81364105>] pci_enable_msix+0x125/0x3b0
May 19 00:12:40.340122 [ 12.672566] RSP: e02b:ffff880005147ad8 EFLAGS: 00010286
May 19 00:12:40.352090 [ 12.672570] RAX: ffffc900000fc00c RBX: ffff8800196d3000 RCX: 00000000fffffffa
May 19 00:12:40.352112 [ 12.672576] RDX: 0000000000000000 RSI: ffff880004fb0200 RDI: ffff880004fb0200
May 19 00:12:40.364097 [ 12.672582] RBP: ffff880005147b38 R08: ffff880004fb0200 R09: ffff88001a400658
May 19 00:12:40.376087 [ 12.672587] R10: 0000000000000000 R11: 000000000001a0f1 R12: 000000000000000d
May 19 00:12:40.376108 [ 12.672593] R13: ffff880005344480 R14: 000000000008800c R15: ffff88000409e998
May 19 00:12:40.388029 [ 12.672607] FS: 00007fc8fb4ed8c0(0000) GS:ffff88001fdc0000(0000) knlGS:0000000000000000
May 19 00:12:40.400084 [ 12.672613] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
May 19 00:12:40.400104 [ 12.672618] CR2: ffffc900000fc00c CR3: 0000000000027000 CR4: 0000000000040660
May 19 00:12:40.412088 [ 12.672627] Stack:
May 19 00:12:40.412105 [ 12.672629] ffff880005147b28 ffff8800196d37a0 0000000000000009 ffff8800196d37a0
May 19 00:12:40.412122 [ 12.672638] ffff88000409e780 0000000000090007 0000000000000007 0000000000000009
May 19 00:12:40.424096 [ 12.672646] ffff8800196d3000 ffff88000409e998 0000000000000009 ffff8800196d3000
May 19 00:12:40.436098 [ 12.672655] Call Trace:
May 19 00:12:40.436114 [ 12.672659] [<ffffffff813643bd>] pci_enable_msix_range+0x2d/0x70
May 19 00:12:40.436130 [ 12.672670] [<ffffffffa0005e76>] igb_set_interrupt_capability+0x86/0x1b0 [igb]
May 19 00:12:40.448097 [ 12.672680] [<ffffffffa0009d63>] igb_probe+0x4d3/0x1270 [igb]
May 19 00:12:40.448117 [ 12.672688] [<ffffffff813530e9>] pci_device_probe+0x69/0xc0
May 19 00:12:40.460094 [ 12.672694] [<ffffffff81414eec>] really_probe+0x6c/0x240
May 19 00:12:40.460114 [ 12.672700] [<ffffffff814151a9>] __driver_attach+0x99/0xa0
May 19 00:12:40.472093 [ 12.672705] [<ffffffff81415110>] ? __device_attach+0x50/0x50
May 19 00:12:40.472114 [ 12.672711] [<ffffffff81413273>] bus_for_each_dev+0x63/0xa0
May 19 00:12:40.484090 [ 12.672717] [<ffffffff81414a89>] driver_attach+0x19/0x20
May 19 00:12:40.484110 [ 12.672722] [<ffffffff8141469c>] bus_add_driver+0x10c/0x210
May 19 00:12:40.496091 [ 12.672727] [<ffffffffa0029000>] ? 0xffffffffa0029000
May 19 00:12:40.496110 [ 12.672733] [<ffffffff81415a8f>] driver_register+0x5f/0xf0
May 19 00:12:40.508095 [ 12.672739] [<ffffffff81351aa6>] __pci_register_driver+0x46/0x50
May 19 00:12:40.508117 [ 12.672748] [<ffffffffa002904f>] igb_init_module+0x4f/0x51 [igb]
May 19 00:12:40.520089 [ 12.672754] [<ffffffff81002128>] do_one_initcall+0x88/0x1e0
May 19 00:12:40.520111 [ 12.672763] [<ffffffff811c0412>] ? __vunmap+0xa2/0x100
May 19 00:12:40.532086 [ 12.672769] [<ffffffff8112d145>] load_module+0x1bd5/0x2320
May 19 00:12:40.532107 [ 12.672775] [<ffffffff8112da16>] SYSC_finit_module+0x96/0xa0
May 19 00:12:40.544087 [ 12.672782] [<ffffffff8112da39>] SyS_finit_module+0x9/0x10
May 19 00:12:40.544108 [ 12.672787] [<ffffffff817fd789>] system_call_fastpath+0x12/0x17
May 19 00:12:40.556083 [ 12.672792] Code: 0c 4c 89 ee 49 8d 04 c7 48 89 55 b8 44 0f b7 70 04 89 08 41 8b 7d 0c 41 c1 e6 04 41 83 c6 0c e8 d2 19 da ff 49 63 c6 49 03 45 28 <8b> 00 be 01 00 00 00 41 89 45 08 4c 89 ef e8 58 83 d0 ff 48 8b
May 19 00:12:40.568096 [ 12.672858] RIP [<ffffffff81364105>] pci_enable_msix+0x125/0x3b0
May 19 00:12:40.580087 [ 12.672865] RSP <ffff880005147ad8>
May 19 00:12:40.580106 [ 12.672868] CR2: ffffc900000fc00c
May 19 00:12:40.580117 [ 12.672873] ---[ end trace 723a474d0c2ed166 ]---
> >
> > (Revision log too long, omitted.)
> >
> >
> > For bisection revision-tuple graph see:
> > http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-3.18/test-amd64-amd64-xl.xen-boot.html
> > Revision IDs in each graph node refer, respectively, to the Trees above.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 13:51 ` Jan Beulich
0 siblings, 0 replies; 19+ messages in thread
From: Jan Beulich @ 2019-05-20 13:51 UTC (permalink / raw)
To: Wei Liu
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini,
Konrad Rzeszutek Wilk, Paul Durrant, xen-devel, Ian Jackson,
Boris Ostrovsky
>>> On 20.05.19 at 13:41, <wei.liu2@citrix.com> wrote:
> On Mon, May 20, 2019 at 11:46:16AM +0100, Ian Jackson wrote:
>> This has been true for some time. osstest has been sending automatic
>> mails including bisection reports like the one below, for about a
>> month.
>>
>> osstest's "tested and good" branch of linux-3.18 is 190 days behind
>> the upstream tip.
>>
>> Do we care about this at all ?
>>
>> Note that the Xen Project does not have a dedicated team of QA
>> engineers who do triage of test reports. It is up to every maintainer
>> of every Xen-related component to keep an eye on these test reports
>> and investigate failures.
>>
>> For the avoidance of any doubt, osstest's "bisection complete" reports
>> can always be relied on to accurately identify a real, repeatable,
>> regression. osstest will only make such a report if it has reproduced
>> several times both the failure at the commit it blames, and the
>> success at the commit it says is OK. (In trees with a lot of merging,
>> the commit that is blamed is sadly often a merge, but one of its
>> parents will be identified as good.)
>>
>> In this case osstest has sent a significant number of functionally
>> identical reports saying it has identified a regression in lots of
>> different tests. But this has not resulted in any action AFAIAA.
>>
>> Please would someone involved with the Linux kernel end of things pick
>> this up.
>>
>> Thanks,
>> Ian.
>>
>> osstest service owner writes ("[linux-3.18 bisection] complete
> test-amd64-amd64-xl"):
>> > branch xen-unstable
>> > xenbranch xen-unstable
>> > job test-amd64-amd64-xl
>> > testid xen-boot
>> >
>> > Tree: linux
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>> > Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
>> > Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
>> > Tree: qemuu git://xenbits.xen.org/qemu-xen.git
>> > Tree: xen git://xenbits.xen.org/xen.git
>> >
>> > *** Found and reproduced problem changeset ***
>> >
>> > Bug is in tree: linux
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> > Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
>> > Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
>> > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
>> >
>
>
> It seems that there is something wrong with the IGB driver.
Which in turn reminds me of a patch of mine that was backported
(and spotted by an earlier bisection), and that I've suggested
(twice already iirc) was either backported in error, or without some
further necessary changes. Iirc the stable tree maintainer for that
branch was Cc-ed back then, and if so I'd conclude he doesn't care.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Xen-devel] Linux 3.18 no longer boots under Xen, please fix
@ 2019-05-20 13:51 ` Jan Beulich
0 siblings, 0 replies; 19+ messages in thread
From: Jan Beulich @ 2019-05-20 13:51 UTC (permalink / raw)
To: Wei Liu
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini,
Konrad Rzeszutek Wilk, Paul Durrant, xen-devel, Ian Jackson,
Boris Ostrovsky
>>> On 20.05.19 at 13:41, <wei.liu2@citrix.com> wrote:
> On Mon, May 20, 2019 at 11:46:16AM +0100, Ian Jackson wrote:
>> This has been true for some time. osstest has been sending automatic
>> mails including bisection reports like the one below, for about a
>> month.
>>
>> osstest's "tested and good" branch of linux-3.18 is 190 days behind
>> the upstream tip.
>>
>> Do we care about this at all ?
>>
>> Note that the Xen Project does not have a dedicated team of QA
>> engineers who do triage of test reports. It is up to every maintainer
>> of every Xen-related component to keep an eye on these test reports
>> and investigate failures.
>>
>> For the avoidance of any doubt, osstest's "bisection complete" reports
>> can always be relied on to accurately identify a real, repeatable,
>> regression. osstest will only make such a report if it has reproduced
>> several times both the failure at the commit it blames, and the
>> success at the commit it says is OK. (In trees with a lot of merging,
>> the commit that is blamed is sadly often a merge, but one of its
>> parents will be identified as good.)
>>
>> In this case osstest has sent a significant number of functionally
>> identical reports saying it has identified a regression in lots of
>> different tests. But this has not resulted in any action AFAIAA.
>>
>> Please would someone involved with the Linux kernel end of things pick
>> this up.
>>
>> Thanks,
>> Ian.
>>
>> osstest service owner writes ("[linux-3.18 bisection] complete
> test-amd64-amd64-xl"):
>> > branch xen-unstable
>> > xenbranch xen-unstable
>> > job test-amd64-amd64-xl
>> > testid xen-boot
>> >
>> > Tree: linux
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>> > Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
>> > Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
>> > Tree: qemuu git://xenbits.xen.org/qemu-xen.git
>> > Tree: xen git://xenbits.xen.org/xen.git
>> >
>> > *** Found and reproduced problem changeset ***
>> >
>> > Bug is in tree: linux
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> > Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
>> > Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
>> > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
>> >
>
>
> It seems that there is something wrong with the IGB driver.
Which in turn reminds me of a patch of mine that was backported
(and spotted by an earlier bisection), and that I've suggested
(twice already iirc) was either backported in error, or without some
further necessary changes. Iirc the stable tree maintainer for that
branch was Cc-ed back then, and if so I'd conclude he doesn't care.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Linux 3.18 no longer boots under Xen, Xen CI dropping it
2019-05-20 13:51 ` [Xen-devel] " Jan Beulich
(?)
@ 2019-05-29 15:57 ` Ian Jackson
-1 siblings, 0 replies; 19+ messages in thread
From: Ian Jackson @ 2019-05-29 15:57 UTC (permalink / raw)
To: stable
Cc: Jan Beulich, Wei Liu, Lars Kurth, Paul Durrant,
Stefano Stabellini, xen-devel, Boris Ostrovsky,
Konrad Rzeszutek Wilk, Juergen Gross
Linux 3.18 no longer boots under Xen.
This has been true for over half a year. The Xen project CI has been
sending automatic mails including bisection reports (see below).
I emailed Xen kernel folks and got no takers for fixing this.
Unless this is fixed soon, or at least someone shows some inclination
to investigate this regression, I intend to drop all testing of this
"stable" branch. It has rotted and no-one is fixing it.
> >> > *** Found and reproduced problem changeset ***
> >> >
> >> > Bug is in tree: linux
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> >> > Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
> >> > Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
> >> > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
> >
> > It seems that there is something wrong with the IGB driver.
Additionally, Jan Beulich writes:
> Which in turn reminds me of a patch of mine that was backported
> (and spotted by an earlier bisection), and that I've suggested
> (twice already iirc) was either backported in error, or without some
> further necessary changes. Iirc the stable tree maintainer for that
> branch was Cc-ed back then, and if so I'd conclude he doesn't care.
Thanks,
Ian.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Linux 3.18 no longer boots under Xen, Xen CI dropping it
@ 2019-05-29 15:57 ` Ian Jackson
0 siblings, 0 replies; 19+ messages in thread
From: Ian Jackson @ 2019-05-29 15:57 UTC (permalink / raw)
To: stable
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, Paul Durrant, Jan Beulich, xen-devel,
Boris Ostrovsky
Linux 3.18 no longer boots under Xen.
This has been true for over half a year. The Xen project CI has been
sending automatic mails including bisection reports (see below).
I emailed Xen kernel folks and got no takers for fixing this.
Unless this is fixed soon, or at least someone shows some inclination
to investigate this regression, I intend to drop all testing of this
"stable" branch. It has rotted and no-one is fixing it.
> >> > *** Found and reproduced problem changeset ***
> >> >
> >> > Bug is in tree: linux
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> >> > Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
> >> > Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
> >> > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
> >
> > It seems that there is something wrong with the IGB driver.
Additionally, Jan Beulich writes:
> Which in turn reminds me of a patch of mine that was backported
> (and spotted by an earlier bisection), and that I've suggested
> (twice already iirc) was either backported in error, or without some
> further necessary changes. Iirc the stable tree maintainer for that
> branch was Cc-ed back then, and if so I'd conclude he doesn't care.
Thanks,
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* [Xen-devel] Linux 3.18 no longer boots under Xen, Xen CI dropping it
@ 2019-05-29 15:57 ` Ian Jackson
0 siblings, 0 replies; 19+ messages in thread
From: Ian Jackson @ 2019-05-29 15:57 UTC (permalink / raw)
To: stable
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, Paul Durrant, Jan Beulich, xen-devel,
Boris Ostrovsky
Linux 3.18 no longer boots under Xen.
This has been true for over half a year. The Xen project CI has been
sending automatic mails including bisection reports (see below).
I emailed Xen kernel folks and got no takers for fixing this.
Unless this is fixed soon, or at least someone shows some inclination
to investigate this regression, I intend to drop all testing of this
"stable" branch. It has rotted and no-one is fixing it.
> >> > *** Found and reproduced problem changeset ***
> >> >
> >> > Bug is in tree: linux
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> >> > Bug introduced: 6b1ae527b1fdee86e81da0cb26ced75731c6c0fa
> >> > Bug not present: ba6984fc0162f24a510ebc34e881b546b69c553b
> >> > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136574/
> >
> > It seems that there is something wrong with the IGB driver.
Additionally, Jan Beulich writes:
> Which in turn reminds me of a patch of mine that was backported
> (and spotted by an earlier bisection), and that I've suggested
> (twice already iirc) was either backported in error, or without some
> further necessary changes. Iirc the stable tree maintainer for that
> branch was Cc-ed back then, and if so I'd conclude he doesn't care.
Thanks,
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux 3.18 no longer boots under Xen, Xen CI dropping it
2019-05-29 15:57 ` Ian Jackson
@ 2019-05-29 16:06 ` Jan Beulich
-1 siblings, 0 replies; 19+ messages in thread
From: Jan Beulich @ 2019-05-29 16:06 UTC (permalink / raw)
To: Ian Jackson
Cc: Lars Kurth, Paul Durrant, Wei Liu, Stefano Stabellini, xen-devel,
Boris Ostrovsky, Konrad Rzeszutek Wilk, Juergen Gross, stable
>>> On 29.05.19 at 17:57, <ian.jackson@citrix.com> wrote:
> Linux 3.18 no longer boots under Xen.
>
> This has been true for over half a year. The Xen project CI has been
> sending automatic mails including bisection reports (see below).
> I emailed Xen kernel folks and got no takers for fixing this.
>
> Unless this is fixed soon, or at least someone shows some inclination
> to investigate this regression, I intend to drop all testing of this
> "stable" branch. It has rotted and no-one is fixing it.
Afaics 3.18 has been marked EOL upstream.
Jan
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux 3.18 no longer boots under Xen, Xen CI dropping it
2019-05-29 15:57 ` Ian Jackson
(?)
(?)
@ 2019-05-29 16:06 ` Jan Beulich
-1 siblings, 0 replies; 19+ messages in thread
From: Jan Beulich @ 2019-05-29 16:06 UTC (permalink / raw)
To: Ian Jackson
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, stable, Paul Durrant, xen-devel,
Boris Ostrovsky
>>> On 29.05.19 at 17:57, <ian.jackson@citrix.com> wrote:
> Linux 3.18 no longer boots under Xen.
>
> This has been true for over half a year. The Xen project CI has been
> sending automatic mails including bisection reports (see below).
> I emailed Xen kernel folks and got no takers for fixing this.
>
> Unless this is fixed soon, or at least someone shows some inclination
> to investigate this regression, I intend to drop all testing of this
> "stable" branch. It has rotted and no-one is fixing it.
Afaics 3.18 has been marked EOL upstream.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Xen-devel] Linux 3.18 no longer boots under Xen, Xen CI dropping it
@ 2019-05-29 16:06 ` Jan Beulich
0 siblings, 0 replies; 19+ messages in thread
From: Jan Beulich @ 2019-05-29 16:06 UTC (permalink / raw)
To: Ian Jackson
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, stable, Paul Durrant, xen-devel,
Boris Ostrovsky
>>> On 29.05.19 at 17:57, <ian.jackson@citrix.com> wrote:
> Linux 3.18 no longer boots under Xen.
>
> This has been true for over half a year. The Xen project CI has been
> sending automatic mails including bisection reports (see below).
> I emailed Xen kernel folks and got no takers for fixing this.
>
> Unless this is fixed soon, or at least someone shows some inclination
> to investigate this regression, I intend to drop all testing of this
> "stable" branch. It has rotted and no-one is fixing it.
Afaics 3.18 has been marked EOL upstream.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux 3.18 no longer boots under Xen, Xen CI dropping it
2019-05-29 16:06 ` [Xen-devel] " Jan Beulich
@ 2019-05-29 16:13 ` Greg KH
-1 siblings, 0 replies; 19+ messages in thread
From: Greg KH @ 2019-05-29 16:13 UTC (permalink / raw)
To: Jan Beulich
Cc: Ian Jackson, Lars Kurth, Paul Durrant, Wei Liu,
Stefano Stabellini, xen-devel, Boris Ostrovsky,
Konrad Rzeszutek Wilk, Juergen Gross, stable
On Wed, May 29, 2019 at 10:06:00AM -0600, Jan Beulich wrote:
> >>> On 29.05.19 at 17:57, <ian.jackson@citrix.com> wrote:
> > Linux 3.18 no longer boots under Xen.
> >
> > This has been true for over half a year. The Xen project CI has been
> > sending automatic mails including bisection reports (see below).
> > I emailed Xen kernel folks and got no takers for fixing this.
> >
> > Unless this is fixed soon, or at least someone shows some inclination
> > to investigate this regression, I intend to drop all testing of this
> > "stable" branch. It has rotted and no-one is fixing it.
>
> Afaics 3.18 has been marked EOL upstream.
Yes, there will not be any more 3.18.y releases on kernel.org anymore.
I don't think I recall any people complaining about 3.18 breaking on
Xen as the only users that I know of for that kernel are some SoC-based
devices, and they do not use Xen.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux 3.18 no longer boots under Xen, Xen CI dropping it
2019-05-29 16:06 ` [Xen-devel] " Jan Beulich
(?)
(?)
@ 2019-05-29 16:13 ` Greg KH
-1 siblings, 0 replies; 19+ messages in thread
From: Greg KH @ 2019-05-29 16:13 UTC (permalink / raw)
To: Jan Beulich
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, stable, Paul Durrant, xen-devel,
Ian Jackson, Boris Ostrovsky
On Wed, May 29, 2019 at 10:06:00AM -0600, Jan Beulich wrote:
> >>> On 29.05.19 at 17:57, <ian.jackson@citrix.com> wrote:
> > Linux 3.18 no longer boots under Xen.
> >
> > This has been true for over half a year. The Xen project CI has been
> > sending automatic mails including bisection reports (see below).
> > I emailed Xen kernel folks and got no takers for fixing this.
> >
> > Unless this is fixed soon, or at least someone shows some inclination
> > to investigate this regression, I intend to drop all testing of this
> > "stable" branch. It has rotted and no-one is fixing it.
>
> Afaics 3.18 has been marked EOL upstream.
Yes, there will not be any more 3.18.y releases on kernel.org anymore.
I don't think I recall any people complaining about 3.18 breaking on
Xen as the only users that I know of for that kernel are some SoC-based
devices, and they do not use Xen.
thanks,
greg k-h
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Xen-devel] Linux 3.18 no longer boots under Xen, Xen CI dropping it
@ 2019-05-29 16:13 ` Greg KH
0 siblings, 0 replies; 19+ messages in thread
From: Greg KH @ 2019-05-29 16:13 UTC (permalink / raw)
To: Jan Beulich
Cc: Juergen Gross, Lars Kurth, Stefano Stabellini, Wei Liu,
Konrad Rzeszutek Wilk, stable, Paul Durrant, xen-devel,
Ian Jackson, Boris Ostrovsky
On Wed, May 29, 2019 at 10:06:00AM -0600, Jan Beulich wrote:
> >>> On 29.05.19 at 17:57, <ian.jackson@citrix.com> wrote:
> > Linux 3.18 no longer boots under Xen.
> >
> > This has been true for over half a year. The Xen project CI has been
> > sending automatic mails including bisection reports (see below).
> > I emailed Xen kernel folks and got no takers for fixing this.
> >
> > Unless this is fixed soon, or at least someone shows some inclination
> > to investigate this regression, I intend to drop all testing of this
> > "stable" branch. It has rotted and no-one is fixing it.
>
> Afaics 3.18 has been marked EOL upstream.
Yes, there will not be any more 3.18.y releases on kernel.org anymore.
I don't think I recall any people complaining about 3.18 breaking on
Xen as the only users that I know of for that kernel are some SoC-based
devices, and they do not use Xen.
thanks,
greg k-h
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2019-05-29 16:13 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-19 19:24 [linux-3.18 bisection] complete test-amd64-amd64-xl osstest service owner
2019-05-19 19:24 ` [Xen-devel] " osstest service owner
2019-05-20 10:46 ` Linux 3.18 no longer boots under Xen, please fix Ian Jackson
2019-05-20 10:46 ` [Xen-devel] " Ian Jackson
2019-05-20 11:17 ` Juergen Gross
2019-05-20 11:17 ` [Xen-devel] " Juergen Gross
2019-05-20 11:41 ` Wei Liu
2019-05-20 11:41 ` [Xen-devel] " Wei Liu
2019-05-20 13:51 ` Jan Beulich
2019-05-20 13:51 ` [Xen-devel] " Jan Beulich
2019-05-29 15:57 ` Linux 3.18 no longer boots under Xen, Xen CI dropping it Ian Jackson
2019-05-29 15:57 ` [Xen-devel] " Ian Jackson
2019-05-29 15:57 ` Ian Jackson
2019-05-29 16:06 ` Jan Beulich
2019-05-29 16:06 ` Jan Beulich
2019-05-29 16:06 ` [Xen-devel] " Jan Beulich
2019-05-29 16:13 ` Greg KH
2019-05-29 16:13 ` [Xen-devel] " Greg KH
2019-05-29 16:13 ` Greg KH
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.