[Tumbleweed] Spurious Interrupts Cauisng System Stuttering and Mouse/Keyboard issues

omni@DellG15:~> sudo fwupdmgr get-updates
Firmware metadata has not been updated for 30 days and may not be up to date.
Update now? (Requires internet connection) [y|N]: y
Updating lvfs
Downloading…             [************************************** ]
Successfully downloaded new metadata:
 • 9 devices are updatable
 • 3 devices are supported in the enabled remotes (an update has been published)
Devices with no available firmware updates:
 • CompalA31CSMB
 • DELL0A6E:00 04F3:317E
 • CT1000T500SSD8
 • KEK CA
 • System Firmware
 • TPM
 • Windows Production PCA
Devices with the latest available firmware version:
 • OM3PDP3-AD NVMe KDI 512GB
Dell Inc. Dell G15 5515
│
├─UEFI CA:
│ │   Device ID:          5bc922b7bd1adb5b6f99592611404036bd9f42d0
│ │   Current version:    2011
│ │   Vendor:             Microsoft (UEFI:Microsoft)
│ │   GUIDs:              26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
│ │                       c34a7e6a-bd86-5244-8bd0-7db66fd3c073 ← UEFI\CRT_E30CF09DABEAB32A6E3B07A7135245DE05FFB658
│ │   Device Flags:       • Internal device
│ │                       • Updatable
│ │                       • Supported on remote server
│ │                       • Needs a reboot after installation
│ │                       • Signed Payload
│ │                       • Can tag for emulation
│ │ 
│ └─Secure Boot Signature Database Configuration Update:
│       New version:      2023
│       Remote ID:        lvfs
│       Release ID:       116503
│       Summary:          UEFI Secure Boot Signature Database
│       License:          Proprietary
│       Size:             10.0 kB
│       Created:          2025-04-29 00:00:00
│       Urgency:          High
│         Tested:         2025-10-17 00:00:00
│         Distribution:   fedora 42 (workstation)
│         Old version:    2011
│         Version[fwupd]: 2.0.16
│         Tested:         2025-09-17 00:00:00
│         Distribution:   fedora 42 (workstation)
│         Old version:    2011
│         Version[fwupd]: 2.0.16
│         Tested:         2025-07-24 00:00:00
│         Distribution:   nixos 25.11
│         Old version:    2011
│         Version[fwupd]: 2.0.12
│       Vendor:           Linux Foundation
│       Release Flags:    • Trusted metadata
│                         • Is upgrade
│       Description:      
│       This updates the 3rd Party UEFI Signature Database (the "db") to the latest release from Microsoft.It also adds the latest OptionROM UEFI Signature Database update.
│       Checksum:         6819c8098f09f4332a102194df6a033563aa288073b16315c5b88860fefb7e74
│     
└─UEFI dbx:
  │   Device ID:          362301da643102b9f38477387e2193e57abaa590
  │   Summary:            UEFI revocation database
  │   Current version:    20240301
  │   Minimum Version:    20240301
  │   Vendor:             Microsoft (UEFI:Microsoft)
  │   Install Duration:   1 second
  │   GUID:               f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
  │   Device Flags:       • Internal device
  │                       • Updatable
  │                       • Supported on remote server
  │                       • Needs a reboot after installation
  │                       • Device is usable for the duration of the update
  │                       • Only version upgrades are allowed
  │                       • Signed Payload
  │                       • Can tag for emulation
  │ 
  ├─Secure Boot dbx Configuration Update:
  │     New version:      20250902
  │     Remote ID:        lvfs
  │     Release ID:       130035
  │     Summary:          UEFI Secure Boot Forbidden Signature Database
  │     Variant:          x64
  │     License:          Proprietary
  │     Size:             24.1 kB
  │     Created:          2025-09-02 00:00:00
  │     Urgency:          High
  │       Tested:         2025-12-15 00:00:00
  │       Distribution:   ubuntu 25.10
  │       Old version:    20230501
  │       Version[fwupd]: 2.0.16
  │       Tested:         2025-12-05 00:00:00
  │       Distribution:   fedora 42 (workstation)
  │       Old version:    20250507
  │       Version[fwupd]: 2.0.17
  │       Tested:         2025-11-10 00:00:00
  │       Distribution:   fedora 43 (kde)
  │       Old version:    20230501
  │       Version[fwupd]: 2.0.16
  │     Vendor:           Linux Foundation
  │     Duration:         1 second
  │     Release Flags:    • Trusted metadata
  │                       • Is upgrade
  │                       • Tested by trusted vendor
  │     Description:      
  │     This updates the list of forbidden signatures (the "dbx") to the latest release from Microsoft.
  │     
  │     Some insecure versions of the IGEL bootloader were added, due to a security vulnerability that allowed an attacker to bypass UEFI Secure Boot.
  │     Issue:            CVE-2025-47827
  │     Checksum:         7178302fa23fcb875e7540900e299fb30a76758663efb7e1c56edc25cd3f316a
  │   
  ├─Secure Boot dbx Configuration Update:
  │     New version:      20250507
  │     Remote ID:        lvfs
  │     Release ID:       115586
  │     Summary:          UEFI Secure Boot Forbidden Signature Database
  │     Variant:          x64
  │     License:          Proprietary
  │     Size:             24.0 kB
  │     Created:          2025-01-17 00:00:00
  │     Urgency:          High
  │       Tested:         2025-10-17 00:00:00
  │       Distribution:   fedora 42 (workstation)
  │       Old version:    20230501
  │       Version[fwupd]: 2.0.16
  │       Tested:         2025-06-11 00:00:00
  │       Distribution:   fedora 42 (workstation)
  │       Old version:    20241101
  │       Version[fwupd]: 2.0.11
  │     Vendor:           Linux Foundation
  │     Duration:         1 second
  │     Release Flags:    • Trusted metadata
  │                       • Is upgrade
  │                       • Tested by trusted vendor
  │     Description:      
  │     This updates the list of forbidden signatures (the "dbx") to the latest release from Microsoft.
  │     
  │     Some insecure versions of BiosFlashShell and Dtbios by DT Research Inc were added, due to a security vulnerability that allowed an attacker to bypass UEFI Secure Boot.
  │     Issues:           806555
  │                       CVE-2025-3052
  │     Checksum:         40d3a4630619b83026f66bc64d97a582bbd9223ad53aa3f519ff5e2121d11ca6
  │   
  └─Secure Boot dbx Configuration Update:
        New version:      20241101
        Remote ID:        lvfs
        Release ID:       105821
        Summary:          UEFI Secure Boot Forbidden Signature Database
        Variant:          x64
        License:          Proprietary
        Size:             15.1 kB
        Created:          2025-01-17 00:00:00
        Urgency:          High
          Tested:         2025-10-31 00:00:00
          Distribution:   ubuntu 24.04
          Old version:    20230501
          Version[fwupd]: 1.9.28
        Vendor:           Linux Foundation
        Duration:         1 second
        Release Flags:    • Trusted metadata
                          • Is upgrade
        Description:      
        This updates the list of forbidden signatures (the "dbx") to the latest release from Microsoft.
        
        An insecure version of Howyar's SysReturn software was added, due to a security vulnerability that allowed an attacker to bypass UEFI Secure Boot.
        Issues:           529659
                          CVE-2024-7344
        Checksum:         093e6913dfecefbdaa9374a2e1caee7bf7e74c7eda847624e456e344884ba5f6
      

