August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1229745] New: [Build 20240825] dbus-broker: no network after switchjing from NM to wicked
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229745 Bug ID: 1229745 Summary: [Build 20240825] dbus-broker: no network after switchjing from NM to wicked Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4434925/modules/prep are_test_data/steps/13 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation We have a few tests, that install a default GNOME setup (based on NetworkManager), then switch to wicked: After wicked has been started, the network stack seems not to be operational though openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ui_devel@64bit fails in [prepare_test_data](https://openqa.opensuse.org/tests/4434925/modules/prepar… ## Test suite description Maintainer: zluo yast2 upstream test suites. https://progress.opensuse.org/issues/20206 ## Reproducible Fails since (at least) Build [20240825](https://openqa.opensuse.org/tests/4433680) ## Expected result Last good: [20240823](https://openqa.opensuse.org/tests/4430444) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1229555] New: Wicked dummy interfaces no longer come up / "no-device"
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229555 Bug ID: 1229555 Summary: Wicked dummy interfaces no longer come up / "no-device" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876866 --> https://bugzilla.suse.com/attachment.cgi?id=876866&action=edit asgard2.i.o.o journal after boot Hi, we have various interfaces of type `dummy` configured on our openSUSE infrastructure firewall VMs, so far with no issues. They are all configured equally, here is one example: ``` # more /etc/sysconfig/network/ifcfg-d-os-code # ... comments ... STARTMODE='auto' BOOTPROTO='none' INTERFACETYPE='dummy' ``` Since installing updates and rebooting today, they no longer come up (neither automatically nor manually through ifup), returning "no-device". I will attach some information which I hope is useful .. .. from after boot: - `journalctl` .. from after enabling WICKED_DEBUG=all/WICKED_LOG_LEVEL=debug and restarting wickedd: - `wicked --debug all ifup d-os-code` # again just one example interface - `wicked show-config` - `wicked ifstatus --verbose all` - `grep 2024-08-21 /var/log/zypp/history` Let me know if anything of interest is missing. Would appreciate any ideas! I'm reluctant to update the second machine in the pair with this issue. There is another (presumably kernel) issue after the update, which I think is not related and hence reported separately at https://bugzilla.opensuse.org/show_bug.cgi?id=1229552. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1225352] New: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 Bug ID: 1225352 Summary: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://openqa.opensuse.org/tests/4217406/modules/prep are_firstboot/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: --- The Leap 15.5 JeOS image fails to boot in openQA for some time now. Initially it looked to me like an issue with the test infra, but the TW and 15.6 images boot while 15.5 fails consistently. I tried to reproduce the issue locally and except for a slow boot due to no ethernet cable it worked. The package diff between last working and latest build shows changes in aaa_base, coreutils, kernel, less, protobuf, libsemanage, perl, rpm and yast. Could be a kernel issue? ## Observation openQA test in scenario opensuse-15.5-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [prepare_firstboot](https://openqa.opensuse.org/tests/4217406/modules/prepar… ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [13.183](https://openqa.opensuse.org/tests/4120363) ## Expected result Last good: [13.182](https://openqa.opensuse.org/tests/4119085) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 48

[Bug 1228383] New: 'No free space in /boot/efi for new kernel' error during dist-upgrade
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228383 Bug ID: 1228383 Summary: 'No free space in /boot/efi for new kernel' error during dist-upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: v.jag(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876303 --> https://bugzilla.suse.com/attachment.cgi?id=876303&action=edit Zypper dup log During the zypper dup to install 20240725 snapshot i got the following error: “Error: No free space in /boot /efi for new kernel" After reboot PC failed to boot into GUI so i had to rollback to previous snapshot. Zypper output log is attached separately. userv@localhost:~> grep LOADER_TYPE /etc/sysconfig/bootloader LOADER_TYPE="grub2-efi" userv@localhost:~> ls -lR /boot/efi /boot/efi: total 6 drwxr-xr-x 4 root root 2048 Oct 30 2022 EFI drwxr-xr-x 3 root root 2048 Jul 27 12:01 loader drwxr-xr-x 6 root root 2048 Jul 27 16:42 opensuse-tumbleweed /boot/efi/EFI: total 4 drwxr-xr-x 2 root root 2048 Jul 27 12:01 boot drwxr-xr-x 3 root root 2048 Jul 27 12:01 opensuse /boot/efi/EFI/boot: total 3880 -rwxr-xr-x 1 root root 934024 Jul 27 19:16 BOOTX64.EFI -rwxr-xr-x 1 root root 86208 Mar 14 07:58 fallback.efi -rwxr-xr-x 1 root root 155 Jul 27 19:16 grub.cfg -rwxr-xr-x 1 root root 2099056 Jul 27 19:16 grub.efi -rwxr-xr-x 1 root root 846096 Jul 27 19:16 MokManager.efi /boot/efi/EFI/opensuse: total 4124 -rwxr-xr-x 1 root root 64 Jul 27 12:01 boot.csv -rwxr-xr-x 1 root root 155 Jul 30 2023 grub.cfg -rwxr-xr-x 1 root root 2099056 Jul 19 12:59 grub.efi -rwxr-xr-x 1 root root 331776 Jul 27 19:16 grubx64.efi -rwxr-xr-x 1 root root 20 Jul 27 12:01 installed_by_sdbootutil -rwxr-xr-x 1 root root 846096 Mar 14 07:58 MokManager.efi -rwxr-xr-x 1 root root 934024 Mar 14 07:58 shim.efi drwxr-xr-x 2 root root 2048 Mar 30 16:58 x86_64-efi /boot/efi/EFI/opensuse/x86_64-efi: total 4 -rwxr-xr-x 1 root root 3904 Jul 19 12:59 bli.mod /boot/efi/loader: total 4 drwxr-xr-x 2 root root 2048 Mar 30 16:58 entries -rwxr-xr-x 1 root root 32 Jul 27 12:01 random-seed /boot/efi/loader/entries: total 0 /boot/efi/opensuse-tumbleweed: total 8 drwxr-xr-x 2 root root 2048 Jul 30 2023 6.0.5-1-default drwxr-xr-x 2 root root 2048 Jul 27 16:41 6.4.11-1-default drwxr-xr-x 2 root root 2048 Jul 28 09:43 6.9.6-1-default drwxr-xr-x 2 root root 2048 Jul 27 11:54 6.9.9-1-default /boot/efi/opensuse-tumbleweed/6.0.5-1-default: total 0 /boot/efi/opensuse-tumbleweed/6.4.11-1-default: total 0 /boot/efi/opensuse-tumbleweed/6.9.6-1-default: total 0 /boot/efi/opensuse-tumbleweed/6.9.9-1-default: total 0 I'm discussing this issue on openSUSE forums https://forums.opensuse.org/t/no-free-space-in-boot-efi-for-new-kernel-erro… arvidjaar stated that "They attempt to use sdbootutil even though the system is setup to use grub2-efi." -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1229678] New: VUL-0: CVE-2024-45192: element-web: olm: use of base64 when decoding group session keys can lead to successful cache-timing attacks
by bugzilla_noreply＠suse.com 24 Oct '24

24 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229678 Bug ID: 1229678 Summary: VUL-0: CVE-2024-45192: element-web: olm: use of base64 when decoding group session keys can lead to successful cache-timing attacks Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/418589/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: dheidler(a)suse.com Reporter: camila.matos(a)suse.com QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com, cunix(a)mail.de, marius.kittler(a)suse.com, okurz(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1229676 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1229676 +++ An issue was discovered in Matrix libolm (aka Olm) through 3.2.16. Cache-timing attacks can occur due to use of base64 when decoding group session keys. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. References: https://gitlab.matrix.org/matrix-org/olm/ https://gitlab.matrix.org/matrix-org/olm/-/commit/6d4b5b07887821a95b144091c… https://news.ycombinator.com/item?id=41249371 https://soatok.blog/2024/08/14/security-issues-in-matrixs-olm-library/ http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45192 https://www.cve.org/CVERecord?id=CVE-2024-45192 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1229676] New: VUL-0: CVE-2024-45192: TRACKERBUG: olm: use of base64 when decoding group session keys can lead to successful cache-timing attacks
by bugzilla_noreply＠suse.com 24 Oct '24

24 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229676 Bug ID: 1229676 Summary: VUL-0: CVE-2024-45192: TRACKERBUG: olm: use of base64 when decoding group session keys can lead to successful cache-timing attacks Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/418589/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: cunix(a)mail.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- An issue was discovered in Matrix libolm (aka Olm) through 3.2.16. Cache-timing attacks can occur due to use of base64 when decoding group session keys. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. References: https://gitlab.matrix.org/matrix-org/olm/ https://gitlab.matrix.org/matrix-org/olm/-/commit/6d4b5b07887821a95b144091c… https://news.ycombinator.com/item?id=41249371 https://soatok.blog/2024/08/14/security-issues-in-matrixs-olm-library/ http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45192 https://www.cve.org/CVERecord?id=CVE-2024-45192 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1229237] New: games:tools/Bottles: Cursor Size Issue
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229237 Bug ID: 1229237 Summary: games:tools/Bottles: Cursor Size Issue Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software Assignee: vortex(a)z-ray.de Reporter: reiokorn(a)tutanota.com QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When using the Bottles application on openSUSE Tumbleweed (build 20240813) with a display scaling setting above 100%, the cursor size within the GUI becomes excessively large. This issue only occurs under Wayland with scaling enabled. System Information: OS: openSUSE Tumbleweed 20240813 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-1-default (64-bit) Graphics Platform: Wayland Steps to Reproduce: Set display scaling to above 100% in KDE Plasma on Wayland. Launch the Bottles application. Expected Result: The cursor should maintain a consistent size relative to other GUI elements within the application. Actual Result: The cursor size becomes abnormally large when hovering over the Bottles GUI, disrupting the user experience. Terminal Output: Relevant warnings observed during application launch: Gdk-WARNING **: ../gdk/wayland/gdkcursor-wayland.c:210 cursor image size (64) not an integer multiple of theme size (24) This warning is repeated multiple times with different cursor image sizes. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1229019] New: KVM:Starting KVM error "ensure all devices within the iommu_group are bound to their vfio bus driver" after kernel update
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229019 Bug ID: 1229019 Summary: KVM:Starting KVM error "ensure all devices within the iommu_group are bound to their vfio bus driver" after kernel update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: All Status: NEW Severity: Major Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: jniko19aban(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: After start KVM VM I have this error: "Error starting domain: internal error: QEMU unexpectedly closed the monitor (vm=‘win10’): qxl_send_events: spice-server bug: guest stopped, ignoring 2024-08-08T01:45:51.824474Z qemu-system-x86_64: -device {“driver”:“vfio-pci”,“host”:“0000:0b:00.0”,“id”:“hostdev0”,“bus”:“pci.2”,“addr”:“0x0”}: vfio 0000:0b:00.0: group 83 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver." The Intel I350-T2 NIC card is properly configured for VFIO passthrough, it was working correct without any single issue up to kernel 6.4.0-150600.23.14-default. After I did upgrade to latest stable 6.4.0-150600.23.17-default the error described above happened. I have 2 servers which do exactly the same thing after the upgrade to latest stable kernel. I have also tried to passthrough the built in Intel I-217 with the same result. If I revert to the old one 6.4.0-150600.23.14-default everything is working as supposed to be without any single issue. Reproducible: Always Steps to Reproduce: 1.Enable the iommu for Intel on /etc/default/grub 2.Assign the NIC to the VM for passthrough via Virtual Machine Manager (On VM Add Hardware / PCI Host device) 3.Start the VM guest. Actual Results: "Error starting domain: internal error: QEMU unexpectedly closed the monitor (vm=‘win10’): qxl_send_events: spice-server bug: guest stopped, ignoring 2024-08-08T01:45:51.824474Z qemu-system-x86_64: -device {“driver”:“vfio-pci”,“host”:“0000:0b:00.0”,“id”:“hostdev0”,“bus”:“pci.2”,“addr”:“0x0”}: vfio 0000:0b:00.0: group 83 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver." Expected Results: Start the VM guest with the NIC passthrough properly and successfully. -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1218682] New: EFI aarch64 boot failure on honeycomb lx2
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218682 Bug ID: 1218682 Summary: EFI aarch64 boot failure on honeycomb lx2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james.hobson(a)oriel.ox.ac.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We are running micro os (tumbleweed) on two build servers. Two nights ago, these failed to boot after an upgrade, same thing happened last night. The hardware is the honeycomb lx2, the boot log is: Booting `openSUSE MicroOS' Loading Linux 6.6.9-1-default ... Loading initial ramdisk ... [ 0.687447][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000140, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.699962][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.712472][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.724981][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.737490][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.749998][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.762507][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.775015][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.787522][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.800030][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 1.187743][ T99] fsl_mc_bus NXP0008:00: mc_get_version() failed with error -110 [ 5.689703][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.702224][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.714736][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.727248][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.739760][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.752271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.764783][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.777294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.789805][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.802316][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.693031][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.705546][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.718058][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.730569][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.743080][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.755592][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.768102][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.780613][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.793124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.805635][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.696364][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.708881][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.721393][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.733904][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.746416][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.758927][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.771438][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.783949][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.796460][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.808971][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.699708][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.712228][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.724743][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.737256][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.749770][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.762283][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.774797][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.787311][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.799824][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.812337][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.703043][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.715557][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.728071][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.740585][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.753098][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.765611][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.778124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.790637][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.803150][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.815663][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.706370][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.718885][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.731398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.743911][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.756424][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.768937][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.781450][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.793964][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.806477][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.818990][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.709704][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.722219][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.734732][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.747245][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.759758][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.772271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.784785][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.797298][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.809811][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.822325][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.713036][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.725551][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.738064][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.750578][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.763090][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.775603][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.788117][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.800630][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.813143][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.825656][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 44.003022][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [swapper/0:0] [ 45.716367][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.728884][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.741398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.753912][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.766425][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.778939][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.791452][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.803965][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.816479][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.828992][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.719700][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.732214][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.744728][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.757240][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.769754][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.782267][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.794780][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.807294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.819807][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.832320][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 7