[Kernel-packages] [Bug 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao) -- 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/2060748 Title: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card Status in linux package in Ubuntu: New Bug description: I just installed Kubuntu 23.10 (using latest default kernel) on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth card. Here is output from lspci -v: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi Wifi error popping up every few minutes in Kubuntu I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi card: Code: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi The internet seems to be somewhat working, but at least once a minute I have two "Network Management" error notifications that pop up in KDE that say "Connection Wired Connection 3 deactivated" and "Wired Interface e2x52e8ae7d39d1: IP configuration was unavailable". I checked the logs in /var/log/dmesg and saw that there were a ton of iwlwifi error messages in there that look like this: [ 44.926474] kernel: Intel(R) Wireless WiFi driver for Linux [ 44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002) [ 44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x8000 [ 44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than supported by driver [ 44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 [ 44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm [ 44.955070] kernel: Bluetooth: Core ver 2.22 [ 44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family [ 44.955090] kernel: Bluetooth: HCI device and connection manager initialized [ 44.955095] kernel: Bluetooth: HCI socket layer initialized [ 44.955097] kernel: Bluetooth: L2CAP socket layer initialized [ 44.955101] kernel: Bluetooth: SCO socket layer initialized [ 45.275827] kernel: Bluetooth: hci0: Device revision is 0 [ 45.275833] kernel: Bluetooth: hci0: Secure boot is enabled [ 45.275836] kernel: Bluetooth: hci0: OTP lock is enabled [ 45.275838] kernel: Bluetooth: hci0: API lock is enabled [ 45.275840] kernel: Bluetooth: hci0: Debug lock is disabled [ 45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 45.278400] kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi [ 45.278415] kernel: Bluetooth: hci0: Boot Address: 0x100800 [ 45.278416] kernel: Bluetooth: hci0: Firmware Version: 254-28.23 [ 47.405919] kernel: iwlwifi :e4:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20 [ 47.405936] kernel: iwlwifi :e4:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 47.405945] kernel: iwlwifi :e4:00.0: WFPM_AUTH_KEY_0: 0x90 [ 47.405955] kernel: iwlwifi :e4:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0 [ 47.493908] kernel: iwlwifi :e4:00.0: Registered PHC clock: iwlwifi-PTP, with index: 2 [ 48.366248] kernel: Bluetooth:
[Kernel-packages] [Bug 2060770] Re: NVMe drive fails at high write workload after kernel upgrades
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => Kai-Heng Feng (kaihengfeng) -- 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/2060770 Title: NVMe drive fails at high write workload after kernel upgrades Status in linux package in Ubuntu: New Bug description: My problem is similarly described in this old thread: https://unix.stackexchange.com/questions/742360/ journalctl message: one of the many related logs Apr 09 15:37:40.096850 ** kernel: Linux version 6.5.0-26-lowlatency (buildd@lcy02-amd64-109) (x86_64-linux-gnu-gcc-12 (Ubunntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #26.1~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Mar 13 10:41:42 UTC (Ubuntu 6.5.0-26.26.1~22.04.1-lowlatency 6.5.13) Apr 09 15:43:46.238697 ** kernel: nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Apr 09 15:43:46.239162 ** kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Apr 09 15:43:46.239266 ** kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug Apr 09 15:43:46.690200 ** kernel: nvme :06:00.0: enabling device ( -> 0002) Apr 09 15:43:46.690409 ** kernel: nvme nvme0: Disabling device after reset failure: -19 Apr 09 15:43:46.698188 ** kernel: I/O error, dev nvme0n1, sector 1216896 op 0x1:(WRITE) flags 0xc800 phys_seg 1 prio clas> I was using 22.04.4 with hwe kernel, as shown above (kernel 6.5) upgrade to 24.04 dev hoping the problem would be resolved, but no it still exists (kernel 6.8) The problem happens after some kernel upgrades that I'd done after 2024-03-01, but I cannot pinpoint when; the nvme_core kernel param as shown in the message above does not help. The problem does NOT exist with 22.04 regular kernel: Currently I'd created a VM to perform my heavy write workload using pci passthrough of the NVMe drive, and it works okay. Cannot downgrade host to older kernel because of ZFS pool being upgraded VM info (where my NVMe drive works okay) uname -r 5.15.0-78-lowlatency lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy (maybe) related hardware spec CPU: AMD Ryzen 5750G (x8x4x4) Chipset: AMD B450 NVMe: Samsung MZ1LB960HBJR-000FB (PM983a, f/w EDW73F2Q) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060770/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu)
--
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/2060989
Title:
package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
New
Bug description:
-
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nela 2694 F wireplumber
/dev/snd/controlC1: nela 2694 F wireplumber
/dev/snd/seq:nela 2674 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Apr 11 10:13:36 2024
ErrorMessage: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-30 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: HACN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion S7 15ACH6
dmi.ec.firmware.release: 1.27
dmi.modalias:
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
dmi.product.family: Legion S7 15ACH6
dmi.product.name: 82K8
dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
dmi.product.version: Legion S7 15ACH6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060981] Re: ACPI BIOS errors
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => Ivan Hu (ivan.hu) -- 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/2060981 Title: ACPI BIOS errors Status in linux package in Ubuntu: New Bug description: dmesg show the below ACPI errors, is this normal? # dmesg | grep -i acpi [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 [0.020042] ACPI: Early table checksum verification disabled [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_) [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 01072009 INTL 20191018) [0.020070] ACPI: FACS 0x59EBC000 40 [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt 3000 INTL 20191018) [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 01072009 AMI. 0005) [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 01072009 ASUS 0001) [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 1000 INTL 20191018) [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt 3000 INTL 20191018) [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL IgfxSsdt 3000 INTL 20191018) [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL TcssSsdt 1000 INTL 20191018) [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 01072009 AMI 0113) [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt INTL 20191018) [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 1000 INTL 20191018) [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC INTL 20191018) [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 1000 INTL 20191018) [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL EDK2 0002 0113) [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef HgRpSsdt 1000 INTL 20191018) [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel ADebTabl 1000 INTL 20191018) [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL RstVmdE ?? ) [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL RstVmdV ?? ) [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 0001 AMI ) [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 1000 INTL 20191018) [0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 0005 MSFT 010D) [0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I 01072009 AMI 0113) [0.020184] ACPI: Reserving FACP table memory at [mem 0x59dbd000-0x59dbd113] [0.020186] ACPI: Reserving DSDT table memory at [mem 0x59d6-0x59dbc523] [0.020187] ACPI: Reserving FACS table memory at [mem 0x59ebc000-0x59ebc03f] [0.020187] ACPI: Reserving MCFG table memory at [mem 0x59dc1000-0x59dc103b] [0.020188] ACPI: Reserving SSDT table memory at [mem 0x59dbe000-0x59dc055c] [0.020189] ACPI: Reserving FIDT table memory at [mem 0x59d5f000-0x59d5f09b] [
[Kernel-packages] [Bug 2058750] Re: i915 GPU HANG: ecode 12:1:db96edba
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => GuoqingJiang (guoqingjiang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058750 Title: i915 GPU HANG: ecode 12:1:db96edba Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: This has happened several times over a period of months when visiting the site https://www.windy.com and viewing satellite images. The computer completely freezes and must be hard restarted. I don't think I have triggered this freeze by visiting any other site. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 14:14:41 2024 InstallationDate: Installed on 2023-04-12 (344 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 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.5/+bug/2058750/+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 2060727] Re: The keyboard does not work after latest kernel update
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu) -- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060727] Re: The keyboard does not work after latest kernel update
I have a Dell XPS 13 running Kubuntu 22.04. Keyboard works fine on fresh boot but the keyboard doesnt work at all after resuming from suspend. linux-image-6.5.0-27-generic is the kernel I started having the problem with. Booting an older 6.5 kernel and keyboard works again after resume. -- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
I downloaded the files linked at the top labeled 20240315 and extracted them and installed it on my UZG-01 and I show "20230507" but it is stable as of right now. I have not gotten any more disconnect notices from my automation to monitor it since the update and connections do seem to be faster and more reliable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2053283] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el cód
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2053283 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: El problema persiste después de algunas semanas... linux 6.5.0-18-generic. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 16:31:46 2024 ErrorMessage: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2022-09-01 (532 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2053283/+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 2060709] Re: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate
Further testing ... ArchLinux 2024.04.01 ISO (Kernel 6.8.2) does boot up successfully on the same hardware environment. dmesg output enclosed. ** Attachment added: "dmesg-arch-linux-6.8.2-arch2-1.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+attachment/5764899/+files/dmesg-arch-linux-6.8.2-arch2-1.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060709 Title: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate Status in linux package in Ubuntu: New Bug description: Ubuntu with kernel 5.15 runs fine. With kernel 6.8, the system does not boot up. USB peripherals do not work, keyboard LEDs are off. Further error messages in screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xxx1799 F wireplumber /dev/snd/controlC0: xxx1799 F wireplumber /dev/snd/seq:xxx1797 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Apr 9 17:28:31 2024 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp1s0no wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fb4c915-afb5-4195-90f9-1e21e105aa17 ro noplymouth PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-101-generic N/A linux-backports-modules-5.15.0-101-generic N/A linux-firmware 20240202.git36777504-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+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 2061248] Re: kernel 5.15.0-102 - CIFS mount problem (NAS)
Now I noticed that the files I was able to save to the CIFS shared drive while the .102 kernel was active were not readable when I switched back to the .101 kernel. -- 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/2061248 Title: kernel 5.15.0-102 - CIFS mount problem (NAS) Status in linux package in Ubuntu: New Bug description: CIFS are regulary mounted via fstab (system has been stable for several years) and everything was fine with .101 but after the 08-apr-2024 kernel update suddenly the NAS shares are often stuck or timed out, unresponsive and not accessible (unavailable). Reverting from .102 to .101 brought everything back to working order as it was before kernel update. Something in the latest kernel 5.15.0-102 is not good for CIFS shares. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061248/+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 2061248] [NEW] kernel 5.15.0-102 - CIFS mount problem (NAS)
Public bug reported: CIFS are regulary mounted via fstab (system has been stable for several years) and everything was fine with .101 but after the 08-apr-2024 kernel update suddenly the NAS shares are often stuck or timed out, unresponsive and not accessible (unavailable). Reverting from .102 to .101 brought everything back to working order as it was before kernel update. Something in the latest kernel 5.15.0-102 is not good for CIFS shares. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2061248 Title: kernel 5.15.0-102 - CIFS mount problem (NAS) Status in linux package in Ubuntu: New Bug description: CIFS are regulary mounted via fstab (system has been stable for several years) and everything was fine with .101 but after the 08-apr-2024 kernel update suddenly the NAS shares are often stuck or timed out, unresponsive and not accessible (unavailable). Reverting from .102 to .101 brought everything back to working order as it was before kernel update. Something in the latest kernel 5.15.0-102 is not good for CIFS shares. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061248/+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 2058750] Re: i915 GPU HANG: ecode 12:1:db96edba
Another crash (viewing satellite images on windy.com) with a different
ecode:
Apr 13 20:32:58 james-xps kernel: [1286582.354762] i915 :00:02.0: [drm]
*ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x
Apr 13 20:32:58 james-xps kernel: [1286582.404294] i915 :00:02.0: [drm] GPU
HANG: ecode 12:1:84db, in CanvasRenderer [366470]
Apr 13 20:32:58 james-xps kernel: [1286582.404465] i915 :00:02.0: [drm]
Resetting chip for GuC failed to reset engine mask=0x1
Apr 13 20:32:58 james-xps kernel: [1286582.507012] i915 :00:02.0: [drm]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Apr 13 20:32:58 james-xps kernel: [1286582.507733] i915 :00:02.0: [drm]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Apr 13 20:32:58 james-xps kernel: [1286582.507886] i915 :00:02.0: [drm]
CanvasRenderer[366470] context reset due to GPU hang
Apr 13 20:32:58 james-xps kernel: [1286582.507988] i915 :00:02.0: [drm]
GT0: GuC firmware i915/adlp_guc_70.bin version 70.5.1
Apr 13 20:32:58 james-xps kernel: [1286582.507997] i915 :00:02.0: [drm]
GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Apr 13 20:32:58 james-xps kernel: [1286582.524574] i915 :00:02.0: [drm]
GT0: HuC: authenticated for all workloads
Apr 13 20:32:58 james-xps kernel: [1286582.525447] i915 :00:02.0: [drm]
GT0: GUC: submission enabled
Apr 13 20:32:58 james-xps kernel: [1286582.525448] i915 :00:02.0: [drm]
GT0: GUC: SLPC enabled
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058750
Title:
i915 GPU HANG: ecode 12:1:db96edba
Status in linux-signed-hwe-6.5 package in Ubuntu:
New
Bug description:
This has happened several times over a period of months when visiting
the site https://www.windy.com and viewing satellite images. The
computer completely freezes and must be hard restarted. I don't think
I have triggered this freeze by visiting any other site.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 14:14:41 2024
InstallationDate: Installed on 2023-04-12 (344 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
SourcePackage: linux-signed-hwe-6.5
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.5/+bug/2058750/+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 2048768] Re: Autopkgtest failures on amd64
This bug was fixed in the package gcc-11 - 11.4.0-9ubuntu1 --- gcc-11 (11.4.0-9ubuntu1) noble; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. gcc-11 (11.4.0-9) unstable; urgency=medium * Update to git 20240412 from the gcc-11 branch. - Fix PR fortran/114474. * Fix the gm2 bootstrap. -- Matthias Klose Fri, 12 Apr 2024 10:32:22 +0200 ** Changed in: gcc-11 (Ubuntu Noble) Status: Won't Fix => Fix Released -- 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/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Fix Released Status in gcc-13 package in Ubuntu: Fix Released Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Won't Fix Status in gcc-11 source package in Noble: Fix Released Status in gcc-12 source package in Noble: Fix Released Status in gcc-13 source package in Noble: Fix Released Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Won't Fix Status in linux source package in Noble: Fix Released Status in llvm-toolchain-14 source package in Noble: Won't Fix Status in llvm-toolchain-15 source package in Noble: Won't Fix Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped)
[Kernel-packages] [Bug 2059237] Comment bridged from LTC Bugzilla
--- Comment From kowshik.j...@in.ibm.com 2024-04-13 13:57 EDT--- With the latest kernel, issue is not getting reproduced. Hence closing this bug. -- 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/2059237 Title: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: == Comment:- Kowshik Jois B S == ---Problem Description--- Below trace messges are observed in dmesg after every reboot. [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [0.475750] Freeing unused kernel image (initmem) memory: 8832K [0.507388] Checked W+X mappings: passed, no W+X pages found [0.507400] Run /init as init process [0.507403] with arguments: [0.507404] /init [0.507405] with environment: [0.507406] HOME=/ [0.507407] TERM=linux [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic [0.511892] [ cut here ] [0.511904] UBSAN: array-index-out-of-bounds in /build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17 [0.511909] index 0 is out of range for type 'char [*]' [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic #11-Ubuntu [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries [0.511921] Call Trace: [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.511931] [c6683650] [c0c7bc58] __ubsan_handle_out_of_bounds+0xc4/0x12c [0.511938] [c6683700] [c005d2a8] module_frob_arch_sections+0x4ec/0x8d0 [0.511943] [c66837e0] [c02b98cc] layout_and_allocate.isra.0+0x38/0x2a8 [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0 [0.511953] [c6683990] [c02baca8] init_module_from_file+0xb4/0x14c [0.511958] [c6683a70] [c02baf70] sys_finit_module+0x230/0x48c [0.511963] [c6683b80] [c0033248] system_call_exception+0xe8/0x240 [0.511967] [c6683e50] [c000d15c] system_call_vectored_common+0x15c/0x2ec [0.511972] --- interrupt: 3000 at 0x7879b903b8a8 [0.511977] NIP: 7879b903b8a8 LR: CTR: [0.511980] REGS: c6683e80 TRAP: 3000 Not tainted (6.8.0-11-generic) [0.511984] MSR: 8000f033 CR: 48222428 XER: [0.511993] IRQMASK: 0 GPR00: 0161 7fffd683b580 7879b9166d00 0004 GPR04: 7879b8e0c160 0004 0010 0004 GPR08: 0001 GPR12: 7879b99d3a00 2000 0002 GPR16: 1b5c7d7453e0 7fffd683ba68 GPR20: 1b5c82154ae0 1b5c82142360 GPR24: 7879b957f7b0 1b5c82154ae0 1b5c82142160 GPR28: 7879b8e0c160 0002 1b5c82154ae0 1b5c82142380 [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8 [0.512032] LR [] 0x0 [0.512034] --- interrupt: 3000 [0.512036] ---[ end trace ]--- [0.518326] systemd[1]: Inserted module 'autofs4' [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) [0.521583] systemd[1]: Detected virtualization powervm. [0.521589] systemd[1]: Detected architecture ppc64-le. [0.521593] systemd[1]: Running in initrd. [0.521743] systemd[1]: No hostname configured, using default hostname. [0.521789] systemd[1]: Hostname set to . [0.521847] systemd[1]: Initializing machine ID from random generator. [0.600736] systemd[1]: Queued start job for default target initrd.target. Machine Type = P10 LPAR Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com ---Steps to Reproduce--- 1. reboot the system 2. Once the system is booted back, look at dmesg ---uname output--- Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux Additional Information: Same trace messages are seen on L2
[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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
Re: [Kernel-packages] [Bug 2032642] Re: nouveau 0000:01:00.0: gr: DATA_ERROR 0000009c [] ch 2 [103fe46000 gnome-shell[1951]] subc 0 class b197 mthd 0d78 data 00000004
Thanks, but I can't check. The Wayland session is no longer available, this
is apparently another bug. gdm3/custom.conf wayland is forcibly enabled and
udev gdm.rules allows wayland . However, gdm refers to the incorrect value
of XDG_SESSION_DESKTOP=x11. I haven't found what sets this environment
variable yet... but it doesn't look like it's a video driver.
ср, 27 мар. 2024 г. в 03:55, xslh <2032...@bugs.launchpad.net>:
> try:
> /etc/udev/rules.d/61-mutter-primary-gpu.rules
>
> content:
> ENV{DEVNAME}=="/dev/dri/card1", TAG+="mutter-device-preferred-primary"
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2032642
>
> Title:
> nouveau :01:00.0: gr: DATA_ERROR 009c [] ch 2 [103fe46000
> gnome-shell[1951]] subc 0 class b197 mthd 0d78 data 0004
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> nouveau+i965 second monitor is always black in wayland session.
> x11 works fine on nouveau and nvidia drivers.
> On logo screen (boot, reboot) both monitors are working fine.
> In some condition mouse can walk both screen, windows cant.
> nouveau driver constantly spam errors in syslog on any window related op
> (only in wayland session).
> multihead is achieved through motherboard firmware - lucid logic
> (something like Nvidia Prime)
>
> ps xorg package is chosen by ubuntu-bug
>
> ProblemType: Bug
> DistroRelease: Ubuntu 23.04
> Package: xorg 1:7.7+23ubuntu2
> ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
> Uname: Linux 6.2.0-27-generic x86_64
> ApportVersion: 2.26.1-0ubuntu2
> Architecture: amd64
> BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
> CasperMD5CheckResult: pass
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Aug 22 13:55:15 2023
> DistUpgraded: 2023-04-24 23:17:01,007 DEBUG Running PostInstallScript:
> '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
> DistroCodename: lunar
> DistroVariant: ubuntu
> DkmsStatus: scap/0.1.1dev+git20220316.e5c53d64, 6.2.0-27-generic,
> x86_64: installed
> ExtraDebuggingInterest: Yes
> GraphicsCard:
>Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family
> Integrated Graphics Controller [1043:844d]
>NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1)
> (prog-if 00 [VGA controller])
> Subsystem: Palit Microsystems Inc. GM204 [GeForce GTX 970] [1569:13c2]
> InstallationDate: Installed on 2023-03-04 (170 days ago)
> InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
> MachineType: System manufacturer System Product Name
> ProcEnviron:
>LANG=ru_RU.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic
> root=UUID=56e62340-8b2d-446b-9b23-437bf49a846b ro quiet splash vt.handoff=7
> SourcePackage: xorg
> Symptom: display
> UpgradeStatus: Upgraded to lunar on 2023-04-24 (119 days ago)
> dmi.bios.date: 01/15/2015
> dmi.bios.release: 4.6
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 3802
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: P8Z68-V PRO GEN3
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: Rev 1.xx
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr3802:bd01/15/2015:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
> dmi.product.family: To be filled by O.E.M.
> dmi.product.name: System Product Name
> dmi.product.sku: SKU
> dmi.product.version: System Version
> dmi.sys.vendor: System manufacturer
> version.compiz: compiz N/A
> version.libdrm2: libdrm2 2.4.114-1
> version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
> version.libgl1-mesa-glx: libgl1-mesa-glx N/A
> version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
> version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20210115-1
> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.17-2build1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032642/+subscriptions
>
>
--
С уважением Пядухов Роман
--
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/2032642
Title:
nouveau :01:00.0: gr: DATA_ERROR 009c [] ch 2 [103fe46000
gnome-shell[1951]] subc 0 class b197 mthd 0d78 data 0004
Status in
