unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Mark H Weaver <mhw@netris.org>, 43143@debbugs.gnu.org
Subject: bug#43143: Building iwd on armhf triggers kernel panic
Date: Mon, 21 Sep 2020 13:32:08 -0700	[thread overview]
Message-ID: <87a6xirhvb.fsf@ponder> (raw)
In-Reply-To: <87k0xc22gu.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 2775 bytes --]

On 2020-09-02, Mark H Weaver wrote:
> Vagrant Cascadian <vagrant@debian.org> writes:
>> On 2020-08-31, Vagrant Cascadian wrote:
>>> On 2020-08-31, Mark H. Weaver wrote:
>>>> Vagrant Cascadian <vagrant@debian.org> writes:
>>>>> I've been getting kernel panics when i try to build iwd, a dependency of
>>>>> network-manager.
>>>>
>>>> Which kernel package variant(s) and version(s) have you seen panic when
>>>> building iwd?  What hardware?
>>>
>>> The hardware is veryron-speedy (a.k.a. asus chromebook c201p), with a
>>> rockchip rk3288 CPU and 4GB of ram; I might be able to test on
>>> additional hardware at some point (I've got a pretty old guix install on
>>> a novena, but don't recall if it was in good working order last time it
>>> booted).
>
> That message went on to say the following, although you omitted it here:
>
>>> linux-libre-arm-generic@5.4 5.4.57, and presumably older versions as
>>> well, as I had commits in my local guix from mid June disabling iwd on
>>> network-manager.
>
>> Ok, managed to build iwd just fine on a novena imx6 platform, running
>> armhf on "linux-libre" 5.4.25 (haven't yet finished upgrading the
>> system).
>>
>> So it appears to potentially be hardware-specific? The imx6 vs. rk3288
>> are pretty different platforms;
>
> Based on what you wrote, it sounds like it could either be a
> hardware-specific problem, or else a kernel-configuration-specific
> problem, since you used radically different kernel configurations in
> these two cases.
>
> If I understand correctly, 'linux-libre-arm-generic@5.4' is the variant
> that panicked on an rk3288, whereas the 'linux-libre@5.4' variant with
> our hand-crafted default configuration worked on an imx6.
>
> I don't know whether it's possible to use precisely the same kernel
> configuration on these two systems.  Anyway, it would be helpful to
> retry the 'iwd' build on these two devices with kernel versions and
> configurations that are identical except for a minimal set of required
> differences.  That would help us narrow down the set of possible causes
> for this kernel panic.

Sorry for the late follow-up...

Using a more recent version of linux-libre-arm-generic@5.4, it failed to
build on both the veyron-speedy (rk3288) and the novena (imx6). It
doesn't necessarily *always* trigger a kernel panic; I haven't
identified which conditions trigger the kernel panic, but so far I've
only seen them on the veyron-speedy. I haven't seen it successfully
build with any recent linux-libre-arm-generic kernel, though recent
linux-libre@5.4 and @5.8 worked.

So it seems something in iwd needs specific kernel features in order to
build at all...

Not sure when I'll get a chance to debug further, but figured I'd update
about what I've tried so far.

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-09-21 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 23:26 bug#43143: Building iwd on armhf triggers kernel panic Vagrant Cascadian
2020-09-01  1:13 ` Mark H Weaver
2020-09-01  5:40   ` Vagrant Cascadian
2020-09-02  3:02     ` Vagrant Cascadian
2020-09-02  5:04       ` Mark H Weaver
2020-09-21 20:32         ` Vagrant Cascadian [this message]
2022-09-29  0:26           ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6xirhvb.fsf@ponder \
    --to=vagrant@debian.org \
    --cc=43143@debbugs.gnu.org \
    --cc=mhw@netris.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).