October 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1191244] New: USB speaker working when plugged while system is up but not on reboot
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191244 Bug ID: 1191244 Summary: USB speaker working when plugged while system is up but not on reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter.stark(a)storck.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have multiple raspberry PI 4Bs with openSUSE Leap 15.3 and some with raspbian 9. I got a USB speaker (e2b7:0811) which I connected to the 4Bs using Leap 15.3. This speaker works fine when I plug it in when the PI is already running: rpi15:~ # uname -a Linux rpi15 5.3.18-59.24-default #1 SMP Mon Sep 13 15:06:42 UTC 2021 (2f872ea) aarch64 aarch64 aarch64 GNU/Linux rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 007: ID e2b7:0811 Jie Li CD002 Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 [Sa Okt 2 10:56:09 2021] usb 1-1.2: USB disconnect, device number 4 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 6 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 7 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has no interface number 0 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device found, idVendor=e2b7, idProduct=0811, bcdDevice= 1.00 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Product: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Manufacturer: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: SerialNumber: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: 9:1: bogus dB values (-12800/-12700), disabling dB reporting [Sa Okt 2 10:56:17 2021] input: CD002 CD002 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.3/0003:E2B7:0811.0003/input/input1 However, after a reboot with the device still connected (no change) the kernel boots and does not even see the device. rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 rpi15:~ # I have tried the same USB speaker on another PI4B with Leap 15.3 with the same result. So, it doesn't seem to be that PI. When I connect the speaker to a PI3 with raspbian 9, it works as expected. root@rpi13:~# dmesg -T |grep 1-1.3 [Sa Okt 2 10:33:08 2021] usb 1-1.3: new full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:33:08 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0001/input/input0 [Sa Okt 2 10:42:57 2021] usb 1-1.3: reset full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:42:58 2021] usb 1-1.3: USB disconnect, device number 4 [Sa Okt 2 10:42:58 2021] usb 1-1.3: 9:1: cannot get min/max values for control 2 (id 9) [Sa Okt 2 10:43:04 2021] usb 1-1.3: new full-speed USB device number 6 using dwc_otg [Sa Okt 2 10:43:04 2021] usb 1-1.3: device descriptor read/64, error -32 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:43:04 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0002/input/input1 I noticed that the raspbian uses dwc_otg vs. xhci_hcd on Leap. However, dwc_otg doesn't seem to be a separate module in raspbian nor it is available on leap. As the speaker is working when I un-plug and plug it in again, I wonder what may causes this strange behavior. Especially as I do not see the device via lsusb after reboot, though it is still connected. Any ideas on how to fix it? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1201963] New: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70°C until it reaches 54°C
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201963 Bug ID: 1201963 Summary: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70�C until it reaches 54�C Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: gryffus(a)hkfree.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860458 --> https://bugzilla.suse.com/attachment.cgi?id=860458&action=edit Turbostat log output I have a Dell Latitude 5420 laptop and i am experiencing CPU slowdown when using any graphical / CPU demanding application. The laptop contains 11th Gen Intel(R) Core(TM) i5-1145G7 which can do 4,4GHz on turbo. When the system reaches about 70�C, all cores switch to 400MHz and stay there until temperature hits 53-54�C. I can see this behavior especially in Vulkan graphics applications, but not only in them, it just happens almost instantly there, since the 70�C is reached within about 30 seconds there. I would want to raise the temperature limits to at least 80-90�C or disable throttling completely (at my own responsibility of cooking it). But throttling from 70�C seems as a complete nonsense to me - the CPU package gets to this temperature in 10-20 seconds under load, so i basically never make use of the 4,4GHz. What i have tried: 1) Kernel 5.19 from Kernel:HEAD - no change 2) installed throttled ( https://github.com/erpalma/throttled ) - no change 3) blacklisted intel_powerclamp, intel_rapl_msr, processor_thermal_rapl, intel_rapl_common kernel modules - no change 4) cpupower frequency-set -g performance - no change # cat /sys/devices/platform/*/uuids/current_uuid INVALID # cat /sys/devices/platform/*/uuids/available_uuids UNKNOWN # cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 4.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 3.16 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes # cpupower idle-info CPUidle driver: intel_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 4 Available idle states: POLL C1_ACPI C2_ACPI C3_ACPI POLL: Flags/Description: CPUIDLE CORE POLL IDLE Latency: 0 Usage: 265266 Duration: 8068126 C1_ACPI: Flags/Description: ACPI FFH MWAIT 0x0 Latency: 1 Usage: 10617293 Duration: 1984558460 C2_ACPI: Flags/Description: ACPI FFH MWAIT 0x31 Latency: 253 Usage: 273458 Duration: 261649941 C3_ACPI: Flags/Description: ACPI FFH MWAIT 0x60 Latency: 1048 Usage: 206150 Duration: 509227956 # cpupower info analyzing CPU 0: perf-bias: 0 Turbostat debug log attached. Some further reading with probably related reports: https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU-Throttl… https://github.com/intel/thermal_daemon/issues/341 https://github.com/intel/thermal_daemon/issues/293 https://github.com/erpalma/throttled Any clues? -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1189946] New: [trackerbug] Ancient patch cleanup
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1189946 Bug ID: 1189946 Summary: [trackerbug] Ancient patch cleanup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeffm(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- This is the tracker bug for cleaning up old patches in the master branch. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1203519] New: floating shutdown problem on pinebook pro
by bugzilla_noreply＠suse.com 08 Dec '22

