I reported the "kworker/u32:2+events_unbound" problem as a Bug #2099748.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2098668
Title:
nouveau crashes when fwupd requests DPCD reads on d
Public bug reported:
When viewing videos sometimes the kernel thread
kworker/u32:2+events_unbound starts to consume 100% CPU while the screen
response (including mouse) drops to less than 1 image per second. I
managed to crash the kernel and capture the core image of that crash
while the kernel wa
Another workaround would be to disable the offending services:
"sudo snapctl stop --disable firmware-updater.firmware-notifier"
"sudo systemctl disable fwupd-refresh"
"sudo systemctl disable fwupd"
Beware that this disables firmware updates for your hardware, though.
Also beware that I did not te
I enabled crash dumping and triggered the bug but found no crash dump.
So I now think that the USB subsystem in my computer is busted.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
I no longer suspect that this bug can cause Ubuntu to crash or behave
abnormally. I have the nouveau driver disabled for now but today I again
experienced this bug. The kernel thread name was
"kworker/u32:2+events_unbound". Time to file another bug.
--
You received this bug notification because y
Public bug reported:
When connecting a high speed external USB disk (essentially a M.2 NVMe
disk in a box AXAGON EEM2-SG2), the system either locks up or instantly
reboots. There is nothing in /var/syslog indicative of what exactly
happened. The system is stable when not running any of these, so i
The lockup/freeze happens in less than a minute after I start to copy a
file from the device to the computer. Not using USB storage or using
slow USB storage causes no issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
I finally got around to experimenting with modprobe.blacklist=nouveau.
The result is that the problem is gone when there is no nouveau in
kernel so this bug definitely is in the nouveau kernel module.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notific
I also suspect that this bug can cause Ubuntu to crash or behave
abnormally when this bug is triggered. My experience says that when
viewing videos on YouTube, a kernel thread
"kworker/u32:0+events_unbound" starts to eat 100% CPU and the GUI
becomes extremely unresponsive (it updates roughly once i
If the workaround appears to not work, try this quite elaborate process
to try and find out why.
First enter these two commands:
"sudo snap stop firmware-updater.firmware-notifier"
"sudo service fwupd-refresh stop"
These stop everything that tries to access the broken fwupd service.
Now wait un
Changed this to "Incomplete" because I need to do this:
> Can you please experiment with modprobe.blacklist=nouveau?
(I am waiting for a certain long lasting job to finish, it takes about
3-4 days to do so)
Meanwhile could someone running the same hardware ("ASUS TUF Gaming A15
FA507NU_FA507NU/F
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2098668
Title:
nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN
> Can you please experiment with modprobe.blacklist=nouveau?
Unfortunately, no. The ASUS TUF Gaming laptop may need it to run the
display. I suspect that because long ago the nvidia hardware got reset
and the system could not recover from that cleanly. The result was a
computer with dead screen bu
Well, getting the name of the TPM module turns out to be harder than I
expected. The documentation says "Allow blocking specific plugins by
name. Use fwupdmgr get-plugins to get the list of plugins." But running
that command tries to start fwupd via systemd which has no hope of
working so I need to
Ok, here is the complete section of log file with fwupd messing around
with nouveau. I suspect the bug is in nouveau. Requests from userspace
shall not cause kernel to crash.
** Attachment added: "Complete (and huge) log with fwupd messing with nouveau"
https://bugs.launchpad.net/ubuntu/+sourc
Ok, now the thing got running and I got the plugin list but I have no
idea which plugin to disable. I tried amd_gpu and nvme but no luck.
What can I glean from the logs is that the "drm_dp_aux_dev" is the
troublemaker here but I have no freaking idea what plugin uses that.
After some DuckDuckGoing
Well it appears I caught something:
2025-02-17T18:52:07.826887+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU
fwupd[55170]: 17:52:07.824 FuBackendfailed to open device
/sys/devices/virtual/drm_dp_aux_dev/drm_dp_aux0: DPCD read failed: failed to
read 14: Connection timed out
2025-02-
Ok, so now I changed the systemd config to give it 30 minutes to start
and while I was at it I added "-vv" to the Exec line (it is in the same
file) just out of curiosity whether it would work despite my scepticism.
It does so here is the log. And now it makes me think that tpm isn't
going to be th
Mario Limonciello (superm1): Great, we are making some progress now.
Unfortunately I have to wait again because that stupid fwupd is stuck in
that stupid wait (again). Hopefully after I learn about this
DisablePlugins key, it will unstuck itself.
--
You received this bug notification because you
Ok, I have more info now.
1. Adding `-vv` to the Exec line in fwupd.service and posting the new
log will probably not help. The problem is that fwupd takes 20 minutes
to start.
2. There is something rotten in what fwupd is doing. During the 20
minute startup pause the syslog is replete with the D
Richard Hughes (richard-hughes): I tried "-v" and I posted what I found
two comments above. Will try "-vv" as soon as I am done with my current
experiment (it takes about 20 minutes to get rid of a freshly running
fwupd.
--
You received this bug notification because you are a member of Kernel
Pac
Mario Limonciello (superm1): Right now I don't think the nouveau problem
has anything to do with this. This is why I tried to remove these
(rather large) log parts. I posted the full log so that you could try
and find anything else related to fwupd or firmware-updater.firmware-
notifier that I miss
Well, I tried to stop the firmware-updater.firmware-notifier service,
running fwupd in verbose mode and then start the firmware-
updater.firmware-notifier service again. I noticed two problems:
1. For some reason the fwupd program needs 20 minutes to recognize the
TPM module in my computer:
14:38
23 matches
Mail list logo
