This bug also exists with kernel 6.11.0-25, i.e. HWE 24.04.
--
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/2065153
Title:
[qxl] Ubuntu 24.04 VM guest console freezes after some hours
St
I don't believe it's your machine. Just encountered the same exact
problem here (MCE boot failure) with a 9684x Genoa + Supermicro H13SSL
on Arch linux 6.14.1 kernel. Downgrading to 6.12.22 allowed the system
to boot + operate normally again. Likely points to an upstream problem
with the kernel
Public bug reported:
The main symptom is that, after the system boots up fine, reaches GDM,
and the user logs in, the screen turns black before the Gnome Desktop
appears. Switching to a text-based TTY and back to the Desktop works
around it, making the Desktop show and work normally.
This issue b
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu.
https://bugs.launchpad.net/bugs/2103957
Title:
Black screen
Public bug reported:
5.4.0-208 kernel only allows 4:3 resolutions on Samsung 226BW widescreen
monitor. For example, 1680 by 1050 resolution is not available. This
issue is resolved by rolling back to 5.4.0-148 kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
I just found that similar patches were discussed here:
https://lore.kernel.org/all/a7b0b637-8ecb-4092-b6a9-162bafb95...@lunn.ch/T/
but were not merged.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Summary changed:
- usbnet.c regression
+ Interface name wrong for USB terher
** Summary changed:
- Interface name wrong for USB terher
+ Interface name wrong for USB tether
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
** Description changed:
5.15.0-131 works
5.15.0-133 no networking
This fix
https://github.com/torvalds/linux/commit/8a7d12d674ac6f2147c18f36d1e15f1a48060edf
- is included in 133. It cause my usb tether adapter to be named eth0
+ is included in 133. It caused my usb tether adapter
Public bug reported:
5.15.0-131 works
5.15.0-133 no networking
This fix
https://github.com/torvalds/linux/commit/8a7d12d674ac6f2147c18f36d1e15f1a48060edf
is included in 133. It cause my usb tether adapter to be named eth0
instead of usb0. I have another adapter that gets renamed (via netplan)
t
Public bug reported:
I connected an external usb NVME disk to one of the usb-3 ports on a
raspi 4b. The disk can't be used and dmesg says:
[snipped]
[ 47.309485] ieee80211 phy0: brcmf_p2p_send_action_frame: Unknown Frame:
category 0xa, action 0x8
[ 137.048321] usb 2-1: new SuperSpeed USB devi
As of today, I can say that deactivating TPM in the BIOS has permanently
solved the problems with suspend and resume for me. In the meantime, I
have also reactivated INTEL_IOMMU without any negative effects. All the
problems described no longer occur. It works as a workaround as long as
you don't h
Interesting post in the Fedora forum:
https://discussion.fedoraproject.org/t/shutdown-reboot-broken-in-f37-since-kernel-6-1-x/79944/23
Here, disabling TPM in the BIOS brought permanent improvement. This is
the referenced kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=217890
I also dea
Public bug reported:
Hello
When I try to install the package with : ```sudo apt install
bcmwl-kernel-source```
I have the error ```Enable to locate package bcmwl-kernel-source``` I think is
cause the package seems not available for my Ubuntu release (the last one)
Ubuntu 24.10 Oracular Oriole
PID ACCESS COMMAND
/dev/snd/seq:thomas 1896 F pipewire
/dev/snd/controlC0: thomas 1900 F wireplumber
/dev/snd/controlC1: thomas 1900 F wireplumber
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Mon Nov 18 17:15:16 2024
ErrorMessage: Abhängigkeitsprobleme
As before, I did not find any anomalies in the log. In daily operation, 6.6.18
behaves more stable with regard to this problem. With the new version it
happens again very often, computer goes into HALT, but does not switch off or
resume does not work.
Intel_iommu is still deactivated.
--
You r
A feeling of familiarity kicks in. Nice to meet you on Oracular.
Linux uENVY 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14
13:19:59 UTC 2024 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
Well, with kernel 6.8.x we finally ended up at the problematic point
again. It took longer, but it came some time. Now working with 6.6.18
and it looks pretty good. I haven't tested it systematically yet, but
you can use the notebook in the usual way again. Intel_iommu is still
deactivated.
--
Yo
** Also affects: linux-aws-6.8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2081745
Title:
Anbox 1.23 Version Application f
Found messages like these in some old logs:
Jun 27 07:06:15 uENVY kernel: DMAR: IOMMU feature fl1gp_support inconsistent
Jun 27 07:06:15 uENVY kernel: DMAR: IOMMU feature pgsel_inv inconsistent
Jun 27 07:06:15 uENVY kernel: DMAR: IOMMU feature nwfs inconsistent
Jun 27 07:06:15 uENVY kernel: DMAR:
** Summary changed:
- Ubuntu 24.04: Suspend & Power off
+ Kernel 6.x: Suspend & Power off
--
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/2031969
Title:
Kernel 6.x: Suspend & Power off
Also with kernel 6.6.17 problems have shown up at some point, as so
often before with this issue. Completely random. Resume did not work.
But deactivating intel_iommu seems to be the solution. Works great, no
matter if 6.6.17 or 6.8.0. Will disabling it cause any drawbacks, maybe
in terms of perfo
I installed kernel 6.6.17 yesterday, and fortunately it works here too.
I'm a bit cautious here, as in the past the problems only became
apparent after longer periods of use. Just closing the lid of the
notebook and continuing to work the next morning - I haven't had that
with Ubuntu on this device
I have been observing such problems on my notebook since kernel 6.1. A
solution would be really nice. Especially as you can find loads of
similar cases on the net.
My hardware: https://linux-hardware.org/?probe=2a30e00bec
My report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969
--
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2078790
Title:
jammy qemu x86 int3: [#1] SMP NOPTI
Status in linux-lowla
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2076217
Title:
booting an 24.10 or 24.04 ec2 instance w
Confirmed the fix solves the bug in focal, jammy, jammy-hwe
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Virtualbox Guru meditation on VM start caused by kernel
I tested the linux-image-6.8.0-40-generic kernel on Ubuntu noble.
It fixed the bcache errors, but graphics were unusable, I had to revert
to linux-image-6.8.0-39-generic to get GDM on Wayland working (I haven't
tested GDM on Xorg).
--
You received this bug notification because you are a member o
This isn't fixed in the jammy 6.5.0-1024-aws kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2018303
Title:
move sev-guest module from linux-modules-extra to linux-modules
St
When do we get this new kernel? It seems to solve the problem.
--
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/2068738
Title:
AMD GPUs fail with null pointer dereference when IOMMU enable
BUILD_EXCLUSIVE errors were there in 104 also. Wireguard still works.
--
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/2060780
Title:
CIFS stopped working/is unstable with kernel update to
I had no problem installing and testing 5.15.0-104, but when I try to
install 105 I get:
Setting up linux-headers-5.15.0-105-generic (5.15.0-105.115) ...
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.15.0-105-generic
Error! The
/var/lib/dkms/wireguard
I also see that message - not only at boot - my dmesg is full of it:
[1017116.534368] evict_inodes inode 77d96b5a, i_count = 1, was skipped!
[1017116.534369] evict_inodes inode 973ed623, i_count = 1, was skipped!
[1017116.534370] evict_inodes inode a18d9813, i_count = 1, wa
Maybe related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2008774
Title:
Ubuntu 22.04 not waking up afte
i'm on Linux 6.5.0-1009-oem x86_64 and still not working :(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2038859
Title:
No driver for 14c3:7902
Status in linux-signed-h
For me this is solved with
5.15.0-91 and 6.2.0-39
--
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/2042039
Title:
AUDIO POPPING After New Kernel install: 5.15.0-88.98
Status in linux pack
Public bug reported:
I can't get any desktop, neither with Xorg, neither with Wayland (it
even does not fallback on llvmpipe).
The dmesg reports a null pointer dereference in nouveau kernel module.
This makes Ubuntu 23.10 not working at all on this computer.
lspci:
```
Slot: 00:02.0
Class:
** Package changed: ubuntu-advantage-tools (Ubuntu) => linux-aws
(Ubuntu)
** Summary changed:
- Enabling fips-preview on Jammy AWS fails with: Unexpected APT error
+ Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips (>=
5.15.0.1042.43) but it is not installable
--
You rece
With #2043924 I did not observed any data corruption as described in
this case.
--
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/2019153
Title:
ntfs3 kernel driver corrupts volume during f
Maybe related: https://bugs.launchpad.net/bugs/2043924
--
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/2019153
Title:
ntfs3 kernel driver corrupts volume during file move operations
Stat
I can confirm this audio popping on two Asus PN50. One with Kernel 5.15.0-87
the other with 6.2.0-36.
Rolling back to older kernel solved it on both machines.
System:
Kernel: 6.2.0-35-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon
5.8.4 tk: GTK 3.24.33
wm: muffin dm: LightDM Dist
** Tags added: ntfs3
--
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/2043924
Title:
Apparently empty files when writing to NTFS partition
Status in linux package in Ubuntu:
New
Bug de
These messages get triggered randomly (I suspect on unmounting NFS
mounts, which are managed by systemd automounter) on my Ubuntu 23.10
machines and end up in systemd journal and kern.log (gigabytes of
messages), system uses 4 CPUs completely and gets unresponsive.
--
You received this bug notifi
Public bug reported:
For some time now I have been observing strange effects on my dual-boot
system when writing to a shared NTFS partition. It is only for data and
not the partition on which Windows is installed.
The drive is mounted with these parameters:
/dev/sda1 on /media/tom/DATA type ntfs3
> Is this a regression, i.e., has it worked before?
This is a new desktop PC so idk if this is a regression. But from what I
read on the internet, it seems to be broken forever
> Are you running the latest BIOS?
Yes. This is with "ROG STRIX X670E-F GAMING WIFI BIOS 1709" (1709 is the
version her
Yes, it still exists on Mantic,
6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC
2023
--
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/2031969
Title:
Ubuntu 23.04:
Public bug reported:
I have a "ASUSTeK COMPUTER INC. ROG STRIX X670E-E GAMING WIFI"
motherboard and the builtin ethernet card does fail from time to time
(randomly - usually some hours).
Steps to reproduce:
- activate ethernet
- wait hour(s)
- then ethernet will no longer work
The kernel logs
This came indeed in via a cherry-pick made by Ubuntu [0], that was an
early attempt to fix a bug that was actually present in the ceph layer,
as confirmed by the original patch author[1], and fixed actually there
now [2].
[0]: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/man
Public bug reported:
Since I upgraded from lunar to mantic I get a load of those errors (41
on a fresh boot) in dmesg:
```
[4.277343] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
[4.277728] index 4 is out of range for type 'btree_ite
Public bug reported:
Install a new Ubuntu 22.04 Jammy system and run the following commands
in a bash shell:
sudo -i
apt-get update && apt-get install -y iproute2 # often not necessary
depmod -a
modprobe ifb numifbs=1
ip link add ifb0 type ifb
ip link set dev ifb0 up
tc qdisc add dev lo ingress
I did test the kernel from lunar proposed (6.2.0.1015.16) on AWS. The
image boots with sev-snp enabled:
# sudo dmesg | grep -i sev
[5.563677] Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP
[6.140250] SEV: Using SNP CPUID table, 64 entries present.
[8.507286] SEV: SNP guest p
Sorry, but that was a kind request, very respectful. Not with a single
word I did imply any malicious intent. How respectful is this treatment
of other people's wording? Anyway, it just doesn't make sense to mix
these things up, as mentioned earlier. Even if it will end up with the
same cause, a bu
@cfgnunes: Please do not hijack and mangle other people's reports.
I did not have this experience with 22.04.3 LTS. The logs and the description
belong to 23.04. Changing only the summary is pointless.
Maybe the problem exists in other Ubuntu versions too. It probably has to do
with kernel vers
Update: The issue did not persist after upgrading to 6.2.0-33-generic!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2035622
Title:
Update broke keyboard on a Fujitsu Lifebook
FYI, we solved a similar sounding issue by clearing the PKRU bit if it
was set in the to-be-restored XSAVE blob, but not available in the
current vCPU feature flags:
https://git.proxmox.com/?p=pve-
kernel.git;a=blob;f=patches/kernel/0008-kvm-xsave-set-mask-out-PKRU-bit-
in-xfeatures-if-
vCPU.patch
Ah. I see. KSM_ENABLED=AUTO from /etc/default/qemu-kvm is used through
/usr/share/qemu/init/qemu-kvm-init via the qemu-kvm.service systemd
service. thanks for the hint!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
this is included in all available EKS images (and in general in Ubuntu
images on AWS). Feel free to reopen if you still encounter this problem.
** Changed in: cloud-images
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
@Seth,
ksm is disabled by default so it's still opt-in:
# cat /sys/kernel/mm/ksm/run
0
it only gets activated when you install ksmtuned (which is not installed
by default). So I think that's fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
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.
https://b
** 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 an
Will the patch be dropped if the Nvidia kernel is not tested on AMD
GPUs?
Rebooting the computer affected by the bug will cost me 1 or 2 hours of
work so that's a very high cost for a patch I already marked as
verified.
--
You received this bug notification because you are a member of Kernel
Pac
Should we really test that Nvidia kernel for a bug affecting AMD GPUs,
otherwise the already verified fix would be dropped?
--
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:
Why should we test an Nvidia kernel for a bug affecting AMD GPUs?
--
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 and invalid load o
root@srv1:~# dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut
here"
[Di Mai 23 15:13:00 2023] [ cut here ]
[Di Mai 23 15:13:00 2023] WARNING: CPU: 2 PID: 438 at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
[Di Mai 23 15:13:00 2023] Modules linked
Have the same Problem after Update right now to 5.4.0-149-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2018960
Title:
linux-image-5.4.0-149-generic (focal-proposed): 0 a
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
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 GCN
I now see the original message was edited, with this words added:
> [Test case]
> Install the update, check that display works again on amdgpu
I confirm display works again on amdgpu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I'm on 5.19.0-44.45 right now.
What 5.19.0-44.45 is expected to fix?
- The computer boots properly, I have both R7 240 and R9 390X displaying
something fine, so that error is fixed.
- I still have an error message in dmesg:
```
[7.609329]
===
Public bug reported:
After the kernel update from 5.19.0-32 to 5.19.0-41, the built-in
wireless card MT7921 is not working anymore. I could not find any
missing firmware messages in dmesg, the device instead is not
recongnized. This should be part of the output of `sudo lshw -C
network`:
*-networ
This is the patch by Alex Deucher that is believed to fix the NULL
pointer dereference. I have not tested it but the issue looks very
close. It is needed anyway.
> Guchun Chen
> Regarding the NULL pointer access, it should be duplicated of #2388. And the
> fix is "63a9ab264a8c drm/amd/pm/smu7: mo
I've reported the issues upstream on drm side:
- https://gitlab.freedesktop.org/drm/amd/-/issues/2540
Linux 5.19 amdgpu: NULL pointer on GCN2 (R9 390X Hawaii/Grenada)
- https://gitlab.freedesktop.org/drm/amd/-/issues/2541
Linux 5.19 amdgpu: invalid load on GCN1 (R7 240 Oland)
For the NULL po
** Summary changed:
- Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2
+ Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
So to summarize:
with Linux 5.19.0-42-generic amdgpu on GCN1: kernel NULL pointer
dereference
- no display
- stuck boot requiring SysRq+K to continue
- errors in dmesg
- reboot requiring SysRq+B to continue
with Linux 5.19.0-42-generic amdgpu on CGN2: kernel UBSAN invalid load,
load of value 8 i
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671007/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.txt
--
You received this bug notification because you are a member of
--
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 GCN1 and invalid load on GCN2
Status in linux package in Ubuntu:
Confirmed
Bug descrip
** Attachment added:
"dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671008/+files/dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt
--
You received this bug notification because you are
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671001/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.txt
--
You received this bug notification because you are a member of
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671000/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.txt
--
You received this bug notification because you are a member of
** Attachment added:
"dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670998/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt
--
You received this bug notification because you are
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670999/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.txt
--
You received this bug notification because you are a member of
So, in the end I spent some times to do more dmesg logs, just producing
6 of them took me multiple hours because of how slow such kind of
computer BIOS is to boot, and also because of how complicated it can be
to get a shell when everything goes wrong with those bugs.
Something I forgot to mention
Public bug reported:
The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to
stick on Linux 5.15 because 5.19 was not working with my computer. The
last two days I spent time to find a way to run Linux 5.19, and found
one version working: 5.19.0-23.
Here are the versions I tested:
Public bug reported:
AWS did recently announce AMD SEV-SNP support (see
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To
have that working in the ubuntu AWS images, the module needs to be
available (linux-modules-extra is not installed by default).
So please move the module to
Same problem on Lenovo W540 with Quadro K1100M. Upgraded to 23.04
yesterday (coming from 22.10)
If I boot with an older 5.x kernal it works. So it seems to be an issue
with the new 6.x kernal.
According to this forum post over on nvidias forum
https://forums.developer.nvidia.com/t/390-154-driver-
I have the same issue on one of my Mac minis. I have three of them with
Ubuntu 22.04.2 LTS, all with the Intel Core i5-4278U, but only one of
them has the issue. The one with the problem has a 1TB Fusion drive
while the other two that work have SSDs.
--
You received this bug notification because
I know it is long time since this was opened, however herewith I want to
declare that this problem still exists nowadays in all Thinkpad line and
it is not related to Linux.
From all what I have learned so far there is only one conclusion:
Lenovo is gapping its fans to keep their products at low
Issued occured at 2023-02-26 on a fully patched Ubuntu Jammy (22.04).
System #1:
2023-02-26 15:35:56.996ZInfotomcat9 java.io.IOException: Duplicate
accept detected. This is a known OS bug. Please consider reporting that you are
affected: https://bugs.launchpad.net/ubuntu/+source/linu
Affected as well, same environment:
* Ubunutu 22.04.1
* Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT /
5700/5700 XT]
* Connection uses DisplayPort
* Booting with kernel version 5.15.0-53 fails early (no logs from systemd), no
video signal
--
You received this bug
Unfortunately I just hit the same issue this morning:
$ dpkg -l | grep linux-firmwar
ii linux-firmware 20220329.git681281e4-0ubuntu3.6
all Firmware for Linux kernel drivers
So seems that the issue can still occur.
--
You received this bug notifica
I just installed that firmware update, in my experience it takes a week
or so to hit the issue; so we'll see if it reoccurs.
--
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/1971656
I've been hitting this issue for a couple of months now and just
recently found this bug. For my use-case my laptop sits idling (not
suspended) overnight most days. I run into this issue a couple times a
month -- the key takeaway there being that it seems to not be related to
suspend (since I don't
I can confirm that the (naive) patch sidesteps the issue, but that it is
otherwise present on all our 5.15/ZFS installs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1980848
Title:
This bug also breaks `lxc file push` functionality.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990849
Title:
LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
Added sudo systemctl reload snap.lxd.daemon after disabling shiftfs.
** Description changed:
Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS
are broken.
Reproducer steps:
```
sudo snap install lxd
sudo snap set lxd shiftfs.enable=true
sudo lxd init --auto
Public bug reported:
Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS
are broken.
Reproducer steps:
```
sudo snap install lxd
sudo snap set lxd shiftfs.enable=true
sudo lxd init --auto
lxc storage create zfs zfs
lxc launch images:ubuntu/jammy c1 -s zfs
lxc exec c1 -- touch /
Ok, I created this issue:
https://gitlab.freedesktop.org/drm/amd/-/issues/2088
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2088
https://gitlab.freedesktop.org/drm/amd/-/issues/2088
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Sorry something went wrong with copy/paste in the description.
Central issue is that the part where the MOK certificates are loaded (in
5.15.0-33-generic):
```Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate:
UEFI:MokListRT (MOKvar table)
Mai 25 00:14:56 silvershadow ker
Public bug reported:
I started to test the oem kernel on ubuntu 22.04 jammy. Doing so I
wondered why all my dkms modules don't load when secure boot is active
although they are correctly signed. After investigating quite a while I
found that the MOK certificates are not loaded during boot. This is
** Attachment added: "lspci-dell-latitude-7300.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590019/+files/lspci-dell-latitude-7300.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
** Attachment added: "cpuinfo-dell-latitude-7300.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590018/+files/cpuinfo-dell-latitude-7300.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Same issue with Dell Latitude 7300. Device detection like disks fail,
apparently randomly. Some media keys don't work, Wifi was OK.
Previous kernel build is fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
1 - 100 of 1228 matches
Mail list logo
