[Kernel-packages] [Bug 2022318] Re: [SRU] IO gets stuck on 5.19 kernel
** Description changed: [ Impact ] When running fio on a NVME on an AWS test instance with 5.19 kernel, IOs get stuck and fio never ends fio command: sudo fio --name=read_iops_test --filename=/dev/nvme1n1 --filesize=50G --time_based --ramp_time=2s --runtime=1m --ioengine=libaio --direct=1 --verify=0 --randrepeat=0 --bs=16K --iodepth=256 --rw=randread read_iops_test: (g=0): rw=randread, bs=(R) 16.0KiB-16.0KiB, (W) 16.0KiB-16.0KiB, (T) 16.0KiB-16.0KiB, ioengine=libaio, iodepth=256 fio-3.28 Starting 1 process Jobs: 1 (f=0): [/(1)][-.-%][eta 01m:02s] IOs completely get stuck, after a while kernel log shows: Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.230970] INFO: task fio:2545 blocked for more than 120 seconds. Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.232878] Not tainted 5.19.0-43-generic #44~22.04.1-Ubuntu Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.234738] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237053] task:fio state:D stack:0 pid: 2545 ppid: 2495 flags:0x0002 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237057] Call Trace: Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237058] Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237061] __schedule+0x257/0x5d0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237066] schedule+0x68/0x110 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237068] io_schedule+0x46/0x80 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237069] blk_mq_get_tag+0x117/0x300 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237072] ? destroy_sched_domains_rcu+0x40/0x40 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237076] __blk_mq_alloc_requests+0xc4/0x1e0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237079] blk_mq_get_new_requests+0xf6/0x1a0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237080] blk_mq_submit_bio+0x1eb/0x440 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237082] __submit_bio+0x109/0x1a0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237085] submit_bio_noacct_nocheck+0xc2/0x120 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237087] submit_bio_noacct+0x209/0x590 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237088] submit_bio+0x40/0xf0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237090] __blkdev_direct_IO_async+0x146/0x1f0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237092] blkdev_direct_IO.part.0+0x40/0xa0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237093] blkdev_read_iter+0x9f/0x1a0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237094] aio_read+0xec/0x1d0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237097] ? __io_submit_one.constprop.0+0x113/0x200 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237099] __io_submit_one.constprop.0+0x113/0x200 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237100] ? __io_submit_one.constprop.0+0x113/0x200 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237101] io_submit_one+0xe8/0x3d0 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237103] __x64_sys_io_submit+0x84/0x190 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237104] ? do_syscall_64+0x69/0x90 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237106] ? do_syscall_64+0x69/0x90 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237107] do_syscall_64+0x59/0x90 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237108] ? syscall_exit_to_user_mode+0x2a/0x50 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237110] ? do_syscall_64+0x69/0x90 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237111] entry_SYSCALL_64_after_hwframe+0x63/0xcd Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237113] RIP: 0033:0x7f44f351ea3d Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237116] RSP: 002b:7fff1dcfe558 EFLAGS: 0246 ORIG_RAX: 00d1 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237117] RAX: ffda RBX: 7f44f2272b68 RCX: 7f44f351ea3d Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237118] RDX: 56315d9ad828 RSI: 0001 RDI: 7f44f224f000 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237119] RBP: 7f44f224f000 R08: 7f44e943 R09: 02d8 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237120] R10: R11: 0246 R12: 0001 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237120] R13: R14: 56315d9ad828 R15: 56315d9e1830 Jun 1 03:57:52 ip-172-31-39-141 kernel: [ 370.237122] This issue can not be reproduced on 5.15 and 6.2 kernels From call trace, it got stuck more than 120 seconds waiting on previous IOs to complete for freeing some tags, so new IO requests are able to obtain tags But in fact, not all previous IOs got stuck, at least some of previous IOs should have completed, but the waiters were not waken up This issue is
[Kernel-packages] [Bug 2022877] Re: debug in ubuntu_kvm_unit_test timeout with "icebp" related test with J-realtime on openstack AMD64
The same issue still exist with the latest upstream kvm-unit-tests code (02d8befe99f8) Not sure if it's worth it to dig deeper as this is running kvm unit tests inside a VM (on openstack). ** Also affects: linux-realtime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-realtime in Ubuntu. https://bugs.launchpad.net/bugs/2022877 Title: debug in ubuntu_kvm_unit_test timeout with "icebp" related test with J-realtime on openstack AMD64 Status in ubuntu-kernel-tests: New Status in linux-realtime package in Ubuntu: New Bug description: debug test in ubuntu_kvm_unit_test will timeout with J-realtime on openstack amd64 instance. This issue can be seen after we start testing on openstack with 5.15.0-1036.39 in sru-20230320. Test log: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/debug' BUILD_HEAD=d8edb59a timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=tcg -kernel /tmp/tmp.41OPX1wv8j -smp 1 # -initrd /tmp/tmp.iW4XNY1xjR enabling apic smp: waiting for 0 APs PASS: DR4==DR6 with CR4.DE == 0 PASS: DR4 read got #UD with CR4.DE == 1 PASS: #BP PASS: hw breakpoint (test that dr6.BS is not set) PASS: hw breakpoint (test that dr6.BS is not cleared) PASS: Single-step #DB basic test PASS: Usermode Single-step #DB basic test PASS: Single-step #DB on emulated instructions PASS: Usermode Single-step #DB on emulated instructions PASS: Single-step #DB w/ STI blocking PASS: Usermode Single-step #DB w/ STI blocking PASS: Single-step #DB w/ MOVSS blocking PASS: Usermode Single-step #DB w/ MOVSS blocking qemu-system-x86_64: terminating on signal 15 from pid 9487 (timeout) FAIL debug (timeout; duration=90s) I tried to bump the timeout to 240s but it's not helping, and there is no output from dmesg when running this test. It's worthy to note that this test has passed with j/ibm, the whole test sequence should be like this: DR4==DR6 with CR4.DE == 0 DR4 read got #UD with CR4.DE == 1 #BP hw breakpoint (test that dr6.BS is not set) hw breakpoint (test that dr6.BS is not cleared) Single-step #DB basic test Usermode Single-step #DB basic test Single-step #DB on emulated instructions Usermode Single-step #DB on emulated instructions Single-step #DB w/ STI blocking Usermode Single-step #DB w/ STI blocking Single-step #DB w/ MOVSS blocking Usermode Single-step #DB w/ MOVSS blocking Single-Step + ICEBP #DB w/ MOVSS blocking Usermode Single-Step + ICEBP #DB w/ MOVSS blocking Single-step #DB w/ MOVSS blocking and DR7.GD=1 hw watchpoint (test that dr6.BS is not cleared) hw watchpoint (test that dr6.BS is not set) icebp MOV SS + watchpoint + ICEBP MOV SS + watchpoint + int $1 MOV SS + watchpoint + INT3 It's the "icebp" related tests causing this timeout. If we comment out these 3 tests from kvm-unit-tests/x86/debug.c: Usermode Single-Step + ICEBP #DB w/ MOVSS blocking icebp MOV SS + watchpoint + ICEBP The debug test can finish with one failure: PASS: DR4==DR6 with CR4.DE == 0 PASS: DR4 read got #UD with CR4.DE == 1 PASS: #BP PASS: hw breakpoint (test that dr6.BS is not set) PASS: hw breakpoint (test that dr6.BS is not cleared) PASS: Single-step #DB basic test PASS: Usermode Single-step #DB basic test PASS: Single-step #DB on emulated instructions PASS: Usermode Single-step #DB on emulated instructions PASS: Single-step #DB w/ STI blocking PASS: Usermode Single-step #DB w/ STI blocking PASS: Single-step #DB w/ MOVSS blocking PASS: Usermode Single-step #DB w/ MOVSS blocking FAIL: Single-step #DB w/ MOVSS blocking and DR7.GD=1 PASS: hw watchpoint (test that dr6.BS is not cleared) PASS: hw watchpoint (test that dr6.BS is not set) PASS: MOV SS + watchpoint + int $1 PASS: MOV SS + watchpoint + INT3 SUMMARY: 18 tests, 1 unexpected failures FAIL debug (18 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2022877/+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 2022826] Re: Ethernet hangs
@John, what did you do to make the ehternet unavailable? upgrade/install some pacakages? thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+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 2015228] Re: Dell Inspiron 7577 Bluetooth not working rfkill Soft blocked: yes
[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/2015228 Title: Dell Inspiron 7577 Bluetooth not working rfkill Soft blocked: yes Status in linux package in Ubuntu: Expired Bug description: Hi Devs, Hope you're all keeping well. The problem I have is similar to: https://answers.launchpad.net/ubuntu/+question/699306 Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither the laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB dongle (not sure it was recommended for raspberry pi and works on desktop with 22.04 just fine: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). It works fine in a live USB image on the same laptop. I get the following with rfkill: rfkill list all 1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: yes Hard blocked: no - Unblocking with rfkill doesn't work - Restarting bluetooth doesn't work - Getting another device doesn't work I recall having issues with WiFi around the time I got the laptop, and recall changing settings for that - but I couldn't tell you what they were (~2017 ish). Plus I believe I've reinstalled since then due to an SSD failure. It has been upgraded from LTS to LTS since 18.04 though. Any thoughts, ideas, or questions, I'm more than happy to try anything, or even help as much as possible to help get this resolved, its been going on for a couple of years now and mainly ignored it because I was mostly fine without, but I really need it to work now and appreciate any help on this. Thanks so much in advance, love you all for the work you do. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 4 12:47:27 2023 InstallationDate: Installed on 2020-04-09 (1089 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7577 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=761c1e7a-7759-4f7d-a985-33c7654bccad ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2023-01-12 (82 days ago) dmi.bios.date: 03/18/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0XCNGT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd03/18/2022:br1.17:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0XCNGT:rvrA00:cvnDellInc.:ct10:cvr:sku07FA: dmi.product.family: Inspiron dmi.product.name: Inspiron 7577 dmi.product.sku: 07FA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015228/+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 2022872] Re: package linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-470-server-5.19.0-43-gene
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2022872 Title: package linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 failed to install/upgrade: installed linux- modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: New Bug description: Can,t install Nvidia proprietary driver. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 5 09:03:51 2023 DuplicateSignature: package:linux-modules-nvidia-470-server-5.19.0-43-generic:5.19.0-43.44~22.04.1+1 Setting up linux-modules-nvidia-470-server-5.19.0-43-generic (5.19.0-43.44~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-470-server-5.19.0-43-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-530-open-generic-hwe-22.04: not found dpkg: error processing package linux-modules-nvidia-470-server-5.19.0-43-generic (--configure): installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-06-04 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2022872/+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 2022872] [NEW] package linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-470-server-5.19.0-43-ge
Public bug reported: Can,t install Nvidia proprietary driver. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 5 09:03:51 2023 DuplicateSignature: package:linux-modules-nvidia-470-server-5.19.0-43-generic:5.19.0-43.44~22.04.1+1 Setting up linux-modules-nvidia-470-server-5.19.0-43-generic (5.19.0-43.44~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-470-server-5.19.0-43-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-530-open-generic-hwe-22.04: not found dpkg: error processing package linux-modules-nvidia-470-server-5.19.0-43-generic (--configure): installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-06-04 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2022872 Title: package linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 failed to install/upgrade: installed linux- modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: New Bug description: Can,t install Nvidia proprietary driver. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 5 09:03:51 2023 DuplicateSignature: package:linux-modules-nvidia-470-server-5.19.0-43-generic:5.19.0-43.44~22.04.1+1 Setting up linux-modules-nvidia-470-server-5.19.0-43-generic (5.19.0-43.44~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-470-server-5.19.0-43-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-530-open-generic-hwe-22.04: not found dpkg: error processing package linux-modules-nvidia-470-server-5.19.0-43-generic (--configure): installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-06-04 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-470-server-5.19.0-43-generic 5.19.0-43.44~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-470-server-5.19.0-43-generic package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2022872/+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 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169
SRUed for lunar, https://lists.ubuntu.com/archives/kernel-team/2023-June/140005.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Fix only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Triaged Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.13 source package in Lunar: Invalid Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 1950627] Re: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/443985 -- 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/1950627 Title: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: This is from ADT testing (amd64) but I believe I occasionally saw this before. It feels like sometimes the receiver does not get ready before the transmission starts. IIRC this goes away when re-trying. 02:52:31 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh 02:52:31 DEBUG| [stdout] # IPv4 02:52:31 DEBUG| [stdout] # No GRO ok 02:52:32 DEBUG| [stdout] # GRO frag listok 02:52:32 DEBUG| [stdout] # GRO fwd ok 02:52:33 DEBUG| [stdout] # UDP fwd perfudp rx: 333 MB/s 271894 calls/s 02:52:33 DEBUG| [stdout] # udp tx:378 MB/s 6422 calls/s 6422 msg/s 02:52:34 DEBUG| [stdout] # udp rx:383 MB/s 312480 calls/s 02:52:34 DEBUG| [stdout] # udp tx:383 MB/s 6506 calls/s 6506 msg/s 02:52:35 DEBUG| [stdout] # udp rx:381 MB/s 310202 calls/s 02:52:35 DEBUG| [stdout] # udp tx:380 MB/s 6458 calls/s 6458 msg/s 02:52:36 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 344 MB/s 280814 calls/s 02:52:36 DEBUG| [stdout] # udp tx:389 MB/s 6612 calls/s 6612 msg/s 02:52:37 DEBUG| [stdout] # udp rx:364 MB/s 297088 calls/s 02:52:37 DEBUG| [stdout] # udp tx:383 MB/s 6512 calls/s 6512 msg/s 02:52:38 DEBUG| [stdout] # udp rx:448 MB/s 365435 calls/s 02:52:38 DEBUG| [stdout] # udp tx:453 MB/s 7686 calls/s 7686 msg/s 02:52:39 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:39 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:39 DEBUG| [stdout] # UDP tunnel fwd perf ./udpgso_bench_tx: sendmsg: Connection refused 02:52:39 DEBUG| [stdout] # fail client exit code 1, server 0 02:52:40 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 236 MB/s 192389 calls/s 02:52:41 DEBUG| [stdout] # udp tx:284 MB/s 4826 calls/s 4826 msg/s 02:52:41 DEBUG| [stdout] # udp rx:295 MB/s 240586 calls/s 02:52:42 DEBUG| [stdout] # udp tx:306 MB/s 5206 calls/s 5206 msg/s 02:52:42 DEBUG| [stdout] # udp rx:306 MB/s 249784 calls/s 02:52:43 DEBUG| [stdout] # udp tx:310 MB/s 5263 calls/s 5263 msg/s 02:52:43 DEBUG| [stdout] # IPv6 02:52:43 DEBUG| [stdout] # No GRO ok 02:52:43 DEBUG| [stdout] # GRO frag listok 02:52:43 DEBUG| [stdout] # GRO fwd ok 02:52:44 DEBUG| [stdout] # UDP fwd perfudp rx: 82 MB/s66844 calls/s 02:52:45 DEBUG| [stdout] # udp tx:334 MB/s 5668 calls/s 5668 msg/s 02:52:45 DEBUG| [stdout] # udp rx:374 MB/s 305206 calls/s 02:52:46 DEBUG| [stdout] # udp tx:375 MB/s 6377 calls/s 6377 msg/s 02:52:46 DEBUG| [stdout] # udp rx:373 MB/s 303948 calls/s 02:52:47 DEBUG| [stdout] # udp tx:371 MB/s 6299 calls/s 6299 msg/s 02:52:48 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 340 MB/s 277046 calls/s 02:52:48 DEBUG| [stdout] # udp tx:389 MB/s 6601 calls/s 6601 msg/s 02:52:49 DEBUG| [stdout] # udp rx:390 MB/s 318311 calls/s 02:52:49 DEBUG| [stdout] # udp tx:391 MB/s 6639 calls/s 6639 msg/s 02:52:50 DEBUG| [stdout] # udp rx:396 MB/s 322528 calls/s 02:52:50 DEBUG| [stdout] # udp tx:406 MB/s 6891 calls/s 6891 msg/s 02:52:50 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:50 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:52 DEBUG| [stdout] # UDP tunnel fwd perf udp rx: 93 MB/s76354 calls/s 02:52:52 DEBUG| [stdout] # udp tx:257 MB/s 4360 calls/s 4360 msg/s 02:52:53 DEBUG| [stdout] # udp rx:297 MB/s 241883 calls/s 02:52:53 DEBUG| [stdout] # udp tx:315 MB/s 5352 calls/s 5352 msg/s 02:52:54 DEBUG| [stdout] # udp rx:286 MB/s 233207 calls/s 02:52:54 DEBUG| [stdout] # udp tx:304 MB/s 5172 calls/s 5172 msg/s 02:52:55 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 267 MB/s 217607 calls/s 02:52:55 DEBUG| [stdout] # udp tx:297 MB/s 5039 calls/s 5039 msg/s 02:52:56 DEBUG| [stdout] # udp rx:300 MB/s 244255 calls/s 02:52:56 DEBUG| [stdout] # udp tx:304 MB/s
[Kernel-packages] [Bug 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169
** Summary changed: - Can only reach PC3 when ethernet is plugged r8169 + Fix only reach PC3 when ethernet is plugged r8169 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Fix only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Triaged Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.13 source package in Lunar: Invalid Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 1874241] Re: iwlwifi intel ax201 crashing on intel nuc10i7fnh
activity. still an issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1874241 Title: iwlwifi intel ax201 crashing on intel nuc10i7fnh Status in linux-firmware package in Ubuntu: Expired Bug description: The intel iwlwifi firmware will crash when you insert a device into the thunderbolt3 port, and this will be trigger probabilistically. wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 Linux-firmware version: 1.187 thunderbolt3 chip model: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) dmesg output: [ 103.777908] pcieport :00:1c.0: PME: Spurious native interrupt! [ 103.777918] pcieport :00:1c.0: PME: Spurious native interrupt! [ 104.118148] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 104.147184] usb 4-1: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32 [ 104.147190] usb 4-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ 104.147194] usb 4-1: Product: USB3.0 Card Reader [ 104.147197] usb 4-1: Manufacturer: Generic [ 104.147199] usb 4-1: SerialNumber: 1532 [ 104.183374] usb-storage 4-1:1.0: USB Mass Storage device detected [ 104.183952] scsi host3: usb-storage 4-1:1.0 [ 104.184172] usbcore: registered new interface driver usb-storage [ 104.187897] usbcore: registered new interface driver uas [ 105.217035] scsi 3:0:0:0: Direct-Access Generic STORAGE DEVICE 1532 PQ: 0 ANSI: 6 [ 105.217792] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 105.233978] sd 3:0:0:0: [sdb] Attached SCSI removable disk [ 109.998995] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 109.999102] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999111] iwlwifi :00:14.3: Status: 0x0040, count: 6 [ 109.999119] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0 [ 109.999128] iwlwifi :00:14.3: 0x4435 | ADVANCED_SYSASSERT [ 109.999135] iwlwifi :00:14.3: 0x008026F4 | trm_hw_status0 [ 109.999142] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 109.999148] iwlwifi :00:14.3: 0x004CA228 | branchlink2 [ 109.999154] iwlwifi :00:14.3: 0x0E26 | interruptlink1 [ 109.999161] iwlwifi :00:14.3: 0x0E26 | interruptlink2 [ 109.999168] iwlwifi :00:14.3: 0x000161A0 | data1 [ 109.999174] iwlwifi :00:14.3: 0xDEADBEEF | data2 [ 109.999180] iwlwifi :00:14.3: 0xDEADBEEF | data3 [ 109.999186] iwlwifi :00:14.3: 0xF90167B5 | beacon time [ 109.999192] iwlwifi :00:14.3: 0x51938809 | tsf low [ 109.999199] iwlwifi :00:14.3: 0x0010 | tsf hi [ 109.999205] iwlwifi :00:14.3: 0x | time gp1 [ 109.999211] iwlwifi :00:14.3: 0x064A1430 | time gp2 [ 109.999217] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 109.999224] iwlwifi :00:14.3: 0x0030 | uCode version major [ 109.999231] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor [ 109.999239] iwlwifi :00:14.3: 0x0351 | hw version [ 109.999245] iwlwifi :00:14.3: 0x00C89004 | board version [ 109.999252] iwlwifi :00:14.3: 0x069E001C | hcmd [ 109.999259] iwlwifi :00:14.3: 0x8002 | isr0 [ 109.999265] iwlwifi :00:14.3: 0x0100 | isr1 [ 109.999271] iwlwifi :00:14.3: 0x08F2 | isr2 [ 109.999278] iwlwifi :00:14.3: 0x04C1FFCC | isr3 [ 109.999284] iwlwifi :00:14.3: 0x | isr4 [ 109.999290] iwlwifi :00:14.3: 0x069D001C | last cmd Id [ 109.999297] iwlwifi :00:14.3: 0x8B70 | wait_event [ 109.999304] iwlwifi :00:14.3: 0x4208 | l2p_control [ 109.999310] iwlwifi :00:14.3: 0x2020 | l2p_duration [ 109.999317] iwlwifi :00:14.3: 0x033F | l2p_mhvalid [ 109.999324] iwlwifi :00:14.3: 0x00E6 | l2p_addr_match [ 109.999331] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [ 109.999337] iwlwifi :00:14.3: 0x | timestamp [ 109.999344] iwlwifi :00:14.3: 0xB8DC | flow_handler [ 109.999391] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999398] iwlwifi :00:14.3: Status: 0x0040, count: 7 [ 109.999406] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [ 109.999413] iwlwifi :00:14.3: 0x | umac branchlink1 [ 109.999420] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2 [ 109.999427] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink1 [ 109.999434] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink2 [ 109.999441] iwlwifi :00:14.3: 0x0400 | umac data1 [ 109.999447] iwlwifi :00:14.3: 0x8048DBD2 | umac data2 [ 109.999454] iwlwifi :00:14.3: 0x | umac data3 [ 109.999461] iwlwifi :00:14.3: 0x0030 | umac major [
[Kernel-packages] [Bug 2022868] [NEW] 104 failures reported in test_verifier from ubuntu_bpf with J-realtime openstack arm64
Public bug reported: This is not a regression, this issue can be seen after we start testing on openstack with 5.15.0-1036.39 in sru-20230320, we just need a new bug to record different failures reported there. There are 104 failures reported in this test_verifier tests with J/realtime openstack arm64. Failed cases as follows: #21/u BPF_ATOMIC_AND without fetch FAIL Failed to load prog 'Unknown error 524'! verification time 53 usec stack depth 8 processed 12 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #21/p BPF_ATOMIC_AND without fetch FAIL Failed to load prog 'Unknown error 524'! verification time 41 usec stack depth 8 processed 10 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #22/u BPF_ATOMIC_AND with fetch FAIL Failed to load prog 'Unknown error 524'! verification time 56 usec stack depth 8 processed 16 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #22/p BPF_ATOMIC_AND with fetch FAIL Failed to load prog 'Unknown error 524'! verification time 47 usec stack depth 8 processed 14 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #23/u BPF_ATOMIC_AND with fetch 32bit FAIL Failed to load prog 'Unknown error 524'! verification time 72 usec stack depth 4 processed 14 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #23/p BPF_ATOMIC_AND with fetch 32bit FAIL Failed to load prog 'Unknown error 524'! verification time 63 usec stack depth 4 processed 14 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL Failed to load prog 'Unknown error 524'! verification time 47 usec stack depth 8 processed 12 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL Failed to load prog 'Unknown error 524'! verification time 40 usec stack depth 8 processed 12 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL Failed to load prog 'Unknown error 524'! verification time 33 usec stack depth 8 processed 6 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #26/u atomic compare-and-exchange smoketest - 64bit FAIL Failed to load prog 'Unknown error 524'! verification time 94 usec stack depth 8 processed 23 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #26/p atomic compare-and-exchange smoketest - 64bit FAIL Failed to load prog 'Unknown error 524'! verification time 61 usec stack depth 8 processed 23 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #27/u atomic compare-and-exchange smoketest - 32bit FAIL Unexpected verifier log! EXP: R0 leaks addr into mem RES: FAIL Unexpected error message! EXP: R0 leaks addr into mem RES: verification time 109 usec stack depth 4 processed 23 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 verification time 109 usec stack depth 4 processed 23 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #27/p atomic compare-and-exchange smoketest - 32bit FAIL Failed to load prog 'Unknown error 524'! verification time 288 usec stack depth 4 processed 23 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #30/u BPF_W cmpxchg should zero top 32 bits FAIL Unexpected verifier log! EXP: R0 leaks addr into mem RES: FAIL Unexpected error message! EXP: R0 leaks addr into mem RES: verification time 66 usec stack depth 8 processed 13 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0 verification time 66 usec stack depth 8 processed 13 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0 #30/p BPF_W cmpxchg should zero top 32 bits FAIL Failed to load prog 'Unknown error 524'! verification time 173 usec stack depth 8 processed 13 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0 #31/p Dest pointer in r0 - succeed, check 2 FAIL Failed to load prog 'Unknown error 524'! verification time 28 usec stack depth 8 processed 7 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #33/p Dest pointer in r0 - succeed, check 4 FAIL Failed to load prog 'Unknown error 524'! verification time 56 usec stack depth 8 processed 7 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL Failed to load prog 'Unknown error 524'! verification time 55 usec stack depth 8 processed 12 insns (limit 100) max_states_per_insn 0
[Kernel-packages] [Bug 2022867] [NEW] 67 failures reported in test_verifier from ubuntu_bpf with J-realtime openstack amd64
Public bug reported: This is not a regression, this issue can be seen after we start testing on openstack with 5.15.0-1036.39 in sru-20230320, we just need a new bug to record different failures reported there. There are 67 failures reported in this test_verifier tests with J/realtime openstack amd64. Failed cases as follows: #27/u atomic compare-and-exchange smoketest - 32bit FAIL Unexpected success to load! verification time 59 usec stack depth 4 processed 23 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #30/u BPF_W cmpxchg should zero top 32 bits FAIL Unexpected success to load! verification time 32 usec stack depth 8 processed 13 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0 #143/p bpf_get_stack return R0 within range FAIL Failed to load prog 'Invalid argument'! trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL Unexpected verifier log! EXP: arg#0 pointer type STRUCT prog_test_ref_kfunc must point RES: FAIL Unexpected error message! EXP: arg#0 pointer type STRUCT prog_test_ref_kfunc must point RES: kernel btf_id 0 is not a function verification time 17 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 kernel btf_id 0 is not a function verification time 17 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #511/p helper access to variable memory: map, JMP, correct bounds FAIL Failed to load prog 'Invalid argument'! trace type programs can only use preallocated hash map verification time 9 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #512/p helper access to variable memory: map, JMP, wrong max FAIL Unexpected verifier log! EXP: invalid access to map value, value_size=48 off=0 size=49 RES: FAIL Unexpected error message! EXP: invalid access to map value, value_size=48 off=0 size=49 RES: trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #513/p helper access to variable memory: map adjusted, JMP, correct bounds FAIL Failed to load prog 'Invalid argument'! trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #514/p helper access to variable memory: map adjusted, JMP, wrong max FAIL Unexpected verifier log! EXP: R1 min value is outside of the allowed memory range RES: FAIL Unexpected error message! EXP: R1 min value is outside of the allowed memory range RES: trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #525/p helper access to variable memory: size = 0 allowed on != NULL map pointer (!ARG_PTR_TO_MEM_OR_NULL) FAIL Failed to load prog 'Invalid argument'! trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #526/p helper access to variable memory: size possible = 0 allowed on != NULL stack pointer (!ARG_PTR_TO_MEM_OR_NULL) FAIL Failed to load prog 'Invalid argument'! trace type programs can only use preallocated hash map verification time 6 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #527/p helper access to variable memory: size possible = 0 allowed on != NULL map pointer (!ARG_PTR_TO_MEM_OR_NULL) FAIL Failed to load prog 'Invalid argument'! trace type programs can only use preallocated hash map verification time 7 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #551/p helper access to map: full range FAIL Failed to load prog 'Invalid argument'! trace type programs can only use preallocated hash map verification time 6 usec stack depth 0 processed 0 insns (limit 100) max_states_per_insn 0
[Kernel-packages] [Bug 2019076] Re: Raptor Lake S/P Audio Enablement
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2019076 Title: Raptor Lake S/P Audio Enablement Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Summary] Support audio on Raptor Lake S/P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2019076/+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 2001567] Re: Add support for newer I219-LM NICs to the 5.4.0 kernel
This NIC is supported by the 5.4.0 Focal LTS kernel, however, any changes on the switch side or even disconnecting and connecting the Ethernet cable causes the card to hang: Jun 03 18:32:58 kvm-02 kernel: e1000e :00:1f.6 eno1: Detected Hardware Unit Hang: TDH TDT next_to_use next_to_clean buffer_info[next_to_clean]: time_stamp <11e83da17> next_to_watch jiffies <11e83ddb8> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> I tried adding pcie_aspm=off to kernel boot parameters, however that does not seem to change anything. I have two Dell Optiplex 3080 Micro machines and both are experiencing this issue: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (11) I219-LM DeviceName: Onboard - Ethernet Subsystem: Dell Ethernet Connection (11) I219-LM Flags: bus master, fast devsel, latency 0, IRQ 124 Memory at 9120 (32-bit, non-prefetchable) [size=128K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: e1000e Kernel modules: e1000e My older machines do not have this issue: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-LM Subsystem: Dell Ethernet Connection (5) I219-LM Flags: bus master, fast devsel, latency 0, IRQ 125 Memory at f710 (32-bit, non-prefetchable) [size=128K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] PCI Advanced Features Kernel driver in use: e1000e Kernel modules: e1000e -- 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/2001567 Title: Add support for newer I219-LM NICs to the 5.4.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: Some newer Dell systems (I experienced this on an Optiplex 7000) include an Intel I219-LM NIC that is not supported by the 5.4.0 kernel. Later versions of the HWE kernel do support this NIC. That makes it impossible to use these systems with the FIPS kernel. Since our imaging environment does not have FIPS mode enabled, we need support for this NIC when used both with and without FIPS mode. Please backport the latest stable e1000e driver to both the 5.4.0 non- FIPS kernel & the 5.4.0 FIPS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001567/+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 2022860] Re: My trackpad is not working. It was working when installed but when I restarted my pc, it stoped working
** Package changed: ubuntu => linux-signed-hwe-5.19 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2022860 Title: My trackpad is not working. It was working when installed but when I restarted my pc, it stoped working Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: My trackpad is not working. It was working when installed but when I restarted my pc, it stoped working ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 22:16:10 2023 InstallationDate: Installed on 2023-06-04 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 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-5.19/+bug/2022860/+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 2022826] Re: Ethernet hangs
I bought the computer just under a year ago: it's an Asus (barebones) mini PN50-1 with a Ryzen 7 4700-U CPU. So it's always been using 22.04. I transferred the memory and SSD from my previous old computer. I think that I previously said that this computer was working on both Ethernet & Wi-Fi until about 2 weeks ago. Interestingly my wife's computer (an old Pentium laptop) is still Ok: it runs on 22.04 and had been upgraded Ok from 20.04 and previous LTS versions). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+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 2022826] Re: Ethernet hangs
@John, before 22.04(5.19 kernel), have you ever get the Ethernet connection with 20.04 or other released version? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+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 2021749] Re: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
Fixes have been posted for review for both Jammy and Focal. ** Description changed: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] - Same functionality and testing as on BlueField-1/2/2. No functionality change. - Add negative tests: + Same functionality and testing as on BlueField-1/2/3. No functionality change. + Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+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 1834085]
New error messages when communication is lost with Magic Trackpad: I booted Ubuntu 23.04(kernel 6.2.0) from a flash drive - the same error: https://pastebin.com/5KtUjCHQ I booted from Fedor's(kernel 6.2.9) flash drive - error: https://pastebin.com/4LJC7NJQ When using Fedora, communication breaks also occur. -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev:
[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2
Asus N46VM with nvidia GT 630M here. I can confirm too, the package nvidia-driver-390 version 390.157-0ubuntu5.23.04.1 does not fix anything on my Ubuntu 23.04 (Kernel 6.2.0-20). Same with @bojan023, after installing the package and rebooting, I'm left with black screen just after the boot logo is shown. I had to revert back to using nouveau to be able to log to GUI. -- 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/2019869 Title: nvidia-dkms-390: better support for kernel 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-390 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Bug description: [Impact] Instead of disabling acpi support completely with nvidia-dkms-390, we should try instead to see if it's possible to support it somehow. [Fix] This patch looks promising (even if it says huge hack in the comments...): https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch Apply this patch and drop any 6.0 and 6.2 related patches. [Regression potential] With this patch nvidia-dkms-390 should build against 6.2 kernels without disabling any feature, but users of this driver may experience kernel bugs / crashes. However, the nvidia 390 driver is unmaintained so we should start to consider phasing it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+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 2008774] Re: Ubuntu 22.04 not waking up after second suspend
I was also hit by this issue on a `HP ProBook 635 Aero G7 (2E9E4EA)` with a `AMD Ryzen 7 4700U with Radeon Graphics`. I found (by experiments) a different solution: Calling (as root) `/lib/systemd/systemd-sleep suspend` makes the wake up from suspend to work every time (not only the first time). This has the drawback that the screen is not locked. Then I did the following (with a passwordless sudo rule for `/lib/systemd/systemd-sleep`): ~~~ /usr/bin/xdg-screensaver lock; sudo /lib/systemd/systemd-sleep suspend ~~~ In this configuration, I had back the old buggy behaviour (2nd suspend does not wake up). I switched now to ~~~ sudo /lib/systemd/systemd-sleep suspend; /usr/bin/xdg-screensaver lock ~~~ and this works reliably. Unfortunately, there is a short moment where the plain screen content is visible after wake up, but the screen is locked almost immediately. So this is hacky, but **far more** better than before, as I can now use suspend and hibernate :-) * If the laptop is stolen suspended, the attacker has less than half a second to see what is on the screen, then it is locked * If the laptop is stolen hibernated, the attacker needs the disk encryption password before the machine really boots. Maybe this weird setup helps in debugging. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 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-5.19/+bug/2008774/+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