Tried ‘N’ first, but it didn’t do anything (outputted a similar list as the ‘Y’ command.) My muscle memory took over and I typed clear before I thought “maybe I should include the output of ‘N’”.

@Pandoroeo and what does fwupdmgr security show?

If you check with the hardware manufacturer is there a BIOS update?

omni@DellG15:~> fwupdmgr security
Host Security ID: HSI:1! (v2.0.19)

HSI-1
✔ SMM locked down:               Locked
✔ BIOS firmware updates:         Enabled
✔ Fused platform:                Locked
✔ Supported CPU:                 Valid
✔ TPM empty PCRs:                Valid
✔ TPM v2.0:                      Found
✔ UEFI bootservice variables:    Locked
✔ UEFI platform key:             Valid

HSI-2
✔ SPI write protection:          Enabled
✔ IOMMU:                         Enabled
✔ Platform debugging:            Locked
✔ TPM PCR0 reconstruction:       Valid
✘ UEFI memory protection:        Disabled

HSI-3
✔ CET Platform:                  Supported
✔ Suspend-to-idle:               Enabled
✔ Suspend-to-ram:                Disabled
✘ SPI replay protection:         Disabled
✘ Pre-boot DMA protection:       Disabled

HSI-4
✔ SMAP:                          Enabled
✘ Processor rollback protection: Disabled
✘ Encrypted RAM:                 Not supported

