- Arch-general - lists.archlinux.org

[arch-general] In pacman view, -debug package doesn't depends on its non -debug package
by u34＠net9.ga 25 May '22

25 May '22

Am I right the new -debug packages do not depend, pacman wise, on their binary, non -debug packages? By that I mean pacman --upgrade somepkg-debug will sucsseed even when somepkg is not installed. Such dependency looks to me obvoius. Why was it decided not to have it? -- u34

2 1

[arch-general] A tiny linux 5.17.7-arch1 compilation issue with a custom config
by u34＠net9.ga 16 May '22

16 May '22

This is most probably not an arch specific issue. And does not concern arch official linux, as arch official linux does not have CONFIG_WERROR=y. Hopefully, the linux kerenl people can better fix the following. It could be it is already fixed. I managed to sweep it under the rug with 29c29 < CONFIG_WERROR=y --- > # CONFIG_WERROR is not set My point is I used to have CONFIG_WERROR=y in the linux .config file for some time. It could be that until the gcc 11.2.0-4 -> 12.1.0-1 upgrade, the following was partially, or fully, over looked by the compilation process. But it could also be that the source was somewhat changed lately. Or that there are other issues involved, which I am not aware of. The following is with 5.17.7-arch1 source, and CONFIG_WERROR=y. CC drivers/acpi/acpica/utdebug.o drivers/acpi/acpica/utdebug.c: In function 'acpi_ut_init_stack_ptr_trace': drivers/acpi/acpica/utdebug.c:40:38: error: storing the address of local variable 'current_sp' in 'acpi_gbl_entry_stack_pointer' [-Werror=dangling-pointer=] 40 | acpi_gbl_entry_stack_pointer = &current_sp; | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~ drivers/acpi/acpica/utdebug.c:38:19: note: 'current_sp' declared here 38 | acpi_size current_sp; | ^~~~~~~~~~ In file included from ./include/acpi/acpi.h:31, from drivers/acpi/acpica/utdebug.c:12: drivers/acpi/acpica/acglobal.h:196:26: note: 'acpi_gbl_entry_stack_pointer' declared here 196 | ACPI_GLOBAL(acpi_size *, acpi_gbl_entry_stack_pointer); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./include/acpi/acpixf.h:45:21: note: in definition of macro 'ACPI_GLOBAL' 45 | extern type name | ^~~~ cc1: all warnings being treated as errors make[3]: *** [scripts/Makefile.build:288: drivers/acpi/acpica/utdebug.o] Error 1 make[2]: *** [scripts/Makefile.build:550: drivers/acpi/acpica] Error 2 make[1]: *** [scripts/Makefile.build:550: drivers/acpi] Error 2 make: *** [Makefile:1831: drivers] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Without CONFIG_WERROR=y, compilation continues, since the lines beginning at cc1: all warnings being treated as errors are avoided. Which is expected. -- u34

2 1

[arch-general] intel-ucode 20220510-1 killed my wifi
by Simeon Felis 15 May '22

15 May '22

