Public bug reported:
[Impact]
Headset MIC cannot record any sound.
[Fix]
Update HDA pin table to use correct verb.
[Test]
Affected system can record sound via headset now.
[Where problems could occur]
The fix uses system ID and codec variant to match platform, so only one
system will be affect
** Description changed:
+ SRU Justification
+
+ [Impact]
+
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7
Comment #30 saved my day! I started to be affected by this bug just
today, everything fine until now.
--
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/1970043
Title:
[amdgpu] freeze occurs
Public bug reported:
I'm running Ubuntu 18.04 LTS with latest lowlatency kernel. In practice
I've installed package linux-lowlatency-hwe-18.04-edge which has
resulted packages linux-image-5.4.0-117-lowlatency and linux-
modules-5.4.0-117-lowlatency to be installed right now.
$ dpkg -L linux-modul
Okay, I updated to the latest kernel 5.13.0-1031-aws and the problem
doesn't seem to be present anymore:
sudo apt update
apt list --upgradable
apt-transport-https/focal-updates 2.0.9 all [upgradable from: 2.0.8]
apt-utils/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
apt/focal-updates 2.0.9 a
** Also affects: linux (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.
https://bugs.launchpad.net/bugs/1977847
Title:
OVS/CT kernel stack trace during boot on Jammy O
This appears to now be addressed in stable:
https://www.mail-archive.com/ovs-dev@openvswitch.org/msg65275.html
And that fix is currently queued in jammy/master-next:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-next&id=352a39407e5bab5a5965e5bcb7abf1
Public bug reported:
[Impact]
* Upgrade LRM to v6
* Enable arm64 in package.config
* Enable arm64 in kernel-versions
[Test Plan]
* Rebuild lrm, lrg, lrs in a private repository
* Ensure that packages build with old and new kernel-versions
[Where problems could occur]
* Builds failing
Tim,
We're seeing some unrelated issues with the arm64 test kernel you shared.
Is it possible for you to provide arm64 test kernel that is based on
5.15.0-39 instead of 5.15.0-37?
Thanks,
Vishnu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
[Impact]
The brightness is not changed obviously during 200 to 255.
[Fix]
max_cll defines the content light luminance for individual pixel.
max_fall defines frame-average level luminance.
Use max_fall value instead of max_cll as a limit for brightness control.
[Test]
Verifie
** Description changed:
[Impact]
The brightness is not changed obviously during 200 to 255.
[Fix]
max_cll defines the content light luminance for individual pixel.
max_fall defines frame-average level luminance.
Use max_fall value instead of max_cll as a limit for brightness control
Hi Vishnu,
Try the kernel at https://kernel.ubuntu.com/~rtg/jammy-vmci-updates-
lp1978145/5.15.0-41.44~lp1972662.1/. This is the kernel that will be
tested for this SRU cycle. I've also updated the git repo at
'git://git.launchpad.net/~timg-tpi/ubuntu/+source/linux/+git/jammy
jammy-vmci-updates-lp
In my scenario, the 'out of memory' occurred in grub_memalign().
--
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/1842320
Title:
Out of Memory on boot with 5.2.0 kernel
Status in grub:
This happened on a Lenovo L380 Yoga laptop.
$ sudo dmidecode -s bios-version
R0RET45W (1.28 )
** Attachment added: "fw.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978359/+attachment/5597801/+files/fw.txt
--
You received this bug notification because you are a member of Kerne
Public bug reported:
* Explain the bug(s)
commit a3ca11eec78 introduced a flags validity check for XFRM , the check
excluded flag XFRM_OFFLOAD_FULL from the check hence the flag is being blocked
from getting to the kernel space.
The above is preventing IPsec states from being added with the fu
Hi Sumit,
Any updates on my question from comment #7 ?
--
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/1971151
Title:
[Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG)
Public bug reported:
Touchpad is not getting detected properly
It shows wireless keyboard battery is low warnings but i am using built in
laptop keyboard
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-4
Thanks a lot, Tim! This worked and our testing went fine.
So, to sum up -- our testing on both x86 and arm64 passed and
looks good from our point of view
Thanks,
Vishnu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
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
** Summary changed:
- [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
intel_idle.max_cstate=2 are added)
+ [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
--
You received this bug notification beca
There actually aren't any changes in the i915 driver between 5.17.6 and
5.17.7. But there are changes to iommu code... Please try this with one
of the failing kernel versions:
intel_iommu=off
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Summary changed:
- Wrong external screen resolution after wake up from sleep
+ [amdgpu] Wrong external screen resolution after wake up from sleep
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags adde
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/1978980
Title:
[amdgpu] Wrong external screen
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0
Fixed by https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
next&id=352a39407e5bab5a5965e5bcb7abf1f3e1e34f7f
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: openvswitch (Ubuntu Jammy)
Importance: Undeci
Public bug reported:
Since I update my ubuntu to 22.04 LTS, I get these errors during boot:
Jun 13 14:37:55 ubuntu kernel: ACPI BIOS Error (bug): Failure creating named
object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Jun 13 14:37:55 ubuntu kernel: ACPI Error: AE_
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/1979030
Title:
Multiple error and bugs during
27 matches
Mail list logo
