Re: [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages]

From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages]
Date: Thu, 19 Jan 2017 13:44:47 -0500	[thread overview]
Message-ID: <1e906253-01b0-da34-6cc8-0e4e29c63f75@oracle.com> (raw)
In-Reply-To: <22656.65504.493026.552412@mariner.uk.xensource.com>

On 01/19/2017 01:05 PM, Ian Jackson wrote:
> Boris Ostrovsky writes ("Re: [Xen-devel] [linux-linus test] 104237: regressions - FAIL"):
>> On 01/18/2017 10:05 AM, osstest service owner wrote:
>>> flight 104237 linux-linus real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/104237/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>>  test-amd64-amd64-xl-qemut-win7-amd64  6 xen-boot          fail REGR. vs. 59254
>>>  test-amd64-i386-qemuu-rhel6hvm-amd  6 xen-boot            fail REGR. vs. 59254
>> Assuming that the last session in serial-nocera1.log is the one that
>> failed, I wonder whether these is something with the mpt2sas --- it's
>> the last thing that's reported before debug-keys are activated:
>>
>> Jan 18 08:47:25.033615 [   40.938069] sd 4:0:0:0: attempting task abort! scmd(db67b800)
>> Jan 18 08:47:47.705686 [   40.938090] sd 4:0:0:0: [sda] tag#0 CDB: ATA command pass through(12)/Blank a1 08 2e 00 01 00 00 00 00 ec 00 00
>> Jan 18 08:47:47.713625 [   40.938097] scsi target4:0:0: handle(0x0009), sas_address(0x4433221107000000), phy(7)
>> Jan 18 08:47:47.721635 [   40.938102] scsi target4:0:0: enclosure_logical_id(0x5b083fe0e50a5700), slot(0)
>> Jan 18 08:47:47.729630 [   40.938129] sd 4:0:0:0: task abort: SUCCESS scmd(db67b800)
> I have had other reports of problems with mptsas.  For example,
> see this bug:  http://bugs.debian.org/850425

That particular bug appears to have swiotlb "overflow" in its signature,
which osstest log doesn't have.

>
> The osstest bisector worked on this:
>
> osstest service owner writes ("[linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64"):
>> branch xen-unstable
>> xenbranch xen-unstable
>> job test-amd64-amd64-xl-qemut-win7-amd64
>> testid xen-boot
>>
>> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.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/torvalds/linux-2.6.git
>>   Bug introduced:  0aa0313f9d576affd7747cc3f179feb097d28990
>>   Bug not present: bcc981e9ed84c678533299d7eff17d2c81e4d5de
>>   Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/104305/
> Unfortunately it has fingered a merge commit.
>
> This means that the bug is in commits which diverged before the last
> pass of this test.
>
> (Did your filters get you a copy of the bisection email?)

No, I haven't set a filter for the bisector but I did see this message
and didn't find bisection results particularly useful. bcc981e9ed84 is
from about a year ago, which, I think, is when you stopped running this
test. And so the question might be whether "Bug not present" is really true?

-boris

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel