You are not logged in.

#1 2022-08-14 12:58:51

perseus
Member
Registered: 2007-01-28
Posts: 152

Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

I have two machines, a  desktop (homebuilt about 8 years old) and a laptop HP Pavilion (2018).  Obviously very different hardware and I won't bloat this post with details unless someone asks. Both run current kernels and always have. I almost always update with my Syu on the day of release.  I boot using syslinux, which has always suited me. Both machines have /boot on a separate partition, and everything else ( / ) on the other partition.

I installed the new kernel on both about 6am this morning UK time. On reboot, both went into endless boot loops. I backup the desktop to a hard drive, but never the laptop (nothing mission critical on it). So I set about booting from the desktop backup and reinstalling 5.18.16-arch1 on it.  (I keep two prior versions of everything locally.) That took some time, because I don't keep it configured as a working drive (years since that was the case), but here I am now.

I guess that I will have to recover the laptop with a live USB or some such, but it will take time to make one.

/boot contains:
EFI (dir)
syslinux (dir)
intramfs-linux-fallback.img
intramfs-linux.img
intel-ucode.img
vmlinuz.linux


Relevant stanzas from syslinux.cfg

LABEL Arch_with_microcode
    MENU LABEL Arch_with_microcode
    LINUX ../../vmlinuz-linux
    APPEND root=/dev/sda2 rw acpi_enforce_resources=lax
    INITRD ../../intel-ucode.img,../../initramfs-linux.img

LABEL arch
    MENU LABEL Arch_without_microcode
    LINUX ../../vmlinuz-linux
    APPEND root=/dev/sda2 rw acpi_enforce_resources=lax
    INITRD ../../initramfs-linux.img

LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../../vmlinuz-linux
    APPEND root=/dev/sda2 rw acpi_enforce_resources=lax
    INITRD ../../initramfs-linux-fallback.img

Apart from one (possible) post here (Kernel panic on boot by palmighty), I can't find any other instances of this problem, which must (I suppose), be due to my own (mis?)configuration of both machines. I am baffled and looking for clues / initial advice please.

Offline

#2 2022-08-14 14:36:38

seth
Member
Registered: 2012-09-03
Posts: 33,644

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

> Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1
> both went into endless boot loops

Which one is it?
Can you boot the multi-user.target? (2nd link below)
If it "locks", can you reboot w/ frenetically™ pressing ctrl+alt+del ? (At some point systemd interprets that as "user wants to really reboot")

The LTS kernel will likely allow you to boot the system w/o the need of further downgrades.

Offline

#3 2022-08-14 15:30:26

perseus
Member
Registered: 2007-01-28
Posts: 152

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

seth wrote:

> Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1
> both went into endless boot loops

Which one is it?
Can you boot the multi-user.target? (2nd link below)
If it "locks", can you reboot w/ frenetically™ pressing ctrl+alt+del ? (At some point systemd interprets that as "user wants to really reboot")

The LTS kernel will likely allow you to boot the system w/o the need of further downgrades.

Thanks for the helpful response Seth, and sorry for the lack of clarity.

As to which one it is. The machines would boot to the syslinux menu with a 5 second countdown before defaulting to the first entry. Assume I let that run down, so that it boots to "Arch_with_microcode" . In the bottom left corner of the screen, appearing and disappearing too fast to read properly, photograph or video, I see (I think)

Loading intramfs-linux.img ok
Loading intel-ucode.img ok
Loading vmlinuz.linux ok

The screen clears momentarily, then the syslinux menu appears again.  This repeats until I press the powerdown button.

I can select from the menu, but (again I think), I see the "Loading" entries relevant to the option - but they all revert to the same loop and I can exit only by powering down. The ctrl-alt-del frantic repetition doesn't help - but I don't suppose that, given the above, you would expect it to.

Incidentally, I never boot into a graphical environment. I boot to a terminal before starting fluxbox. A bit old-fashioned, but it has worked for me for a long time now.

If I am understanding your multi-user.target point - I don't think I can get that far, but I am responding quickly and will study more.

I was thinking of LTS - I have used it before, but it just seems so weird to me that two different machines, one of them not so old, that share the same boot configuration here, exhibit the same catastrophic problem - when nobody else (I can find), has it with this kernel.

Unless you have a different suggestion, my next step will be to create that live USB or rescue kit of some kind, just to get back into the laptop,.

Offline

#4 2022-08-14 19:15:23

seth
Member
Registered: 2012-09-03
Posts: 33,644

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

If you get the UEFI/BIOS post before returning to syslinux, this would be an actual reboot (the multi-user.target would have been more interesting if the system had "locked", in case that meant "my GUI doesn't start")
Why is there "acpi_enforce_resources=lax" and what if you remove that (or use the default "strict")?
Some driver writing into the ACPI could easily trigger a reboot.

Offline

#5 2022-08-14 21:14:57

perseus
Member
Registered: 2007-01-28
Posts: 152

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

Thanks again Seth.

I found that I the Tab can still be used to interrupt the boot and edit the appended text. Bad news is that it made no difference. I did also try using it to experiment with the systemd targets you suggest, but also to no avail.

Some of the contents of those appends have been there for years, there was a reason at the time, and the computers didn't suffer, so nothing changed. The more I think about it, and do more research now, the more I think that the issue simply must lie with my use / configuration of syslinux.

I haven't had time today to make a rescue USB, but when I can, I will use it to reconfigure syslinux entirely on the laptop and use that as a testbed.  I don't want to do that immediately on the desktop, because I rely on it for daily work.

I will report back when I have (hopefully),  made progress.

Offline

#6 2022-08-15 20:25:49

seth
Member
Registered: 2012-09-03
Posts: 33,644

Offline

#7 2022-08-16 14:05:41

msrd0
Member
From: Germany
Registered: 2015-10-18
Posts: 6

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

I have the same problem, Kernel 5.19.1 (neither official nor zen version) can boot. Both on my laptop (Acer Spin 3) and my desktop (Ryzen 3900X / Radeon RX 570) bootloop infinitely, i.e. once syslinux starts the kernel, I get an immediate reboot. Loading an Arch Install Stick, installing linux-lts kernel, and booting from that works perfectly.

