This should be marked as importance: High. Without this, the system is
pretty much unusable.
--
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/1992266
Title:
input/keyboard: the keyboard on
Hi Christian, all,
both kernels are now ready:
1) with "s390/archrandom: simplify back to earlier design and initialize
earlier" reverted:
f98553359746 (HEAD -> master-next) Revert "s390/archrandom: simplify back to
earlier design and initialize earlier"
(https://launchpad.net/~fheimes/+archive/
*** This bug is a duplicate of bug 1991351 ***
https://bugs.launchpad.net/bugs/1991351
As per comment #1, I will mark this one as duplicated.
** This bug has been marked a duplicate of bug 1991351
test_verifier in ubuntu_bpf failed with 3 test cases (#27, #30, #150) on
J-AMD64
--
You re
For comment 2, I found it's 3 failures for all of the AMD64 instances.
ARM64 instances on other clouds can fail with 40 failures like this here.
I will update the bug title / description.
** Summary changed:
- test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic
kernel /
That's a wait timeout error probably from usb_start_wait_urb(), and that
timeout was specified by the caller. In ivsc-driver, file
drivers/mfd/ljca.c, it has:
#define USB_WRITE_TIMEOUT 200
#define USB_WRITE_ACK_TIMEOUT 500
#define USB_ENUM_STUB_TIMEOUT 20
Again that maybe an intermittent is
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs.launchpad.net/bugs/1992714
Title:
[SRU] SoF for RPL platform support
Status in HWE Next:
New
Status in firmwa
Do the warm reset on PORT-DVT2-D4_202203-30070 90 rounds, it hits the
issue one time.
Therefore, I'll put reproduce rate 1/90 here.
** Description changed:
- The Camera doesn't work with 5.15.0-52-generic
+ The Camera doesn't work with 5.15.0-52-generic during warm reset stress
The userspac
All autopkgtests for the newly accepted linux-meta-nvidia (5.15.0.1009.9) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.6 (amd64)
Please visit the excuses page listed below and investigate the failures,
Performing verification for Kinetic.
I installed the 5.19.0-23-generic kernel from -updates, and edited
/etc/default/grub to set GRUB_CMDLINE_LINUX_DEFAULT to
"lsm=landlock,bpf,apparmor", updated grub, and rebooted.
The system came up as expected and all LSM modules loaded.
[0.264264] LSM: S
Performing verification for Jammy
I started a fresh Jammy VM, running 5.15.0-52-generic from -updates.
I edited /etc/default/grub and set GRUB_CMDLINE_LINUX_DEFAULT to
"lsm=landlock,bpf,apparmor", updated grub, and rebooted.
The system panicked with the usual splat:
[0.355151] LSM: Security
Solved: updating kernel from 5.15.0.52.58 to 5.18.0.
After six hours trying all kind of workarounds, drivers versions, bios
configurations, wayland/xorg, etc. The one only thing that seems to has solved
the built-in black screen after suspend/blank-screen lock, is update kernel to
5.18.0.
Of co
Solved: updating kernel from 5.15.0.52.58 to 5.18.0.
After six hours trying all kind of workarounds, drivers versions, bios
configurations, wayland/xorg, etc. The one only thing that seems to has solved
the built-in black screen after suspend/blank-screen lock, is update kernel to
5.18.0.
Of co
b60e31bf18a70 ("thunderbolt: Add DP OUT resource when DP tunnel is
discovered")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1983143
Title:
AMD Rembrandt: DP tunneling fails w
Public bug reported:
SRU Justification:
[Impact]
* Support GPIO driver for BlueField-3 SoCs.
[Fix]
* Support GPIO driver for BlueField-3 SoCs.
* Allows user to alter GPIO value when direction is set to output
* Support configuring GPIOs as interrupts for dependent drivers such as
pwr-mlxbf an
Another build is running right now at
https://launchpad.net/~fheimes/+archive/ubuntu/test2
with 's390/archrandom: simplify back to earlier design and initialize earlier'
still in and 's390/setup: init jump labels before command line parsing' on top.
This will take a while - will test it tomorrow.
--- Comment From cborn...@de.ibm.com 2022-10-26 14:29 EDT---
(In reply to comment #21)
> Hi Harald, see my previous comment - I could recreate this on z15 now (but
> it's fine on z13).
> So seems to be related to (z14) z15 and newer?!
We do patch the kernel depending on hardware level and
A test kernel is being build at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/test
(will be available in some minutes)
--
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/1994601
Tit
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/1994823
Title:
package linux-libc-dev 5.4.0-1
Public bug reported:
update failed
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-libc-dev 5.4.0-131.147
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.24
AptOrderin
Tested and fails on m68k with ext4 and btrfs; occurs across arches and
across file systems.
--
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/1994079
Title:
fallocate on 32 bit boundary on
Tested and fails also on m68k Linux 4.16
--
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/1994079
Title:
fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to
generate S
So I repeated the setup sequence ... and no segfaults. All is working
without any problems.
So ... close as a fluke?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-allwinner-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1994
--- Comment From justin.da...@us.ibm.com 2022-10-26 12:54 EDT---
My configuration is OpenSUSE (KVM host) on a z14- we used the latest cloud
build from:
https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-s390x.img
--
You received this bug notification because you are a
Hi Harald, see my previous comment - I could recreate this on z15 now (but it's
fine on z13).
So seems to be related to (z14) z15 and newer?!
--
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
--- Comment From fre...@de.ibm.com 2022-10-26 12:09 EDT---
Well, my fresh installed kvm guest from
https://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.5-server-s390x.iso
crashes even with security updates enabled.
--
You received this bug notification because you are a member
Ah - interesting.
I could recreate the situation on z15 / L1III:
$ virsh start bionic --console
Domain 'bionic' started
Connected to domain 'bionic'
Escape character is ^] (Ctrl + ])
ubuntu@z15test:~$
There is obviously a difference in the behavior of the z13 and z15.
I can create a test kernel
--- Comment From fre...@de.ibm.com 2022-10-26 11:48 EDT---
Digging into details gives:
The reason seems to be that the patch
moves the decission about if arch randomness
is available to setup.c function setup_randomness().
This code uses a static_key s390_arch_random_available.
But in the
If there is a reason to revert 's390/archrandom: simplify back to
earlier design and initialize earlier' we could consider that, but works
here (z13 with z/VM 6.4 and z13 with Ubuntu 22.10 KVM ost).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Since the Ubuntu kernel team does for every kernel update and SRU regression
testing, a non-bootable kernel would have been identified and the kernel would
not have left -proposed, it would even not have landed in -proposed.
That makes me think that the issue is elsewhere - at the KVM host side?!
@Chris, the oldest machine i found in cert lab is intel 6th gen.
all 6th gen machines are occupied for verifying the proposed.
have no idea when will they be freed.
I also found intel 7th, KBL, intel 8th, CFL and
1. install thermald 2.5.1.
2. fire thermald with passive policy or adaptive policy m
Again, 18.04.5 installations for for me, I used this (latest) 18.04.5 ISO:
https://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.5-server-s390x.iso
If there is a reason to revert 's390/archrandom: simplify back to
earlier design and initialize earlier' we could consider that, but works
he
Public bug reported:
[Issue]
The linux-kvm wasn't using annotations from debian.master, and that
induced a skew in important options between master and kvm.
[Fix]
Apply the attached series.
[How to test]
Crank updateconfigs shouldn't report any check-config error.
** Affects: linux-kvm (Ubun
** Description changed:
[Impact]
* thermald prematurely throttling GPU
[Test Plan]
Test1,
* Run game on the target machine.
- * the FPS must not be significantly reduced.
+ * the FPS must not be significantly reduced.
Test2,
- * Run on others platform, e.g. TGL/CML.
+ * Run on
Btw. for the KVM guest install I used:
sudo qemu-img create -f qcow2 /var/lib/libvirt/images/bionic.qcow2 8G
sudo virt-install --name bionic --vcpus 2 --ram 1024 --disk
path=/var/lib/libvirt/images/bionic.qcow2,size=5,bus=virtio,format=qcow2
--os-type linux --os-variant generic --network
network=
Trying to recreate, I was just able:
- to successfully complete an 18.04 installation on a 22.10 host (that what I
just had at hand) and
- a successful 18.04 installation on a z/VM 6.4 host
I selected in both cases the strongly recommended option 'Install security
updates automatically'.
(And do
tested kernel linux/5.15.0-53.59 on both jammy and focal
* Create 2 jammy instances
* Add SRIOV interface with vlan tag
* Configure interface with mtu 9000, and errors in dmesg
* Enabled proposed and installing the linux-image-generic package
* reboot both instances
* network with MTU up via netpl
--- Comment From fre...@de.ibm.com 2022-10-26 11:12 EDT---
I have the strong suggestion that this is the cause:
commit 6edb63a7b6cd57825e47cf6a8600b694a19f0d90
Author: Jason A. Donenfeld
Date: Sat Jun 11 00:20:23 2022 +0200
s390/archrandom: simplify back to earlier design and initializ
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1994516
Title:
Kernels after 5.16 cannot execute x32-ABI binaries
Sta
This bug is awaiting verification that the linux-azure/5.4.0-1095.101
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
problem still exists,
Thanks for reporting this.
What is the version of the Ubuntu host where you want to install the 18.04
guest onto?
So that I can try to properly recreate this.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned)
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/1994601
Default Comment by Bridge
** Attachment added: "crash log output"
https://bugs.launchpad.net/bugs/1994601/+attachment/5627021/+files/log.out
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You r
This issue is critical. Is there any update on this?
--
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/1992266
Title:
input/keyboard: the keyboard on some Asus laptops can't work
Status in
You have been subscribed to a public bug:
---Problem Description---
Ubuntu 18.04 crashes during IPL with no output on the console.
Contact Information = Viktor Mihajlovski
---uname output---
n/a
Machine Type = 3096
---Debugger---
A debugger is not configured
---Steps to Reproduce---
All autopkgtests for the newly accepted linux-meta-oem-6.0 (6.0.0.1007.7) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.6 (amd64)
nvidia-graphics-drivers-515/515.76+really.515.65.01-0ubuntu0.22.04.1 (amd64)
Public bug reported:
my wireless is not working
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture
The segfault only happened with a fresh Ubuntu's LicheeRV image, written
to a separate SD-card.
The Armbian-like image was on another sd-card, not in the Lichee.
I will repeat the Ubuntu's LicheeRV image writing & boot & wifi-install
procedure to see if I can reproduce the problem (or that it wa
Sander, as you mentioned Armbian just for clarification: Did you
experience the problem with a fresh install using Ubuntu's LicheeRV
image or with some Armbian stuff still in your installation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626991/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626995/+files/acpidump.txt
--
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/19
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626994/+files/UdevDb.txt
--
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/1994516
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626993/+files/PulseList.txt
--
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/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626992/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626987/+files/Lsusb-v.txt
--
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/1994
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626989/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626990/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626988/+files/PaInfo.txt
--
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/1994516
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626986/+files/Lsusb-t.txt
--
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/1994
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626985/+files/Lsusb.txt
--
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/1994516
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626984/+files/Lspci-vt.txt
--
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/19
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626982/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1994516/+attachment/5626983/+files/Lspci.txt
--
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/1994516
apport information
** Tags added: apport-collected
** Description changed:
The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
kernel 5.17 and higher (amd64). x32 binaries are now reporting:
cannot execute binary file: Exec format error
The x32-ABI has its proven
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7
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,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7
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,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7
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,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7
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,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7
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,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7
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,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7
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,
This bug affects me, albeit with another chip that used to work with
kernel 5.15 from Ubuntu 22.04
dmesg output:
```
[5.641569] Bluetooth: hci0: BCM: chip id 110
[5.642558] Bluetooth: hci0: BCM: features 0x2f
[5.658564] Bluetooth: hci0: BCM4350C5
[5.658570] Bluetooth: hci0: BCM4350
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pipewire (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/199366
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/1993668
This test took:
* B-oracle: test skipped - 'VMCS shadowing' not supported.
* F-oracle: 6m42s / 6m46s / 6m42s
* J-oracle: 6m26s / 6m27s / 6m26s
CONFIG_DEBUG_VM was not enabled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kv
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 1994516
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
kernel 5.17 and higher (amd64). x32 binaries are now reporting:
cannot execute binary file: Exec format error
The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
intensive tasks) because
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 1990916
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1991974
Title:
AMD Yellow Carp system ha
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1982749
Title:
New device IDs for Intel Raptor Lake S
** Changed in: linux-oem-6.0 (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/1991609
Title:
Add support for AMD PMF Cool
** Changed in: linux-oem-6.0 (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/1993715
Title:
AMD Cezanne takes 5 minutes
** Package changed: linux-signed-hwe-5.15 (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/1994442
Title:
XPS 9315 camera not working
Status in linux package in
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Confirmed
--
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/1971712
Title:
Add support for Intel DG2
St
...for oem-6.0
--
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/1992723
Title:
Enable DP tunneling functionality on AMD Pink Sardine
Status in HWE Next:
New
Status in linux pack
this came via stable
--
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/1992723
Title:
Enable DP tunneling functionality on AMD Pink Sardine
Status in HWE Next:
New
Status in linu
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-6.0 (Ubuntu)
Status: Incomplete => Invalid
--
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.lau
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
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/1990922
Title:
Fix USB
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: New => Fix Released
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
P
fixed in 6.0 1006
so the revert needs a follow-up bug..
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchp
or maybe not, just reopen this for 6.0 when the reverts are sent
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1991366
Title:
Fix Thunderbolt device hotplug fail when connect v
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1991365
Title:
Fix Tur
fixed in 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
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/1987670
Title:
Add support
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1988461
Title:
intel_p
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990161
Title:
Fix RPL
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990240
Title:
To supp
fixed in 6.0 1006
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990242
Title:
Intel g
Also affected on a T480 without Nvidia GPU, and issue only occurs when
notebook is docked onto docking station via usb-c.
OS randomly gives kernel panic, sometimes it works for hours, sometimes
it drops panic just after the boot...
Oct 26 09:43:07 perseus kernel: [ 13.579008] BUG: kernel NULL p
1 - 100 of 115 matches
Mail list logo
