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
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
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,
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
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
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
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
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
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
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
** 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
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
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
> 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
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-
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
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
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
@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
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-
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.
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
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.
** 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
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
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
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
** 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
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`:
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:
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
** 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.
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
** 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
** 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
** 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
** 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
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
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
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:
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
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
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
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
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
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
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
** 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.
** 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
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.
xubuntu and kubuntu, as lubuntu do use pipewire for audio.
kali switched last night to use it.
openSUSE did so too.
i did not test on a plain vanilla gnome based ubuntu until now. Will do
it later this day (if time permits).
--
You received this bug notification because you are a member of
These modules seem to collide with pipewire-media-session, but are
required by bluez-stack to connect bluetooth headsets (or other devices)
to pulseaudio.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Meanwhile even the distros working until yesterday stopped working today
(5. May 2022 around 22:00).
The bug seems related to pipewire and switching to this new infrastructure.
It breaks nearly everything related with sound and bluetooth.
Modules involved:
- pipewire-pulse
- wireplumber
--
You
Public bug reported:
Bluetooth devices do not connect. Or better: they connect, disconnect,
connect, then finally disconnect.
It is the same using graphical tools or cli.
It is the same for
- ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta)
- debian 11.3
- fedora 35
When the ethernet device was working:
lsusb -vt
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
ID 1d6b:0003 Linux Foundation 3.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M
ID 17ef:30ab Lenovo
|__ Port 1: Dev 3, If 0, Class=Vendor
Quirk: etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.quirks=0bda:8153:k"
This doesn't fix the issue. After the second suspend I tested the
ethernet connection died.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
I've bought ThinkPad T14s with a USB-based docking station. Everything
is working marvelously, but after suspend the ethernet port on the
docking station won't connect. I've discovered the following messages in
my dmesg:
[ 9511.552448] r8152 4-1.1:1.0 enxf4a80d264083: Tx
Public bug reported:
linux-generic kernels are missing nbd modules.
Since these modules are not build and not found in linux-generic-extra
or other packages it is not possible to
- use nbd-devices
- it is not possible to mount *.qcow2 qemu virtual harddrives into your host
system
You can
Christopher,
Thank-you for the work you have put into researching this. It is really
appreciated.
The system I originally used to reproduce this bug has since been updated to:
linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1
I have just attempted to reproduce the issue and I have been unable
Public bug reported:
Paired Bluetooth devices are connected, then disconnected, connected
again, then finally disconected.
This is with
- Ubuntu, xUbuntu 21.10
- Ubuntu, xUbuntu 22.04(beta)
It works with
- kali (latest)
- debian 11.3 (latest)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Public bug reported:
Since upgrade to kernel 5.15 I have problems with irq/204-rmi4_sm which
fires extreme CPU spike (10-20% shown in top) if the touchpad of my
Lenovo Thinkpad Extreme is touched in any way. The touchpad is disabled
in BIOS as well as in X configuration. Unfortunately I can not
Public bug reported:
happened while update
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-libc-dev 5.13.0-30.33
ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
** Changed in: linux-raspi (Ubuntu)
Status: Incomplete => Invalid
** Changed in: snappy
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1959452
Public bug reported:
happens while update
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-modules-extra-5.13.0-30-generic (not installed)
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture:
Start-Date: 2022-02-21 01:16:18
Commandline: apt -y upgrade
Requested-By: tps (1000)
Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1,
97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3,
2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1),
libctf-nobfd0:amd64
Public bug reported:
bluetooth connects with headset, then times out, deconnects.
Forcing it to connect again it does, then times out and deconnects again.
Seen this with:
- Cyber jack
- Phonak Hearing Aids
- Sennheiser Headset
Since it worked until Feb. 21st, 2022 latest fixes applied at
-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1409 F pipewire-media-
thomas 1410 F pulseaudio
/dev/snd/seq:thomas 1408 F pipewire
CasperMD5CheckResult: pass
CurrentDe
ic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1409 F pipewire-media-
thomas 1410 F pulseaudio
/dev/snd/seq:
SS COMMAND
/dev/snd/controlC0: thomas 1409 F pipewire-media-
thomas 1410 F pulseaudio
/dev/snd/seq:thomas 1408 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Jan 25 20:06:44 2022
InstallationDate: Installed on 202
vicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1409 F pipewire-media-
thomas 1410 F pulseaudio
/dev/snd/seq:thomas 1408 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Jan 25 20:
17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1409 F pipewire-media-
thomas 1410 F pulseaudio
/d
I also have this issue on a Thinkpad T14s, AMD Ryzen 7 PRO 4750U.
The issue is not present with kernels 5.9.10 or 5.15.23. It is present
with the default kernel from the most recent KDE Neon (5.13).
Here's a short video, it's the same pattern (static and vertical lines on the
right) as the
Hello,
Thanks for the help! :)
Are these cifs patches present in 5.13.0.27? I got similar issues with
5.4.0.97 and 5.13.0.27, and moving to previous releases fixed the issues
in both cases! :)
Cheers!
Thomas
--
You received this bug notification because you are a member of Kernel
Packages
10,8V
I've updated the BIOS to latest version 1.12 already, with no better result.
What is the problem here, and how can I fix it?
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: th
chitecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1409 F pipewire-media-
thomas 1410 F pulseaudio
/dev/snd/seq:thomas 1408 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Have a look at this webpage..
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-
suspend/hibernate-issues
In short:
1. edit your /etc/default/grub
a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this:
GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend
In short:
1. edit your /etc/default/grub
a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this:
GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
2. run 'sudo update-grub' to reflect the changes
3.
I will help you a little:
1. edit your /etc/default/grub
a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this:
GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
2. run 'sudo update-grub' to reflect the
it is just written what to do on the webpage and this informations are not for
OS developers.
Without your help nobody can do something about it and the bug report can be
closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
1 - 100 of 1182 matches
Mail list logo
