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, 31 Aug 2020 22:40:05 -0700 [thread overview]
Message-ID: <87h7sirr62.fsf@ponder> (raw)
In-Reply-To: <878sdufgdu.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
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).
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.
I've had issues booting linux-libre 5.6+ on this hardware, and struggled
to get the right initrd modules to use the regular "linux-libre"
variant, though in theory that should also be possible, but might
require additional kernel config options, and I'd like to postpone
exploring those rabbit holes for the moment...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-09-01 5:41 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 [this message]
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
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=87h7sirr62.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).