** Tags added: kern-6281
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2013027
Title:
Issues over broadcom brcmfmac43455 firmware
Status in linux-firmware package in Ubuntu:
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2013160
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
lxc checkpoint-restore test case is failing with the following error (it
seems to be unable to connect to a counterpart, maybe it requires to
enable other components):
480010:27:55 INFO | START
ubuntu_lxc.lxc-test-checkpoint-restore
ubuntu_lxc.lxc-test
Ignore "OsLookupColor" -- all Xorg crashes without debug symbols are
reported as being in that function.
--
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/2012832
Title:
Xorg crashes on sec
This bug was fixed in the package pulseaudio -
1:15.99.1+dfsg1-1ubuntu2.1
---
pulseaudio (1:15.99.1+dfsg1-1ubuntu2.1) jammy; urgency=medium
[ Kai-Heng Feng ]
* d/p/0018-bluetooth-Amend-writeout-to-send-more-initial-frames.patch
(LP: #2007331)
-- Kai-Heng Feng Thu, 16 Feb 2
This test is good with newer releases, and we don't have this issue in
newer kernel anymore.
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a m
We have timeout set to 45 minutes, closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
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/1947012
Title:
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2007584
Title:
Jammy update: v6.1.11 upstream stable release
Status
Hi Christian, Alfredo,
5.4.0-146-generic was released yesterday with a fix for the NFS
regression, and it should have less bandwidth consumption than
5.4.0-144-generic.
There is still some reports that it still has higher NFS requests than
before the regression was introduced, so please chime in
Hello, is there anyone who can help here ?
--
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/2012335
Title:
Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores
(256)
Sta
** Changed in: linux
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse rando
I wrote before that on my Lenovo IdeaPad 5 14ARE05 I never got my touchpad
failing randomly.
I did write however that by plugging/unplugging the charger the laptop would
wake up from suspend, and if done while the lid was closed, then the touchpad
would stop working until you suspend and wake up
(In reply to tinozzo123 from comment #15)
> ... meaning I don't experience this bug in
> any form anymore.
Thanks very much for testing this out and reporting the results! Please
don't hesitate to report any other issues you trip over!
I'm going to close this issue as "resolved" by these commits
** Changed in: libpcap (Debian)
Status: Unknown => Won't Fix
--
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/2006557
Title:
Enable rdma-sniffer for libpcap
Status in libpcap packa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubunt
Linux Mint 21.1 Cinnamon (vera) NO SOUND OUTPUT
Issue on Intel NUC8i7HVK with AMD Radeon chip works OK with kernel
5.19.0-32 but failed SOUND output after kernel upgraded to 5.19.0.38.39
and also earlier kernel 5.19.0.35.36.
alsamixer shows no sign of the HDA ATI HDMI sound card after the kernel
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217214.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
Hello. I am still experiencing this bug on 6.1. Could you reopen this
bug, so we will be able to solve it?
--
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/1290110
Title:
Fan stops after r
Created attachment 303914
app
--
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/1922406
Title:
Intel AX210 Wi-Fi card does not work since updating to 1.196
Status in Linux:
In Progress
S
> Thanks for the suggestion. I tried the upstream 5.4.0-144 and also saw
> there's a newer version 5.4.0-145, so I tried that one as well, but the issue
> still persist.
Can you try a newer kernel outside the 5.4 series? Perhaps the latest
LTS kernel, 6.1?
--
You received this bug notification
(In reply to Mario Limonciello (AMD) from comment #79)
> > Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
> > kernel version 5.4.0-137 on HP Elitebook 745
>
> Can you please try with an upstream kernel? Being a distro kernel, it's
> very possible they're missing some
Hello,
Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
kernel version 5.4.0-137 on HP Elitebook 745
I installed the latest: 5.4.0-144 and the issue still persists.
It's not only that the messages appear on the console, but actually takes
several restarts (using the b
> Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
> kernel version 5.4.0-137 on HP Elitebook 745
Can you please try with an upstream kernel? Being a distro kernel, it's
very possible they're missing some of these patches.
--
You received this bug notification because
At least from an "interface to userspace" perspective I think we should
abstract the differences from one platform to another.
It might mean slicing and dicing strings in the kernel, but at least
then we don't have to carry a pile of quirks for every software above
the kernel.
--
You received th
I've got an internal ticket open with the FW team on the possible_values
issue. The ThinkStation implementation doesn't support the WMI call that
provides the possible_values separately (instead they've lumped them in
with the current_value).
The type - I'd forgotten about this. It's not really a
Launchpad has imported 104 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=43197.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
@Victor @Jaroslav Can we have one made for PH315-53 too?
--
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/1912052
Title:
[Acer Spin 5 - SP513-54N] External headset microphone not working o
> Thanks for the suggestion. I tried the upstream 5.4.0-144 and also saw
> there's a newer version 5.4.0-145, so I tried that one as well, but the issue
> still persist.
Can you try a newer kernel outside the 5.4 series? Perhaps the latest
LTS kernel, 6.1?
--
You received this bug notification
(In reply to Mario Limonciello (AMD) from comment #79)
> > Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
> > kernel version 5.4.0-137 on HP Elitebook 745
>
> Can you please try with an upstream kernel? Being a distro kernel, it's
> very possible they're missing some
> Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
> kernel version 5.4.0-137 on HP Elitebook 745
Can you please try with an upstream kernel? Being a distro kernel, it's
very possible they're missing some of these patches.
--
You received this bug notification because
Hello,
Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
kernel version 5.4.0-137 on HP Elitebook 745
I installed the latest: 5.4.0-144 and the issue still persists.
It's not only that the messages appear on the console, but actually takes
several restarts (using the b
I can confirm similar same results as Toni A. with a Qualcomm Atheros
QCA6390 (Dell XPS 15 9500)on Kernels 6.2.7-arch1-1 and 6.1.20-1-lts.
--
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/199
Same issue here with a Qualcomm Atheros QCA6174 chip (Acer Aspire 5) and
a recent 6.1.15 kernel (Fedora 37).
Reloading kernel modules or messing with the USB power settings did not
help. A simple reboot won't do either, you need to poweroff the machine.
My workaround was to disable the Wi-Fi conn
Daniel, thanks for the suggestion!
This is quite possibly a duplicate of
https://gitlab.freedesktop.org/drm/amd/-/issues/2352.
I'm evaluating the suggestion to add "amdgpu.dcdebugmask=0x10" to the
kernel boot parameters. That parameter seems to disable PSR, see below.
➜ ~ sudo cat /sys/kernel/d
Yeah I tried to reproduce the same on 5.15 kernel (since it's supported
by intel-i915-dkms, 5.19 and 6.1 are not supported and fails on i915
module compilation).
The results are in general the same:
https://errors.ubuntu.com/oops/f8d291da-cd9c-11ed-b9ad-fa163ef35206
It's most likely i915 driver,
Public bug reported:
Sorry, I don't have further details.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-kernel-common-525 525.89.02-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvi
** Changed in: gnome-shell
Status: Unknown => New
--
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/2003031
Title:
[i915] Using gnome-shell with a USB-C dock causes the kernel to log
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
In addition a test build for lunar's 6.2 was done in PPA at:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2013088
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: High
Assignee: Skipper Bug Screeners (s
Patch request submitted for lunar:
https://lists.ubuntu.com/archives/kernel-team/2023-March/thread.html#138158
Updating status for series lunar to 'In Progress'.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
[Impact]
Connect 2 or more external monitors via type-C docking station, the dp-mst
function is working correctly. However, after unplugging the docking station,
the internal display seems to freeze for more than 5 seconds to get back with
normal display.
[Fix]
Intel relea
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2013108
Title:
Bluetooth HP810-160 Not Activa
I'm going to set this to Won't Fix because that seems to be an important
part of the solver logic, and the workarounds - running upgrade first,
or using ubuntu-drivers - are easy to do and the potential for
regression significantly outweighs them.
This will get solved eventually by a nicer solver
We tested and confirmed it's fine on proposed kinetic kernel
Thanks!
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
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
** Changed in: apt (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not install nvidia-dri
** Description changed:
+ SRU Bug Template:
+ =
+
+ [ Impact ]
+
+ * In case clear_user() crosses two pages and faults on the second page the
+kernel may write lowcore contents to the first page, instead of
+clearing it.
+
+ * The __clear_user() inline assembly misses
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Summary changed:
- [UBUNTU 18.04] kernel: fix __clear_user() inline assembly constraints
+ kernel: fix __clear_user() inline assembly constraints
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.21) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
apt/2.0.9 (armhf)
bilibop/unknown (s390x)
freeipa/unknown (s390x)
fwupd/1.7.9-1~20.04.1 (armhf)
libsoup2.4/2.70.0-1
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.21) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
apt/2.0.9 (armhf)
bilibop/unknown (s390x)
freeipa/unknown (s390x)
fwupd/1.7.9-1~20.04.1 (armhf)
libsoup2.4/2.70.0-1
This bug was fixed in the package linux-raspi - 6.2.0-1003.3
---
linux-raspi (6.2.0-1003.3) lunar; urgency=medium
* lunar/linux-raspi: 6.2.0-1003.3 -proposed tracker (LP: #2009847)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
* Miscellaneous upstream
Marking CONFIG_SCSI_VIRTIO=y enables initrd-less boot on generic kernel,
enabling any Ubuntu installation to be lifted from any hardware and
converted into a VM which will, even with corrupted initrd and missing
modules, be able to boot by default. This is an extremly useful property
to have on all
I think we debugged this recently but I'm not sure where the end result
of this is that we do not mark packages for removal that have an upgrade
available, hence we end up without a removal request after the first
stage solver, and the Conflicts solver that runs after can't solve that.
--
You rec
Reproduced issue and dumped test case into https://salsa.debian.org/apt-
team/apt-tests/-/blob/main/edsp/fail-ubuntu-1992513.edsp.log for future
analysis when doing solver work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphi
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skip
** Description changed:
Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to
linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots
with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter.
In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8,
Public bug reported:
I could not install it
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-nvidia-5.19-tools-common (not installed)
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
AptOrderi
Just a quick note to inform that the issue is also present with the
ubuntu 6.1.0-1008-oem kernel which should be extra close to the tip of
mainline. Thus, the issue is most likely still present in mainline.
--
You received this bug notification because you are a member of Kernel
Packages, which i
>apport-collect 2013027' and attach dmesg from both when using the
original ubuntu and the windows firmware.
I'll add dmesg after re-install of of the original linux-firmware from
ubuntu which should be close to what original ubuntu does but might not
be totally equivalent to it in case some non-u
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-5.15 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.
Public bug reported:
Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to
linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots
with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter.
In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means
Public bug reported:
Description: kernel: fix __clear_user() inline assembly constraints
Symptom: In case clear_user() crosses two pages and faults on the
second page the kernel may write lowcore contents to the
first page, instead of clearing it.
Problem:
You have been subscribed to a public bug:
Description: kernel: fix __clear_user() inline assembly constraints
Symptom: In case clear_user() crosses two pages and faults on the
second page the kernel may write lowcore contents to the
first page, instead of cle
Thanks again, but why is it not possible to roll back the NFS change and
roll out only the security relevant content in the meanwhile?
Nearly one month and counting for balancing the need for systems being
up vs. having security updates is not quite tenable for most system
administrators.
--
You
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
--
You received this bug not
I apologize for any confusion that may have arisen.
The test kernel 5.15.0-67.74+test20230307b2h2cbb6062f8eb has completely
reverted the new mechanism, resulting in the same behavior as before.
We understand that this can be concerning, and we want to assure you that we
are actively working towar
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix
Hi Du ChengEn,
Thanks for your efforts in making this change for this SRU cycle.
However, I can confirm that we too are facing challenges with orders of
magnitude (>10x) increases in ACCESS calls, with the newly released
kernels. Still better/differently than 5.15.0-67, but not suitable for
produ
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/2011625
Title:
Focal update: v5.4.232 upstream stable relea
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2012673
Title:
Jammy update: v5.15.94 upstream stable relea
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2012665
Title:
Jammy update: v5.15.93 upstream stable relea
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
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/2012977
Title:
Kinetic update: upstream stable patchset 2
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
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/2012307
Title:
Kinetic update: upstream stable patchset 2
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
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/2012438
Title:
Kinetic update: upstream stable patchset 2
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is awaiting verification that the linux/5.19.0-40.41 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, chan
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2013064
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2013063
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
16637 zram01 5 TINFO: make xfs filesystem on /dev/zram3
16638 Filesystem must be larger than 300MB.
16639 Usage: mkfs.xfs
16640 /* blocksize */[-b size=num]
16641 /* config file */[-c options=xxx]
16642 /*
Public bug reported:
212921:50:41 INFO | START
ubuntu_kvm_unit_tests.debug-wp-migration
ubuntu_kvm_unit_tests.debug-wp-migrationtimestamp=1679867441
timeout=1800localtime=Mar 26 21:50:41
213021:50:41 DEBUG| Persistent state client._record_indent now
I think Ben's question could be clarified with:
How does "login" relate to non-login (non-interactive) processes started
automatically via system processes?
Our issue is with suexec-like mechanisms, and the 2 orders of magnitude
increase ACCESS and 1 order of magnitude for LOOKUP, while significa
** Tags added: gamma lunar nightlight
** Changed in: mutter (Ubuntu)
Status: Invalid => Confirmed
** Tags added: tearing
--
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/1990377
Tit
Skipped "media: dvb-core: Fix UAF due to refcount races at releasing" already
applied as CVE-2022-41218.
Skipped "drm/vmwgfx: Validate the box size for the snooped cursor" already
applied as CVE-2022-36280.
Skipped "ext4: fix corruption when online resizing a 1K bigalloc fs" and "ext4:
fix corru
Du ChengEn, thank-you for your additional comments. We are seeing good
behaviour after the patch.
However, (and please feel free to call me stupid) when you talk about user's
login time, how does this reflect with system processes, such as www-data
(apache2), or similar? Is a "login" for suc
Hi,
I would like to share my thoughts on the increase in LOOKUP operations, which
may be attributed to a new mechanism introduced in the Linux 6.2-rc3 NFS client
side.
This mechanism clears the access cache as soon as the cache timestamp becomes
older than the user's login time.
Its primary obj
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: amdgpu hybrid multigpu multimmonitor nvidia
** Summary changed:
- Second screen blank on laptop
+ Second screen blank on AMD+NVID
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2013027
Title:
Issues over broadcom brcmfmac43455 firmware
*** This bug is a duplicate of bug 1995956 ***
https://bugs.launchpad.net/bugs/1995956
** This bug has been marked a duplicate of bug 1995956
amdgpu no-retry page fault resulting in black screen and unresponsive system
** Description changed:
Mar 27 12:50:37 juliuswork kernel: [ 9754.38
Retriggered systemd adt tests for all architectures supported for
bionic:linux-meta-hwe-5.15, version
5.15.0-69.76~20.04.1 and test now passes. Logs for reference:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20230328_034339_ab6b2@/log.gz
https://autopkgtest.ubu
While the operation rates are drastically improved compared to the
broken kernel, even with the the patched kernel 5.15.0-69.76 we're still
seeing a large increase in NFS ACCESS operations, up from about 90/s to
1500/s over a couple servers. Additionally, about a 5x increase in
LOOKUP operations is
1 - 100 of 109 matches
Mail list logo
