Package Details: linux-next-git 20240417.r0.g4eab35893071-1

Git Clone URL: https://aur.archlinux.org/linux-next-git.git (read-only, click to copy)
Package Base: linux-next-git
Description: The Linux NEXT kernel and modules
Upstream URL: http://www.kernel.org/
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: Nefelim4ag
Maintainer: sir_lucjan (ptr1337)
Last Packager: sir_lucjan
Votes: 17
Popularity: 0.006556
First Submitted: 2014-10-12 19:04 (UTC)
Last Updated: 2024-04-17 16:06 (UTC)

Dependencies (15)

Required by (7)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »

gamezelda commented on 2021-10-08 20:25 (UTC)

Since recently I've had to add the resolve_btfids tool in order to build external (DKMS) modules:

   # add objtool for external module building and enabled VALIDATION_STACK option
   install -Dt "$builddir/tools/objtool" tools/objtool/objtool
+  install -Dt "$builddir/tools/bpf/resolve_btfids" tools/bpf/resolve_btfids/resolve_btfids

   # add xfs and shmem for aufs building

catman commented on 2021-08-23 04:02 (UTC)

@sir_lucjan

works now. thanks.

sir_lucjan commented on 2021-08-21 18:15 (UTC)

@catman

Could you try now? I've disabled html docs.

catman commented on 2021-08-21 00:58 (UTC)

Sphinx parallel build error: docutils.utils.SystemMessage: /home/catman/linux-next-git/src/linux-next/Documentation/powerpc/associativity.rst:1: (SEVERE/4) Title overline & underline mismatch.

Ttz_ztT commented on 2021-01-12 16:45 (UTC) (edited on 2021-01-15 07:14 (UTC) by Ttz_ztT)

@habys : same here. builds fine, doesn't want to boot. with an almost identical entry for /boot (nvme0n1p1 instead) on booting kernel.

dmesg gives lots of "BPF:No data" and "failed to validate module [crc*] BTF: -22" ?

The only difference I see in dmesg is that -next finds a numa node on my ryzen 3xxx now...

Edit: 210115 works.

habys commented on 2021-01-09 16:39 (UTC)

This is building for me. Anyone else having their system die as I can't manage to mount /boot? (wrong fs type, bad option, bad superblock).

From my working kernel I see: /dev/nvme1n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

eggz commented on 2020-12-07 01:46 (UTC)

confirmed for my part (rc7). revert that commit and the (upstream) kernels wil build. Lets hope upstream will wake up to this soon.

sir_lucjan commented on 2020-12-06 23:41 (UTC)

I suspect that this is the culprit.

https://github.com/torvalds/linux/commit/3351b16af4946fff0d46481d155fb91adb28b1

eggz commented on 2020-12-06 23:36 (UTC)

Looks like upstream has done nothing yet. This error is now also present in linux v5.10-rc7