Public bug reported:
SRU Justification:
[Impact]
The mlxbf-bootctl driver is not using the latest upstream commits.
There is a SAUCE patch in Jammy that can be reverted and replaced with upstream.
Also, there are three upstream patches that are missing from the mlxbf-bootctl
driver in Jammy.
[F
Public bug reported:
SRU Justification:
[Impact]
The 'smatch' static analyzer tool raised 5 warnings against the EDAC
driver. There is one warning for each call to "bluefield_edac_readl()"
since the code uses the result of the function call even if there is an
error (leaving resulting value uni
Public bug reported:
Ubuntu goes to blank screen and shuts down with no warning or information.
It has happen three times in the last month.
Firefox was open at the time.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: crash (not installed)
ProcVersionSignature: Ubuntu 6.8.0-52.53~22.04.1-g
Public bug reported:
Ubuntu 25.04.5 abruptly shuts down without any action.
I tried to use apport-retrace but no result.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: crash (not installed)
ProcVersionSignature: Ubuntu 6.8.0-52.53~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-52-generic x86_64
Public bug reported:
Sorry if I'm reporting this against the wrong package.
The default `/boot/firmware/config.txt` file in `noble` server contains
the directive `enable_uart=1` in a section for `[all]` Raspberry Pi
versions. The documentation at
https://www.raspberrypi.com/documentation/computer
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_gige driver does not utilize the msglvl infrastructure, so
there is no way to dynamically enable/disable certain debug log entries
from the driver.
[Fix]
The fix is to add logic for setting a default msglvl, providing support
for get/s
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_gige driver open() method includes a segment of BF2-specific
code that waits for autoneg completion before proceeding. The open()
method should not pend waiting for this link up event.
[Fix]
The fix is to move BF2 autoneg logic out of
Interesting, are you able to share which kernel versions include the
fixes for this issue?
--
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/2038492
Title:
workqueue: inode_switch_wbs_work_
Public bug reported:
Running sudo apt upgrade, I received the following:
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (=
6.8.0-52.53); however:
Package linux-headers-generic-hwe-24.04 is not conf
Public bug reported:
Running sudo apt upgrade, I received the following:
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (=
6.8.0-52.53); however:
Package linux-headers-generic-hwe-24.04 is not conf
Public bug reported:
SRU Justification:
[Impact]
There are paths in the mlxbf_gige driver open() and probe() functions
where a failure happens without a dmesg log entry.
[Fix]
The fix is to add dmesg log entries for all open() and probe() failures
[Test Case]
Unit tested only, since these ar
Thanks for sharing all of this, Gerald. I confirm that I am unable to
reproduce the issue after installing your test kernel. In case anyone is
interested, I wrote a blog post about our debugging journey on this
issue: https://dasl.cc/2025/01/01/debugging-our-new-linux-kernel/
--
You received this
Problem related to the nouveau driver.
when right clicking the sub menu flickers, after a few times the system freezes.
I can't find a compatible driver.
david@david-ThinkPad-T510:~$ inxi -G
Graphics:
Device-1: NVIDIA GT218M [NVS 3100M] driver: nouveau v: kernel
Device-2: Lenovo Integ
Seeing similar issues in kernel versions linux-image-5.15.0-127-generic
and linux-image-5.15.0-128-generic.
level=warning msg="Failed to install iptables rules" error="cannot
install static proxy rules: unable to run 'ip6tables -t mangle -A
CILIUM_PRE_mangle -m socket --transparent -m mark ! --mar
BACKGROUND
-
We were also seeing these log lines on some of our web servers at Etsy:
workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 4 times,
consider switching to WQ_UNBOUND
Kernel version: Linux 6.8.0-1019-gcp #21~22.04.1-Ubuntu SMP x86_64
x86_64 x86_64 GNU/Linux
When t
@Anant and @rickywu,
The current build of Mint 22 (as of 15 Dec. 2024 seems to execute
xmrig-6.22.2 without a problem.
--
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/2074520
Title:
Linu
I just got an asrock taichi lite x870e motherboard with 5Gbps ethernet port on
it, and it fails to work.
# uname -a
Linux asrock 6.11.0-1006-oem #6-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 23 11:51:29
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
# lspci -vvnn| grep Real
71:00.0 Ethernet controller [0200]:
Public bug reported:
SRU Justification:
[Impact]
The BlueField-1/BlueField-2 EDAC driver in Jammy repo consists of several SAUCE
patches.
There are now equivalent upstream patches that should be used instead.
[Fix]
1) Revert the three SAUCE patches for bluefield_edac driver
2) Cherry pick fo
Public bug reported:
after the latest update I am having the wifi drop out sporadically also
it seems to take quite a long time to find wifi on start up.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-45-generic 6.8.0-45.45
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic
Confirmed mitigations=off gets things down to 18s in production
environment. I suppose there is still the outstanding question of why
the same python binary is 40% slower on ubuntu24 than ubuntu21, but at
least it isn't 6 times slower or worse.
** Changed in: linux (Ubuntu)
Status: New =>
Looking at the patch between 5.15.0-43-generic and 5.15.0-46-generic, I
saw that some mitigations were introduced. Even though my colleague
indicated he had already determined that mitigations=off did not help, I
decided it was worth double checking.
Using mitigations=off with today's daily serve
The above attachments were collected on a ubuntu20 install booting the
latest hwe kernel. In retrospect, that is probably confusing since the
title of this bug is about ubuntu22. ubuntu 24 server LTS is what I
actually care about. I am happy to gather those attachments on any
OS/kernel combinati
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824240/+files/acpidump.txt
--
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/20
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824239/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824238/+files/UdevDb.txt
--
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/2083077
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824236/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824237/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824235/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824234/+files/Lsusb-v.txt
--
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/2083
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824233/+files/Lsusb-t.txt
--
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/2083
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824232/+files/Lspci-vt.txt
--
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/20
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824230/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2083077/+attachment/5824231/+files/Lspci.txt
--
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/2083077
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
I suspect this is a kernel bug.
With ubuntu <= 21, I find that this runs in about 13 seconds:
python3 -c "import timeit; print(timeit.Timer('for _ in range(0,1000):
pass').timeit())"
Wi
More data points:
RHEL9 (kernel 5.14.0) w/ HT: 22s
RHEL9 (kernel 5.14.0) w/o HT: 22s
Slackware (kernel 5.15.161) w/ HT: 155s
Slackware (kernel 5.15.161) w/o HT: 22s
ubuntu20 (kernel 5.4.0-196-generic) w/ HT: 14s
ubuntu20 (UPGRADED kernel 5.11.0-22-generic) w/ HT: 19s
ubuntu20 (UPGRADED kernel 5.13
Since I've modified my /etc/default/grub
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1 nvidia-
drm.fbdev=1 amdgpu.sg_display=0"
and reinstalled grub I haven't had the issue again
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Having the same issue with external monitor occasional flicker. Moving
the mouse stops the flicker when it occurs. Happens every 15 to 30
minutes.
Adding intel_iommu=igfx_off to /etc/default/grub resolved the issue for
me too.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=igfx_off"
VGA
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I also have this problem with an Acer Nitro 17
AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
6.8.0-41-generic
Nvidia 4060
32GB
Ubuntu 24.04.1 LTS
I can sometimes trigger it by using OrcaSlicer and manipulating 3D objects I'm
going to print.
--
You received this bug notification because you are a
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_livefish driver depends on CONFIG_ACPI but that requirement
is not specified in the driver's Kconfig. So, any attempt to build a
kernel with CONFIG_ACPI not set and CONFIG_MLXBF_LIVEFISH set will
result in a build error.
[Fix]
* Upda
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:david 2643 F pipewire
/dev/snd/controlC0: david 2649 F wireplumber
/dev/snd/controlC1: david 2649 F wireplumber
/dev/snd/controlC2: david 2649
@kees Thanks for jumping on this thread!
>From a technical perspective I agree with you, but I would reason that
it's not really a change one would want end-users of the Ubuntu LTS
kernel to implement.
It comes back to the reasoning mentioned by @Andy in #70 and @Gustav in
#73: a kernel update on
@mruffell Perhaps I'm missing something, but the kernel discussion
thread you linked specifically ends with "The CVE has now been rejected,
thanks for the review!".
Surely that means that the Ubuntu team can revert the commit then?
(unless you are of the opinion that the security vulnerability the
Public bug reported:
SRU Justification:
[Impact]
During the reboot and power cycle testing, QA found an intermittent issue
where "oob_net0" interface would experience RX MAC errors and fail to get
a DHCP-assigned IP. There is a small window where packets can be received
before the RX path is fu
--
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/1936678
Title:
Samsung Laptop support module doesn't load
Status in linux package in Ubuntu:
Won't Fix
Bug description:
This is identi
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_gige driver shutdown() is invoked during reboot
processing, but the stop() logic is not guaranteed to execute
on all distros. If stop() does not execute NAPI remains enabled
during system shutdown and can cause an exception if NAPI is
sch
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_gige driver encounters a NULL pointer exception in
mlxbf_gige_open() when kdump is enabled. The exception happens
because there is a pending RX interrupt before the call to
request_irq(RX IRQ) executes. Then, the RX IRQ handler fires
im
Public bug reported:
SRU Justification:
[Impact]
The support for mlxbf_gige pause frame counters was added to Jammy
via a SAUCE patch. After upstream review, a small issue was fixed
that makes the SAUCE patch different from the upstream commit.
[Fix]
The fix is to replace the SAUCE patch in the
Public bug reported:
SRU Justification:
[Impact]
The BlueField-2 and BlueField-3 silicon designs include a
provision for reporting pause frame counters, but the driver
(mlxbf_gige) does not have software support yet.
[Fix]
The fix is to update the mlxbf_gige driver to support the
"get_pause_st
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 2455 F wireplumber
/dev/snd/controlC1: david 2455 F wireplumber
/dev/snd/seq:david 2438 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Dmesg log from OEM kernel
** Attachment added: "dmesg_out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+attachment/5748485/+files/dmesg_out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
lsusb output
** Attachment added: "lsusb_out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+attachment/5748486/+files/lsusb_out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
When you connect the headset which is based on Bluetooth LE it connects
and then almost immediately disconnects. This does not happen when
using the 6.5.0-1009-oem kernel Can you poirt whatever changes to
bluetooth from the oem kernel to the generic as the cutomer will not u
Public bug reported:
SRU Justification:
[Impact]
A regression has been introduced in the latest 22.04 kernel by including
the following two commits:
revert "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
addition of upstream "mlxbf_gige: fix receive packet race condition"
The
Public bug reported:
SRU Justification:
[Impact]
There is a SAUCE patch that addresses a mlxbf-gige RX race condition
"UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
This SAUCE patch should be reverted and replaced with upstream content.
[Fix]
Bring in the following upstream c
Public bug reported:
SRU Justification:
[Impact]
There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
report when a secure boot enabled card is using development keys. The program
will instead report lifecycle state as "GA Secured" which is misleading.
[Fix]
Bring in the f
I assume you mean to run this
journalctl -k > journal_good.txt
from the working journal?
--
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/2042075
Title:
Black screen at login after updat
** Attachment added: "journal_good.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716723/+files/journal_good.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Hope these help!
** Attachment added: "journal_good.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716137/+files/journal_good.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Attachment added: "journal_bad.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716136/+files/journal_bad.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
Dell Inspiron AMD A10 Laptop
Linux Mint Mate O/S
After updating the kernel I restarted the laptop. After entering my
password and logging in the screen goes black with occasional flashes
of, I guess i'd call it static.
The same thing happened with the previous kernel I
Just in case I should add the kernels that caused the problem for my
laptop are Linux kernel 5.15.0-88.98, and 5.15.0-87
--
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/2042075
Title:
Bla
I'm experiencing the same issue as well.
I'm using an Asus TUF A15 with an RTX 4050.
Gnome crashes when using multiple screens with Firefox and the file
explorer.
One tip is to debug 'the frozen screen' by changing the screen order in
Settings > Display.
Best regards,
--
You received this bug
** Changed in: linux-meta-oracle (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/2035135
Title:
Oracle Cloud systems not gett
This appears to have been resolved as of 5.15.0.1044.39:
apt-cache policy linux-oracle
linux-oracle:
Installed: 5.15.0.1044.39
Candidate: 5.15.0.1044.39
Version table:
*** 5.15.0.1044.39 500
500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main
amd64 Packages
Public bug reported:
SRU Justification:
[Impact]
The Mellanox BlueField power driver (pwr-mlxbf) has a dependency
on either the BlueField-2 or BlueField-3 GPIO driver. The current
Kconfig does not have the BlueField-3 dependency.
[Fix]
There is an upstream commit that extends the Kconfig to
Public bug reported:
(Please forgive my ignorance of the kernel release process, maybe I've
gotten this all wrong.)
There have been several kernel releases for Jammy lately but the two
systems I have on Oracle Cloud (one amd64 and one arm64) have not been
receiving updates since kernel 5.15.0-104
Public bug reported:
When doing a kernel make in our Jammy repo we notice the follow error
being emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
It appears that while the Jammy baseline is 5.15.99 (as per the top-level
Makefile)
the file s
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_bootctl BlueField platform driver in the Jammy repo
consists of some SAUCE patches. These need to be replaced.
[Fix]
The fix is to revert the four SAUCE patches, replacing them with
upstream commits for the same functionality. One patc
@kleber-souza do you have any reference for which kind of bugs were
resolved between 5.15.0-73-generic and 5.15.0-76.83 that might have
addressed this? Our testing indicates that the newer kernel version is
stable. It would be good to know what specifically caused this issue
--
You received this
-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 4017 F wireplumber
/dev/snd/controlC1: david 4017 F wireplumber
/dev/snd/seq:david 4013 F pipewire
CRDA: N/A
Thanks, we are trying out the jammy kernel to confirm it resolves the
issue. Will report back
--
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/2026229
Title:
Crashing issue with 5.15 kerne
** Description changed:
We have been working on making self-hosted GitHub actions runners
available in Canonical and have encountered an issue which seems to be
- with the kernel. This is a doc with more details:
- https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge-
- MKyQARFDY6hxSjhFFf
Public bug reported:
We have been working on making self-hosted GitHub actions runners
available in Canonical and have encountered an issue which seems to be
with the kernel. This is a doc with more details:
https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge-
MKyQARFDY6hxSjhFFfPvA/edit?usp=
@Samer Attrah (samerattrah)
I had exactly the same problem that you have, I solved it by disabling secure
boot from bios.
(to have permission to disable secure boot I also had to set a supervisory
password from bios as well).
--
You received this bug notification because you are a member of Ke
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 4450 F pulseaudio
CasperMD5CheckResult: unknown
Date: Tue Jun 13 09:45:54 2023
Dependencies:
DuplicateSignature:
package:linux-libc-dev:5.15.0-72.79
Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.2) over
I am experiencing a similar issue, but I'm not sure if it's the same or
not. What I experience is that *if I boot with the second monitor
attached*, once I unplug it, it will never be detected again. However,
if I boot with the second monitor unattached, and then plug it in, I can
consistently un
Public bug reported:
Found after updating from 20.04 to 22.04
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnvidia-gl-390 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98
Uname: Linux 5.15.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture:
In Tomcat versions 9.0.56 to 9.0.58, this message was sometimes emitted
in error; this was fixed in 9.0.59. Since 9.0.63, the log message also
explicitly recommends to use Kernel 5.10 or later, but I am not seeing
that in any of the logs reported here, so these Tomcat versions must be
older than 9.
I am seeing this same issue (static screen) on a fully updated Jammy
system. It is a Beelink Renoir system and I have two external monitors
plugged in via HDMI.
It seems to happen fairly randomly, but most often after the monitors go
to sleep and then are woken up. It resolves itself eventually an
FWIW, the fix mentioned earlier is indeed in Kernel 5.10-RC6 and later:
https://github.com/torvalds/linux/commit/01770a166165738a6e05c3d911fb4609cc4eb416
But if people are hitting it with e.g. a 5.15 Kernel, then... that fix
didn't fix it ;)
--
You received this bug notification because you are
I believe I fixed this in my case by installing the latest DispayLink
drivers from https://www.synaptics.com/products/displaylink-
graphics/downloads/ubuntu. You may also find choosing the not-latest
kernel in the boot menu will help.
--
You received this bug notification because you are a member
x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 3982 F wireplumber
/dev/snd/controlC1: david 3982 F wireplumber
/dev/snd/seq:david 3979 F pipewire
CRDA: N/A
CasperMD5CheckResult
Windows was installed but it’s removed now. I have seen suggestions to
create a bootable usb to disable the WiFi adapter but I’m not sure if
that would work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https:
@Matthew No luck i'm afraid I removed the module and I'm still getting
the same issue. @Jeremy is there any other steps I can try ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs
I have removed the backports and now i'm getting this:
sudo dmesg |grep -i wifi
[3.412202] Intel(R) Wireless WiFi driver for Linux
[3.412300] iwlwifi :00:14.3: enabling device ( -> 0002)
[3.525445] iwlwifi :00:14.3: CSR_RESET = 0x10
[3.525473] iwlwifi :00:14.3: Host
Alos seeing this:
[2.691388] iwlwifi_compat: loading out-of-tree module taints kernel.
[2.698204] Loading modules backported from iwlwifi
[2.698208] iwlwifi-stack-public:master:9904:0e80336f
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Public bug reported:
After upgrading from 22.04 to 23.04 the intel wifi driver is not
loading, I am seeing the following in dmesg:
[ 215.024382] Loading of unsigned module is rejected
[ 262.051998] [ cut here ]
[ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/gene
In my case, they did not.
On Tue, Apr 25, 2023 at 4:01 AM homerlinux <1969...@bugs.launchpad.net>
wrote:
> May be, by any chance, that your zvols contain LVMs?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1969457
>
>
Users of our software (singularity) were affected by this issue.
https://github.com/sylabs/singularity/issues/1499
For historic reasons (old kernels without /dev/loop-control), we have
been creating /dev/loopXX devices directly via mknod, if needed, before
using them.
After the backport of https
prl_fs prl_tg
ApportVersion: 2.26.0-0ubuntu2
Architecture: arm64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david-noble 1659 F wireplumber
/dev/snd/seq:david-noble 1656 F pipewire
CasperMD5CheckResult: pass
Date: Fri Mar 31 14:47:08 2023
I'm on the latest kernel for 22.04 and I still can't get the wifi driver
to load I keep seeing the following:
[ 3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="man_gr
off" pid=522 comm="apparmor_parser"
[ 3.960935] iwlwifi
Public bug reported:
sudo cat /sys/kernel/debug/usb/devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 5.19
S: Manufacturer=Linux 5
Public bug reported:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo contains SAUCE
patches that enable BlueField-3 support. This same functionality
is contained in upstream commits and Jammy repo should utilize them.
[Fix]
The BlueField-3 support will be provided
Thanks, I think I'm now using 5.19.0-35 with the new driver. I'll
monitor for crashes. Is there anything in particular I should look for
in "journalctl -k -b"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https
1 - 100 of 2665 matches
Mail list logo
