[Bug 2084979] Re: Device Mapper accepts writes even when the underlying devices are dead (offline or transport-offline)

Hi Miroslaw,

I finally got around to trying this out. I reproduced on:

Focal with 5.4.0-200-generic
Jammy with 5.15.0-122-generic
Noble with 6.8.0-49-generic
Plucky with 6.12.0-3-generic

They all behave the same, and they all behave as you report in the bug
report.

I will note that every dmesg will report that the underlying disk is
offline:

[ 108.055848] I/O error, dev sda, sector 2048 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.056279] Buffer I/O error on dev dm-0, logical block 0, lost async page write
[ 108.056612] Buffer I/O error on dev dm-0, logical block 1, lost async page write
[ 108.056996] Buffer I/O error on dev dm-0, logical block 2, lost async page write
[ 108.057335] Buffer I/O error on dev dm-0, logical block 3, lost async page write
[ 108.057694] Buffer I/O error on dev dm-0, logical block 4, lost async page write
[ 108.058013] Buffer I/O error on dev dm-0, logical block 5, lost async page write
[ 108.058342] Buffer I/O error on dev dm-0, logical block 6, lost async page write
[ 108.058703] Buffer I/O error on dev dm-0, logical block 7, lost async page write
[ 108.059023] Buffer I/O error on dev dm-0, logical block 8, lost async page write
[ 108.059359] Buffer I/O error on dev dm-0, logical block 9, lost async page write
[ 108.060034] I/O error, dev sda, sector 2304 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.060549] I/O error, dev sda, sector 2560 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.061012] I/O error, dev sda, sector 2816 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.061465] I/O error, dev sda, sector 3072 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.061908] I/O error, dev sda, sector 3328 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.062318] I/O error, dev sda, sector 3584 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.062744] I/O error, dev sda, sector 3840 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.063188] I/O error, dev sda, sector 4096 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0
[ 108.063616] I/O error, dev sda, sector 4352 op 0x1:(WRITE) flags 0x104000 phys_seg 32 prio class 0

Its just that dd succeeds, and exits 0. A bit frustrating I suppose.

Since this affects the very latest mainline, we should probably ask upstream
about it.

Will you write to the upstream device mapper maintainers?

Thanks,
Matthew

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084979

Title:
Device Mapper accepts writes even when the underlying devices are dead
(offline or transport-offline)

Status in linux package in Ubuntu:
New

Bug description:
**********
#### Steps to reproduce
**********

root@ubusrv:~# lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 2G 0 disk
└─sda1 8:1 0 2G 0 part
root@ubusrv:~#

root@ubusrv:~# pvcreate /dev/sda1
Physical volume "/dev/sda1" successfully created.
root@ubusrv:~# vgcreate vgtmp /dev/sda1
Volume group "vgtmp" successfully created
root@ubusrv:~# lvcreate -n lvtmp -l 100%free vgtmp
Logical volume "lvtmp" created.
root@ubusrv:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- 18.22g
lvtmp vgtmp -wi-a----- <2.00g
root@ubusrv:~#

root@ubusrv:~# cat /sys/block/sda/device/state
running
root@ubusrv:~# echo offline > /sys/block/sda/device/state
root@ubusrv:~# cat /sys/block/sda/device/state
offline
root@ubusrv:~#

root@ubusrv:~# l file.tar
-rw-r--r-- 1 root root 2.4G Oct 19 14:12 file.tar
root@ubusrv:~#


----------------------
1. Reading from faulty DM device: OK - expected behavior
root@ubusrv:~# dd if=/dev/mapper/vgtmp-lvtmp
dd: error reading '/dev/mapper/vgtmp-lvtmp': Input/output error
0+0 records in
0+0 records out
0 bytes copied, 0.00298229 s, 0.0 kB/s
root@ubusrv:~#

2. Reading from faulty/offline underlying sda: OK - expected behavior
root@ubusrv:~# dd if=/dev/sda1
dd: failed to open '/dev/sda1': No such device or address
root@ubusrv:~#

3. Writing to faulty/offline underlying sda: OK - expected behavior
root@ubusrv:~# dd of=/dev/sda1
dd: failed to open '/dev/sda1': No such device or address
root@ubusrv:~#