Offline

#8 2022-08-16 19:56:21

Substring
Member
Registered: 2022-02-20
Posts: 5

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

Hi,

I'm having the same problem almost and have been able to target linux 5.19 as the culprit. I've been throughly testing the archlinux installation on Virtual Box + UEFI + syslinux. The syslinux + kernel 5.19 crashes the EFI boot, had to downgrade to 5.18.9 to get a working arch install

Offline

#9 2022-08-16 21:36:39

loqs
Member
Registered: 2014-03-06
Posts: 15,505

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

https://drive.google.com/file/d/16XVhtz … sp=sharing linux-5.19.1-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1qQQnat … sp=sharing linux-headers-5.19.1-1-x86_64.pkg.tar.zst

5.19.1 using the config from 5.18.16-arch1 + make olddefconfig.  Any difference from 5.19.1.arch2-1?

Offline

#10 2022-08-17 12:58:53

Maelstr0m
Member
Registered: 2014-06-17
Posts: 1

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

Same problem as everyone here on an Asus N76VM laptop, with multiple lvm partitions.
Instant reboot after syslinux tries to start the kernel.
Downgrading the linux kernel and headers to 5.18.6 fixed the issue.

Offline

#11 2022-08-17 14:00:05

BwK
Member
Registered: 2019-09-25
Posts: 14

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

loqs wrote:

https://drive.google.com/file/d/16XVhtz … sp=sharing linux-5.19.1-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1qQQnat … sp=sharing linux-headers-5.19.1-1-x86_64.pkg.tar.zst

5.19.1 using the config from 5.18.16-arch1 + make olddefconfig.  Any difference from 5.19.1.arch2-1?

No difference with these packages. Another thing I copied this time before rebooting: After updating linux-headers, the DKMS modules are updated. On 5.19 the openafs module fails:

