[Kernel-packages] [Bug 1932081] Re: Disable hv-kvp-daemon.service on certain instance types
@xonx I'm not sure is it fixed or not? Cos my instances come up REALLY SLOW (wait for at least 2 min timeout) right now when I run these in KVM instead of Azure $ uname -a Linux localhost 5.15.0-1037-azure #44-Ubuntu SMP Thu Apr 20 13:19:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.15.0-1037-azure root=PARTUUID=f9934843-1ba0-4d04-9cdf-f5e35e434259 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 $ systemctl status hv-kvp-daemon.service ○ hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor preset: enabled) Active: inactive (dead) May 09 01:03:56 localhost systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. May 09 01:03:56 localhost systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Or do I need to change kernel to normal one instead of that Azure abomination? -- 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/1932081 Title: Disable hv-kvp-daemon.service on certain instance types Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] * Disable hv-kvp-daemon.service on certain instance types. As requested for some azure instance types, hv-kvp-daemon is prohibited from starting, and currently it takes a long time to come up and fail. Configure to disable the service on those instances. At the moment, we can key off kernel command line to detect those. [Test Plan] * Boot preview image in azure * Check that hv-kvp-daemon.service is not running [Where problems could occur] * The conditions/detection could have been more specific as to when the daemon is pointless to run. Thus key-off kernel commandline is good enough for now, but may require changes in the future. [Other Info] @ Kernel team, also see https://trello.com/c/JbomiFOe https://lists.ubuntu.com/archives/kernel-team/2021-June/121384.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932081/+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 1975444] Re: mt7921e wifi fails to resume after suspend
Works fine for me on 5.18 But it is pain in the ass to keep mainline kernel working. Hibernation and other systemd integrations don't work. -- 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/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vend