Apparently I have a Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74 on a Lenovo Thinkpad x230t. I hope that this is a ucode issue and not a rotting hardware. Here is what happens with intel-ucode 20220510-1 [ 18.138516] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532 6000-4.ucode op_mode iwldvm [ 18.246943] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG enabled [ 18.246948] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled [ 18.246950] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled [ 18.246952] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74 [ 18.302418] ------------[ cut here ]------------ [ 18.302422] Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff) [ 18.302442] WARNING: CPU: 1 PID: 576 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2117 __iwl_trans_pcie_grab_nic_access+0x1ec/0x220 [iwlwifi] [ 18.302467] Modules linked in: iwldvm(+) kvm_intel(+) snd_intel_dspcfg mac80211 kvm libarc4 snd_intel_sdw_acpi iTCO_wdt snd_hda_codec joydev intel_pmc_bxt iwlwifi nls_iso8859_1 at24 think_lmi(+) vfat mousedev irqbypass firmware_attributes_class wmi_bmof mei_hdcp mei_pxp mei_wdt iTCO_vendor_support rapl intel_cstate fat iwlmei intel_ uncore i2c_i801 snd_hda_core pcspkr thinkpad_acpi i2c_smbus cfg80211 snd_hwdep psmouse ledtrig_audio i915 platform_profile snd_pcm wmi rfkill snd_timer tpm_tis ttm e1000e snd mei_me video tpm_tis_core lpc_ich intel_gtt mei soundcore mac_hid vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) dm_multipath ipmi_devintf ipmi_msghandler sg crypto_us er fuse bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 dm_crypt cbc encrypted_keys dm_mod trusted asn1_encoder tee tpm rng_core serio_raw crct10dif_pclmul atkbd libps2 crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd sdhci_pci cqhci sdhci i8042 xhci_pci usbhid mmc_core [ 18.302532] xhci_pci_renesas serio [ 18.302535] CPU: 1 PID: 576 Comm: modprobe Tainted: G OE 5.17.6-arch1-1 #1 6a465b5cdd6c23594925dd1c6b33fddeebe18127 [ 18.302538] Hardware name: LENOVO 3435CTO/3435CTO, BIOS GCETB5WW (2.75 ) 09/25/2019 [ 18.302539] RIP: 0010:__iwl_trans_pcie_grab_nic_access+0x1ec/0x220 [iwlwifi] [ 18.302558] Code: 48 89 df e8 b6 af fe ff 4c 89 f7 e8 2e 3a 36 c9 e9 e6 fe ff ff 89 c6 48 c7 c7 28 ae a3 c0 c6 05 89 7c 04 00 01 e8 14 b4 2f c9 <0f> 0b e9 01 ff ff ff 48 8b 7b 40 48 c7 c2 90 ae a3 c0 31 f6 e8 4b [ 18.302560] RSP: 0018:ffffb9b98090fb30 EFLAGS: 00010282 [ 18.302562] RAX: 0000000000000000 RBX: ffff97e086a2c028 RCX: 0000000000000027 [ 18.302563] RDX: ffff97e38e6616e8 RSI: 0000000000000001 RDI: ffff97e38e6616e0 [ 18.302564] RBP: 00000000ffffffff R08: 0000000000000000 R09: ffffb9b98090f948 [ 18.302565] R10: ffffb9b98090f940 R11: 0000000000000003 R12: 0000000000000001 [ 18.302567] R13: 0000000000000000 R14: ffff97e086a2e944 R15: 0000000000000011 [ 18.302568] FS: 00007f713f50f740(0000) GS:ffff97e38e640000(0000) knlGS:0000000000000000 [ 18.302570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 18.302571] CR2: 00007fc7d5006000 CR3: 000000010e484006 CR4: 00000000001706e0 [ 18.302573] Call Trace: [ 18.302575] <TASK> [ 18.302578] iwl_trans_pcie_grab_nic_access+0x16/0x40 [iwlwifi 9bf797cd3fa1dfe7d95f58c5bd0c22cc3010b7df] [ 18.302595] iwl_write_prph_delay+0x23/0x70 [iwlwifi 9bf797cd3fa1dfe7d95f58c5bd0c22cc3010b7df] [ 18.302610] iwl_pcie_apm_init+0x131/0x1c0 [iwlwifi 9bf797cd3fa1dfe7d95f58c5bd0c22cc3010b7df] [ 18.302625] iwl_trans_pcie_start_hw+0x96/0x2b0 [iwlwifi 9bf797cd3fa1dfe7d95f58c5bd0c22cc3010b7df] [ 18.302641] iwl_op_mode_dvm_start+0x298/0xcd0 [iwldvm c4082a7f19be48965d2a2c00f53b750277e654b3] [ 18.302655] _iwl_op_mode_start+0x98/0xc0 [iwlwifi 9bf797cd3fa1dfe7d95f58c5bd0c22cc3010b7df] [ 18.302670] iwl_opmode_register+0x68/0xd0 [iwlwifi 9bf797cd3fa1dfe7d95f58c5bd0c22cc3010b7df] [ 18.302685] ? 0xffffffffc0b96000 [ 18.302687] iwl_init+0x34/0x1000 [iwldvm c4082a7f19be48965d2a2c00f53b750277e654b3] [ 18.302698] ? 0xffffffffc0b96000 [ 18.302699] do_one_initcall+0x56/0x220 [ 18.302704] do_init_module+0x4a/0x240 [ 18.302707] __do_sys_init_module+0x138/0x1b0 [ 18.302711] do_syscall_64+0x58/0x80 [ 18.302717] ? vfs_read+0xf4/0x190 [ 18.302720] ? syscall_exit_to_user_mode+0x23/0x50 [ 18.302722] ? do_syscall_64+0x67/0x80 [ 18.302725] ? syscall_exit_to_user_mode+0x23/0x50 [ 18.302726] ? do_syscall_64+0x67/0x80 [ 18.302729] ? exc_page_fault+0x71/0x170 [ 18.302731] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 18.302735] RIP: 0033:0x7f713f62a3ee [ 18.302736] Code: 48 8b 0d ad 59 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7a 59 0e 00 f7 d8 64 89 01 48 [ 18.302738] RSP: 002b:00007ffc37bd5b78 EFLAGS: 00000246 ORIG_RAX: 00000000000000af [ 18.302740] RAX: ffffffffffffffda RBX: 0000564030699ee0 RCX: 00007f713f62a3ee [ 18.302742] RDX: 000056403022fa2a RSI: 00000000000a82d0 RDI: 00005640307b0d30 [ 18.302743] RBP: 00005640307b0d30 R08: 00000000000a82d0 R09: 0000000000000000 [ 18.302744] R10: 000000000010f7c1 R11: 0000000000000246 R12: 000056403022fa2a [ 18.302745] R13: 000056403069a010 R14: 0000564030699ee0 R15: 000056403069a8e0 [ 18.302747] </TASK> [ 18.302748] ---[ end trace 0000000000000000 ]--- [ 18.302752] iwlwifi 0000:03:00.0: iwlwifi transaction failed, dumping registers [ 18.303524] iwlwifi 0000:03:00.0: iwlwifi device config registers: [ 18.304397] iwlwifi 0000:03:00.0: 00000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.305186] iwlwifi 0000:03:00.0: 00000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.305985] iwlwifi 0000:03:00.0: 00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.306736] iwlwifi 0000:03:00.0: 00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.307472] iwlwifi 0000:03:00.0: 00000080: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.308196] iwlwifi 0000:03:00.0: 000000a0: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.308922] iwlwifi 0000:03:00.0: 000000c0: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.309654] iwlwifi 0000:03:00.0: 000000e0: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.310358] iwlwifi 0000:03:00.0: 00000100: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.311043] iwlwifi 0000:03:00.0: 00000120: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.311731] iwlwifi 0000:03:00.0: 00000140: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.312440] iwlwifi 0000:03:00.0: iwlwifi device memory mapped registers: [ 18.313162] iwlwifi 0000:03:00.0: 00000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.313863] iwlwifi 0000:03:00.0: 00000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff [ 18.315155] iwlwifi 0000:03:00.0: iwlwifi parent port (0000:00:1c.1) config registers: [ 18.315997] iwlwifi 0000:00:1c.1: 00000000: 1e128086 00100007 060400c4 00810010 00000000 00000000 00030300 200000f0 [ 18.316671] iwlwifi 0000:00:1c.1: 00000020: f1c0f1c0 0001fff1 00000000 00000000 00000000 00000040 00000000 00020207 [ 18.317378] iwlwifi 0000:00:1c.1: 00000040: 01428010 00008000 00100000 02123c12 50110042 000cb200 01480000 00000000 [ 18.318075] iwlwifi 0000:00:1c.1: 00000060: 00000000 00000016 00000000 00000000 00010002 00000000 00000000 00000000 [ 18.318782] iwlwifi 0000:00:1c.1: 00000080: 00009005 00000000 00000000 00000000 0000a00d 220317aa 00000000 00000000 [ 18.319464] iwlwifi 0000:00:1c.1: 000000a0: c8020001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.320276] iwlwifi 0000:00:1c.1: 000000c0: 00000000 00000000 00000000 00000000 01000000 00000b02 81118000 00000000 [ 18.321114] iwlwifi 0000:00:1c.1: 000000e0: 00000300 00000000 00000001 00000000 00000000 00000000 08040f87 00000000 [ 18.321910] iwlwifi 0000:00:1c.1: 00000100: 00000000 00000000 00000000 00060011 00000000 00002000 00000000 00000000 [ 18.322573] iwlwifi 0000:00:1c.1: 00000120: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.323203] iwlwifi 0000:00:1c.1: 00000140: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.323812] iwlwifi 0000:00:1c.1: 00000160: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.324408] iwlwifi 0000:00:1c.1: 00000180: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.325007] iwlwifi 0000:00:1c.1: 000001a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.325606] iwlwifi 0000:00:1c.1: 000001c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.326168] iwlwifi 0000:00:1c.1: 000001e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 18.326718] iwlwifi 0000:00:1c.1: 00000200: 00000000 00000000 00000000 [ 18.370403] iwlwifi 0000:03:00.0: bad EEPROM/OTP signature, type=OTP, EEPROM_GP=0x00000007 [ 18.371598] iwlwifi 0000:03:00.0: EEPROM not found, EEPROM_GP=0xffffffff [ 18.372418] iwlwifi 0000:03:00.0: Unable to init EEPROM [ 18.373179] iwlwifi 0000:03:00.0: retry init count 0 [ 18.373951] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG enabled [ 18.373954] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled [ 18.373956] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled [ 18.373958] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74 [ 18.418123] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 18.448746] iwlwifi 0000:03:00.0: bad EEPROM/OTP signature, type=OTP, EEPROM_GP=0x00000007 [ 18.449514] iwlwifi 0000:03:00.0: EEPROM not found, EEPROM_GP=0xffffffff [ 18.450309] iwlwifi 0000:03:00.0: Unable to init EEPROM [ 18.451079] iwlwifi 0000:03:00.0: retry init count 1 [ 18.451872] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG enabled [ 18.451875] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled [ 18.451877] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled [ 18.451879] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74 Linux pandora 5.17.6-arch1-1 #1 SMP PREEMPT Tue, 10 May 2022 23:00:39 +0000 x86_64 GNU/Linux Downgraded with pacman -U /var/cache/pacman/pkg/intel-ucode-20220419-1-any.pkg.tar.zst I would probably need more reboots and re-installs to confirm and rule out hardware issues. If I don't post on this any more it was probably a hardware issue.

3 3

[arch-general] Qemu 7 can not be upgraded on my machine.
by Matthew Dyer 14 May '22

14 May '22

Hi all, I have 2 machines 1 of wich is x86 and the other is arm based. On On the arm machine I am using stormux which is based on arch arm. Here is the issue. On my stormux/arm pi400 machine which btw I I am writing this message on, I am unabble to upgrade or for thart mater remove qemu. Upgrading qemu or installing qemu-desktop tells me that there are broken dependencys. I for the time being, have added the following packages to be ignored in my pacman.conf. qemu-headless and qemu-img. I am not sure if this should be posted on the list, but could not find a way to resaulved this and would to get this problem. Is there a flag such as allow or force of sore sort which can be used in some cases? On my main x86 machine this upgrade went without a problem. If there is a way to remove qemu since I don't really use it that would be wonderfull as well since I don't use it. Matthew

2 1

[arch-general] Rollback to specific date works fine -- but really slow download
by David C. Rankin 13 May '22

13 May '22

Arch folks, Had the need to do a first rollback to 3/15/22 for a samba bug report on 4.16 failure to discover [homes] (https://bugzilla.samba.org/show_bug.cgi?id=15062). The rollback worked flawlessly, but is there anything that can be done to help the download rate? Due to the ICU 7.0->7.1 update, there were 368 packages in 1.3GiB to download. At 300->500KiB it took forever. -- David C. Rankin, J.D.,P.E.

3 5

[arch-general] sound problem with chromium
by Pascal 11 May '22

11 May '22

hi, I have an ArchLinux installed on a usb disk (eg. "mobile"). ~ # uname -r 5.15.37-1-lts ~ # pacman -Q | egrep 'alsa|chromium|firefox|mplayer' alsa-lib 1.2.6.1-1 alsa-topology-conf 1.2.5.1-1 alsa-ucm-conf 1.2.6.3-1 alsa-utils 1.2.6-1 chromium 101.0.4951.54-1 firefox 100.0-1 mplayer 38359-1 when it runs on my Dell Latitude E5250, Chromium works without any difficulty to play a YouTube video for example : the sound is ok (same for Firefox or Mplayer). on the other hand, when it runs on my Lenovo ThinkPad X1 Carbon, Chromium has problems with the sound (which is not the case for Firefox or Mplayer which both produce sound). it happens from time to time in this (hardware) environment that Chromium produces sound and the next moment (simple stop/restart of the browser) it fails (without anything being done in between) ! another surprising thing is that if I access a video (zunRcH4nUPI) this way "chromium https://www.youtube.com/" (and then click on the desired video) I often don't get any sound while if I access it this way "chromium https://www.youtube.com/watch?v=zunRcH4nUPI" the sound works ! I spent a lot of time trying to understand the problem and looking for a solution/track on the internet but, having found nothing, I throw a bottle in the water... regards, lacsaP.

5 12

[arch-general] pacsave for nouveau blacklist in nvidia-utils
by The Puzzlemaker 08 May '22

08 May '22

I've found that when I need to keep nvidia-utils installed whilst still using nouveau (even while using the suggested method in https://wiki.archlinux.org/title/nouveau#Keep_NVIDIA_driver_installed) it gets overridden upon update of nvidia-utils. I believe the way to solve this would be to add a backup section in the PKGBUILD (https://wiki.archlinux.org/title/PKGBUILD#backup)? But I'm not entirely sure. This would be helpful, in my opinion, though, as it would prevent the blacklist from getting invisibly uncommented, and causing problems which may be hard to debug.

2 1

[arch-general] Status of llvm / clang
by Spencer Collyer 08 May '22

08 May '22

Hope this is the right mailing list to send this too. If not, apologies and please direct me to the right one. I'm wondering when the llvm and clang packages are going to be updated. Version 14 of both have been out since late March but doing a package search for them still shows version 13. I did see a thread that said compilers sometimes take longer to be updated because they need testing to make sure they don't break any existing packages that use them, but it also said they normally got put into Testing to do that and I don't see llvm or clang in the Testing area. Not really a biggie, but there are some things in Clang14 that I'd like to start using and I'd prefer to use official Arch packages than building my own version. Thanks for your attention, Regards, Spencer S

2 2

Re: [arch-general] Why is clock_gettime called when the mouse moves?
by Ralph Corderoy 07 May '22

07 May '22

Hi Piscium, Second attempt, the first went to the old list address. > What I posted before was just a short snippet. In > the link below there is a trace for leafpad, available for 7 days. > https://we.tl/t-BAbO60lnGN > > > I suggest using the simplest X client you can which shows the issue, > > e.g. xev(1). ... > Good suggestion. I tried xev and I cannot reproduce the issue. The > simplest app that I tried that shows the issue is leafpad. > > > The second, if you read the two other emails in the thread, fixes the > > problem by changing the kernel's clock source which may differ between > > your two test machines? > > I am not sure what you are referring to, maybe a link for the second > page is missing? Sorry. https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1823248.h… > There are tons of GUI apps. I have tested just a handful of them. > Have the clock_gettime issue: leafpad, mousepad, emacs, audacious, konsole. > Don't have the issue: xev, xterm. > > I tried to figure out if there is a common library used by all apps > that have the problem but so far have not found it. A way to figure > this out might be using gdb and putting a breakpoint on clock_gettime, > but i am reluctant to do this as it would take a lot of time It may be perf_events would help you analyse the frequency of difference clock_gettime() callers, say by maintaining frequency counts of the previous three functions in the call stack, but I don't know enough to suggest how. https://www.brendangregg.com/perf.html -- Cheers, Ralph.

1 0

[arch-general] sequoia-octopus-librnp 1.3.0-1 not working with new thunderbir 91.8.1-1
by Javier 06 May '22

06 May '22

Today's thunderbird upgrade broke sequoia-octopus-librnp (universe), it might be octopus just requires a new build with up to date sys libraries, or that a new octopus librnp version is required. For now, keeping thunderbird on 91.8.1-1, not allowing it to upgrade is a workaround. -- Javier

4 5