4. And writing to faulty DM device: not OK - UNEXPECTED behavior
root@ubusrv:~# dd if=file.tar of=/dev/mapper/vgtmp-lvtmp bs=10M count=204
204+0 records in
204+0 records out
2139095040 bytes (2.1 GB, 2.0 GiB) copied, 4.57038 s, 468 MB/s <<<<<<<<
root@ubusrv:~#
----------------------


******** Where this data has been stored?
Not in memory - not enough space:
root@ubusrv:~# free
total used free shared buff/cache available
Mem: 961Mi 361Mi 200Mi 1.3Mi 556Mi 599Mi <<<<
Swap: 2.0Gi 0B 2.0Gi
root@ubusrv:~#


And the same applies to iSCSI+MPIO.
----------------------
root@ubusrv:~# multipath -ll
mpatha (3600140582d6e7c50c0347908f0d094c2) dm-2 LIO-ORG,ubusrv-wrbk
size=4.4G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=50 status=active
|- 8:0:0:135 sdc 8:32 active ready running
`- 7:0:0:135 sdb 8:16 active ready running
mpathb (3600140512e2d3ad7ae048aba1ee0a33a) dm-3 LIO-ORG,ubusrv-wrth
size=3.9G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=50 status=active
|- 8:0:0:235 sdd 8:48 active ready running
`- 7:0:0:235 sde 8:64 active ready running
root@ubusrv:~#

#### poweroff iSCSI target/server

root@ubusrv:~# egrep 'mpath[ab]' /var/log/syslog | tail
2024-10-19T15:07:01.810687+02:00 ubusrv multipathd[382]: checker failed path 8:64 in map mpathb
2024-10-19T15:07:01.811658+02:00 ubusrv multipathd[382]: mpathb: remaining active paths: 1
2024-10-19T15:07:02.810464+02:00 ubusrv multipathd[382]: checker failed path 8:16 in map mpatha
2024-10-19T15:07:02.813151+02:00 ubusrv multipathd[382]: mpatha: Entering recovery mode: max_retries=12
2024-10-19T15:07:02.813182+02:00 ubusrv multipathd[382]: mpatha: remaining active paths: 0
2024-10-19T15:07:04.811717+02:00 ubusrv multipathd[382]: checker failed path 8:48 in map mpathb
2024-10-19T15:07:04.813169+02:00 ubusrv multipathd[382]: mpathb: Entering recovery mode: max_retries=12
2024-10-19T15:07:04.813206+02:00 ubusrv multipathd[382]: mpathb: remaining active paths: 0
2024-10-19T15:08:02.844668+02:00 ubusrv multipathd[382]: mpatha: Disable queueing
2024-10-19T15:08:04.845680+02:00 ubusrv multipathd[382]: mpathb: Disable queueing
root@ubusrv:~#

root@ubusrv:~# iscsiadm -m session -P 3 | grep Att
Attached SCSI devices:
Attached scsi disk sdb State: transport-offline
Attached scsi disk sde State: transport-offline
Attached SCSI devices:
Attached scsi disk sdc State: transport-offline
Attached scsi disk sdd State: transport-offline
root@ubusrv:~#

root@ubusrv:~# multipath -ll
mpatha (3600140582d6e7c50c0347908f0d094c2) dm-2 LIO-ORG,ubusrv-wrbk
size=4.4G features='0' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=0 status=active
|- 8:0:0:135 sdc 8:32 failed faulty running
`- 7:0:0:135 sdb 8:16 failed faulty running
mpathb (3600140512e2d3ad7ae048aba1ee0a33a) dm-3 LIO-ORG,ubusrv-wrth
size=3.9G features='0' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=0 status=active
|- 8:0:0:235 sdd 8:48 failed faulty running
`- 7:0:0:235 sde 8:64 failed faulty running
root@ubusrv:~#

root@ubusrv:~# cat /sys/block/sd[b-e]/device/state
transport-offline
transport-offline
transport-offline
transport-offline
root@ubusrv:~#

root@ubusrv:~# l /dev/mapper/mpath*
lrwxrwxrwx 1 root root 7 Oct 19 13:35 /dev/mapper/mpatha -> ../dm-2
lrwxrwxrwx 1 root root 7 Oct 19 13:35 /dev/mapper/mpatha-part1 -> ../dm-4
lrwxrwxrwx 1 root root 7 Oct 19 13:35 /dev/mapper/mpathb -> ../dm-3
lrwxrwxrwx 1 root root 7 Oct 19 13:35 /dev/mapper/mpathb-part1 -> ../dm-5
root@ubusrv:~#

