This is now fixed on zesty and xenial stable-phone-overlay PPA, but
notably not on normal xenial. xenial SRUs could still be affected,
although SRUs having affected tests run during build time might be rare.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: ubuntu-push-qml (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1630906
Title:
QML segfault on arm64 due to builder kernel change
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Status: In Progress => Fix Released
** Changed in: unity8 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: online-accounts-api (Ubuntu)
Status: New =>
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages,
(...and meanwhile the workarounded builder kernel not using the new
setting is still required)
** Also affects: qtdeclarative-opensource-src (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Status: New => Triaged
--
You
This is fixed in zesty in Qt 5.7.1.
It should be eventually part of also LTS Qt 5.6.3 release some time
later in first half of 2017.
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
It looks like I’m being bit by this problem again. Building webbrowser-
app packages fails on xenial+overlay arm64. Tests that execute QML code
segfault. Attaching a log file.
Note that the same tests all pass when building on zesty arm64.
** Attachment added:
It sounded to me the old value would be around 41 or so, and the
motivation to increase was a need to have it only slightly bigger?
Meanwhile, the Qt patch is about freeing "2 more bits" so maybe 46 or 47
would work too, unless 48 is the magical "good" value that is wanted to
be had.
--
You
The kernel running on the builders is a custom fork at the moment, which
isn't a good long-term situation, so please don't mark the kernel task
here as Fix Released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
As per the agreement, the xenial-based builders seem to be now running a
newer custom kernel (4.4.0-42-generic) that seems to no longer segfault
on QML code for arm64.
I suppose we can set the kernel task as Fix Released? Since I suppose
CONFIG_ARM64_VA_BITS=48 is the right way to go, with Qt
I've now also asked on #ubuntu-kernel if CONFIG_ARM64_VA_BITS=48 is here
to stay for the 4.4 kernel or not, pointing to this bug. It sounds like
no-one is currently considering going back to the 4.2 kernel on the
arm64 builders at least.
Meanwhile I'm collecting rebuilds of
Otherwise "ok" so far regarding rebuilds but unmodified UITK starts to
fail two subtests on arm64: bug #1631941. Those did pass before the
builder kernel update, and it's now not sure where those new failures
come from. But they do happen on both xenial and yakkety:
> Unfortunately the upstream fix seems to, while fixing arm64, cause
segfaults in Unity 8 on armhf and i386:
It seems we need rebuilds of everything that uses qtdeclarative-private
internal headers as those changed.
--
You received this bug notification because you are a member of Kernel
Unfortunately the upstream fix seems to, while fixing arm64, cause
segfaults in Unity 8 on armhf and i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-2055/yakkety/armhf/u/unity8/20161007_180848@/log.gz
The linux kernel part of this is setting of CONFIG_ARM64_VA_BITS=48.
Also reverting of just that in the 4.4 kernel would work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1630906
xenial and yakkety needed symbol updates but now they have compiled and
work at least on desktop, and the arm64 build finished so it's likely
the arm64 build issue would be solved now. I've asked QA to look into
it.
--
You received this bug notification because you are a member of Kernel
Albert pointed to https://codereview.qt-project.org/#/c/169892
-> https://bileto.ubuntu.com/#/ticket/2055 (xenial and yakkety currently
building)
I need to stop for today but if someone has time please check if 5.4
backport is possible.
--
You received this bug notification because you are a
Correction to the code url:
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/qml/jsruntime/qv4object.cpp?h=5.6.2#n184
(5.6.1 branch doesn't exist over there, but code seems unchanged)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
For completeness, also the other copy-pastes I made:
Thread 1 "qmlplugindump" received signal SIGSEGV, Segmentation fault.
QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
184 jsruntime/qv4object.cpp: No such file or
I got a temporary access (now revoked) to an arm64 box where I could
reproduce the segfault by running qmlplugindump.
Here's the backtrace:
QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
184 jsruntime/qv4object.cpp: No such
This happens in launchpad builders. I don't think it is possible for us
to log in and run apport-collect. Also there are many logs linked in the
bug description. Putting back to Confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
21 matches
Mail list logo
