You are not logged in.

#1 2023-10-04 06:53:45

Windeycastle
Member
Registered: 2023-10-04
Posts: 5

[DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

Hi

I'm trying to install Arch Linux, to give it a try. I already have Windows and Zorin OS (derivative from Ubuntu) dual booted, but wanted to give Arch a try, just to experiment.

I've prepared a usb to boot into, I can even boot into it, but when the prompt appears from Arch, I get a repeating LOAD and UNLOAD audit log in the terminal. It is still a bit possible to type commands, but those audit logs come a little bit too frequent, about every 4 seconds.

This is a bit annoying, and I couldn't find any helping articles online yet, so I'm hoping someone can help.

I don't really know how to attach an image, but my screen looks a bit like this:

root@archiso " # [ 187.527369] kauditd_printk_skb: 66 callbacks suppressed
[ 187.527371] audit: type=1334 audit(1696365091.567:124): prog-id=61 op=LOAD
[ 187.671421] audit: type=1130 audit(1696365091.710:125): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=reflector comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 187.671421] audit: type=1334 audit(1696365091.730:126): prog-id=61 op=UNLOAD

The above 3 messages repeat every 4 seconds, with the last 3 digits of audit(...:...) counting up, just ike prog-id counting up, and auid and ses seeming to stay the same.


I've already tried a new .iso file (first one came from a Belgian server, second from the worldwide server), but both have the same behaviour.


If it matters, I'm on a laptop with an AMD ryzen 7, 5000 series cpu.

Last edited by Windeycastle (2023-10-05 15:00:59)

Offline

#2 2023-10-04 13:00:57

seth
Member
Registered: 2012-09-03
Posts: 53,068

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

I don't really know how to attach an image

Not. Upload it somewhere (imgur etc.) and post the link.
https://wiki.archlinux.org/title/Audit_ … stallation
Adding "audit=0" to the kernel parameters will suppress that, there seems to be an issue w/ invoking reflector, pot. b/c you don't have any network access?

Offline

#3 2023-10-04 13:50:56

Windeycastle
Member
Registered: 2023-10-04
Posts: 5

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

After getting wifi-acces, the message keeps popping up. I'll look into adding "audit=0" to the kernel parameters, thank you.

Offline

#4 2023-10-04 14:04:51

seth
Member
Registered: 2012-09-03
Posts: 53,068

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

If you've internet and still can, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

to record what's actually causing trouble here.

Offline

#5 2023-10-04 15:59:32

Windeycastle
Member
Registered: 2023-10-04
Posts: 5

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

I succesfully ran the journal command, now the audit logs have stopped...

Offline

#6 2023-10-04 16:06:15

seth
Member
Registered: 2012-09-03
Posts: 53,068

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

That would have uploaded the journal to 0x0.st and presented you w/ a url to share - it would not have stopped the audits (but "audit=0" would)

Offline

#7 2023-10-04 16:10:30

Windeycastle
Member
Registered: 2023-10-04
Posts: 5

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

Offline

#8 2023-10-04 21:56:56

seth
Member
Registered: 2012-09-03
Posts: 53,068

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

After ~2 minutes

Oct 04 15:52:32 archiso systemd-networkd-wait-online[554]: Timeout occurred while waiting for network connectivity.
Oct 04 15:52:32 archiso systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Oct 04 15:52:32 archiso systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Oct 04 15:52:32 archiso systemd[1]: Failed to start Wait for Network to be Configured.
Oct 04 15:52:32 archiso audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 04 15:52:32 archiso kernel: audit: type=1130 audit(1696434752.650:59): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

systemd-networkd-wait-online.service gives up waiting and after that reflector tries once every 10s, causing the audit spam (the rendition in the OP is actually BPF)

The reason for that seems a delay caused by

Oct 04 15:50:33 archiso udevadm[564]: systemd-udev-settle.service is deprecated. Please fix livecd-alsa-unmuter.service not to pull it in.
Oct 04 15:51:31 archiso systemd-udevd[435]: 0000:01:00.0: Worker [466] processing SEQNUM=3486 is taking a long time
Oct 04 15:51:33 archiso systemd-udevd[435]: hdaudioC1D0: Worker [447] processing SEQNUM=4098 is taking a long time
Oct 04 15:51:33 archiso systemd-udevd[435]: hdaudioC0D0: Worker [452] processing SEQNUM=4099 is taking a long time
Oct 04 15:52:33 archiso udevadm[564]: Timed out for waiting the udev queue being empty.
Oct 04 15:52:33 archiso systemd[1]: systemd-udev-settle.service: Main process exited, code=exited, status=1/FAILURE
Oct 04 15:52:33 archiso systemd[1]: systemd-udev-settle.service: Failed with result 'exit-code'.
Oct 04 15:52:33 archiso systemd[1]: Failed to start Wait for udev To Complete Device Initialization.
Oct 04 15:52:33 archiso audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-settle comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 04 15:52:33 archiso kernel: audit: type=1130 audit(1696434753.397:60): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-settle comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

which is