********
root@ubusrv:~# dd if=file.tar of=/dev/mapper/mpatha-part1 bs=10M
240+1 records in
240+1 records out
2526904320 bytes (2.5 GB, 2.4 GiB) copied, 5.65064 s, 447 MB/s <<<<<<<<
root@ubusrv:~#
********
----------------------


Is it a Device Mapper feature?


--
Regards,
Mirek

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-47-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/hwC0D0', '/dev/snd/controlC0', '/dev/snd/by-path'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
Date: Sat Oct 19 15:39:00 2024
InstallationDate: Installed on 2024-09-03 (46 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 (20240423)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-47-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-47-generic N/A
linux-backports-modules-6.8.0-47-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.3-debian-1.16.3-2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-8.2
dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.3-debian-1.16.3-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.2:cvnQEMU:ct1:cvrpc-q35-8.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-8.2
dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084979/+subscriptions

[Bug 2083022] Re: [SRU] Fix AST DP output after resume

Verified proposed kernel image 6.8.0-50-generic #51-Ubuntu.

suspend 100 times, DP output is good always. No error in dmesg.

$ cat /sys/class/drm/card0-DP-1/status
connected

** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2083022

Title:
[SRU] Fix AST DP output after resume

Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.8 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Committed
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-oem-6.8 source package in Oracular:
Invalid

Bug description:
[Impact]
After resume from suspend, the mini-DP output from ASPEED BMC card
is either blank or mess up.

[Fix]
From upstream 6.11 kernel,

1, a fix of the blank screen after resume:
12c35c5582acb drm/ast: Fix black screen after resume

2, DP detection fix:
0ce91928ec62d drm/ast: astdp: Wake up during connector status detection

3, the patchset refactors the CRTC's mode-setting code:
https://lore.kernel.org/all/20240627153638.8765-1-tzimmermann@suse.de/

[Test]
Tested on hardware by vendor for 10 times of suspend and resume.
The screen is OK.

[Where problems could occur]
It may break ASPEED drm support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2083022/+subscriptions

[Bug 2061254] Re: No mic detected - Ubuntu 24.04 Beta

** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released

** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Released

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2061254

Title:
No mic detected - Ubuntu 24.04 Beta

Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Released

Bug description:
On Ubuntu 23.10, my laptop microphone is detected/working fine, but can't be detected on Ubuntu 24.04.
Tried direct direct install of 24.04 and upgrade fromo 23.10, same problem

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: burnarz 43101 F.... pipewire
/dev/snd/controlC0: burnarz 43106 F.... wireplumber
/dev/snd/controlC1: burnarz 43106 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 14 01:04:10 2024
InstallationDate: Installed on 2024-04-13 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412)
MachineType: LENOVO 83AR
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2024
dmi.bios.release: 1.33
dmi.bios.vendor: LENOVO
dmi.bios.version: MDCN33WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Pro 5 16APH8
dmi.ec.firmware.release: 1.33
dmi.modalias: dmi:bvnLENOVO:bvrMDCN33WW:bd01/24/2024:br1.33:efr1.33:svnLENOVO:pn83AR:pvrIdeaPadPro516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrIdeaPadPro516APH8:skuLENOVO_MT_83AR_BU_idea_FM_IdeaPadPro516APH8:
dmi.product.family: IdeaPad Pro 5 16APH8
dmi.product.name: 83AR
dmi.product.sku: LENOVO_MT_83AR_BU_idea_FM_IdeaPad Pro 5 16APH8
dmi.product.version: IdeaPad Pro 5 16APH8
dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061254/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.15/5.15.0.1071.77~20.04.1)

All autopkgtests for the newly accepted linux-meta-oracle-5.15 (5.15.0.1071.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

dpdk/19.11.14-0ubuntu0.20.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-oracle-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013

Title:
Packaging resync

Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix

Bug description:
Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 2088733] Re: low CPU frequency after wake up AMD Ryzen

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 subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733

Title:
low CPU frequency after wake up AMD Ryzen

Status in linux package in Ubuntu:
Confirmed

Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:

$ watch lscpu -e=CPU,MHZ

standard output looks like:

CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050

while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.

Restart fixes the issue or plug power cable off and in again.

My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC

I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.

https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1

This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions

[Bug 2088733] Re: low CPU frequency after wake up AMD Ryzen