Runtime Suffix -!
✔ CET OS Support:                Supported
✔ fwupd plugins:                 Untainted
✘ Linux kernel lockdown:         Disabled
✘ Linux swap:                    Unencrypted
✘ Linux kernel:                  Tainted
✘ UEFI db:                       Invalid
✘ UEFI secure boot:              Disabled

This system has HSI runtime issues.
 » https://fwupd.github.io/hsi.html#hsi-runtime-suffix

Upload these anonymous results to the Linux Vendor Firmware Service to help other users? [y|N]: 

Based off of my memory (and checked with dmidecode), I am on BIOS version 1.18.0 (released 2024.) The latest bios version available is 1.29.0 (1.26.0 if I want the ability to roll back to my current version). The only issue with updating to newer versions of the BIOS is that I’ve seen semi-frequent complaints about newer BIOS versions.

@Pandoroeo what does the BIOS update README say about the updates through to the latest release say? To me it’s very likely a hardware issue, not operating system releated…

It seems DELL has wiped all BIOS versions from the Dell G15 5515 Ryzen Edition drivers page except for 1.29.0 and 1.26.0, so I am unable to read the changelogs/readme
https://www.dell.com/support/product-details/en-us/product/g-series-15-5515-laptop/drivers
Edit: Nevermind. Clicking into the latest BIOS version, scrolling down, and clicking “Other Available Versions” allows me to see previous versions. But it still seems like some are missing (like version 1.18.0)

Huh?


1 Like

My Dell OptiPlex devices, I have three, an XE3 and two 3080 Micros all updated the BIOS and other firmware over fwupd… Can’t remember if the 5820 workstation did, it may have at some point…

Seems like all the models you listed have support for Linux (found under “Operating System” in their respective driver support page). My model only seems to have Windows 10/11 listed, so that could be why.

Seems like a likely conclusion… Why not download them all and upgrade one at a time to see if that helps?

If you press the F12 key at boot, do you have the option “Firmware Upgrades” if so likely can do it from there…

Among my options of Other Options, I have ‘Bios Setup’, ‘Diagnostics’, ‘SupportAssist OS Recovery’, and ‘Bios Flash Update’. BIOS Flash Update seems to be that.
Just to check, would this run the risk of corrupting the BIOS (as I will be having to do it so many times)?

@Pandoroeo I wouldn’t think so, make sure you read up on the process to upgrade and try one?

Tried a few more things, none of which worked (but I would have done them anyway, so yeah)
Installing steam and prismlauncher
Fixing an error (Selinux and postalias - #25 by cookie170)
Trying x11

Going to post in one more spot before changing BIOS versions because I’m hesitant to update to new a newer BIOS (based on peoples comments)

Note: I take back the ‘only after hibernation/sleeping’ claim. It happens even after fresh boots

Hello,
My issue seems to have been fixed with the help of a knowledgeable (and perceptive) person.

It turns out my system BIOS was using local time instead of UTC time, and linux, for whatever reason, wasn’t automatically setting BIOS to UTC time.
I do also dualboot windows, but I hadn’t booted into windows since a few weeks before installing tumbleweed.

The fix:

I forced windows to use UTC time with reg add HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation /v RealTimeIsUniversal /t REG_DWORD /d 1
I rebooted into windows and then rebooted into linux. Linux was still using local time, even though BIOS was correct.
I ran timedatectl set-local-rtc 0 --adjust-system-clock and then rebooted.
Problem solved!

A side note:
Turns out I was also using proprietary NVIDIA drivers instead of the open NVIDIA drivers.
Fix:
zypper in nvidia-open-driver-G06-signed-kmp-meta
zypper inr

It still has not shown up. I will be marking this as solved.