console-conf crashes on UC18 on arm64 (dragonboard and pi3 in 64bit mode)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Fix Released
|
Undecided
|
Michael Hudson-Doyle | ||
probert (Ubuntu) |
Fix Released
|
Undecided
|
Michael Hudson-Doyle | ||
Bionic |
Fix Released
|
Critical
|
Michael Hudson-Doyle |
Bug Description
[impact]
We are working on the UC18 release right now. The test images can be found at http://
We ran into the issue that console-conf just crashes. We did some face-to-face debugging in brussels but not much progress there. This bug is mostly so that we can track the issue as this is a release blocker.
[test case]
As above, build an UC18 image, install it on a dragonboard and see if console-conf crashes at start up.
A more targeted test:
1. get yourself an arm64 environment which has a wlan device
2. make sure that device is down (ip link set dev $wlan down)
3. install probert
4. run the "probert" command
if it doesn't segfault, we're good (if it doesn't segfault it will crash with an attributeerror which is a bug but not one that console-conf will run into)
[regression potential]
It's a one line patch that can be observed to be correct. Barring things like a toolchain update causing probert to be miscompiled, there is no potential for regression.
Changed in subiquity: | |
status: | New → In Progress |
assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
tags: | added: id-5bbf6ea4fcb32e19d95e2ec2 |
Changed in subiquity: | |
status: | In Progress → Fix Released |
So I've poked at this a bit and basically failed to get anywhere. How should I go about debugging this? I need to be able to run console-conf under gdb on the dragonboard in an environment that has full access to the wifi device (I tried a bionic lxd container on an ubuntu core 16 system but failed on this last point). I'm a bit out of ideas :(