08 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203519 Bug ID: 1203519 Summary: floating shutdown problem on pinebook pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- intermittent shutdown problem on pinebook pro, the problem is expressed as follows: after the laptop is turned off (it doesn��t matter by the button in the menu or via sudo systemctl shutdown), a regular shutdown occurs, the service stop log is visible and everything is as it should be, BUT, after the screen goes blank, the board remains on. this can be checked if you try to turn it on, pressing the button does not work. only a long press of the power key (to completely turn off) for 7-10 seconds, and a second press (to turn it on) allows you to turn on the pinebook. the problem is not observed in other distributions (tried on manjaro, armbian, gentoo) and is specific to opensuse. in my case, the installation differs from the typical one in that the operating system is installed on a microsd card (due to the death of emmc), can this affect? but in other distributions, even installed on the same microsd card, the problem is not observed. I'm using opensuse tumbleweed installed from the openSUSE-Tumbleweed-ARM-KDE-pinebookpro.aarch64.raw.xz image. at the moment there are all the latest updates, but the problem has existed for quite a long time. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1193599] New: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193599 Bug ID: 1193599 Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following errors appear at boot broken atomic modeset userspace detected, disabling atomic [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Full log https://paste.opensuse.org/83436185 Hardware Dell Precision 7530 CPU: Intel Xeon E-2186M GPU: Intel P630 / Nvidia Quadro P3200 -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 1191933] New: Kernel can not update on Secure boot envirnment
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191933 Bug ID: 1191933 Summary: Kernel can not update on Secure boot envirnment Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current 20211012, update to 20211016 or 20211019. Kernel-default update failed by fallowing error. subprocess error, secure boot enabled. Is it something change? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200781] New: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd.
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200781 Bug ID: 1200781 Summary: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: publio.escipion.el.africano(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSuSE Leap 15.4 x86_64, kernel 4.14.21-150400.22-default, in a Lenovo IdeaPad 3 15ADA05: https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_3_15ADA05/IdeaPad_… An external mouse stops working after a brief period of time, after login into KDE, or after removing and loading xhci_pci & xhci_hcd. System complaints of: �xhci_hcd 0000:02:00.3 WARNIGN: Host System Error� and: �usb 2-3: device not accepting address 2, error -108� I've tried two bluetooth mice, and a standard cord mouse. The same result. It seems that it's the USB controllers are the only components affected, so far. Mousepad works properly, but I'm not use to it. I have to constantly remove and load xhci_pci & xhci_hcd, as root. rmmod xhci_pci rmmod xhci_hcd modprobe xhci_pci modprobe xhci_hcd Mouse works after that for a short time. Nota bene: Devices work properly under openSuSE Leap 15.2 x86_64, kernel 5.3.18-lp152.106-default (old HP Pavillion). This bug resembles https://bugzilla.opensuse.org/show_bug.cgi?id=1193652 -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1204063] New: Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204063 Bug ID: 1204063 Summary: Kernel 5.19.8 appears to be missing lpuart earlycon and console Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: afaerber(a)suse.com Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddavis(a)suse.com, dmueller(a)suse.com, guillaume.gardet(a)arm.com, kernel-bugs(a)opensuse.org, mbrugger(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- Despite kernel command line "console=ttyLP0,115200 earlycon=lpuart32,0x5a060000,115200" on an NXP i.MX 8QM based Variscite VAR-SOM-MX8 module based device, I am not seeing any kernel serial output other than EFI stub: Loading Linux 5.19.8-1-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... or without EFI: Starting kernel ... Having ruled out a red herring of EFI stub: ERROR: Failed to install memreserve config table! as caused by old U-Boot 2018.03 having a hardcoded config table array size of 2, the lack of output most likely is because of: CONFIG_SERIAL_FSL_LPUART=m git-blame points to a SLE15-SP2 sync: https://github.com/openSUSE/kernel-source/commit/769684a2fa08#diff-a9e1c242… Serial Kconfig options need to be built-in (=y) in order to enable their sub-option *_CONSOLE=y, needed for both console= and earlycon= kernel options. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1203748] New: Laptop very slow in battery mode (Lenovo Thinkpad T470)
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203748 Bug ID: 1203748 Summary: Laptop very slow in battery mode (Lenovo Thinkpad T470) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For some reason my laptop gets very slow in battery only mode. I notice this when watching videos. It makes it rather unusable when not connecting it to power. It looks like it goes into some deep powersave mode. I would like to avoid this even if this would half the running time in battery mode. Which information do you need? -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 1202138] New: PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202138 Bug ID: 1202138 Summary: PowerPC machine crashes frequently after upgrading to Leap 15.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: marius.kittler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading a PowerPC machine (the openQA worker qa-power8-4-kvm.qa.suse.de) from Leap 15.3 to Leap 15.4 that machine crashes frequently. It usually does not stay on for more than a few hours. Downgrading the machine (by rolling back to the last BTRFS snapshot with Leap 15.3) allows the machine to run stable again. Note that there's actually a second machine (the openQA worker qa-power8-5-kvm.qa.suse.de) that we managed to operate without crashes on Leap 15.4. Both machines seems very similar to me so I'm not sure whether one is crashing and the other one not. Note that in the first place both machines did not boot on Leap 15.4. It seemed to be stuck at some point and the kernel logged messages like ``` [ 197.877239][ C62] watchdog: BUG: soft lockup - CPU#62 stuck for 25s! [swapper/62:0]` quite frequently ``` quite frequently. So I added the kernel parameter `nmi_watchdog=0`. With this parameter both machines could boot on Leap 15.4 (but as mentioned only qa-power8-5 runs stable without crashing). So the kernel command line used is: ``` root=UUID=89ca2dff-86af-478b-8d4c-2a45ca689fd5 nospec kvm.nested=1 kvm_intel.nested=1 kvm_amd.nested=1 kvm-arm.nested=1 crashkernel=210M nmi_watchdog=0 ``` Not sure what other details could be relevant. Unfortunately the journal does not have any interesting message right before the crash. Via SOL I could once see a kernel panic being logged: ``` QA-Power8-4-kvm login: [ 365.807470][ T3923] EXT4-fs error (device sdb1) in ext4_free_inode:362: Corrupt filesystem [ 438.050890][ T94] Kernel panic - not syncing: corrupted stack end detected inside scheduler [ 438.051046][ T94] CPU: 16 PID: 94 Comm: ksof ``` (The filesystem error is likely just a symptom of the crashes.) Any advice what I could try? Maybe another kernel parameter? Maybe booting Leap 15.4 but with the kernel version from 15.3 (not sure how I'd do that, though - so any advice would be welcome if that idea sounds helpful)? By the way, that's `/proc/cpuinfo` on the problematic machine: ``` root=UUID=eebe647f-e867-416e-a0fa-7a6732bfcf9d nospec kvm.nested=1 kvm_intel.nested=1 kvm_amd.nested=1 kvm-arm.nested=1 crashkernel=210M martchus@QA-Power8-4-kvm:~> cat /proc/cpuinfo processor : 0 cpu : POWER8, altivec supported clock : 3857.000000MHz revision : 2.0 (pvr 004d 0200) [�� repeated 7 more times with processor 8, 16, 24, 32, 40, 48 and 56] timebase : 512000000 platform : PowerNV model : 8348-21C machine : PowerNV 8348-21C firmware : OPAL MMU : Hash ``` On the stable machine it looks very similar but it is actually a model with more processors: ``` processor : 0 cpu : POWER8 (raw), altivec supported clock : 3857.000000MHz revision : 2.0 (pvr 004d 0200) [�� repeated 13 more times with processor 8, 16, 24, ��] timebase : 512000000 platform : PowerNV model : 8335-GCA machine : PowerNV 8335-GCA firmware : OPAL MMU : Hash ``` That's the relevant ticket on the openQA infrastructure tracker (for additional context): https://progress.opensuse.org/issues/114565 -- You are receiving this mail because: You are the assignee for the bug.

1 32