:: Post-transaction-Hooks werden gestartet …
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Install DKMS modules
==> dkms install --no-depmod evdi/1.11.0 -k 5.19.1-1
==> dkms install --no-depmod vboxhost/6.1.36_OSE -k 5.19.1-1
==> dkms install --no-depmod openafs/1.8.8.1 -k 5.19.1-1
Error! Bad return status for module build on kernel: 5.19.1-1 (x86_64)
Consult /var/lib/dkms/openafs/1.8.8.1/build/make.log for more information.
==> WARNING: `dkms install --no-depmod openafs/1.8.8.1 -k 5.19.1-1' exited 10
==> depmod 5.19.1-1

I am not sure if this is related to the issue. I expect that I would have to recompile openapfs with the new kernel for this to work. Anyway, here is the according log:

DKMS make.log for openafs-1.8.8.1 for kernel 5.19.1-1 (x86_64)
Mi 17. Aug 15:46:50 CEST 2022
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/time.h... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for grep that handles long lines and -e... /usr/bin/grep
checking for gcc options needed to detect all undeclared functions... none needed
checking how to run the C preprocessor... gcc -E
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libxslt... no
checking for saxon... no
checking for xalan-j... no
checking for xsltproc... xsltproc
checking for fop... no
checking for dblatex... no
checking for docbook2pdf... no
configure: WARNING: Docbook stylesheets not found; some documentation can't be built
checking for kindlegen... no
checking for doxygen... doxygen
checking for dot... dot
checking for library containing strerror... none required
checking for pid_t... yes
checking for size_t... yes
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for bison... bison -y
checking for flex... flex
checking for lex output file root... lex.yy
checking for lex library... none needed
checking for library containing yywrap... no
checking whether yytext is a pointer... yes
checking if lex is flex... yes
checking whether byte order is known at compile time... yes
checking whether byte ordering is bigendian... no
checking whether printf understands the %z length modifier... yes
checking your OS... linux
checking your AFS sysname... amd64_linux26
checking for ranlib... (cached) ranlib
checking for as... as
checking for mv... mv
checking for rm... rm
checking for ld... ld
checking for cp... cp
checking for gencat... gencat
checking if gcc accepts -march=pentium... no
checking if gcc needs -fno-strength-reduce... yes
checking if gcc needs -fno-strict-aliasing... yes
checking if gcc supports -fno-common... yes
checking if gcc supports -pipe... yes
checking if linux kbuild requires EXTRA_CFLAGS... no
checking if linux kernel module build works... yes
checking operation follow_link in inode_operations... no
checking operation put_link in inode_operations... no
checking operation rename in inode_operations... no
checking operation create in inode_operations... yes
checking for linux/cred.h... yes
checking for linux/config.h... no
checking for linux/exportfs.h... yes
checking for linux/freezer.h... yes
checking for linux/key-type.h... yes
checking for linux/semaphore.h... yes
checking for linux/seq_file.h... yes
checking for linux/sched/signal.h... yes
checking for linux/uaccess.h... yes
checking for linux/stdarg.h... yes
checking for struct vfs_path... no
checking for kuid_t... yes
checking for struct proc_ops... yes
checking for time_t... no
checking for backing_dev_info in struct address_space... no
checking for write_begin in struct address_space_operations... yes
checking for dirty_folio in struct address_space_operations... yes
checking for readahead in struct address_space_operations... yes
checking for name in struct backing_dev_info... no
checking for session_keyring in struct cred... yes
checking for ctl_name in struct ctl_table... no
checking for d_u.d_alias in struct dentry... yes
checking for d_automount in struct dentry_operations... yes
checking for gid in struct group_info... yes
checking for i_alloc_sem in struct inode... no
checking for i_blkbits in struct inode... yes
checking for i_blksize in struct inode... no
checking for i_mutex in struct inode... no
checking for i_security in struct inode... yes
checking for f_path in struct file... yes
checking for flock in struct file_operations... yes
checking for iterate in struct file_operations... yes
checking for read_iter in struct file_operations... yes
checking for sendfile in struct file_operations... no
checking for mount in struct file_system_type... yes
checking for truncate in struct inode_operations... no
checking for get_link in struct inode_operations... yes
checking for payload.value in struct key... no
checking for instantiate_prep in struct key_type... no
checking for match_preparse in struct key_type... yes
checking for preparse in struct key_type... yes
checking for msg_iter in struct msghdr... yes
checking for path in struct nameidata... no
checking for owner in struct proc_dir_entry... no
checking for proc_compat_ioctl in struct proc_ops... yes
checking for s_bdi in struct super_block... yes
checking for s_d_op in struct super_block... yes
checking for alloc_inode in struct super_operations... yes
checking for evict_inode in struct super_operations... yes
checking for cred in struct task_struct... yes
checking for exit_state in struct task_struct... yes
checking for parent in struct task_struct... yes
checking for real_parent in struct task_struct... yes
checking for rlim in struct task_struct... no
checking for sig in struct task_struct... no
checking for sighand in struct task_struct... yes
checking for sigmask_lock in struct task_struct... no
checking for tgid in struct task_struct... yes
checking for thread_info in struct task_struct... yes
checking for total_link_count in struct task_struct... no
checking for signal->rlim in struct task_struct... yes
checking for buf in read_descriptor_t... no
checking for __vfs_write... no
checking for kernel_write... yes
checking for bdi_init... no
checking for super_setup_bdi... yes
checking for PageChecked... yes
checking for PageFsMisc... no
checking for clear_inode... yes
checking for current_kernel_time... no
checking for d_alloc_anon... yes
checking for d_count... yes
checking for d_make_root... yes
checking for do_sync_read... no
checking for fatal_signal_pending... yes
checking for file_dentry... yes
checking for find_task_by_pid... no
checking for generic_file_aio_read... no
checking for grab_cache_page_write_begin... no
checking for hlist_unhashed... yes
checking for ihold... yes
checking for i_size_read... yes
checking for inode_setattr... no
checking for iter_file_splice_write... yes
checking for kernel_setsockopt... no
checking for ktime_get_coarse_real_ts64... yes
checking for ktime_get_real_ts64... yes
checking for locks_lock_file_wait... yes
checking for override_creds... yes
checking for page_follow_link... no
checking for page_get_link... yes
checking for page_offset... yes
checking for pagevec_lru_add_file... no
checking for path_lookup... no
checking for proc_create... yes
checking for rcu_read_lock... no
checking for set_nlink... yes
checking for setattr_prepare... no
checking for sock_create_kern... no
checking for sock_create_kern_ns... yes
checking for splice_direct_to_actor... yes
checking for default_file_splice_read... no
checking for svc_addr_in... yes
checking for zero_user_segments... yes
checking for noop_fsync... yes
checking for kthread_run... yes
checking for inode_nohighmem... yes
checking for inode_lock... yes
checking for lru_cache_add_file... no
checking for in_compat_syscall... yes
checking for lru_cache_add... yes
checking for ip_sock_set... yes
checking for kthread_complete_and_exit... yes
checking for non-vectorized aio kernel functions... yes
checking if proc_root_fs is defined and exported... no
checking for new kmem_cache init function parameters... no
checking whether kmem_cache_t exists... no
checking whether kmem_cache_create takes a destructor argument... no
checking whether kmem_cache_create constructor takes a void pointer... yes
checking if d_path() takes a struct path argument... yes
checking if kernel uses new export ops... yes
checking for inode_setattr return type... no
checking whether struct iattr->ia_ctime takes struct timespec64 or 32-bit struct timespec... yes
checking whether inode_operations.create takes a nameidata... no
checking whether inode_operations.lookup takes a nameidata... no
checking whether inode_operations.permission takes flags... no
checking whether inode_operations.permission takes a nameidata... no
checking whether inode_operations.put_link takes an opaque cookie... no
checking whether dentry.d_op->d_delete takes a const argument... yes
checking whether dentry_operations.d_revalidate takes a nameidata... no
checking whether file_operations.flush takes a fl_owner_t... yes
checking whether file_operations.fsync takes a dentry argument... no
checking whether file_operations.fsync takes a range... yes
checking whether aop.writepage takes a writeback_control... yes
checking for splice_write and splice_read in struct file_operations... yes
checking for 3rd argument in posix_lock_file found in new kernels... yes
checking for 2nd argument in pagevec_init found in pre-4.15 kernels... no
checking if posix_test_lock returns a struct file_lock... no
checking if posix_test_lock takes a conflict argument... no
checking for 5th argument in sock_create found in some SELinux kernels... no
checking for exported key_type_keyring... yes
checking for redhat kernel configuration... no
checking for recalc_sigpending arg type... yes
checking for exported tasklist_lock... yes
checking for struct vfsmount * in get_sb_nodev()... no
checking for dentry in statfs... yes
checking whether refrigerator takes PF_FREEZE... no
checking for try_to_freeze... yes
checking for linux kernel keyring support... yes
checking if key_alloc() takes a struct task *... no
checking if key_alloc() takes credentials... no
checking whether INIT_WORK has a _data argument... no
checking whether register_sysctl_table has an insert_at_head argument... yes
checking for dcache_lock... no
checking if dentry->d_count is an int... no
checking whether 4.11+ inode.i_op->getattr takes a struct path argument... no
checking whether inode.i_op->mkdir takes a umode_t argument... no
checking whether inode.i_op->create takes a umode_t argument... no
checking whether export operation encode_fh takes inode arguments... yes
checking whether kmap_atomic takes no km_type argument... yes
checking whether dentry_open takes a path argument... yes
checking whether dentry->d_alias is an hlist... yes
checking whether hlist iterators don't need a node parameter... yes
checking whether inode_operations.create takes a bool... no
checking whether dentry_operations.d_revalidate takes an unsigned int... yes
checking whether inode operation lookup takes an unsigned int... yes
checking whether d_invalidate returns void... yes
checking whether offset is the last argument to kernel_read... yes
checking whether keyring_search has the recurse parameter... yes
checking if compiler has __sync_add_and_fetch... yes
checking if struct sockaddr has sa_len field... no
checking for library containing socket... none required
checking for library containing connect... none required
checking for library containing gethostbyname... none required
checking for the useability of arpa/nameser_compat.h... yes
checking for res_search... yes
checking for retransmit support in res_state... yes
checking for setsockopt(, SOL_IP, IP_RECVERR)... yes
checking for pthread_attr_init in -lpthread... yes
checking for tivoli tsm butc support... no
checking for egrep... /usr/bin/grep -E
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for arpa/inet.h... yes
checking for arpa/nameser.h... yes
checking for curses.h... yes
checking for direct.h... no
checking for errno.h... yes
checking for fcntl.h... yes
checking for grp.h... yes
checking for math.h... yes
checking for mntent.h... yes
checking for ncurses.h... yes
checking for ncurses/ncurses.h... no
checking for netdb.h... yes
checking for netinet/in.h... yes
checking for pthread_np.h... no
checking for pwd.h... yes
checking for regex.h... yes
checking for security/pam_appl.h... yes
checking for signal.h... yes
checking for stdint.h... (cached) yes
checking for stdio_ext.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/bitypes.h... yes
checking for sys/bswap.h... no
checking for sys/dk.h... no
checking for sys/fcntl.h... yes
checking for sys/file.h... yes
checking for sys/fs_types.h... no
checking for sys/fstyp.h... no
checking for sys/ioctl.h... yes
checking for sys/ipc.h... yes
checking for sys/lockf.h... no
checking for sys/map.h... no
checking for sys/mount.h... yes
checking for sys/mntent.h... no
checking for sys/mnttab.h... no
checking for sys/pag.h... no
checking for sys/param.h... yes
checking for sys/resource.h... yes
checking for sys/select.h... yes
checking for sys/statfs.h... yes
checking for sys/statvfs.h... yes
checking for sys/socket.h... yes
checking for sys/sysctl.h... no
checking for sys/time.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/uio.h... yes
checking for sys/un.h... yes
checking for sys/vfs.h... yes
checking for syslog.h... yes
checking for termios.h... yes
checking for time.h... yes
checking for ucontext.h... yes
checking for unistd.h... (cached) yes
checking for windows.h... no
checking for resolv.h... yes
checking for net/if.h... yes
checking for netinet/if_ether.h... yes
checking for security/pam_modules.h... yes
checking for linux/errqueue.h... yes
checking for fsblkcnt_t... yes
checking for struct stat.st_ctimespec... no
checking for struct stat.st_ctimensec... no
checking for libintl... no
checking for arc4random... yes
checking for closelog... yes
checking for fcntl... yes
checking for fseeko64... yes
checking for ftello64... yes
checking for getcwd... yes
checking for getegid... yes
checking for geteuid... yes
checking for getgid... yes
checking for getuid... yes
checking for getrlimit... yes
checking for issetugid... no
checking for mkstemp... yes
checking for openlog... yes
checking for poll... yes
checking for pread... yes
checking for preadv... yes
checking for preadv64... yes
checking for pwrite... yes
checking for pwritev... yes
checking for pwritev64... yes
checking for regcomp... yes
checking for regerror... yes
checking for regexec... yes
checking for setitimer... yes
checking for setvbuf... yes
checking for sigaction... yes
checking for strcasestr... yes
checking for strerror... yes
checking for sysconf... yes
checking for sysctl... no
checking for syslog... yes
checking for tdestroy... yes
checking for timegm... yes
checking for usable system libroken... no
checking for usable system libhcrypto... no
checking for initscr in -lncurses... yes
checking for LINES in -lncurses... yes
configure: checking for curses library... -lncurses
(cached) configure: checking for curses library... -lncurses
checking getmaxyx macro... yes
checking for __attribute__... yes
checking for _Pragma... yes
checking for _Pragma recognition of -Wtautological-pointer-compare... yes
checking for chown... yes
checking for fchown... yes
checking for gethostname... yes
checking for lstat... yes
checking for inet_aton... yes
checking for putenv... yes
checking for readv... yes
checking for setenv... yes
checking for strdup... yes
checking for strftime... yes
checking for strndup... yes
checking for strsep... yes
checking for unsetenv... yes
checking for asprintf... yes
checking for asnprintf... no
checking for vasprintf... yes
checking for vasnprintf... no
checking for vsnprintf... yes
checking for snprintf... yes
checking for daemon... yes
checking for ecalloc... no
checking for emalloc... no
checking for erealloc... no
checking for err... yes
checking for errx... yes
checking for flock... yes
checking for freeaddrinfo... yes
checking for gai_strerror... yes
checking for getaddrinfo... yes
checking for getdtablesize... yes
checking for getnameinfo... yes
checking for getopt... yes
checking for getprogname... no
checking for gettimeofday... yes
checking for inet_ntop... yes
checking for inet_pton... yes
checking for localtime_r... yes
checking for mkstemp... (cached) yes
checking for setenv... (cached) yes
checking for setprogname... no
checking for strcasecmp... yes
checking for strlcat... no
checking for strnlen... yes
checking for strlcpy... no
checking for strsep... (cached) yes
checking for tdelete... yes
checking for tfind... yes
checking for tsearch... yes
checking for twalk... yes
checking for unsetenv... (cached) yes
checking for verr... yes
checking for verrx... yes
checking for vsyslog... yes
checking for vwarn... yes
checking for vwarnx... yes
checking for warn... yes
checking for warnx... yes
checking for err.h... yes
checking for search.h... yes
checking whether h_errno is declared... yes
checking for bswap16... no
checking for bswap32... no
checking for positional I/O... yes
checking for vectored positional I/O... yes
checking for POSIX regex library... yes
checking for pthread_set_name_np... no
checking for pthread_setname_np... yes
checking for signature of pthread_setname_np... three arguments
checking size of void *... 8
checking size of unsigned long long... 8
checking size of unsigned long... 8
checking size of unsigned int... 4
checking for intptr_t... yes
checking for uintptr_t... yes
checking for ssize_t... yes
checking for sig_atomic_t... yes
checking for socklen_t... yes
checking for off64_t... no
checking for ssize_t... (cached) yes
checking for struct winsize... yes
checking for sa_family_t... yes
checking for socklen_t... (cached) yes
checking for struct sockaddr... yes
checking for struct sockaddr_storage... yes
checking for sa_family_t... (cached) yes
checking for struct addrinfo... yes
checking for long long... yes
checking size of long... 8
checking whether PAM prefers const... yes
checking for swig... no
checking for crypt in -lcrypt... yes
checking for label support in structs... yes
checking checking for dirfd... yes
checking for dd_fd in DIR... no
checking for ru_idrss in struct rusage... yes
checking for uuid/uuid.h... yes
checking for uuid_generate in -luuid... yes
checking for uuid_generate... no
checking for ctfconvert... no
checking for ctfmerge... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/config/Makefile
config.status: creating src/config/Makefile.config
config.status: creating src/config/Makefile.lwp
config.status: creating src/config/Makefile.version-CML
config.status: creating src/config/Makefile.version-NOCML
config.status: creating src/libafs/Makefile.common
config.status: creating src/libafs/MakefileProto
config.status: creating src/config/afsconfig.h
cd src && cd config && make
make[1]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/config“ wird betreten
rm -f Makefile.version
gcc -fPIC     -O   -I/var/lib/dkms/openafs/1.8.8.1/build/src/config -I/var/lib/dkms/openafs/1.8.8.1/build/include -I. -I.      -o mc.o -c mc.c
if  [ -r /var/lib/dkms/openafs/1.8.8.1/build/src/CML/state ] ; \
then  cp Makefile.version-CML Makefile.version ; \
else  cp Makefile.version-NOCML Makefile.version ; \
fi
gcc     -O   -I/var/lib/dkms/openafs/1.8.8.1/build/src/config -I/var/lib/dkms/openafs/1.8.8.1/build/include -I. -I.       -L/var/lib/dkms/openafs/1.8.8.1/build/lib -L/var/lib/dkms/openafs/1.8.8.1/build/lib  -O   \
  -o mkvers ./mkvers.c
if [ "Xparam.linux26.h" != "X" ] ; then \
  cat ./param.linux26.h ./param.amd64_linux26.h > param.h.new ; \
else \
  cat ./param.amd64_linux26.h > param.h.new ; \
fi
make -f Makefile.version AFS_component_version_number.c
/usr/bin/install -c -m 644 param.h.new /var/lib/dkms/openafs/1.8.8.1/build/include/afs/param.h
make[2]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/config“ wird betreten
( VERSION=`/var/lib/dkms/openafs/1.8.8.1/build/build-tools/git-version /var/lib/dkms/openafs/1.8.8.1/build "1.8.8.1"` && \
if [ "$SOURCE_DATE_EPOCH" ]; then \
     echo 'char cml_version_number[]="@(#)OpenAFS '$VERSION `date -u -d "@$SOURCE_DATE_EPOCH" +"%Y-%m-%d" 2>/dev/null || date -u -r "$SOURCE_DATE_EPOCH" +"%Y-%m-%d"`'";'; \
else \
     echo 'char cml_version_number[]="@(#)OpenAFS '$VERSION `date +"%Y-%m-%d"` $USER@`hostname`'";'; \
fi >AFS_component_version_number.c.NEW && \
echo 'char* AFSVersion = "openafs '$VERSION'";' >>AFS_component_version_number.c.NEW && \
if cmp AFS_component_version_number.c.NEW AFS_component_version_number.c > /dev/null 2>&1 ; then : ; else \
mv AFS_component_version_number.c.NEW AFS_component_version_number.c ; fi )
/bin/sh: Zeile 5: hostname: Kommando nicht gefunden.
rm -f AFS_component_version_number.c.NEW
make[2]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/config“ wird verlassen
gcc -fPIC     -O   -I/var/lib/dkms/openafs/1.8.8.1/build/src/config -I/var/lib/dkms/openafs/1.8.8.1/build/include -I. -I.      -o config.o -c config.c
gcc   -L/var/lib/dkms/openafs/1.8.8.1/build/lib -L/var/lib/dkms/openafs/1.8.8.1/build/lib  -O      -O   -I/var/lib/dkms/openafs/1.8.8.1/build/src/config -I/var/lib/dkms/openafs/1.8.8.1/build/include -I. -I.      -o config config.o mc.o
make[1]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/config“ wird verlassen
src/config/config src/libafs/MakefileProto \
  src/libafs/Makefile amd64_linux26
Wrote new makefile 'src/libafs/Makefile'.
cd src && cd libafs && make
make[1]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/libafs“ wird betreten
rm -f h net netinet sys rpc
ln -fs rx rpc
for m in SP ; do \
  KDIR=MODLOAD-5.19.1-1-$m; \
  mkdir -p ${KDIR}; \
  ln -fs ../Makefile ${KDIR}/Makefile.afs ; \
  ln -fs ../Makefile.common ${KDIR}/Makefile.common; \
  ln -fs ../config ${KDIR}/config; \
done
rm -f h
rm -f sys
rm -f netinet
if [ -d /usr/lib/modules/5.19.1-1/build/include2 ] ; then                  \
    ln -fs /usr/lib/modules/5.19.1-1/build/include2/asm/../linux h       ; \
    ln -fs /usr/lib/modules/5.19.1-1/build/include2/asm/../linux sys     ; \
    ln -fs /usr/lib/modules/5.19.1-1/build/include2/asm/../linux netinet ; \
else                                                            \
    ln -fs /usr/lib/modules/5.19.1-1/build/include/linux h               ; \
    ln -fs /usr/lib/modules/5.19.1-1/build/include/linux sys             ; \
    ln -fs /usr/lib/modules/5.19.1-1/build/include/linux netinet         ; \
fi
rm -f linux
ln -fs /usr/lib/modules/5.19.1-1/build/include/linux linux
rm -f net
ln -fs /usr/lib/modules/5.19.1-1/build/include/net net
rm -f asm-generic
ln -fs /usr/lib/modules/5.19.1-1/build/include/asm-generic asm-generic
rm -f asm
ln -fs /usr/lib/modules/5.19.1-1/build/include/asm-x86_64 asm
if [ "yes" ] ; then \
    TARGPREFIX="pack_"; \
fi ; \
for m in SP ; do \
  KDIR=MODLOAD-5.19.1-1-$m ; \
  echo Building in directory: ${KDIR} ; \
  if [ "$m" = "MP" ] ; then \
    SMP_DEF="-DAFS_SMP  " ; \
    TARG="libafs.mp" ; \
  elif [ "$m" = "EP" ] ; then \
    SMP_DEF="-DAFS_SMP  " ; \
    TARG="libafs.ep" ; \
  elif [ "$m" = "BM" ] ; then \
    SMP_DEF="-DAFS_SMP  " ; \
    TARG="libafs.bm" ; \
  else  \
    SMP_DEF=" " ; \
    TARG=libafs ; \
  fi ; \
  cd ${KDIR} ; \
  make -f Makefile.afs SMP_DEF="${SMP_DEF}" linux_compdirs_${TARGPREFIX}${TARG} CLIENT=5.19.1-1 KDIR=${KDIR} || exit $?; \
  cd ../ ; \
done
Building in directory: MODLOAD-5.19.1-1-SP
make[2]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP“ wird betreten
env EXTRA_CFLAGS="" /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/make_kbuild_makefile.pl MODLOAD-5.19.1-1-SP openafs.ko /var/lib/dkms/openafs/1.8.8.1/build/src/config/Makefile.config Makefile.afs Makefile.common
( env EXTRA_CFLAGS="" \
  make -C /usr/lib/modules/5.19.1-1/build M=/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP modules 2>&1 \
  || echo "FAILURE: make exit code $?" ) | tee .makelog
make[3]: Verzeichnis „/usr/lib/modules/5.19.1-1/build“ wird betreten
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/sha256-kernel.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rand-timer-kernel.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_atomlist.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_lhash.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_analyze.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_axscache.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_buffer.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_bypasscache.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_callback.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_cbqueue.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_cell.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_chunk.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_conn.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_daemons.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_dcache.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_dir.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_disconnected.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_dynroot.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_error.o
In Datei, eingebunden von /var/lib/dkms/openafs/1.8.8.1/build/src/afs/afs.h:24,
                 von /var/lib/dkms/openafs/1.8.8.1/build/src/afs/afsincludes.h:48,
                 von /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_dcache.c:18:
/var/lib/dkms/openafs/1.8.8.1/build/include/opr/jhash.h: In Funktion »opr_jhash«:
/var/lib/dkms/openafs/1.8.8.1/build/include/opr/jhash.h:82:17: Warnung: diese Anweisung könnte durchfallen [-Wimplicit-fallthrough=]
   82 |       case 3 : c+=k[2];
      |                ~^~~~~~
/var/lib/dkms/openafs/1.8.8.1/build/include/opr/jhash.h:84:7: Anmerkung: hier
   84 |       case 2 : b+=k[1];
      |       ^~~~
/var/lib/dkms/openafs/1.8.8.1/build/include/opr/jhash.h:84:17: Warnung: diese Anweisung könnte durchfallen [-Wimplicit-fallthrough=]
   84 |       case 2 : b+=k[1];
      |                ~^~~~~~
/var/lib/dkms/openafs/1.8.8.1/build/include/opr/jhash.h:86:7: Anmerkung: hier
   86 |       case 1 : a+=k[0];
      |       ^~~~
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_icl.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_init.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_lock.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_mariner.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_memcache.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_fetchstore.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_osi.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_osidnlc.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_osi_alloc.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_osi_pag.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_osi_uio.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_osi_vget.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_osi_vm.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_segments.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_server.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_stat.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_syscall.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_tokens.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_user.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_util.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vcache.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_access.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_attrs.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_dirops.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_create.o
/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vcache.c: In Funktion »afs_StaleVCacheFlags«:
/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vcache.c:3161:25: Warnung: der Vergleich wird immer als »false« ausgewertet, da die Adresse von »v« niemals NULL sein wird [-Waddress]
 3161 |             AFSTOV(avc) == NULL || vType(avc) == VDIR ||
      |                         ^~
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_fid.o
In Datei, eingebunden von /var/lib/dkms/openafs/1.8.8.1/build/src/afs/afsincludes.h:48,
                 von /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vcache.c:44:
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/afs.h:853:18: Anmerkung: »v« ist hier deklariert
  853 |     struct vnode v;             /* Has reference count in v.v_count */
      |                  ^
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_flock.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_link.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_lookup.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_open.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_read.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_readdir.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_remove.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_rename.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_strategy.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_symlink.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_vnop_write.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_volume.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afs_warn.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/afsaux.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/xdr_update.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/xdr_refernce.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/Kvice.xdr.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/xdr_arrayn.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/xdr_array.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/xdr_int32.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/xdr_int64.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/Kvice.cs.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/fcrypt.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_call.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_conn.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_peer.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_rdwr.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_clock.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_event.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_globals.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_identity.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_kmutex.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_knet.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_kcommon.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_misc.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_null.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_opaque.o
  CC [M]  /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_getaddr.o
In Datei, eingebunden von /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_kmutex.c:24:
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:143:1: Fehler: abweichende Typen für »grab_cache_page_write_begin«; der bestehende Typ ist »struct page *(struct address_space *, long unsigned int,  unsigned int)«
  143 | grab_cache_page_write_begin(struct address_space *mapping, pgoff_t index,
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:144:29: Anmerkung: vorherige Deklaration von »grab_cache_page_write_begin« vom Typ »struct page *(struct address_space *, long unsigned int)«
  144 |                             unsigned int flags) {
      |                             ^~~~~~~~
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h: In Funktion »grab_cache_page_write_begin«:
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:145:12: Fehler: Implizite Deklaration der Funktion »__grab_cache_page«; meinten Sie »grab_cache_page«? [-Werror=implicit-function-declaration]
  145 |     return __grab_cache_page(mapping, index);
      |            ^~~~~~~~~~~~~~~~~
      |            grab_cache_page
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:145:12: Warnung: Rückgabe von »int« aus einer Funktion mit Rückgabetyp »struct page *« wandelt eine Zahl in einen Zeiger um, ohne explizite Typkonvertierung [-Wint-conversion]
  145 |     return __grab_cache_page(mapping, index);
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: Einige Warnungen werden als Fehler behandelt
make[4]: *** [scripts/Makefile.build:249: /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_kmutex.o] Fehler 1
make[4]: *** Es wird auf noch nicht beendete Prozesse gewartet....
In Datei, eingebunden von /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_knet.c:37:
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:143:1: Fehler: abweichende Typen für »grab_cache_page_write_begin«; der bestehende Typ ist »struct page *(struct address_space *, long unsigned int,  unsigned int)«
  143 | grab_cache_page_write_begin(struct address_space *mapping, pgoff_t index,
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:144:29: Anmerkung: vorherige Deklaration von »grab_cache_page_write_begin« vom Typ »struct page *(struct address_space *, long unsigned int)«
  144 |                             unsigned int flags) {
      |                             ^~~~~~~~
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h: In Funktion »grab_cache_page_write_begin«:
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:145:12: Fehler: Implizite Deklaration der Funktion »__grab_cache_page«; meinten Sie »grab_cache_page«? [-Werror=implicit-function-declaration]
  145 |     return __grab_cache_page(mapping, index);
      |            ^~~~~~~~~~~~~~~~~
      |            grab_cache_page
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:145:12: Warnung: Rückgabe von »int« aus einer Funktion mit Rückgabetyp »struct page *« wandelt eine Zahl in einen Zeiger um, ohne explizite Typkonvertierung [-Wint-conversion]
  145 |     return __grab_cache_page(mapping, index);
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: Einige Warnungen werden als Fehler behandelt
make[4]: *** [scripts/Makefile.build:249: /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP/rx_knet.o] Fehler 1
make[3]: *** [Makefile:1843: /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP] Fehler 2
make[3]: Verzeichnis „/usr/lib/modules/5.19.1-1/build“ wird verlassen
FAILURE: make exit code 2
make[2]: *** [Makefile.afs:280: openafs.ko] Fehler 1
make[2]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.19.1-1-SP“ wird verlassen
make[1]: *** [Makefile:187: linux_compdirs] Fehler 2
make[1]: Verzeichnis „/var/lib/dkms/openafs/1.8.8.1/build/src/libafs“ wird verlassen
make: *** [Makefile:15: all] Fehler 2

Offline

#12 2022-08-17 14:15:04

daaku
Member
Registered: 2019-12-01
Posts: 5

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

Same problem here on an LG Gram laptop, with a single lvm partition. Syslinux loads the initrds (intel-ucode & initramfs), then system reboots without any other messages. No kernel options for logging I've tried have helped to collect useful logs for debugging the cause. linux 5.19.1.arch2-1 is the cause of the issue, downgrading to 5.18.16.arch1-1 restores the system. Happy to help test or collect more information to help debug.

Offline

#13 2022-08-17 14:28:34

loqs
Member
Registered: 2014-03-06
Posts: 15,505

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

5.19 without the first stable patch set.
https://drive.google.com/file/d/1s5xhb3 … sp=sharing linux-5.19-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1PDYx0u … sp=sharing linux-headers-5.19-1-x86_64.pkg.tar.zst

Offline

#14 2022-08-17 16:06:58

BwK
Member
Registered: 2019-09-25
Posts: 14

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

loqs wrote:

5.19 without the first stable patch set.
https://drive.google.com/file/d/1s5xhb3 … sp=sharing linux-5.19-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1PDYx0u … sp=sharing linux-headers-5.19-1-x86_64.pkg.tar.zst

Also not working :-(

Last edited by BwK (2022-08-17 16:07:15)

Offline

#15 2022-08-17 16:10:38

loqs
Member
Registered: 2014-03-06
Posts: 15,505

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

BwK wrote:
loqs wrote:

5.19 without the first stable patch set.
https://drive.google.com/file/d/1s5xhb3 … sp=sharing linux-5.19-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1PDYx0u … sp=sharing linux-headers-5.19-1-x86_64.pkg.tar.zst

Also not working :-(

linux 5.19.2.arch1-1 is now in testing.  I will build the first bisect test kernel between 5.18 and 5.19.
Edit:
https://drive.google.com/file/d/1oXWnBg … sp=sharing linux-5.18.r7905.gc011dd537ffe-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1qmzCZw … sp=sharing linux-headers-5.18.r7905.gc011dd537ffe-1-x86_64.pkg.tar.zst

Last edited by loqs (2022-08-17 16:31:36)

Offline

#16 2022-08-17 17:59:08

BwK
Member
Registered: 2019-09-25
Posts: 14

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

loqs wrote:

[...]
https://drive.google.com/file/d/1oXWnBg … sp=sharing linux-5.18.r7905.gc011dd537ffe-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1qmzCZw … sp=sharing linux-headers-5.18.r7905.gc011dd537ffe-1-x86_64.pkg.tar.zst

Not working either.

Offline

#17 2022-08-17 18:39:02

loqs
Member
Registered: 2014-03-06
Posts: 15,505

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

git bisect bad
Bisecting: 2961 revisions left to test after this (roughly 12 steps)
[7e062cda7d90543ac8c7700fc7c5527d0c0f22ad] Merge tag 'net-next-5.19' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next

https://drive.google.com/file/d/1VAupLB … sp=sharing linux-5.18.r4943.g7e062cda7d90-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/15lSzBw … sp=sharing linux-headers-5.18.r4943.g7e062cda7d90-1-x86_64.pkg.tar.zst

Offline

#18 2022-08-17 18:58:50

BwK
Member
Registered: 2019-09-25
Posts: 14

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

loqs wrote:
git bisect bad
Bisecting: 2961 revisions left to test after this (roughly 12 steps)
[7e062cda7d90543ac8c7700fc7c5527d0c0f22ad] Merge tag 'net-next-5.19' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next

https://drive.google.com/file/d/1VAupLB … sp=sharing linux-5.18.r4943.g7e062cda7d90-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/15lSzBw … sp=sharing linux-headers-5.18.r4943.g7e062cda7d90-1-x86_64.pkg.tar.zst

Not working ... this was my last test for today. I'm going to bed. I can continue testing tomorrow afternoon ... Thanks for your effort!

Offline

#19 2022-08-17 19:57:54

loqs
Member
Registered: 2014-03-06
Posts: 15,505

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

git bisect bad
Bisecting: 2538 revisions left to test after this (roughly 11 steps)
[3842007b1a33589d57f67eac479b132b77767514] Merge tag 'zonefs-5.19-rc1-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs

https://drive.google.com/file/d/1PfVRMO … sp=sharing linux-5.18.r2404.g3842007b1a33-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1kPneHP … sp=sharing linux-headers-5.18.r2404.g3842007b1a33-1-x86_64.pkg.tar.zst
Also a sanity check,  does the kernel below work?
https://drive.google.com/file/d/1uHRoaz … sp=sharing linux-5.18-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1pdXEj3 … sp=sharing linux-headers-5.18-1-x86_64.pkg.tar.zst

Offline

#20 2022-08-19 05:50:42

BwK
Member
Registered: 2019-09-25
Posts: 14

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

Sorry, had no time to test yesterday. Nevertheless, I tested now with a second system (which is configured similar)  with the current kernel (5.19.2.arch1-1) and it's booting from syslinux. Thsi afternoon or on the weekend I can test with the system where I initially faced the issue.

Offline

#21 2022-08-19 06:51:13

BwK
Member
Registered: 2019-09-25
Posts: 14

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

Ok, it looks like these two systems are not as similar as expected. I tested the second system with this kernels, too. More ore less "unfortunately", it is booting fine.

loqs wrote:

https://drive.google.com/file/d/1VAupLB … sp=sharing linux-5.18.r4943.g7e062cda7d90-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/15lSzBw … sp=sharing linux-headers-5.18.r4943.g7e062cda7d90-1-x86_64.pkg.tar.zst

Nevertheless, maybe we can use this to find the difference between these two systems to narrow down the root cause of the issue. Do you have any idea what I should look for?

There are two major differences I am aware of for now:
1. One has its root & home partition in an encrypted LVM. But as others face the same issue without having an LVM, this should not be the reason.
2. One is UEFI (not working) the other is BIOS (working)

Offline

#22 2022-08-19 07:19:28

seth
Member
Registered: 2012-09-03
Posts: 33,644

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

Do both syslinux.cfg look the same?
Esp. wrt. intel-ucode.img?

Offline

#23 2022-08-19 07:47:20

BwK
Member
Registered: 2019-09-25
Posts: 14

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

I do not see any big difference.

Working:

# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
#   * menu.c32 - provides a text menu
#   * vesamenu.c32 - provides a graphical menu
#   * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
#   * hdt.c32 - hardware detection tool
#   * reboot.c32 - reboots the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples

DEFAULT arch
PROMPT 0        # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl

# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
#UI menu.c32
UI vesamenu.c32

MENU WIDTH 78
MENU MARGIN 4
MENU ROWS 7
MENU VSHIFT 10
MENU TABMSGROW 14
MENU CMDLINEROW 14
MENU HELPMSGROW 16
MENU HELPMSGENDROW 29

# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
MENU BACKGROUND splash.png
#MENU BACKGROUND boot/syslinux/splash.png
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

LABEL arch
    MENU LABEL Arch Linux (Stick)
    LINUX ../vmlinuz-linux
    APPEND root=UUID=9b597191-7d41-46c8-8cec-cf0688e18402 rw
    INITRD ../initramfs-linux.img

LABEL arch-lts
    MENU LABEL Arch Linux LTS
    LINUX ../vmlinuz-linux-lts
    APPEND root=UUID=9b597191-7d41-46c8-8cec-cf0688e18402 rw
    INITRD ../initramfs-linux-lts.img

LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=UUID=9b597191-7d41-46c8-8cec-cf0688e18402 rw
    INITRD ../initramfs-linux-fallback.img

#LABEL sysrescuecd
#    MENU LABEL System Backup
#    COM32 chain.c32
#    APPEND hd6 1

LABEL windows
        MENU LABEL Windows
        COM32 chain.c32
        APPEND mbr:0x3e786fe3
#        APPEND hd1 1

LABEL hdt
        MENU LABEL HDT (Hardware Detection Tool)
        COM32 hdt.c32

LABEL reboot
        MENU LABEL Reboot
        COM32 reboot.c32

LABEL poweroff
        MENU LABEL Poweroff
        COM32 poweroff.c32

NOT working:

# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
#   * menu.c32 - provides a text menu
#   * vesamenu.c32 - provides a graphical menu
#   * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
#   * hdt.c32 - hardware detection tool
#   * reboot.c32 - reboots the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples

DEFAULT arch
PROMPT 0        # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl

# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32

# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

LABEL arch
    MENU LABEL Arch Linux
    LINUX ../../vmlinuz-linux
    APPEND cryptdevice=UUID=016e92c8-53c0-4788-a12f-c12fe4c7fd2f:main root=/dev/mapper/main-root rw
    INITRD ../../initramfs-linux.img

LABEL archbkp
    MENU LABEL Arch Linux (backup)
    LINUX ../../vmlinuz-linux
    APPEND cryptdevice=/dev/nvme0n1p2:main root=/dev/mapper/main-root rw
    INITRD ../../initramfs-linux.img

LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda3 rw
    INITRD ../initramfs-linux-fallback.img

#LABEL windows
#        MENU LABEL Windows
#        COM32 chain.c32
#        APPEND hd0 1

LABEL hdt
        MENU LABEL HDT (Hardware Detection Tool)
        COM32 hdt.c32

LABEL reboot
        MENU LABEL Reboot
        COM32 reboot.c32

LABEL poweroff
        MENU LABEL Poweroff
        COM32 poweroff.c32

Offline

#24 2022-08-19 12:40:21

MH2012
Member
Registered: 2020-08-25
Posts: 7

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

I have the same issue. Upgraded from 5.18.9 to 5.19.2 and reboots when the before mentioned 3 lines of text is displayed:

Loading intramfs-linux.img ok
Loading intel-ucode.img ok
Loading vmlinuz.linux ok

I solved the issue by downgrading to 5.18.9, but a solution could be nice. Otherwiser, I hope a new kernel release solves the problem (a lazy approach I know).

Offline

#25 2022-08-19 15:04:55

seth
Member
Registered: 2012-09-03
Posts: 33,644

Re: Lock up on upgrade kernel 5.18.16-arch1-1 to 5.19.1-arch2-1

I do not see any big difference.

2. One is UEFI (not working) the other is BIOS (working)

https://wiki.archlinux.org/title/Syslin … I_Syslinux
Does anyone affected boot a BIOS system?

Offline

Board footer

Powered by FluxBB