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
I reported the "kworker/u32:2+events_unbound" problem as a Bug #2099748.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098668
Title:
nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN
T
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 Ubuntu
Bugs, which is subscribed to
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
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 am adding a version of the test program that uses ASan to verify no
memory bugs occur.
** Attachment added: "An asan enabled version of the posix-memalign test
program"
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1798601/+attachment/5858625/+files/memalign-asan.tgz
--
You receiv
Gone in noble
** Changed in: eglibc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798601
Title:
posix_memalign corrupts heap
To manage notifications ab
Gone in noble
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798601
Title:
posix_memalign corrupts heap
To manage notifications abou
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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098668
Title:
nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN
To manage n
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
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
> 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
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-
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
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
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
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 Ubuntu
Bug
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
Additionally I noticed that there is a fwupd process consuming roughly
15% CPU. Trying to kill this process does not work (not even kill -9). I
don't understand why because this process isn't stuck in uninterruptible
sleep. The process eventually dies and another one replaces it almost
immediately,
Public bug reported:
I was reviewing logs while trying to find evidence of an unrelated issue
and found that fwupd.service fails to start due to a timeout. The logs
below contain only the failure, I could not find the startup:
2025-02-16T00:03:39.859015+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA50
Probably xwayland as my setup does not involve running xorg. Or gnome: why is
org.gnome.SettingsDaemon.XSettings.service needed on Wayland? Gnome does not
use xwayland to run itself, it runs on wayland natively.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
When I think about it now, I started to suspect that the Wayland
compositor in Gnome went wacko when the GPU reset occured.
Unfortunately, I can't replicate this as I have no idea how to easily
trigger a GPU reset. Generally submitting a GPU load that overloads it
should do the trick but constructi
Ok, now I realized that my system runs on Wayland. So no xorg problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066187
Title:
org.gnome.SettingsDaemon.XSettings.service fails to restart proper
Public bug reported:
GNOME did not recover successfully from a GPU reset event. The system is
still running but no direct interaction with it is possible. Keyboard
appears to be running but the screen shows what was on it when the GPU
crashed.
Attached is a SYSLOG fragment showing the problem. At
It looks the syslog fragment I was talking about in the bug report got
lost in the bug submission process. Here it is.
** Attachment added: "SYSLOG fragment showing symptoms of the problem"
https://bugs.launchpad.net/ubuntu/+bug/2066187/+attachment/5780125/+files/syslogfragment
--
You receiv
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832436
Title:
login page first appears sideways for Lenovo miix 510 ubuntu
Public bug reported:
This might be also bug in pulse-audio. The problem
manifests in these ways:
Scenario 1:
1. Assuming output is to a built-in speaker, set the
volume to non-100%.
2. Connect an audio output device (e.g. headphones).
3. Set the volume to non-100% but visibly different from
The chromium-browser metadata needs fixing (as explained in my last
comment) so that libnss3 gets upgraded automatically on "apt-get install
chromium-browser".
** Changed in: chromium-browser (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of
> chromium-browser requires a newer version of libnss3 than what was
initially installed.
It is the job of the package manager to either upgrade an outdated
version of a dependency package when the user tries to install something
or to ask the user to update the system first and then try again, no
Public bug reported:
Steps to reproduce (and also what I expected and what happened):
1. Disconnect computer from Internet
2. Install Ubuntu (complete with reboot at the end).
3. After running the (freshly installed) system, connect it to Internet
and open a terminal and follow with the sessio
The additional attached information was sampled at the time after the
chromium-browser successfully completed its install (and after that was
confirmed by successfully launching it as shown in the terminal session)
so any traces of its misbehavior might be long gone before the
attachments were crea
Public bug reported:
The attached program exposes a bug in posix_memalign that causes it to
either silently corrupt heap or cause the memory allocation checker to
report spurious failures. I believe that the former is the case here
because on more complex software (minetest or Irrlight tutorial
ex
40 matches
Mail list logo