Oct 04 15:50:29 archiso kernel: nouveau 0000:01:00.0: enabling device (0000 -> 0003)
Oct 04 15:50:29 archiso kernel: nouveau 0000:01:00.0: NVIDIA GA107 (b77000a1)

which has

Oct 04 15:50:29 archiso kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
Oct 04 15:50:29 archiso kernel: BUG: kernel NULL pointer dereference, address: 0000000000000020
Oct 04 15:50:29 archiso kernel: #PF: supervisor read access in kernel mode
Oct 04 15:50:29 archiso kernel: #PF: error_code(0x0000) - not-present page
Oct 04 15:50:29 archiso kernel: PGD 0 P4D 0 
Oct 04 15:50:29 archiso kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Oct 04 15:50:29 archiso kernel: CPU: 0 PID: 203 Comm: (udev-worker) Not tainted 6.4.12-arch1-1 #1 3e6fa2753a2d75925c34ecb78e22e85a65d083df
Oct 04 15:50:29 archiso kernel: Hardware name: ASUSTeK COMPUTER INC. ROG Strix G513QC_G513QC/G513QC, BIOS G513QC.331 02/24/2023
Oct 04 15:50:29 archiso kernel: RIP: 0010:nvif_object_mthd+0xa6/0x200 [nouveau]
Oct 04 15:50:29 archiso kernel: Code: 00 e8 ee 49 db e2 49 8b 44 24 08 41 8d 56 20 4c 8d 7c 24 28 49 39 c4 0f 84 f9 00 00 00 4c 89 63 10 31 c9 48 89 de c6 43 06 ff <48> 8b 78 20 48 8b 40 38 48 8b 40 28 e8 f9 b8 dc e2 48 8b 3c 24 4c
Oct 04 15:50:29 archiso kernel: RSP: 0018:ffffc026c7e776d0 EFLAGS: 00010246
Oct 04 15:50:29 archiso kernel: RAX: 0000000000000000 RBX: ffffc026c7e776d8 RCX: 0000000000000000
Oct 04 15:50:29 archiso kernel: RDX: 0000000000000028 RSI: ffffc026c7e776d8 RDI: ffffc026c7e77700
Oct 04 15:50:29 archiso kernel: RBP: ffff9ac3e4075800 R08: ffffc026c7e77930 R09: ffff9ac3db75ec78
Oct 04 15:50:29 archiso kernel: R10: ffff9ac3c1413760 R11: ffffc026c056dfff R12: ffff9ac3e11cc540
Oct 04 15:50:29 archiso kernel: R13: ffffc026c7e776d8 R14: 0000000000000008 R15: ffffc026c7e776f8
Oct 04 15:50:29 archiso kernel: FS:  00007f077548a480(0000) GS:ffff9ac6ce600000(0000) knlGS:0000000000000000
Oct 04 15:50:29 archiso kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 04 15:50:29 archiso kernel: CR2: 0000000000000020 CR3: 0000000119ebc000 CR4: 0000000000750ef0
Oct 04 15:50:29 archiso kernel: PKRU: 55555554
Oct 04 15:50:29 archiso kernel: Call Trace:
Oct 04 15:50:29 archiso kernel:  <TASK>
Oct 04 15:50:29 archiso kernel:  ? __die+0x23/0x70
Oct 04 15:50:29 archiso kernel:  ? page_fault_oops+0x171/0x4e0
Oct 04 15:50:29 archiso kernel:  ? exc_page_fault+0x7f/0x180
Oct 04 15:50:29 archiso kernel:  ? asm_exc_page_fault+0x26/0x30
Oct 04 15:50:29 archiso kernel:  ? nvif_object_mthd+0xa6/0x200 [nouveau b8e72d24c0b1a77b546655436986065c5a2f5113]
Oct 04 15:50:29 archiso kernel:  nvif_conn_hpd_status+0x39/0xf0 [nouveau b8e72d24c0b1a77b546655436986065c5a2f5113]
Oct 04 15:50:29 archiso kernel:  nouveau_dp_detect+0x86/0x4f0 [nouveau b8e72d24c0b1a77b546655436986065c5a2f5113]
Oct 04 15:50:29 archiso kernel:  nouveau_connector_detect+0xa4/0x5a0 [nouveau b8e72d24c0b1a77b546655436986065c5a2f5113]
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  drm_helper_probe_detect+0x88/0xb0
Oct 04 15:50:29 archiso kernel:  drm_helper_probe_single_connector_modes+0x455/0x540
Oct 04 15:50:29 archiso kernel:  ? __kmem_cache_alloc_node+0x18f/0x310
Oct 04 15:50:29 archiso kernel:  drm_client_modeset_probe+0x24b/0x1530
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? __pm_runtime_suspend+0x4a/0xd0
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? nouveau_drm_open+0x8e/0x1e0 [nouveau b8e72d24c0b1a77b546655436986065c5a2f5113]
Oct 04 15:50:29 archiso kernel:  __drm_fb_helper_initial_config_and_unlock+0x3d/0x540
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  drm_fbdev_generic_client_hotplug+0x6a/0xb0
Oct 04 15:50:29 archiso kernel:  drm_client_register+0x79/0xc0
Oct 04 15:50:29 archiso kernel:  nouveau_drm_probe+0x258/0x280 [nouveau b8e72d24c0b1a77b546655436986065c5a2f5113]
Oct 04 15:50:29 archiso kernel:  local_pci_probe+0x45/0xa0
Oct 04 15:50:29 archiso kernel:  pci_device_probe+0xc1/0x260
Oct 04 15:50:29 archiso kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Oct 04 15:50:29 archiso kernel:  really_probe+0x19e/0x3e0
Oct 04 15:50:29 archiso kernel:  ? __pfx___driver_attach+0x10/0x10
Oct 04 15:50:29 archiso kernel:  __driver_probe_device+0x78/0x160
Oct 04 15:50:29 archiso kernel:  driver_probe_device+0x1f/0x90
Oct 04 15:50:29 archiso kernel:  __driver_attach+0xd2/0x1c0
Oct 04 15:50:29 archiso kernel:  bus_for_each_dev+0x88/0xd0
Oct 04 15:50:29 archiso kernel:  bus_add_driver+0x116/0x220
Oct 04 15:50:29 archiso kernel:  driver_register+0x59/0x100
Oct 04 15:50:29 archiso kernel:  ? __pfx_nouveau_drm_init+0x10/0x10 [nouveau b8e72d24c0b1a77b546655436986065c5a2f5113]
Oct 04 15:50:29 archiso kernel:  do_one_initcall+0x5d/0x240
Oct 04 15:50:29 archiso kernel:  do_init_module+0x60/0x240
Oct 04 15:50:29 archiso kernel:  __do_sys_finit_module+0xad/0x130
Oct 04 15:50:29 archiso kernel:  do_syscall_64+0x60/0x90
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? ksys_mmap_pgoff+0xec/0x1f0
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Oct 04 15:50:29 archiso kernel:  ? srso_alias_return_thunk+0x5/0x7f
Oct 04 15:50:29 archiso kernel:  ? do_syscall_64+0x6c/0x90
Oct 04 15:50:29 archiso kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Oct 04 15:50:29 archiso kernel: RIP: 0033:0x7f0775f3ed6d
Oct 04 15:50:29 archiso kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 93 ef 12 00 f7 d8 64 89 01 48
Oct 04 15:50:29 archiso kernel: RSP: 002b:00007ffc55252128 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Oct 04 15:50:29 archiso kernel: RAX: ffffffffffffffda RBX: 000055ddf1fec8f0 RCX: 00007f0775f3ed6d
Oct 04 15:50:29 archiso kernel: RDX: 0000000000000000 RSI: 00007f07760b6343 RDI: 0000000000000010
Oct 04 15:50:29 archiso kernel: RBP: 00007f07760b6343 R08: 0000000000000000 R09: fffffffffffffe90
Oct 04 15:50:29 archiso kernel: R10: 0000000000000010 R11: 0000000000000246 R12: 0000000000020000
Oct 04 15:50:29 archiso kernel: R13: 000055ddf1fd5730 R14: 000055ddf1fec8f0 R15: 000055ddf1feeeb0
Oct 04 15:50:29 archiso kernel:  </TASK>
Oct 04 15:50:29 archiso kernel: Modules linked in: amdgpu(+) nouveau(+) serio_raw drm_buddy atkbd libps2 mxm_wmi gpu_sched vivaldi_fmap crc32_pclmul crc32c_intel sha512_ssse3 drm_suballoc_helper i2c_algo_bit aesni_intel r8169 drm_ttm_helper ttm nvme crypto_simd realtek cryptd mdio_devres drm_display_helper nvme_core xhci_pci i8042 nvme_common xhci_pci_renesas cec libphy video serio wmi
Oct 04 15:50:29 archiso kernel: CR2: 0000000000000020
Oct 04 15:50:29 archiso kernel: ---[ end trace 0000000000000000 ]---

You probably want to install https://wiki.archlinux.org/title/NVIDIA#Installation at some point.

Offline

#9 2023-10-05 15:00:28

Windeycastle
Member
Registered: 2023-10-04
Posts: 5

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

Solved my issue by deleting Arch. Apparently iwctl wasn't even installed anymore, so the tutorials I followed didn't help me enough.

I'll try again ik a few weeks, or not.

Offline

#10 2023-10-05 15:19:19

seth
Member
Registered: 2012-09-03
Posts: 53,068

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

Your main problem is

so the tutorials I followed didn't help me enough

https://wiki.archlinux.org/title/Installation_guide

Offline

#11 2024-04-17 04:15:48

CESAR
Member
Registered: 2016-12-19
Posts: 2

Re: [DONE] Repeating LOAD/UNLOAD message (trying to install Arch)

Same thing happend to me, I was using a USB flash drive for the installation and changed the port and the message stopped.  Maybe can help to some one.

Offline

Board footer

Powered by FluxBB