Well, I have the exact same issue but for me the issue is completely uncorrelated with being plugged in or out. That means, I have faced the issue in all the following scenarios:
(1) plugged in the all the time
(2) plugged out all the time
(3) plugged in - suspend - plugged out - wake up
(4) plugged out - suspend - plugged in - wake up

However, I think all the times the issue appeared I had closed the lid!

I have Thinkpad, amd 7940hs, ubuntu 2.04.1 6.8.0.49
BIOS is allways updated to the latest version. Must be a linux issue because never faced this problem in windows.
Linux has never been kind to any hardware which is not too old, but this is utter nonsense.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733

Title:
low CPU frequency after wake up AMD Ryzen

Status in linux package in Ubuntu:
Confirmed

Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:

$ watch lscpu -e=CPU,MHZ

standard output looks like:

CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050

while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.

Restart fixes the issue or plug power cable off and in again.

My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC

I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.

https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1

This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle-5.15/5.15.0-1071.77~20.04.1)

All autopkgtests for the newly accepted linux-restricted-modules-oracle-5.15 (5.15.0-1071.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-oracle-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013

Title:
Packaging resync

Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix

Bug description:
Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-5.15/5.15.0-1072.80~20.04.1)

All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.15 (5.15.0-1072.80~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-gcp-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013

Title:
Packaging resync

Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix

Bug description:
Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 2088733] Re: low CPU frequency after wake up AMD Ryzen

there are no updates:

$ sudo fwupdmgr update
Devices with no available firmware updates:
• ELAN07A8:00 04F3:31EC
• HP 5MP Camera
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• WD PC SN810 SDCPNRZ-2T00-1006
Devices with the latest available firmware version:
• Prometheus
• Prometheus IOTA Config
• System Firmware
• UEFI dbx

I tried to update the BIOS from BIOS where I could see version of BIOS
is from August this year. I was not able to confirm there is newer
version of BIOS available. I suppose I could try to write email to HP
support to confirm that information.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733

Title:
low CPU frequency after wake up AMD Ryzen

Status in linux package in Ubuntu:
New

Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:

$ watch lscpu -e=CPU,MHZ

standard output looks like:

CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050

while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.

Restart fixes the issue or plug power cable off and in again.

My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC

I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.

https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1

This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-meta-gke/5.15.0.1070.69)

All autopkgtests for the newly accepted linux-meta-gke (5.15.0.1070.69) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-470-server/unknown (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-gke

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013

Title:
Packaging resync

Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix

Bug description:
Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-meta/6.8.0-50.51)

All autopkgtests for the newly accepted linux-meta (6.8.0-50.51) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

casper/1.498 (amd64)
glibc/2.39-0ubuntu8.3 (ppc64el)
lxc/unknown (ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013

Title:
Packaging resync

Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix

Bug description:
Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset

Fire Kirin APK offers exciting challenges with rewards to keep players
engaged. https://fire-kirinapk.com/

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1258837

Title:
[Dell Latitude E7440] ALPS touchpad keeps having state reset

Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux package in Fedora:
Won't Fix

Bug description:
The mouse cursor keeps on jumping around, and these messages appear in the log when it happens:
Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.

The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad".
This is occurring with Ubuntu 13.10, though I have also seen this
behaviour in the version of Linux Mint based on Ubuntu 13.04.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: allanc 1852 F.... pulseaudio
 /dev/snd/controlC0: allanc 1852 F.... pulseaudio
Date: Sat Dec 7 22:19:22 2013
HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec
InstallationDate: Installed on 2013-12-07 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E7440
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 07F3F4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions

[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset

The Toca Boca World MOD APK version is easy to install and provides an
ad-free experience. https://apktocalife.com/

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1258837

Title:
[Dell Latitude E7440] ALPS touchpad keeps having state reset

Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux package in Fedora:
Won't Fix

Bug description:
The mouse cursor keeps on jumping around, and these messages appear in the log when it happens:
Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.

The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad".
This is occurring with Ubuntu 13.10, though I have also seen this
behaviour in the version of Linux Mint based on Ubuntu 13.04.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: allanc 1852 F.... pulseaudio
 /dev/snd/controlC0: allanc 1852 F.... pulseaudio
Date: Sat Dec 7 22:19:22 2013
HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec
InstallationDate: Installed on 2013-12-07 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E7440
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 07F3F4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions