Github messages for voidlinux
 help / color / mirror / Atom feed
From: BikyAlex <BikyAlex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Segmentation fault by insert zfs module
Date: Fri, 10 Feb 2023 06:18:32 +0100	[thread overview]
Message-ID: <20230210051832.mvr_6Weh5gAvoU4NvevuaWcN5rutsV6BHkegxVD90bA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41613@inbox.vuxu.org>

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

New comment by BikyAlex on void-packages repository

https://github.com/void-linux/void-packages/issues/41613#issuecomment-1425187443

Comment:
I might start looking into this, no promise though. I might just use 5.10 with zfs anyway. I was having issues with building zfs-dkms on aarch64 in the first place, until I found some tools on github that were required to build it, but it was getting segfault on modprobe on my system with 5.15, 5.16, 5.18, 5.19 and 6.0.

I don't think I tried 5.10, it's worth a short if I can get the odroid hc4 to work. If not, I might just use the armbian kernel, build it on that, and then booting void using armbian's kernel (I did this before to get void bootstrapped, but I never got zfs-dkms on armbian to work either, also because of the missing aarch64-tools script).

I might be able to strace what the module is doing when `modprobe`'d, but I'm not sure if I can actually fix it, I'm only a shell script kiddie.

      reply	other threads:[~2023-02-10  5:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  9:06 [ISSUE] " ckyoog
2023-02-10  5:18 ` BikyAlex [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

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

  git send-email \
    --in-reply-to=20230210051832.mvr_6Weh5gAvoU4NvevuaWcN5rutsV6BHkegxVD90bA@z \
    --to=bikyalex@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).