Github messages for voidlinux
 help / color / mirror / Atom feed
From: gtryujb <gtryujb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ZFS module does not compile with 6.2.8_1
Date: Sat, 25 Mar 2023 15:04:20 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43013@inbox.vuxu.org> (raw)

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

New issue by gtryujb on void-packages repository

https://github.com/void-linux/void-packages/issues/43013

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.21_1 x86_64 GenuineIntel uptodate rrrrmmnFFFFFF

### Package(s) Affected

zfs-2.1.9_1 linux6.2-6.2.8_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The module compiles and installs.

### Actual behaviour

The ZFS module fails to compile against 6.2.8_1.

`xbps-reconfigure -f linux6.2`:
```
linux6.2: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: nvidia-525.89.02.
Available DKMS module: zfs-2.1.9.
Building DKMS module: nvidia-525.89.02... done.
Building DKMS module: zfs-2.1.9... FAILED!
Generating kernel module dependency lists... done.
Executing post-install kernel hook: 20-initramfs ...
dracut-install: Failed to find module 'zfs'
dracut: FAILED:  /usr/lib/dracut/dracut-install -D /var/tmp/dracut.b8v8th/initramfs --kerneldir /lib/modules/6.2.8_1/ -m zfs
dracut: installkernel failed in module zfs
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.2.8_1
Found linux image: /boot/vmlinuz-6.1.21_1
Found initrd image: /boot/initramfs-6.1.21_1.img
Found linux image: /boot/vmlinuz-6.1.19_1
Found initrd image: /boot/initramfs-6.1.19_1.img
Found linux image: /boot/vmlinuz-5.19.17_1
Found initrd image: /boot/initramfs-5.19.17_1.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
linux6.2: configured successfully.
```

End of `/var/lib/dkms/zfs/2.1.9/build/make.log`:
```
  LD [M]  /var/lib/dkms/zfs/2.1.9/build/module/zstd/zzstd.o  
  LD [M]  /var/lib/dkms/zfs/2.1.9/build/module/zfs/zfs.o
  MODPOST /var/lib/dkms/zfs/2.1.9/build/module/Module.symvers
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_start_io_acct'
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_end_io_acct_remapped'
make[2]: *** [scripts/Makefile.modpost:138: /var/lib/dkms/zfs/2.1.9/build/module/Module.symvers] Error 1
make[1]: *** [Makefile:1973: modpost] Error 2
make[1]: Leaving directory '/usr/src/kernel-headers-6.2.8_1'
make: *** [Makefile:55: modules-Linux] Error 2
make: Leaving directory '/var/lib/dkms/zfs/2.1.9/build/module'
```

### Steps to reproduce

1. `xbps-reconfigure -f linux6.2`

             reply	other threads:[~2023-03-25 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25 14:04 gtryujb [this message]
2023-03-25 16:30 ` classabbyamp
2023-03-28 18:56 ` adrian-bl
2023-03-31 17:56 ` [ISSUE] [CLOSED] " ahesford
2023-03-31 17:56 ` ahesford

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43013@inbox.vuxu.org \
    --to=gtryujb@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).