All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1099.129) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf)
openafs/unknown (arm64)
openrazer/unknown
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package zfs-linux - 2.2.0-0ubuntu3
---
zfs-linux (2.2.0-0ubuntu3) noble; urgency=medium
* No change rebuild.
-- Paolo Pisati Fri, 17 Nov 2023 09:14:23
+
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
--
You received this
Please use ubuntu-bug to file bug reports, that will include a lot more
useful information. Thanks.
** Information type changed from Private Security to Public
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Package changed: linux (Ubuntu) => ubuntu
--
You received this bug
** Information type changed from Private Security to Public
--
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/2041951
Title:
package linux-tools-common 5.15.0-86.96 failed to
$ uname -a
Linux p5q3 6.6.1-060601-generic #202311151749 SMP PREEMPT_DYNAMIC Thu Nov 16
03:15:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
The same.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm currently using the workaround I found on this page (see Suspend &
Hibernation)
https://github.com/Dunedan/mbp-2016-linux
This gets me around the read-only problem but the bulk of what shows up
in dmesg is still there.
--
You received this bug notification because you are a member of
Public bug reported:
MacBook Pro 13" (late 2016, MacBookPro13,1)
2.4 GHz Dual-Core Intel Core i7
16 GB 1867 MHz LPDDR3
Intel Iris Graphics 540 1536 MB
13.3-inch Built-in Retina Display
1TB Flash Storage
WiFi Broadcom BCM4350 1.0
Dual boot MacOS/Ubuntu with rEFind boot manager.
Ubuntu 22.04.3 LTS
Hello You-Sheng, or anyone else affected,
Accepted firmware-sof into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.6-1ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2039603
Title:
NVIDIA pull requests
** Summary changed:
- NVIDIA pull request 1018-002v1
+ NVIDIA pull request 1018-002v1, 1018-003v1
** Description changed:
Apply pull requests from NVIDIA received on 2023-11-02.
-
Ankur Pawar (1):
- NVIDIA: SAUCE:
** Package changed: linux (Ubuntu) => linux-azure-6.2 (Ubuntu)
** Tags added: jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2043841
Title:
kernel BUG: io_uring openat
This bug is a in the Linux kernel, specifically in the filesystem /
io_uring / audit areas.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
occurs during io_uring openat audit processing. I have a kernel patch
that was accepted into the upstream kernel as well as the v6.6, v6.5.9,
and v6.1.60 releases. The bug was first
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug
** Package changed: ubuntu => linux (Ubuntu)
--
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/2043821
Title:
No resume from deep sleep on i7-8550U w/root on zfs on mantic
Status in linux
Thanks for providing that script Sam. Jamie has nailed the problem in
Comment #2. A *seemingly* obvious solution is to add code to the
/etc/kernel/postinst.d/kdump-tools hook that detects when it is running
in a chroot, and if so, exits before trying to make an initramfs. When
the real system
You have been subscribed to a public bug:
This is an odd one, and I'm unsure what is causing it.
I have a thinkpad T480s with an i7-8550U that used to sleep and resume well in
jammy and lunar.
I have now reinstalled mantic from scratch and I am unable to resume from deep
sleep.
What works and
** Changed in: mesa
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
New
Status
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt
Hello, since the "noble"/24.04 development just started, may I ask if
you/IBM have/has any updates or an opinion if it is be okay to switch
off COMPAT_32BIT_TIME?
(We would like to do switch this off for all architectures.)
** Tags added: noble
--
You received this bug notification because you
Hello, since the "noble"/24.04 development just started, may I ask if
you/IBM have/has any updates or an opinion if it is be okay to switch
off COMPAT_32BIT_TIME?
(We would like to do switch this off for all architectures.)
** Tags added: noble
** Changed in: ubuntu-power-systems
Status:
No update since Oct 27th, unsubscribing sponsors. Please subscribe again
if there is an update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
I don't think we should close it, if you reproduce a hang in Ubuntu it should
be fixed in Ubuntu.
The patch should come in mesa. I already know what patch should fix it in mesa
(it's mentioned in https://gitlab.freedesktop.org/drm/amd/-/issues/2971)
If I build you a PPA to test, can you see if
Folks, A big +1 for enabling bpf LSM by default in the bootconfig.
We are maintainers of KubeArmor (kubearmor.io) and we see that BPF LSM
can go a long way in securing the k8s/containers/VM environments. Not
having BPF LSM by default is a hindrance in the security of these
systems. While we have
Thanks a lot, Mario, for pointing me in the right direction. It's
definitely MCBP what causes it. I've been testing it for a few hours,
and it was _very_ easy to trigger.
It seems to only be triggered (or at least _more frequently_) when using
multiple outputs, and USB-C DP => HDMI through docks.
All autopkgtests for the newly accepted initramfs-tools (0.142ubuntu15.1) for
mantic have finished running.
The following regressions have been reported in tests triggered by the package:
initramfs-tools/0.142ubuntu15.1 (armhf)
Please visit the excuses page listed below and investigate the
** Changed in: linux-azure (Ubuntu Lunar)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
** Changed in: linux-azure (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2042096
Title:
Azure: Update TDX with HCL
Is this bug already fixed and in the update channels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in
Verified requisite change is in focal and jammy releases. Full suite of
boot test and regression tests will suffice for verification.
** Tags removed: verification-needed-focal-linux-gcp
verification-needed-jammy-linux-gcp
** Tags added: verification-done-focal-linux-gcp
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1098.110~18.04.2 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-bionic-linux-
raspi-5.4' to
SRU request submitted to the Ubuntu kernel team mailing list for
unstable/noble, mantic and lunar.
https://lists.ubuntu.com/archives/kernel-team/2023-November/thread.html#146982
Changing status to 'In Progress' for noble, mantic and lunar.
** Changed in: ubuntu-z-systems
Importance:
** Package changed: linux (Ubuntu) => linux-aws (Ubuntu)
** Also affects: linux-aws (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Lunar)
Status: New => In Progress
**
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
+ * Today no s390x-specific vfio-pci devices (zPCI) can be passed
+from a KVM host to a KVM guest (incl. secure execution guests
+in the context of confidential computing).
+
+ * s390x PCI passthrough needs various changes
Public bug reported:
SRU Justification
[Impact]
>From our experiments, we found that not signing leaf functions on AWS
Graviton instances helps improve application performance. We would like
to have the patch
https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8
This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu3
---
firmware-sof (2.2.6-1ubuntu3) noble; urgency=medium
* Integrate 0day mantic SRU 2.2.6-1ubuntu1.1 into noble
* Add RPL topology updates
- UBUNTU: SAUCE: Add topology updates for Intel RPL Dell 0C11 SKU.
I also tried on Jammy,
I confirmed that 20220329.git681281e4-0ubuntu3.23 works well in my pc
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages,
If you want, I can test a specific kernel version for comparision?
--
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/2043561
Title:
rtl8761bu bluetooth dongle bails out or looses device
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Description changed:
make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all
1) there was broad agreement in Riga
2) there is partial agreement in Debian too
-
** Changed in: linux-raspi (Ubuntu Mantic)
Status: Confirmed => In Progress
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-raspi (Ubuntu Mantic)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification
Hello Chris, or anyone else affected,
Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I confirmed that 20230919.git3672ccab-0ubuntu2.4 works well in my mantic
pc
** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Hello You-Sheng, or anyone else affected,
Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
I cannot say, as it is as fresh (K)ubuntu installation.
I can only say, that it depends on Linux, no probs with Windows...
--
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/2043561
Title:
All autopkgtests for the newly accepted linux-meta-lowlatency (5.15.0.91.92)
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-lowlatency/5.15.0-91.101 (amd64, arm64)
systemd/249.11-0ubuntu3.11 (amd64, arm64)
Please visit the
Public bug reported:
Good morning.
Automatic mounting of NTFS partitions is no longer possible.
NTFS3 says they are dirty. This is probably not true. They may not be very
clean. However, this does not pose a particular problem for the NTFS-3G driver.
See this French discussion.
Public bug reported:
make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all
1) there was broad agreement in Riga
2) there is partial agreement in Debian too
https://lists.debian.org/debian-kernel/2023/11/msg00131.html
3) attempt to implement this in noble
4) changes required to:
** Summary changed:
- [UBUNTU 23.04] Kernel config option missing for s390 PCI passthrough
+ [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Nov 17 13:43:45 computer kernel: [14084.051090] watchdog: BUG: soft lockup -
CPU#5 stuck for 719s! [node:36822]
Nov 17 13:43:45 computer kernel: [14084.051099] Modules linked in:
xt_MASQUERADE xt_mark nf_tables nfnetlink ip6table_nat ip6table_filter
ip6_tables iptable_nat
Hello Tom, or anyone else affected,
Accepted initramfs-tools into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.142ubuntu15.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
It turns out that 6.2 is also affected but the bug appears a lot less
often, once every ~20 reboots.
** Changed in: linux-azure (Ubuntu Lunar)
Status: Invalid => Confirmed
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Confirmed
** Description changed:
[Description]
This bug is awaiting verification that the linux-
bluefield/5.15.0-1032.34 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-linux-bluefield' to
On Fri, 17 Nov 2023 at 12:01, Dan <2040...@bugs.launchpad.net> wrote:
>
> @Juerg, here's to you the logs that I grabbed from /var/log/syslog.
> I pasted what I believe it's the useful part in
> https://pastebin.com/raw/KRLAkS4J - anyway, it keeps going and going.
Unfortunately that is not
@Juerg, here's to you the logs that I grabbed from /var/log/syslog.
I pasted what I believe it's the useful part in
https://pastebin.com/raw/KRLAkS4J - anyway, it keeps going and going.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
[Impact]
On the system installed RTL8111EPP with DASH, unable to get the network back
upon system resume
[Fix]
handle DASH during system suspend and resume.
[Test]
Vendor tested on hardware, the ethernet is OK after resume.
[Where problems could
And here is another log from a new install in a new partition in the
same system. I installed Ubuntu 23.10 in this new partition using the
legacy installer and the installation process and first boot was very
different. I hoped that perhaps lowlatency would work here but it still
doesn't.
**
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Invalid => Won't Fix
--
You
This bug is awaiting verification that the linux-oracle/6.2.0-1016.17
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-lunar-linux-oracle' to 'verification-done-
lunar-linux-oracle'.
** Tags added: oem-priority originate-from-2042997 sutton
** Changed in: hwe-next
Status: New => In Progress
** Changed in: hwe-next
Assignee: (unassigned) => AaronMa (mapengyu)
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Yes, sorry, I'm just learning how to do these things. :)
I will attach a log of a past boot but I have to say... the problem has
evaporated and these messages don't appear anymore even if I have
removed "pcie_aspm=off" from GRUB.
While this first installation was done with the new desktop
** Attachment added: "Boot log showing the errors"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/+attachment/5720408/+files/boot23.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Here is the boot log.
** Attachment added: "linux-lowlatency boot log, not loading the desktop."
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/2043469/+attachment/5720407/+files/boot22.txt
--
You received this bug notification because you are a member of Kernel
I asked the askubuntu question here:
https://askubuntu.com/questions/1492364/ubuntu-22-04-3-lts-gui-does-not-
work-with-5-15-0-88-generic for the same error using 22.04.3 (jammy) on
an HP 15-db0598sa laptop, which has a AMD Radeon R4 Graphics Integrated
graphics card.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (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/2042772
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2042772
Public bug reported:
[Impact]
On the system installed RTL8111EPP with DASH, unable to get the network back
upon system resume
[Fix]
handle DASH during system suspend and resume.
[Test]
Vendor tested on hardware, the ethernet is OK after resume.
[Where problems could occur]
It may break r8169
I've also been meeting this bug since kernel serie 6.2 (and 6.1 I think).
However I only have one monitor, but I use a HDMI switch.
It happens on every boot and the monitor is already awaken when reaching linux
boot. The crash happens a few seconds after the graphical target is reached
(whether
@Dan, please describe your issue and post kernel logs of the failure.
It's can't be the same.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2040106
Title:
firmware broken after
All autopkgtests for the newly accepted linux-meta-nvidia (5.15.0.1042.42) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
wireguard/unknown (arm64)
Please visit the excuses page listed below and investigate the failures,
Hello everyone, just chiming in to say that my Ubuntu was installed by me, no
OEM at all, and I am on 6.5.0-10-generic, and still I was affected by this
issue.
Manually copying iwlwifi* and intel/ibt-* from linux-firmware-20230804.tar.xz
solved the issue for me.
--
You received this bug
** Also affects: linux-meta-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2022308
Title:
realtek RTS525A
76 matches
Mail list logo
