[Kernel-packages] [Bug 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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/2038777
Title:
UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
Status in linux package in Ubuntu:
Expired
Bug description:
HiperV VM network problems
[ 19.259297]
[ 19.259536] UBSAN: array-index-out-of-bounds in
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
[ 19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
[ 19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted
6.5.0-7-generic #7-Ubuntu
[ 19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
[ 19.259899] Call Trace:
[ 19.259901]
[ 19.259902] dump_stack_lvl+0x48/0x70
[ 19.259908] dump_stack+0x10/0x20
[ 19.259909] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 19.259912] netvsc_receive+0x437/0x490 [hv_netvsc]
[ 19.259917] netvsc_poll+0x176/0x4b0 [hv_netvsc]
[ 19.259921] __napi_poll+0x30/0x1f0
[ 19.259924] net_rx_action+0x181/0x2e0
[ 19.259925] __do_softirq+0xd6/0x346
[ 19.259927] ? _raw_spin_unlock+0xe/0x40
[ 19.259929] __irq_exit_rcu+0x75/0xa0
[ 19.259932] irq_exit_rcu+0xe/0x20
[ 19.259933] sysvec_hyperv_callback+0x92/0xd0
[ 19.259935]
[ 19.259935]
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.8
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CrashDB: ubuntu
Date: Sun Oct 8 23:09:45 2023
InstallationDate: Installed on 2021-03-07 (945 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64
(20210201.2)
PackageArchitecture: all
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
XDG_RUNTIME_DIR=
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
VarLogDistupgradeLspcitxt:
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 oct 9 20:46 seq
crw-rw 1 root audio 116, 33 oct 9 20:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-03-07 (948 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64
(20210201.2)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lspci-vt:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
XDG_RUNTIME_DIR=
ProcFB: 0 hyperv_drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/06/2022
dmi.bios.release: 4.1
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v4.1
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v4.1
[Kernel-packages] [Bug 2047712] Re: FS disconnects on WD PC SN810 SDCPNRZ HP FW
Hello,
5 minutes after I submitted this bug FS was disconnected again.
Therefore it seems that the issue was not solved.
When I tried to check status of disk, there was no response from nvme
controller.
Tried smartclt and nvme tool.
--
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/2047712
Title:
FS disconnects on WD PC SN810 SDCPNRZ HP FW
Status in linux package in Ubuntu:
New
Bug description:
Hello,
I bought notebook HP ZBook Firefly 14 G10 A with AMD Ryzen 7 7840HS CPU.
This notebook have nvme SSD WD PC SN810 SDCPNRZ-2T00 with HPS2 firmware.
When I use standard Ubuntu kernel 6.5.0-14-generic, disk regularly
disconnects and FS become ReadOnly.
I found similar issue with eg. Kingston A2000 nvme disk. This seems to
Firmware bug.
I tried same solution and this worked.
As first workaround I tried add kernel parameter
"nvme_core.default_ps_max_latency_us=1".
Behavior was much better, but sometimes disk still disconnects (after connect
disconnect from Thunderbolt docking station or after several sleep/wake cycles)
Second workaround was update kernel source code and setup quirk
"NVME_QUIRK_NO_DEEPEST_PS" for disk identifier. Then I build kernel package and
install it on notebook with Ubuntu 23.10.
After ~4days of usage it seems that this is working solution.
Now I running my own kernel build 6.5.3 (from sources downloaded via
apt package manager), this is reason why I cannot provide "ubuntu-bug
linux" output.
Will be possible to add this solution to the default kernel image please?
I'm not a developer and not sure if this is all you need.
I can provide additional info or testing if will be needed.
--
Updated was file "linux-6.5.0/drivers/nvme/host/pci.c" with following lines:
--- drivers-nvme-host-pci.c.original 2023-12-29 20:48:38.048105439 +0100
+++ drivers-nvme-host-pci.c.new 2023-12-29 20:48:38.064104967 +0100
@@ -3399,6 +3399,8 @@
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x15b7, 0x2001), /* Sandisk Skyhawk */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x15b7, 0x5011), /* Sandisk Corp WD PC SN810
SDCPNRZ-2T00 (HPS2 FW) */
+.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
{ PCI_DEVICE(0x1d97, 0x2263), /* SPCC */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x144d, 0xa80b), /* Samsung PM9B1 256G and 512G */
--
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
--
$ apt-cache policy linux-image-6.5.0-14-generic
linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14
Candidate: 6.5.0-14.14
Version table:
*** 6.5.0-14.14 500
500 http://sk.archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
100 /var/lib/dpkg/status
$ apt-cache policy linux-image-6.5.3
linux-image-6.5.3:
Installed: 6.5.3-2
Candidate: 6.5.3-2
Version table:
*** 6.5.3-2 100
100 /var/lib/dpkg/status
--
$ sudo smartctl -ic /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.3] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WD PC SN810 SDCPNRZ-2T00-1006
Serial Number:
Firmware Version: HPS2
PCI Vendor/Subsystem ID:0x15b7
IEEE OUI Identifier:0x001b44
Total NVM Capacity: 2 048 408 248 320 [2,04 TB]
Unallocated NVM Capacity: 0
Controller ID: 8224
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2 048 408 248 320 [2,04 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64:001b44 8b4a02b37b
Local Time is: Fri Dec 29 21:04:43 2023 CET
Firmware Updates (0x14):2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Pers_Ev_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 88 Celsius
Namespace 1 Features (0x02):NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.25W8.25W -0 0 0 00 0
1 + 3.50W3.50W -0 0 0 00 0
2 + 2.60W2.60W -0 0 0 00
[Kernel-packages] [Bug 2047712] [NEW] FS disconnects on WD PC SN810 SDCPNRZ HP FW
Public bug reported:
Hello,
I bought notebook HP ZBook Firefly 14 G10 A with AMD Ryzen 7 7840HS CPU.
This notebook have nvme SSD WD PC SN810 SDCPNRZ-2T00 with HPS2 firmware.
When I use standard Ubuntu kernel 6.5.0-14-generic, disk regularly disconnects
and FS become ReadOnly.
I found similar issue with eg. Kingston A2000 nvme disk. This seems to Firmware
bug.
I tried same solution and this worked.
As first workaround I tried add kernel parameter
"nvme_core.default_ps_max_latency_us=1".
Behavior was much better, but sometimes disk still disconnects (after connect
disconnect from Thunderbolt docking station or after several sleep/wake cycles)
Second workaround was update kernel source code and setup quirk
"NVME_QUIRK_NO_DEEPEST_PS" for disk identifier. Then I build kernel package and
install it on notebook with Ubuntu 23.10.
After ~4days of usage it seems that this is working solution.
Now I running my own kernel build 6.5.3 (from sources downloaded via apt
package manager), this is reason why I cannot provide "ubuntu-bug linux"
output.
Will be possible to add this solution to the default kernel image please?
I'm not a developer and not sure if this is all you need.
I can provide additional info or testing if will be needed.
--
Updated was file "linux-6.5.0/drivers/nvme/host/pci.c" with following lines:
--- drivers-nvme-host-pci.c.original2023-12-29 20:48:38.048105439 +0100
+++ drivers-nvme-host-pci.c.new 2023-12-29 20:48:38.064104967 +0100
@@ -3399,6 +3399,8 @@
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x15b7, 0x2001), /* Sandisk Skyhawk */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x15b7, 0x5011), /* Sandisk Corp WD PC SN810
SDCPNRZ-2T00 (HPS2 FW) */
+.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
{ PCI_DEVICE(0x1d97, 0x2263), /* SPCC */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x144d, 0xa80b), /* Samsung PM9B1 256G and 512G */
--
$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
--
$ apt-cache policy linux-image-6.5.0-14-generic
linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14
Candidate: 6.5.0-14.14
Version table:
*** 6.5.0-14.14 500
500 http://sk.archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
100 /var/lib/dpkg/status
$ apt-cache policy linux-image-6.5.3
linux-image-6.5.3:
Installed: 6.5.3-2
Candidate: 6.5.3-2
Version table:
*** 6.5.3-2 100
100 /var/lib/dpkg/status
--
$ sudo smartctl -ic /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.3] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WD PC SN810 SDCPNRZ-2T00-1006
Serial Number:
Firmware Version: HPS2
PCI Vendor/Subsystem ID:0x15b7
IEEE OUI Identifier:0x001b44
Total NVM Capacity: 2 048 408 248 320 [2,04 TB]
Unallocated NVM Capacity: 0
Controller ID: 8224
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2 048 408 248 320 [2,04 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64:001b44 8b4a02b37b
Local Time is: Fri Dec 29 21:04:43 2023 CET
Firmware Updates (0x14):2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 88 Celsius
Namespace 1 Features (0x02):NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.25W8.25W -0 0 0 00 0
1 + 3.50W3.50W -0 0 0 00 0
2 + 2.60W2.60W -0 0 0 00 0
3 - 0.0250W --3 3 3 3 5000 1
4 - 0.0035W --4 4 4 4 3900 45700
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 2
1 -4096 0 1
--
Thanks
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "OS Report and diff file from my patch."
https://bugs.launchpad.net/bugs/2047712/+attachment/5734736/+files/report-and-patch.zip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1642112] Re: Can’t connect to the second BT device successfully
Same problem for me. System: Ubuntu 22.04 bluez version 5.64 Devices: 2x Playstation 5 DualSense Controllers Problem description: Connecting either of the controllers individually works without a problem. But when trying to connect both of them, the second fails. SOMETIMES it works though and I didn't found out what was different. Can someome tell, if this is fixed in newer versions? If yes, I will try a system upgrade out of the LTS sequence. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1642112 Title: Can’t connect to the second BT device successfully Status in bluez package in Ubuntu: New Bug description: OS: 14.04 bluez version: 4.x After first bt device(eg. mouse) connected, try to connect second device(eg. keyboard), found it has no function when connected, and sometimes it fails to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1642112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
A fresh install of 23.10 on a new ASUS Z790 Formula motherboard had no
working wifi or bluetooth for me.
journalctl showed (among other things):
iwlwifi :05:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-80.ucode
failed with error -2
iwlwifi :05:00.0: no suitable firmware found!
kernel: Bluetooth: hci0: Failed to load Intel firmware file
intel/ibt-0291-0291.sfi (-2)
An install of the package 20230919.git3672ccab-0ubuntu2.5 from proposed
just fixed this for me - thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2028065
Title:
Support for Intel Discrete Gale Peak2/BE200
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
== linux-firmware ==
[Impact]
Missing firmware for Intel BE200 on Intel Meteor Lake platform.
[Fix]
Needed firmware:
- WiFi:
* a6744df81a30 ("iwlwifi: add FWs for new GL and MA device types with
multiple RF modules")
- Bluetooth:
* 37761e2b861b ("Intel Bluetooth: Update firmware file for Intel Bluetooth
BE200")
* a5a6dded0c7f ("Intel Bluetooth: Update firmware file for Intel Bluetooth
BE200")
* ba1aa06f3747 ("Intel Bluetooth: Update firmware file for Intel Bluetooth
BE200")
The driver parts have been landed to linux-oem-6.5/jammy, linux/mantic and
linux/noble.
[Test Case]
Boot with firmware blobs installed, and iwlwifi and btintel should probe
successfully without error.
[Kernel-packages] [Bug 2032767] Re: Fix ACPI TAD on some Intel based systems
Hi, some acpi errors similar to these are appearing here, I don't know if it's appropriate to report here, but maybe it will help. I'm on kubuntu 23.10, intel i3 1115G4 laptop Lenovo ideapad 3 15itl6 82md, acpi bios error (bug) could not resolve symbol [\_SB.PCI0], AE_NOT_FOUND (20230331/dswload2-162) acpi error: ae_not_found during name lookup/catalog (20230331/psobject-220) acpi bios error (bug) could not resolve symbol [\_SB.PC00.DGPV], AE_NOT_FOUND (20230331/psargs-330) acpi error: Aborting method \_SB.PC00.PEG0PCRP._ON due to previous error (AE_NOT_FOUND)(20230331/psparse-529) acpi error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND)(20230331/psparse-529) acpi bios error (bug) could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20230331/psargs-330) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2032767 Title: Fix ACPI TAD on some Intel based systems Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ACPI TAD doesn't really work on several systems. When accessing TAD interface via sysfs, like setting/getting realtime, it also causes errors: [ 478.255453] ACPI Error: No handler for Region [RTCM] (a8d2dd39) [SystemCMOS] (20230331/evregion-130) [ 478.255458] ACPI Error: Region SystemCMOS (ID=5) has no handler (20230331/exfldio-261) [ 478.255461] Initialized Local Variables for Method [_GRT]: [ 478.255461] Local1: f182542cInteger [ 478.255464] No Arguments are initialized for method [_GRT] [ 478.255465] ACPI Error: Aborting method \_SB.AWAC._GRT due to previous error (AE_NOT_EXIST) (20230331/psparse-529) [Fix] Let the driver to install a handler for its SystemCMOS region. The spec on whether certain devices can use SystemCMOS or not is quite vague, so follow the de facto implementation, Windows :) [Test] Once the patch is applied, setting and getting realtime through TAD sysfs work, and there's no more error in dmesg. [Where problems could occur] Now ACPI TAD driver also depends on ACPI RTC driver, so the memory usage will go up slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938474] Re: delve golang debugger can't read vvar on arm64
Fixed in delve.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1938474
Title:
delve golang debugger can't read vvar on arm64
Status in Delve:
Fix Released
Status in delve package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Bug description:
Also documented upstream:
https://github.com/go-delve/delve/issues/2630
In version 1.6.1 of the delve golang debugger, a 'dump' feature was added.
https://github.com/go-delve/delve/pull/2173
Since that time, arm64 autopkgtest of delve has been failing like so:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/delve/20210707_003312_d3699@/log.gz
=== RUN TestDump
proc_test.go:5117: testing normal dump
proc_test.go:5029: bad DumpState
{Mutex:sync.Mutex{state:0, sema:0x0}, Dumping:false,
AllDone:true, Canceled:false, DoneChan:(chan struct {})(nil), ThreadsDone:5,
ThreadsTotal:5, MemDone:0x657b000, MemTotal:0x657d000, Err:error(nil)}
--- FAIL: TestDump (0.98s)
The test fails becaue MemDone != MemTotal.
The decision on what to dump or not is based on smaps.
The failing item is vvar.
err when attempting to read is
error(syscall.Errno) golang.org/x/sys/unix.EIO (5)
Notably however, this test passes in debian CI. (kernel 4.19)
Also, running on older series such as bionic/focal does pass.
vvar section from vm with kernel 5.4 (test pass):
924a4000-924a5000 r--p 00:00 0
[vvar]
Size: 4 kB
KernelPageSize:4 kB
MMUPageSize: 4 kB
Rss: 0 kB
Pss: 0 kB
Shared_Clean: 0 kB
Shared_Dirty: 0 kB
Private_Clean: 0 kB
Private_Dirty: 0 kB
Referenced:0 kB
Anonymous: 0 kB
LazyFree: 0 kB
AnonHugePages: 0 kB
ShmemPmdMapped:0 kB
FilePmdMapped:0 kB
Shared_Hugetlb:0 kB
Private_Hugetlb: 0 kB
Swap: 0 kB
SwapPss: 0 kB
Locked:0 kB
THPeligible:0
VmFlags: rd mr de
vvar from failing case
ac144000-ac146000 r--p 00:00 0
[vvar]
Size: 8 kB
KernelPageSize:4 kB
MMUPageSize: 4 kB
Rss: 0 kB
Pss: 0 kB
Shared_Clean: 0 kB
Shared_Dirty: 0 kB
Private_Clean: 0 kB
Private_Dirty: 0 kB
Referenced:0 kB
Anonymous: 0 kB
LazyFree: 0 kB
AnonHugePages: 0 kB
ShmemPmdMapped:0 kB
FilePmdMapped: 0 kB
Shared_Hugetlb:0 kB
Private_Hugetlb: 0 kB
Swap: 0 kB
SwapPss: 0 kB
Locked:0 kB
THPeligible:0
VmFlags: rd mr pf de
Two noticible differences
1) 4kB vs 8kB size
2) Failing case adds the "pf" flag ("pure PFN range")
Open questions:
1) Would we expect that a debugger could read vvar on arm64?
2) Any thoughts on why this seems to work on older kernels?
3) Do we believe this to be a kernel bug,
or should the delve debugger not expect to read vvar?
4) Is it sensible for a debugger to attempt to read things with the "pf"
flag? Note that the "dd" ("do not include area into core dump")
flag is not set.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic aarch64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jul 29 21:21 seq
crw-rw 1 root audio 116, 33 Jul 29 21:21 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu67
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Thu Jul 29 21:34:34 2021
InstallationDate: Installed on 2021-07-29 (0 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210729)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
MachineType: QEMU QEMU Virtual Machine
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB:
[Kernel-packages] [Bug 2009595] Re: DEP8 failure in lunar
Fixed in 6.2.0-16.16 as per previous comment. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2009595 Title: DEP8 failure in lunar Status in crash package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: I don't know what's wrong with this package, or with the kernel package: ubuntu@l-crash:~$ sudo crash -st /usr/lib/debug/boot/vmlinux-6.1.0-16-generic WARNING: /usr/lib/debug/boot/vmlinux-6.1.0-16-generic and /proc/version do not match! WARNING: /proc/version indicates kernel version: 6.1.0-16-generic crash: please use the vmlinux file for that kernel version, or try using the System.map for that kernel version as an additional argument. It is the same version: ubuntu@l-crash:~$ uname -a Linux l-crash 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l|grep linux- ii binutils-x86-64-linux-gnu2.40-2ubuntu1 ii linux-base 4.5ubuntu9 ii linux-firmware 20230302.git60971a64-0ubuntu1 ii linux-headers-6.1.0-16 6.1.0-16.16 ii linux-headers-6.1.0-16-generic 6.1.0-16.16 ii linux-headers-generic6.1.0.16.16 ii linux-image-6.1.0-16-generic 6.1.0-16.16 ii linux-image-6.1.0-16-generic-dbgsym 6.1.0-16.16 ii linux-image-generic 6.1.0.16.16 ii linux-image-unsigned-6.1.0-16-generic-dbgsym 6.1.0-16.16 ii linux-libc-dev:amd64 6.1.0-16.16 ii linux-modules-6.1.0-16-generic 6.1.0-16.16 ii linux-modules-extra-6.1.0-16-generic 6.1.0-16.16 ii util-linux-extra 2.38.1-4ubuntu1 $ apt-cache policy linux-image-unsigned-6.1.0-16-generic-dbgsym linux-image-unsigned-6.1.0-16-generic-dbgsym: Installed: 6.1.0-16.16 Candidate: 6.1.0-16.16 Version table: *** 6.1.0-16.16 500 500 http://ddebs.ubuntu.com lunar/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2009595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021481] Re: delve ftbfs on amd64 due to bpftool
It looks like this issue was fixed in delve. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/2021481 Title: delve ftbfs on amd64 due to bpftool Status in delve package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: src/github.com/go-delve/delve/pkg/proc/internal/ebpf/helpers.go WARNING: bpftool not found for kernel 6.1.0-9 You may need to install the following packages for this specific kernel: linux-tools-6.1.0-9-amd64 linux-cloud-tools-6.1.0-9-amd64 You may also want to install one of the following packages to keep up to date: linux-tools-amd64 linux-cloud-tools-amd64 The Debian package build-depends on bpftool. But bpftool is different in Debian and Ubuntu. On Ubuntu it's provided by linux-tools-common. However it seems it needs linux-tools-amd64 as well? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/delve/+bug/2021481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047695] [NEW] Increased battery usage while sleeping
Public bug reported: Upgrading from linux-image-5.19.0-50-generic to linux- image-6.2.0-39-generic increases battery usage from about 5-10% to 50-70% during 8-10 hours of the lid being closed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Fri Dec 29 13:00:51 2023 InstallationDate: Installed on 2023-01-27 (336 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2047695 Title: Increased battery usage while sleeping Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Upgrading from linux-image-5.19.0-50-generic to linux- image-6.2.0-39-generic increases battery usage from about 5-10% to 50-70% during 8-10 hours of the lid being closed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Fri Dec 29 13:00:51 2023 InstallationDate: Installed on 2023-01-27 (336 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2047695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047692] Re: "Disable RNG for all AMD fTPMs" breaks TPM on some Intel devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Confirmed -- 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/2047692 Title: "Disable RNG for all AMD fTPMs" breaks TPM on some Intel devices Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: 6.2.0-39.40~22.04.1 includes upstream stable patchset 2023-10-10 (https://launchpad.net/bugs/2038969) with the TPM changes 'Disable RNG for all AMD fTPMs' and 'Add a helper for checking hwrng enabled'. This causes on some Intel devices that TPM does not work (in my case a Gigabyte Brix GB-BSi5-1135G7) with the error " tpm_crb: probe of MSFT0101:00 failed with error 378 " Upstream discussed this issue in https://bugzilla.kernel.org/show_bug.cgi?id=217804 and a fix was found: https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8 Full disclosure: I report this issue based only on above links. I did not try to run my affected device with a patched kernel and switched for the time being back to the HWE kernel 6.2.0-37. But the deswcription of the issue is a very good fit to the behaviour I see with the Gigabyte PC. LSB release infos: Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2047692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047692] [NEW] "Disable RNG for all AMD fTPMs" breaks TPM on some Intel devices
Public bug reported: 6.2.0-39.40~22.04.1 includes upstream stable patchset 2023-10-10 (https://launchpad.net/bugs/2038969) with the TPM changes 'Disable RNG for all AMD fTPMs' and 'Add a helper for checking hwrng enabled'. This causes on some Intel devices that TPM does not work (in my case a Gigabyte Brix GB-BSi5-1135G7) with the error " tpm_crb: probe of MSFT0101:00 failed with error 378 " Upstream discussed this issue in https://bugzilla.kernel.org/show_bug.cgi?id=217804 and a fix was found: https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8 Full disclosure: I report this issue based only on above links. I did not try to run my affected device with a patched kernel and switched for the time being back to the HWE kernel 6.2.0-37. But the deswcription of the issue is a very good fit to the behaviour I see with the Gigabyte PC. LSB release infos: Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New -- 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/2047692 Title: "Disable RNG for all AMD fTPMs" breaks TPM on some Intel devices Status in linux-hwe-6.2 package in Ubuntu: New Bug description: 6.2.0-39.40~22.04.1 includes upstream stable patchset 2023-10-10 (https://launchpad.net/bugs/2038969) with the TPM changes 'Disable RNG for all AMD fTPMs' and 'Add a helper for checking hwrng enabled'. This causes on some Intel devices that TPM does not work (in my case a Gigabyte Brix GB-BSi5-1135G7) with the error " tpm_crb: probe of MSFT0101:00 failed with error 378 " Upstream discussed this issue in https://bugzilla.kernel.org/show_bug.cgi?id=217804 and a fix was found: https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8 Full disclosure: I report this issue based only on above links. I did not try to run my affected device with a patched kernel and switched for the time being back to the HWE kernel 6.2.0-37. But the deswcription of the issue is a very good fit to the behaviour I see with the Gigabyte PC. LSB release infos: Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2047692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028217] Re: MTL: Add support for Meteor Lake
hi acelan, Got it, thanks a lot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Released Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028217] Re: MTL: Add support for Meteor Lake
https://github.com/intel/thermal_daemon/issues/268 It's a known issue on lenovo laptops which lacks of firmware support. Suggested by upstream to add --ingore-cpuid-check to make thermald keeps working. ** Bug watch added: github.com/intel/thermal_daemon/issues #268 https://github.com/intel/thermal_daemon/issues/268 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Released Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028217] Re: MTL: Add support for Meteor Lake
Hi koba, The lastest thermald 2.4.9-1ubuntu0.4 failed to start on my Meteor Lake platform, is it expected cause the dytc_lapmode? Thanks! Dec 29 14:38:16 Mersey-1 thermald[842]: 35 CPUID levels; family:model:stepping 0x6:aa:4 (6:170:4) Dec 29 14:38:16 Mersey-1 thermald[842]: [/sys/devices/platform/thinkpad_acpi/dytc_lapmode] present: Thermald can't run on this platform Dec 29 14:38:16 Mersey-1 thermald[842]: Unsupported cpu model or platform Dec 29 14:38:16 Mersey-1 systemd[1]: thermald.service: Deactivated successfully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Released Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047518] Re: Fix BCM57416 lost after resume
verified work on a ThinkStation device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047518 Title: Fix BCM57416 lost after resume Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] BCM57416 is lost after resume. Error log: [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 0x125d error 0x4 [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 failed. rc:ffe4 err:4 [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: fffb [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb [Fix] Clear the reservations in driver after reset the ethernet card. [Test] Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine. [Where problems could occur] It may break broadcom bnxt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
