January 2023 - openSUSE Users - openSUSE Mailing Lists

[oS-en] new syslog noise about usb
by Carlos E. R. 23 Jan '23

23 Jan '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Leap 15.4 Today, I was getting a lot of these new messages in the log (I did an update yesterday): <1.4> 2023-01-23T12:24:34.810643+01:00 Telcontar tracker-extract 12239 - - Locale 'LANG' is not set, defaulting to C locale <3.6> 2023-01-23T12:24:34.810796+01:00 Telcontar dbus-daemon 6603 - - [session uid=1000 pid=6603] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' <0.4> 2023-01-23T12:24:39.931135+01:00 Telcontar kernel - - - [ 1419.750050][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:40.439134+01:00 Telcontar kernel - - - [ 1420.262039][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:40.471128+01:00 Telcontar kernel - - - [ 1420.294034][ C11] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:24:40.951290+01:00 Telcontar kernel - - - [ 1420.774202][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:40.986395+01:00 Telcontar kernel - - - [ 1420.806033][ C11] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:24:41.467291+01:00 Telcontar kernel - - - [ 1421.286047][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:41.979281+01:00 Telcontar kernel - - - [ 1421.798197][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:42.491121+01:00 Telcontar kernel - - - [ 1422.310037][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:42.651117+01:00 Telcontar kernel - - - [ 1422.470030][ C5] [drm] Fence fallback timer expired on ring sdma1 <0.4> 2023-01-23T12:24:43.003273+01:00 Telcontar kernel - - - [ 1422.822197][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:43.511303+01:00 Telcontar kernel - - - [ 1423.334196][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:43.916745+01:00 Telcontar kernel - - - [ 1423.739516][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:24:49.891122+01:00 Telcontar kernel - - - [ 1429.710009][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:50.399123+01:00 Telcontar kernel - - - [ 1430.218010][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:50.427147+01:00 Telcontar kernel - - - [ 1430.250010][ C11] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:24:50.955118+01:00 Telcontar kernel - - - [ 1430.774008][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:53.755131+01:00 Telcontar kernel - - - [ 1433.574774][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:24:53.963281+01:00 Telcontar kernel - - - [ 1433.782006][ T395] usb 3-2: device not accepting address 32, error -71 <0.6> 2023-01-23T12:24:54.159124+01:00 Telcontar kernel - - - [ 1433.978002][ T395] usb 3-2: new low-speed USB device number 33 using xhci_hcd <0.4> 2023-01-23T12:24:59.935122+01:00 Telcontar kernel - - - [ 1439.753975][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:25:03.783959+01:00 Telcontar kernel - - - [ 1443.606710][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:25:09.623152+01:00 Telcontar kernel - - - [ 1449.445966][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:25:09.623170+01:00 Telcontar kernel - - - [ 1449.445968][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:25:10.143119+01:00 Telcontar kernel - - - [ 1449.961947][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:25:10.175409+01:00 Telcontar kernel - - - [ 1449.993945][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:25:13.624717+01:00 Telcontar kernel - - - [ 1453.446974][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:25:13.835118+01:00 Telcontar kernel - - - [ 1453.653946][ T395] usb 3-2: device not accepting address 33, error -71 <0.3> 2023-01-23T12:25:13.835132+01:00 Telcontar kernel - - - [ 1453.654249][ T395] usb usb3-port2: unable to enumerate USB device usb trouble, and drm trouble. The only things connected to the usb now are in the back of the computer, thus the keyboard, mouse, and other things that should be disconnected. In fact, response at the keyboard stalled, but now seems normal and messages have stopped. Ideas? No, keyboard stalling again, new messages: <1.4> 2023-01-23T12:30:19.882428+01:00 Telcontar tracker-extract 12711 - - Locale 'LANG' is not set, defaulting to C locale <3.6> 2023-01-23T12:30:19.882531+01:00 Telcontar dbus-daemon 6603 - - [session uid=1000 pid=6603] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' <0.3> 2023-01-23T12:30:29.799125+01:00 Telcontar kernel - - - [ 1769.617886][ T395] usb 3-2: device descriptor read/64, error -110 <0.6> 2023-01-23T12:30:29.911120+01:00 Telcontar kernel - - - [ 1769.730163][ T395] usb usb3-port2: attempt power cycle <0.6> 2023-01-23T12:30:30.399127+01:00 Telcontar kernel - - - [ 1770.217854][ T395] usb 3-2: new low-speed USB device number 36 using xhci_hcd <0.4> 2023-01-23T12:30:36.059120+01:00 Telcontar kernel - - - [ 1775.877858][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:36.571120+01:00 Telcontar kernel - - - [ 1776.389858][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:36.855129+01:00 Telcontar kernel - - - [ 1776.677862][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:30:37.083124+01:00 Telcontar kernel - - - [ 1776.901858][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:37.599121+01:00 Telcontar kernel - - - [ 1777.417864][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:38.107212+01:00 Telcontar kernel - - - [ 1777.926139][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:38.619390+01:00 Telcontar kernel - - - [ 1778.438142][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:39.127407+01:00 Telcontar kernel - - - [ 1778.950135][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:39.643394+01:00 Telcontar kernel - - - [ 1779.462155][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:40.024784+01:00 Telcontar kernel - - - [ 1779.847416][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:30:46.015303+01:00 Telcontar kernel - - - [ 1785.833890][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:46.527119+01:00 Telcontar kernel - - - [ 1786.345877][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:47.043303+01:00 Telcontar kernel - - - [ 1786.862061][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:49.860021+01:00 Telcontar kernel - - - [ 1789.682597][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:30:50.070655+01:00 Telcontar kernel - - - [ 1789.889885][ T395] usb 3-2: device not accepting address 36, error -71 <0.6> 2023-01-23T12:30:50.275127+01:00 Telcontar kernel - - - [ 1790.093893][ T395] usb 3-2: new low-speed USB device number 37 using xhci_hcd <0.4> 2023-01-23T12:30:56.031128+01:00 Telcontar kernel - - - [ 1795.849892][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:56.535353+01:00 Telcontar kernel - - - [ 1796.358114][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:57.047311+01:00 Telcontar kernel - - - [ 1796.870071][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:57.559295+01:00 Telcontar kernel - - - [ 1797.382062][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:58.079114+01:00 Telcontar kernel - - - [ 1797.897895][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:59.903115+01:00 Telcontar kernel - - - [ 1799.722583][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:31:05.791119+01:00 Telcontar kernel - - - [ 1805.609906][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:06.303299+01:00 Telcontar kernel - - - [ 1806.121910][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:06.335293+01:00 Telcontar kernel - - - [ 1806.153908][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:31:06.815304+01:00 Telcontar kernel - - - [ 1806.633908][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:06.847122+01:00 Telcontar kernel - - - [ 1806.665906][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:31:07.327297+01:00 Telcontar kernel - - - [ 1807.145928][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:07.359280+01:00 Telcontar kernel - - - [ 1807.177907][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:31:07.839119+01:00 Telcontar kernel - - - [ 1807.658088][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:08.350096+01:00 Telcontar kernel - - - [ 1808.169912][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:08.863136+01:00 Telcontar kernel - - - [ 1808.681913][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:09.371133+01:00 Telcontar kernel - - - [ 1809.189930][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:09.743116+01:00 Telcontar kernel - - - [ 1809.562870][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:31:09.951127+01:00 Telcontar kernel - - - [ 1809.769916][ T395] usb 3-2: device not accepting address 37, error -71 <0.3> 2023-01-23T12:31:09.951142+01:00 Telcontar kernel - - - [ 1809.770222][ T395] usb usb3-port2: unable to enumerate USB device I'll probably try booting an older kernel. [...] Did so. Another problem: system stalled at the "reached boot target" message, but did not power off nor reboot. Now using: cer@Telcontar:~> uname -a Linux Telcontar 5.14.21-150400.24.33-default #1 SMP PREEMPT_DYNAMIC Fri Nov 4 13:55:06 UTC 2022 (76cfe60) x86_64 x86_64 x86_64 GNU/Linux I don't see noise in the log, the keyboard responds normally. cer@Telcontar:~> rpm -q kernel-default kernel-default-5.14.21-150400.24.33.2.x86_64 kernel-default-5.14.21-150400.24.38.1.x86_64 cer@Telcontar:~> - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY85y2Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVuEYAn2nir8ELdOju4kibZ6yI cKW8jQ9zAJ0a4l7tDhMORxCsxMKVdlJ4q+eH7g== =uAXm -----END PGP SIGNATURE-----

1 0

Technical question: does the current grub in Tumbleweed (the current boot loader) understand md/v1.x metadata?
by Stakanov 22 Jan '23

22 Jan '23

Or do I have to create my boot raid with --metadata 0.90 as setting? Thank you.

2 2

Re: Mdadm: can I resize the partition of a mdam if I have only one primary partition per disk and RAID 1? In yast?
by David C. Rankin 22 Jan '23

22 Jan '23

On 1/19/23 14:19, Stratos Zolotas wrote: > I suppose something like > > mdadm --grow --size max /dev/md0 I would not grow to max, but "max - 300M". A replacement 8T drive may not have exactly the same "max" size preventing syncing to the new drive. It is always recommended to leave 1/4 to 1G unused for this reason. -- David C. Rankin, J.D.,P.E.

6 13

[heroes] what changed today that I can't use SeaMonkey 2.53.14 for the forums?
by Felix Miata 21 Jan '23

21 Jan '23

Now the site is headed by: [quote] Unfortunately, your browser is unsupported. Please switch to a supported browser to view rich content, log in and reply.[/quote] It won't let me login. I can't switch to 2.53.15 yet, because Buc's alternate version[1] that supports iso 8601 is not yet available. [1] https://buc.fedorapeople.org/seamonkey/download/ -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

6 15

Mdadm: can I resize the partition of a mdam if I have only one primary partition per disk and RAID 1? In yast?
by Stakanov 20 Jan '23

20 Jan '23

I have a mdam md0 with two hdd 4 TB. They are in use as /home I now have two HDD with 8TB. I normally work with mdam in CLI. I did up to now a planed degrading of the secondary disk of the md0. Then a hot remove. Then I added the first 8TB. with other words: silversurfer:~ # mdadm --manage --set-faulty /dev/md0 /dev/sde1 mdadm: set /dev/sde1 faulty in /dev/md0 silversurfer:~ # mdadm --manage /dev/md0 -r /dev/sde1 mdadm: hot removed /dev/sde1 from /dev/md0 You have new mail in /var/mail/root silversurfer:~ # mdadm --manage /dev/md0 -a /dev/sdg1 mdadm: added /dev/sdg1 It does now sync the data with the 4 TB (hence creating a 4TB on a 8TB disc. Rest of the disk is empty, no other partitions. I will then declare failed the first 4 TB disk, hence hot remove and add 8TB. (here md0 /dev/sdb1) This will again sync 4TB on 8TB disk. Now, one the sync is done, is it possible to expand (e.g. in yast partition manager) the 4TB to the max capacity of the disc, although it is a Raid? How would I proceed and if it is not possible, how would I manage to expand a RAID1? Current status: entropy@silversurfer:~> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 232,9G 0 disk └─sda1 8:1 0 232,9G 0 part └─md127 9:127 0 232,9G 0 raid1 /usr/local /boot/grub2/x86_64-efi /srv /opt /var /root /boot/grub2/i386-pc /.snapshots / sdb 8:16 0 3,6T 0 disk └─sdb1 8:17 0 3,6T 0 part └─md0 9:0 0 3,6T 0 raid1 /home sdc 8:32 0 298,1G 0 disk ├─sdc1 8:33 0 1K 0 part └─sdc5 8:37 0 298,1G 0 part /boot/efi sdd 8:48 0 447,1G 0 disk ├─sdd1 8:49 0 232,9G 0 part │ └─md127 9:127 0 232,9G 0 raid1 /usr/local │ /boot/grub2/x86_64-efi │ /srv │ /opt │ /var │ /root │ /boot/grub2/i386-pc │ /.snapshots │ / ├─sdd2 8:50 0 100G 0 part /var/tmp ├─sdd3 8:51 0 50G 0 part /tmp └─sdd4 8:52 0 64,2G 0 part [SWAP] sde 8:64 0 3,6T 0 disk └─sde1 8:65 0 3,6T 0 part sdf 8:80 0 1,8T 0 disk └─sdf1 8:81 0 1,8T 0 part └─md126 9:126 0 1,8T 0 raid1 ├─md126p1 259:0 0 200G 0 part └─md126p2 259:1 0 1,6T 0 part /var/lib/libvirt sdg 8:96 0 7,3T 0 disk └─sdg1 8:97 0 7,3T 0 part └─md0 9:0 0 3,6T 0 raid1 /home sdh 8:112 0 7,3T 0 disk └─sdh1 8:113 0 1,8T 0 part └─md126 9:126 0 1,8T 0 raid1 ├─md126p1 259:0 0 200G 0 part └─md126p2 259:1 0 1,6T 0 part /var/lib/libvirt sdi 8:128 1 0B 0 disk sdj 8:144 1 0B 0 disk sdk 8:160 1 0B 0 disk sdl 8:176 1 0B 0 disk sr0 11:0 1 1024M 0 rom Thanks in advance

4 7

It seems that I need a 6.1.x kernel, Leap 15.4
by Darryl Gregorash 19 Jan '23

19 Jan '23

Are the kernels at http://download.opensuse.org/repositories/Kernel:/stable/standard/ suitable for use in Leap 15.4? Background: It seems that ASUS removed all WMI support from its motherboards with the X570/B550/TRX40 chipset (apparently as a result of AMD doing so so for the X670/B650 chips (?) ), and that broke temperature/fan speed monitoring on those boards. The lack of WMI support means the NCT6775 module is loaded on these systems, but previously, that driver attempted to read/write directly to the ACPI table, which according to this discussion: https://bugzilla.kernel.org/show_bug.cgi?id=204807# (see especially comment 37) is rather bad thing to allow. The patch to NCT6775 was only accepted into the kernel beginning with ver 6.1.2, and has not yet been backported to the 5.14 kernel. Therefore, to regain temp/fan speed monitoring, I need to install that kernel or later (ver 6.1.7 was just released on download.o.o today).

7 17

Tumbleweed in Microsoft Store
by Roger Oberholtzer 18 Jan '23

18 Jan '23

When installing WSL on Windows, one has a choice to install a Linux distro. SLED15 and an earlier one are amongst the distros available. But no openSUSE distros are available at that level. They are available in the Store. But not direct in Windows at the command line. I'm curious why SLED is the only one available directly. Political? Tumbleweed is available via the store. Here's where it gets interesting: on a company managed Windows PC, they can control what you can get from the Store. In my company at least, Tumbleweed is not on the list. I bet this is the case for many corporate users. So they select a distro from those that are immediately available. For SUSE I guess it is good if an SLED is selected. I get that. But from a openSUSE perspective, the situation is less good. -- Roger Oberholtzer

8 22

rename files
by Simon Becherer 18 Jan '23

18 Jan '23

Hi, i have to rename hunderts of files: 792041_100029699.mi 792090_100029501.mi . . . to 792041.mi 792090.mi . . . i tried: rename ??????_*.mi ??????.mi *.mi rename: ??????_.mi: kein Zugriff: Datei oder Verzeichnis nicht gefunden as you see, no sucess. (first file is gone, all others stay as they are) is there a easy way to do this (without writing a script)? simoN -- www.becherer.de ----------------------------------------------- - Das ist die vorlaeufig endgueltige Version! - Herbert C. Maier Dipl.-Ing. (FH) -----------------------------------------------

11 22

Does openSUSE package perl-rename anywhere?
by David C. Rankin 17 Jan '23

17 Jan '23

All, Simon's question brought up another -- the substitution he wanted to do would be trivial with perl-rename using a regex substitution. However after using zypper to search for "perl-rename", "rename", etc.. nothing but gprename appears. Does opensuse package perl-rename? If so where? Both the rename from util-linux and perl-rename can be installed side-by-side, simply using "perl-rename" as the executable name for it to prevent name collision (or better letting the user choose under the alternatives structure) -- David C. Rankin, J.D.,P.E.

5 6

[oO-en] Restarting ntpd on return from hibernation.
by Carlos E. R. 16 Jan '23

16 Jan '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I want to restart ntpd on return from hibernation. Main reason is to make sure that the pool of servers is correct (can be days later than the previous time), and to ensure correct time, not knowing what ntpd does on hibernation (nothing is logged, so it probably does nothing). So I wonder what is the correct way of achieving this. I'm doing it via a script in "/etc/pm/sleep.d/07time": +++······················· !/bin/bash . /usr/lib/pm-utils/functions . /root/ThingsNeededForBoot/MyScriptDefinitions DATE=`date --rfc-3339=seconds` case "$1" in thaw|resume) $LOGGER -t pm-utils -p daemon.notice "restarting remote clock syncing after hibernating/suspend." systemctl restart ntpd.service ;; *) ;; esac exit $? ·······················++- It works. But I wonder if there is a better way using systemd "somehow". - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHYEARECADYWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY78iPhgcY2FybG9zLmUu ckBvcGVuc3VzZS5vcmcACgkQtTMYHG2NR9Vz3gCdEbmrJaAYsluBLdTc6WbkxVy/ nsQAn1RUTUx1b83Ihb6il0frpCAPQ7l/ =YAY8 -----END PGP SIGNATURE-----

6 15