All autopkgtests for the newly accepted linux-meta-nvidia-tegra
(5.15.0.1022.22) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
wireguard/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Invalid
--
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/2036515
Title:
Fix system boot hang caused by devlink
Per discussion in https://github.com/intel/ivsc-driver/issues/42,
upstreamed ivsc drivers are recommended since kernel v6.8, and it takes
additional fixes to be landed in ipu6-drivers dkms (filed as upstream
issue https://github.com/intel/ipu6-drivers/issues/210).
Mark as INCOMPLETE because we
Next time the problem happens please:
1. Reboot.
2. Run:
journalctl -b-1 > prevboot.txt
3. Attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ Xorg freeze: i915 flips and commits are timing out
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
** Changed
You have been subscribed to a public bug:
Random freezes occur since the installation of 6.5.x kernel.
Freeze occur several times a day, probably after touching the mouse or
keyboard, but I'm not sure.
App continue to work sound is OK, there is just no dispay updated.
Booting to old 6.2 kernel
A temporary fix is to fold down the screen of the laptop and then reopen
it. This may provide a clue as to the underlying problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu.
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
I have suffered the same issue. I have found that I lost one CPU thread
after upgrading amd64-microcode from `3.20191218.1ubuntu1` to
`3.20191218.1ubuntu1.2`. Backporting the latest microcode resolves the
issue.
OS: Ubuntu 20.04.6 LTS
Release: 20.04
Kernel: 5.4.0-144-generic
CPU: 2x EPYC 9654
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-nvidia-tegra' to
Submitted the patch as SRU to mantic. Noble will pick it up when the
kernel team pulls in 6.8-rc5.
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149042.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149043.html
--
You received this bug
** Description changed:
+ BugLink: https://bugs.launchpad.net/bugs/2049634
+
[Impact]
Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
set will see data destruction when copying files from their systems onto
- a cifs smb 1.0 mount.
+ a cifs smb mount.
wsize
https://lists.ubuntu.com/archives/kernel-team/2009-February/004192.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/2054614
Title:
please include dummy_hcd module in kernel package
Public bug reported:
please add CONFIG_USB_DUMMY_HCD=m ( as CONFIG_USB_DUMMY_HCD is not set )
adding this module should do no harm. it's useful for simulating usb
devices
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
is there a reason why ubuntu still has no dummy_hcd module, i.e. is
building kernel without CONFIG_USB_DUMMY_HCD=m ?
this sucks , and other distributions inherit this
https://bugzilla.proxmox.com/show_bug.cgi?id=4879
** Bug watch added: bugzilla.proxmox.com/ #4879
All of these patches are in the latest master-next noble kernel.
git describe --tags
Ubuntu-6.8.0-11.11-1-g04cdb2da2df3
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hello!
Just checking in on this bug to see if there is any new info.
--
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/2043733
Title:
HP Zbook 17 G6 internal microphone causes hard
Indeed -- the Pi isn't compatible with our generic arm64 kernel, so
we'll be sticking with the flavour limit for the time being, and this
does actually reduce our delta with Debian. I've got a couple of other
patches to incorporate into f-k this week, so I'm going to sponsor this
as part of a
This is a public version of the following bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224
--
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/2046875
Title:
[22.04.04]:
This is a public version of the following bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224
--
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/2046722
Title:
Public bug reported:
I need the snd-aloop module (and its dependencies: snd, snd-timer, snd-
pcm) on an AWS server.
The linux-modules-extra-aws package (or the one this drags in) used to provide
that module (as a fix for
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586) but
I have created tests kernels for both Jammy and Mantic. Please test and
provide feedback.
Jammy
https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/jammy/
Mantic
https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/mantic/
--
You received this bug
These patches are already in 6.8
** Summary changed:
- [22.04.04]: megaraid_sas: Critical Bug Fixes
+ [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Michael Reed (mreed8855)
** Also affects: linux (Ubuntu Mantic)
Importance:
Hi Chandrakanth,
Can you also fill in these fields for the SRU process in addition to
testing the test kernels
[Test Plan]
[ Where problems could occur ]
[ Other Info ]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ [Impact]
+
This update has been initiated to include a few critical bug fixes from
upstream into the upcoming 22.04.04 point kernel. Below are the upstream
commit IDs:
+
+ [Fix]
0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
** Summary changed:
- Crash on lock screen
+ Crash on blank screen
** Description changed:
- When my computer locks due to inactivity the screen goes white and
- requires a reboot to recover.
+ When my computer screen goes blank and then locks due to inactivity, the
+ screen goes white and
Request on mailing list for jammy:linux-gke:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149030.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2039720
Title:
Marking Fix Committed as these are all in our 6.8 tree and will land in
24.04, there's nothing more to do here but track it for release.
linux-image-generic | 6.8.0-11.11 | noble-proposed | amd64, arm64,
ppc64el, s390x
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
**
I tested the flock-based solution with some of the CPC pipelines in
jammy and saw consistently clean builds (30 successful images built
yesterday). Thank you very much for everyone's hard work debugging and
fixing this race condition!
--
You received this bug notification because you are a
In the next few days, when I get some "spare" time... I will spin up a
few test Jammy VM's to capture what depends it has to pull in from other
repo's, so that the depends can be ID'ed and maybe those packages can be
added to that Jammy package in this new PPA.
Otherwise, as I just found out with
Recently observed that my computer becomes unusually warm during the
Suspend state, more so than under normal operation. Given the
intermittent nature of the Suspend issue previously reported, I've opted
to disable Suspend functionality as a precaution. I thought it important
to update this report
Public bug reported:
One of my monitors, which is plugged in via a USBC-USBC cable, tends to
reset a couple of times per hour. The screens go blank, then come back
after a second or two. After the display comes back, everything looks
the same as before (the desktop isn't being reset or
did this get the pre-verification already?
--
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/2054487
Title:
There is sound from the speakers and headphones at the same time on
Public bug reported:
Sru justification
[Impact]
Upstream v5.15.139 (#lp2049432) brought commit "selftests/bpf: Test tail call
counting with bpf2bpf and data on stack" that affects one of the bpf kselftests.
because LIBBPF_OPTS macro does not exists, it does not compile. Error below.
[Fix]
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
+ [ Workaround ]
+
+ On most machines you can hide the problem by using these kernel
** Tags added: noble
--
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/1836858
Title:
Display flickers (monitor loses signal briefly) during "flickerfree"
boot, while showing the BIOS
** Description changed:
+ [ Impact ]
+
+ Kernel (and systemd) log messages appear during boot for many machines,
+ when the user should be seeing only the BIOS logo and/or Plymouth splash
+ screens.
+
+ [ Test Plan ]
+
+ 1. Boot Ubuntu on a number of laptops that have the problem and verify
+
Still there on 6.5.*
uname -a
Linux P1 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 7
11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I am facing the same issue, tried Ubuntu and Zorin. It works fine on
Windows and Android. Besides, I am using chromebox.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
@David
could you upload the whole dmesg and lsusb?
For a quick check, the only diff is MT7925.
Is this your bluetooth chip?
--
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/2049938
I tested it in a vm following the instruction from the description and
the error is not reproducible anymore. I'll mark this as verified so
that we can release the kernel
** Tags removed: verification-needed-jammy-linux
verification-needed-mantic-linux
** Tags added:
Allison Karlitskaya (desrt) sorry, just saw your question now.
You can install the new version from -proposed 5.15.0-100.110.
--
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/2049689
Title:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => The Sutton Team (sutton-team)
--
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/2049938
Title:
Bang & Olufsen Cisco 980 loses
I am experiencing the same issue on a Thinkpad P1 Gen6.
--
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/1990272
Title:
PCIe Bus Error: Uncorrected, Transaction Layer, device
** Summary changed:
- ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from
ubuntu_kselftests_ftrace failed on 5.4
+ ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from
ubuntu_kselftests_ftrace failed on 5.4 / 5.15
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received
** Description changed:
- Issue found on B-hwe-5.4.0-173.191~18.04.1
+ Issue found on B-hwe-5.4.0-173.191~18.04.1 F-5.4.0-173.191 and
+ J-5.15.0-96.106, 5.15.0-100.110 in sru-20240205
This kprobe_non_uniq_symbol.tc test case came from stable update (bug
2049024) and landed in our Focal
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
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
** Summary changed:
- Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15
+ Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-oem-6.5 (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.5
63 matches
Mail list logo
