From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: "Ser, Simon" <simon.ser@intel.com>,
"Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ GitLab.Pipeline: warning for Dockerfile.debian*: Switch over to buster
Date: Tue, 11 Aug 2020 10:41:24 +0100 [thread overview]
Message-ID: <cc195a61-c7e2-704e-453e-4ddf5e2ac534@collabora.com> (raw)
In-Reply-To: <93a9ce9310b17517a4985e021524f2d8a0ddc6c6.camel@intel.com>
On 22/07/2019 09:17, Ser, Simon wrote:
> On Mon, 2019-07-22 at 09:03 +0100, Guillaume Tucker wrote:
>> On 15/07/2019 09:13, Arkadiusz Hiler wrote:
>>> On Fri, Jul 12, 2019 at 09:57:17AM +0100, Guillaume Tucker wrote:
>>>> On 08/07/2019 13:21, Arkadiusz Hiler wrote:
>>>>> On Mon, Jul 08, 2019 at 07:25:14AM +0000, Patchwork wrote:
>>>>>> == Series Details ==
>>>>>>
>>>>>> Series: Dockerfile.debian*: Switch over to buster
>>>>>> URL : https://patchwork.freedesktop.org/series/63339/
>>>>>> State : warning
>>>>>>
>>>>>> == Summary ==
>>>>>>
>>>>>> Pipeline status: FAILED.
>>>>>>
>>>>>> See https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/47180 for more details.
>>>>>>
>>>>>> == Logs ==
>>>>>>
>>>>>> For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/47180
>>>>>
>>>>> Seems like it's failing for MIPS realiably:
>>>>>
>>>>> https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/405401
>>>>>
>>>>>
>>>>> One example of many sigsegvs:
>>>>> --- command ---
>>>>> /usr/bin/qemu-mips /builds/gfx-ci/igt-ci-tags/build/lib/tests/igt_invalid_subtest_name
>>>>> --- stdout ---
>>>>> IGT-Version: 1.24-NO-GIT (mips) (Linux: 4.9.0-9-amd64 mips)
>>>>> --- stderr ---
>>>>> (igt_invalid_subtest_name:92) igt_core-CRITICAL: Invalid subtest name "# invalid name !".
>>>>> igt_invalid_subtest_name: ../lib/igt_core.c:1714: igt_exit: Assertion `!test_with_subtests || skipped_one || succeeded_one || failed_one' failed.
>>>>> Received signal SIGABRT.
>>>>> Stack trace:
>>>>> Received signal SIGSEGV.
>>>>> Stack trace:
>>>>> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
>>>>> igt_invalid_subtest_name: ../lib/tests/igt_tests_common.h:46: internal_assert_wsignaled: Assertion `WIFSIGNALED(wstatus) && WTERMSIG(wstatus) == signal' failed.
>>>>> qemu: uncaught target signal 6 (Aborted) - core dumped
>>>>> -------
>>>>>
>>>>> Other architectures seem to be fine and the same thing is passing on
>>>>> stretch.
>>>>>
>>>>> Guillaume, do you have any idea what may be going on before I dig into
>>>>> it?
>>>>
>>>> I've had a look, the segfault is coming from libunwind when
>>>> trying to do a stack trace. The version of libunwind in Debian
>>>> Stretch (1.1) had large parts unimplemented for MIPS, and while
>>>> the one in Buster (1.2.1) seems to be able to fully support that
>>>> it also appears to have a bug causing the segfault.
>>>>
>>>> There have been a few fixes upstream in libunwind for MIPS, maybe
>>>> some of these need to be back-ported to the package in Debian.
>>>> I've built the 1.2.1 version from source and can reproduce the
>>>> problem, I can try the latest version to see if there has been a
>>>> fix for that next week. And if that's the case, ask the Debian
>>>> package maintainer to add some fixes. If the latest upstream
>>>> version still doesn't work, well I guess that would be something
>>>> to report to the MIPS people who worked on libunwind.
>>>>
>>>> Guillaume
>>>
>>> Thanks for investigating this! Poke me here or on the IRC (ivyl) when
>>> you think it might be working with buster. I'll give the series another
>>> spin.
>>
>> Sorry for the slow reply, I've now found a fix for it upstream:
>>
>> https://github.com/libunwind/libunwind/commit/fd44f596b2dad70acdc81cc76983585f888e045d
>>
>> and I've sent a bug report in Debian to ask for this patch to be
>> added to the package in Buster. I don't know how long it will
>> take for this to land but I'll ping you when I get some news.
>
> Excellent. Thanks for this fix and the heads-up! :)
Turned out, it took precisely one year to the day for the
backported fix to get added to the Debian package. I didn't
chase it too hard though as it wasn't a blocker for i-g-t, I
think I could have tried to upload a new package version myself
to speed things up... but I'm not too familiar with that.
So I've just sent a patch to use Buster with the MIPS Docker
image, it passed the pipeline:
https://gitlab.freedesktop.org/gtucker/igt-gpu-tools/-/pipelines/188572
Thanks,
Guillaume
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-08-11 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 6:57 [igt-dev] [PATCH i-g-t] Dockerfile.debian*: Switch over to buster Arkadiusz Hiler
2019-07-08 7:25 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2019-07-08 12:21 ` Arkadiusz Hiler
2019-07-12 8:57 ` Guillaume Tucker
2019-07-15 8:13 ` Arkadiusz Hiler
2019-07-22 8:03 ` Guillaume Tucker
2019-07-22 8:17 ` Ser, Simon
2020-08-11 9:41 ` Guillaume Tucker [this message]
2019-07-08 7:29 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-07-08 7:42 ` [igt-dev] [PATCH i-g-t] " Ser, Simon
2019-07-08 9:43 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
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=cc195a61-c7e2-704e-453e-4ddf5e2ac534@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=simon.ser@intel.com \
/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