Already in lunar and unstable.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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
All autopkgtests for the newly accepted linux-meta-hwe-5.15
(5.15.0.75.82~20.04.36) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.21 (armhf)
Please visit the excuses page listed below and investigate the
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 2023695
and then change the status of the bug to 'Confirmed'.
If, due to the
https://lists.ubuntu.com/archives/kernel-team/2023-June/140361.html
--
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/2023695
Title:
[Azure][MANA][VLANTagging] Support for VLAN Tagging for
Public bug reported:
SRU Justification
[Impact]
This request is from MSFT LSG team to backport the MANA VLAN Tagging
Support, the patch have been accepted upstream in and in the Linux next
tree.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b803d1fded40
[Test
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1033.38~20.04.1 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-focal' to
'verification-done-focal'. If the
** Changed in: linux-intel-iotg (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
PR for the above 30 commits requested for jammy, plus setting a default
for a new kernel option
** Patch added: "-pull.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853306/+attachment/5679544/+files/-pull.patch
--
You received this bug notification because you are a
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: In Progress => Triaged
** Changed in: linux-intel-iotg (Ubuntu)
Status: In Progress => Triaged
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux-intel-iotg (Ubuntu)
** Changed in: linux-intel-iotg (Ubuntu)
Status: New => Triaged
** Changed in: linux-intel-iotg (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
I have identified this as a RAZER Core X Chroma USB port available
across the Thunderbolt 3 connection.
By disconnecting and connecting I see the mfg is set , and this is
indeed on the RAZER Core X Chroma, device 8:
$ lsusb
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004
** Description changed:
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
Appearing in Ubuntu 22.04 as well:
[Mon Jun 12 12:59:44 2023] usb usb8: We don't know the algorithms for LPM
for this host, disabling LPM.
[Mon Jun 12 12:59:44 2023] usb usb8: New USB device found, idVendor=1d6b,
idProduct=0003, bcdDevice= 6.02
[Mon Jun 12 12:59:44 2023] usb usb8: New USB
I hit his bug as well in Ubuntu 22.04 with kernel 5.15.0-67-generic
We have a single RAID 5 on 3 drives for 28T. I'm switching to the workaround
from
comment #5.
Jun 4 12:48:11 server1 kernel: [1622699.548591] INFO: task md0_raid5:406
blocked for more than 120 seconds.
Jun 4 12:48:11 server1
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.15
(5.15.0.75.82~20.04.33) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
linux-lowlatency-hwe-5.15/5.15.0-75.82~20.04.1 (amd64, arm64)
Please visit the excuses
Hi Dominik,
Some suggestions:
* I like that we are disambiguating obtaining 22.04.0 versus something that
acquires the latest version. I think that's a nice improvement overall, not
just for casper.
* I believe that creating the backend for those -latest URLs would need
ubuntu-cdimage changes
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
** Tags added: verification-done-f
** Tags removed: verification-done-f
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2017600
Title:
I have checked this with a lunar derivative (aws), and I can confirm
that the size decreased as expected:
from
112M1003/usr/
to
26M 1005/usr/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
System has been running stable for the entire time when not using dmcrypt on
that disk.
dmcrypt+btrfs has been working perfectly on OS disk since the beginning.
> lsblk
nvme0n1 259:00 2000398934016 0 disk
├─nvme0n1p1 259:10 805306368 0 part
│ └─LUKS_BOOT 253:10
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 2023662
and then change the status of the bug to 'Confirmed'.
If, due to the
I've reproduced this with the 6.3.0-7-generic kernel from mantic-
proposed.
--
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/2023611
Title:
Unable to remove efi variable with 6.2.0-21.21
Please find the screenshot attached.
** Attachment added: "IMG_20230613_195358.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023662/+attachment/5679513/+files/IMG_20230613_195358.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
I am getting this I/O error stating that
EXT4-fs error (device sda2): __ext4_find_entry:1674 inode #23068673: comm
rs:main Q:Reg: checksumming directory block 0
Kindly someone help me with this error
** Affects: linux (Ubuntu)
Importance: Undecided
Status:
I tested linux-nvidia 5.19.0-1014.14 from jammy-proposed on my kinetic
install. Both GCN1 and GCN2 displays work. I get the ASAN debug message
but everything works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
# VERIFICATION JAMMY - glibc
On an Azure TDX instance installed libc6 and libc-bin from -proposed and
rebooted. It boots successfully.
I also installed a test kernel with the kernel workaround reverted and it
also boots with no problems.
** Tags removed: verification-needed
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/2018470
Title:
Linux 5.19 amdgpu: NULL pointer on GCN2
** Changed in: linux-oem-6.1 (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-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949
Title:
Fix Monitor lost after
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => In
All autopkgtests for the newly accepted linux-meta (5.15.0.75.73) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
initramfs-tools/0.140ubuntu13.1 (amd64)
Please visit the excuses page listed below and investigate the failures,
Test kernels (for all major archs, for regression testing) for jammy/22.04
(with VFIO zPCI pass-through for s390x enabled, so CONFIG_VFIO_PCI_ZDEV_KVM=y,
means build in, not as module) are currently building here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1853306
--
You received this
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 2023650
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu
Public bug reported:
[Impact]
The 3.5mm headphone port in front panel cannot detect the microphone.
[Fix]
Add quirk for headset mic pin on P3 Tower.
[Test]
Tested with alsa audio, mic works fine.
[Where problems could occur]
Low risk to add specific hardware ID.
** Affects: hwe-next
** Changed in: linux (Ubuntu)
Status: Invalid => In Progress
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance:
** Description changed:
[Impact]
No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2
[Fix]
Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2.
[Test]
Tested with alsa audio, audio works fine.
[Where problems could occur]
Risk low due to specific
** Summary changed:
- Add audio support for ThinkPad P1 Gen 6
+ Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2
** Description changed:
[Impact]
- No sound output or sound output is too low on ThinkPad P1 Gen 6
+ No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16
All autopkgtests for the newly accepted linux-meta-raspi (5.15.0.1032.29) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
acpi-call/unknown (arm64)
backport-iwlwifi-dkms/unknown (arm64)
bbswitch/0.8-10ubuntu2.1 (arm64)
This bug is awaiting verification that the linux/5.15.0-75.82 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-75.82 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change
** Merge proposal unlinked:
https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/444370
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812194
Title:
rtnetlink.sh in
** Merge proposal unlinked:
https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/444370
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1932549
Title:
seltests/net:
** Merge proposal unlinked:
https://code.launchpad.net/~thibf/+git/adt-matrix-hints/+merge/444544
** Merge proposal unlinked:
https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/444370
--
You received this bug notification because you are a member of Kernel
Packages, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.19 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
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/2023636
Title:
package linux-libc-dev
** Description changed:
[Impact]
+ dell_laptop created a non-working backlight driver before nvidia is loaded,
that leads to the system can't adjust the display brightness.
+
+ [Fix]
+ The patch prevents platform driver(dell_laptop) from creating backlight
driver after win8.
+
Public bug reported:
[Impact]
dell_laptop created a non-working backlight driver before nvidia is loaded,
that leads to the system can't adjust the display brightness.
[Fix]
The patch prevents platform driver(dell_laptop) from creating backlight driver
after win8.
** Tags removed: need-duplicate-check
--
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/2023636
Title:
package linux-libc-dev 5.15.0-72.79 failed to install/upgrade: unable
to open
Public bug reported:
Got a popup with a generic error
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-libc-dev 5.15.0-72.79
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture:
All autopkgtests for the newly accepted linux-meta-intel-iotg (5.15.0.1032.31)
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-intel-iotg/5.15.0-1032.37 (amd64)
Please visit the excuses page listed below and investigate the
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.15
(5.15.0.74.81~20.04.32) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
linux-lowlatency-hwe-5.15/5.15.0-74.81~20.04.1 (amd64, arm64)
Please visit the excuses
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/2023401
Title:
[Dell XPS 17 9700] Upon
Thanks. That log suggests it only took 2 seconds to shut down, and
systemd clearly intended to power off the machine:
juin 13 09:20:47 celian-XPS-17-9700 systemd[1]: Finished
systemd-poweroff.service - System Power Off.
juin 13 09:20:47 celian-XPS-17-9700 systemd[1]: Reached target
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The
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/2023580
Title:
Lenovo Yoga 730-13IWL
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
With a dedicated Management Board, adherence to stringent journalistic
standards, and a commitment to inclusivity and data-driven decision-
making, World Music Views® continues to be a trusted and reputable
source for music news and services https://worldmusicviews.com
--
You received this bug
The Problem remains in the kernel 6.2.0-20.20
--
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/2023580
Title:
Lenovo Yoga 730-13IWL touchscreen only works with Pen
Status in linux
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The
All autopkgtests for the newly accepted linux-meta-raspi (5.15.0.1031.28) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/unknown (arm64)
bbswitch/unknown (arm64)
dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1
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 2023629
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The
Public bug reported:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former contains pages
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 2023585
and then change the status of the bug to 'Confirmed'.
If, due to the
>From what I can tell, this is most likely to be a hardware issue like:
* The graphics card not making clean contact with the slot.
* Hardware failure of the motherboard.
* Hardware failure of the graphics card.
But a bit of googling suggests that other people encountering the same
error
That sounds like a kernel problem, but you're not currently using a
supported Ubuntu kernel. Can you try booting the Ubuntu kernel? It
should be version 6.2.0-20.20
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Summary
78 matches
Mail list logo
