unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Mark H Weaver <mhw@netris.org>, 43143-done@debbugs.gnu.org
Subject: bug#43143: Building iwd on armhf triggers kernel panic
Date: Wed, 28 Sep 2022 20:26:53 -0400	[thread overview]
Message-ID: <875yh7qb3m.fsf@gmail.com> (raw)
In-Reply-To: <87a6xirhvb.fsf@ponder> (Vagrant Cascadian's message of "Mon, 21 Sep 2020 13:32:08 -0700")

Hello,

[...]

> 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.

Bordeaux managed to build it, according to 'guix weather
--system=armhf-linux iwd', hence I'm closing this old forgotten issue.
Please reopen if you still experience it on a standard Guix System
kernel.

Thanks,

Maxim




      reply	other threads:[~2022-09-29  0:28 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
2022-09-29  0:26           ` Maxim Cournoyer [this message]

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=875yh7qb3m.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=43143-done@debbugs.gnu.org \
    --cc=mhw@netris.org \
    --cc=vagrant@debian.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).