[Kernel-packages] [Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91
[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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91 Status in linux package in Ubuntu: Expired Bug description: My home server/router/access point runs under Ubuntu 18.04.4 with all updates and has 2 wifi adapters operated by hostapd one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 9260 (8086:2526, driver iwlwifi). with kernel 4.15.0-88 it worked quite stable, with reboots required mostly after kernel upgrades (much less frequent reboots due to panics) with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a lot of activity happening via Intel 9260. In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and kernel.panic_on_oops=1 overrides of default values. In dmesg logs preceding the reboot, I see multiple warnings with stacks inside iwl_mvm functions which I could provide by apport. Also, multiple messages like "Command LQ_CMD: a command is already active!" or "Error sending LQ_CMD: time out after 2000ms" Unfortunately I run this box headless and I don't have another wired Ethernet host to capture its panics by netconsole The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, nothing overly special. More details I would provide in your further requests but the current kernel behavior is very annoying. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e InstallationDate: Installed on 2009-11-01 (3810 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: ASUS All Series Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 loop.max_part=63 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-96-generic x86_64 UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago) UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src _MarkForUpload: True dmi.bios.date: 07/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+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 1884249] Re: external USB mouse not working
[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/1884249 Title: external USB mouse not working Status in linux package in Ubuntu: Expired Bug description: Thank you for all your great work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 14:23:49 2020 DistUpgraded: 2020-06-13 18:17:13,228 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] InstallationDate: Installed on 2020-06-11 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 002: ID 054c:09c2 Sony Corp. Storage Media Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=28f01aa6-e9ec-4b55-9f9b-b0cd3af72963 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-06-13 (5 days ago) dmi.bios.date: 07/17/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 0XPYYD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd07/17/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0XPYYD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jun 13 14:12:08 2020 xserver.configfile: default xserver.errors: AIGLX error: Calling driver entry point failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5595 vendor CMN xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884249/+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 1879489] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] After updating to the kernel 4.15.0-101-generic dmessg contains an error message
[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/1879489 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] After updating to the kernel 4.15.0-101-generic dmessg contains an error message Status in linux package in Ubuntu: Expired Bug description: System:Kernel: 4.15.0-101-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Dell product: Inspiron 13-5378 Network: Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel port: f040 bus ID: 01:00.0 chip ID: 168c:003e IF: wlp1s0 state: up mac: Device-2: Atheros type: USB driver: btusb bus ID: 1-6:3 chip ID: 0cf3:e007 [ 2046.326644] WARNING: CPU: 1 PID: 16 at /build/linux-sgQT9w/linux-4.15.0/net/core/dev.c:5675 net_rx_action+0x2cb/0x3a0 [ 2046.326647] Modules linked in: ccm rfcomm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp dell_laptop snd_soc_sst_ipc dell_smm_hwmon snd_soc_acpi snd_soc_core snd_hda_codec_generic snd_compress ac97_bus btusb snd_pcm_dmaengine btrtl btbcm btintel snd_hda_intel bluetooth snd_hda_codec snd_hda_core ecdh_generic snd_hwdep hid_multitouch intel_rapl snd_pcm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel nls_iso8859_1 kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event ath10k_pci ath10k_core snd_rawmidi aesni_intel ath aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq mac80211 snd_seq_device snd_timer [ 2046.326696] cfg80211 dell_wmi dell_smbios dcdbas joydev input_leds dell_wmi_descriptor wmi_bmof serio_raw snd soundcore shpchp mei_me idma64 virt_dma mei intel_lpss_pci intel_lpss hid_sensor_rotation hid_sensor_incl_3d hid_sensor_magn_3d hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio intel_pch_thermal nf_log_ipv6 processor_thermal_device intel_soc_dts_iosf xt_hl ip6t_rt intel_vbtn int3403_thermal soc_button_array intel_hid sparse_keymap nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT int3402_thermal nf_reject_ipv6 int340x_thermal_zone nf_log_ipv4 nf_log_common xt_LOG acpi_pad xt_limit int3400_thermal acpi_thermal_rel mac_hid xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 [ 2046.326735] ip6table_filter ip6_tables sch_fq_codel nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat parport_pc nf_conntrack_ftp nf_conntrack libcrc32c ppdev iptable_filter lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic usbhid psmouse i915 i2c_algo_bit drm_kms_helper ahci syscopyarea sysfillrect libahci sysimgblt fb_sys_fops intel_ish_ipc intel_ishtp drm i2c_hid wmi hid video pinctrl_sunrisepoint [ 2046.326773] CPU: 1 PID: 16 Comm: ksoftirqd/1 Tainted: G O 4.15.0-101-generic #102-Ubuntu [ 2046.326775] Hardware name: Dell Inc. Inspiron 13-5378/05C3PP, BIOS 1.21.1 08/25/2017 [ 2046.326782] RIP: 0010:net_rx_action+0x2cb/0x3a0 [ 2046.326784] RSP: 0018:b6c781977de8 EFLAGS: 00010297 [ 2046.326787] RAX: 0044 RBX: 0040 RCX: 8d867a621e68 [ 2046.326789] RDX: 8d837f806000 RSI: fe01 RDI: c0c3b820 [ 2046.326791] RBP: b6c781977e58 R08: 0002 R09: [ 2046.326793] R10: 26b4 R11: 0001 R12: [ 2046.326794] R13: R14: 0003 R15: 8d867a627b60 [ 2046.326797] FS: () GS:8d869048() knlGS: [ 2046.326799] CS: 0010 DS: ES: CR0: 80050033 [ 2046.326802] CR2: 0e6fcca63008 CR3: 00034ae0a001 CR4: 003606e0 [ 2046.326803] Call Trace: [ 2046.326812] ? __switch_to_asm+0x41/0x70 [ 2046.326819] __do_softirq+0xe4/0x2d4 [ 2046.326826] run_ksoftirqd+0x22/0x60 [ 2046.326832] smpboot_thread_fn+0xfc/0x170 [ 2046.326836] kthread+0x121/0x140 [ 2046.326840] ? sort_range+0x30/0x30 [ 2046.326844] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2046.326849] ret_from_fork+0x35/0x40 [ 2046.326851] Code: 24 08 49 83 c4 18 89 d9 44 89 f2 4c 89 fe e8 bd 1f 39 00 4d 8b 14 24 4d 85 d2 75 e1 4c 8b 65 90 44 89 f0 39 c3 0f 8d 85 fe ff ff <0f> 0b 39 c3 0f 8f 83 fe ff
[Kernel-packages] [Bug 1884547] Re: can't activate the bluethooth headsed with a2dp sound
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1884547 Title: can't activate the bluethooth headsed with a2dp sound Status in bluez package in Ubuntu: Expired Bug description: I follow this bug, and still happend https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug/e91ee546 -b48f-11ea-a86b-68b5996a96c8 dpkg --status bluez | grep '^Version:' Version: 5.53-0ubuntu3 cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 22 10:54:05 2020 InstallationDate: Installed on 2020-05-19 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20NYS04V00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET87W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS04V00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET87W(1.65):bd03/27/2020:svnLENOVO:pn20NYS04V00:pvrThinkPadT490s:rvnLENOVO:rn20NYS04V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS04V00 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:ED:33:30:BC:12 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:2532201 acl:38232 sco:36899 events:9437 errors:0 TX bytes:4236888 acl:2223 sco:36783 commands:6938 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2020-06-10T09:52:46.145873 mtime.conffile..etc.bluetooth.main.conf: 2020-06-04T16:03:04.084396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1884547/+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 1892347] Re: HiSilicon HNS3 ethernet broken
pls refer to this follow link issue: https://bugs.launchpad.net/kunpeng920/+bug/1859756 -- 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/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to V
[Kernel-packages] [Bug 1891585] Re: alsa/sof: support 1 and 3 dmics
Installed the linux-firmware 1.187.3, and check the /lib/firmware/intel /sof-tplg, the -1ch.tplg and -3ch.tplg are there. -- 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/1891585 Title: alsa/sof: support 1 and 3 dmics Status in HWE Next: Triaged Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Status in linux-firmware source package in Groovy: Fix Released Bug description: This is for linux-firmware: [Impact] On a Dell tigerlake laptop, the sof driver fails to detect the dmic, it alwasys report 0 dmics on the machine. So users doesn't have internal mic to use. [Fix] Intel provides 2 new topology files to us, they could support 1 dmic and 3 dmics. [Test Case] Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in the linux-firmware, the sof driver could detect the dmic and users have a workable internal mic after booting up. [Regression Risk] This is adding 2 new topology files, not changing anything on current sof-firmware, so the regression posibility is very low. This is for linux kernel: [Impact] On a Dell tigerlake laptop, the sof driver fails to detect the dmic, it alwasys report 0 dmics on the machine. So users doesn't have internal mic to use. [Fix] Intel write a patch to fix this issue, if NHLT table returns 1 or 3 dmics, the sof driver will not fail like before, it can support 1 or 3 dmics after applying this patch. [Test Case] Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in the linux-firmware, the sof driver could detect the dmic and users have a workable internal mic after booting up. [Regression Risk] This patch adds new support for 1 and 3 dmics, it doesn't change anything on existing functions, so the regression posibility is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1891585/+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 1892520] Re: Cannot sent h2c command
Hopefully helpful: [ 45.069078] NVRM: API mismatch: the client has the version 440.95.01, but NVRM: this kernel module has the version 440.100. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. Thanks ** Information type changed from Private Security to Public ** Package changed: linux (Ubuntu) => ubuntu -- 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/1892520 Title: Cannot sent h2c command Status in Ubuntu: New Bug description: When try to start Ubuntu show error like.cannot sent h2c command ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: akshay 1405 F pulseaudio CasperMD5CheckResult: skip Date: Fri Aug 21 20:44:31 2020 InstallationDate: Installed on 2020-07-24 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9cf0b1fe-a751-4d2f-b06d-b3fa63e470fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd01/18/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4TT05PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1892520/+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 1892239] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1892239 Title: Audio Problems Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade to Ubuntu 20.04 I started having problems with audio. From the beginning my internal speakers were recognized but no audio came from them, also at first my headphones didn't work. I started to try different things that I found on the Internet and I got my audio "working". I put it between quotes because my speakers only work sometimes, and when my speakers don't work my headphones do (and when the internal speakers work my headphones don't). Although it can happen that sound comes out of my headphones but its internal microphone doesn't work, however the internal microphone of my PC works(or vice versa). It's a Russian roulette every time I turn on my PC Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: 5.4.0-42-generic Architecture: x86_64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: supremequeen 1616 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 16:02:21 2020 InstallationDate: Installed on 2020-05-08 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 04f2:b5db Chicony Electronics Co., Ltd HP Webcam Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-bp0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=01607e9d-1b80-42d8-9877-dbc9a338bf89 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 835F dmi.board.vendor: HP dmi.board.version: 46.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPLaptop14-bp0xx:pvrType1ProductConfigId:rvnHP:rn835F:rvr46.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-bp0xx dmi.product.sku: 1GR55LA#AC8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892239/+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 1883010] Re: Lenovo-ThinkBook-14-IIL Touchpad not working
*** This bug is a duplicate of bug 1853277 *** https://bugs.launchpad.net/bugs/1853277 This is a bug in the laptops BIOS. You can fix the acpi tables by following comment 66 and 96 in this ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/ -- 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/1883010 Title: Lenovo-ThinkBook-14-IIL Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: The touchpad of this laptop does not seem to be supported. OS: Ubuntu 20.04 LTS Related: https://askubuntu.com/questions/1248939/lenovo-thinkbook-14-iil-touchpad-not-working https://askubuntu.com/questions/1215236/touch-pad-not-working-on-lenovo-thinkbook-14-iml https://askubuntu.com/questions/1245632/lenovo-thinkbook-iml-touchpad-not-recognized cat /proc/bus/input/devices does not list a device. This is the output: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=1d57 Product=0005 Version=0110 N: Name="HID 1d57:0005" P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:1D57:0005.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=5986 Product=2130 Version=5609 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor=00
[Kernel-packages] [Bug 1892239] Re: Audio Problems Ubuntu 20.04
Hello Trinity, Quite often, running pavucontrol is enough to see what needs to be changed to make audio output work correctly. I hope this helps. Thanks ** Information type changed from Private Security to Public -- 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/1892239 Title: Audio Problems Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: When I upgrade to Ubuntu 20.04 I started having problems with audio. From the beginning my internal speakers were recognized but no audio came from them, also at first my headphones didn't work. I started to try different things that I found on the Internet and I got my audio "working". I put it between quotes because my speakers only work sometimes, and when my speakers don't work my headphones do (and when the internal speakers work my headphones don't). Although it can happen that sound comes out of my headphones but its internal microphone doesn't work, however the internal microphone of my PC works(or vice versa). It's a Russian roulette every time I turn on my PC Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: 5.4.0-42-generic Architecture: x86_64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: supremequeen 1616 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 16:02:21 2020 InstallationDate: Installed on 2020-05-08 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 04f2:b5db Chicony Electronics Co., Ltd HP Webcam Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-bp0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=01607e9d-1b80-42d8-9877-dbc9a338bf89 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 835F dmi.board.vendor: HP dmi.board.version: 46.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPLaptop14-bp0xx:pvrType1ProductConfigId:rvnHP:rn835F:rvr46.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-bp0xx dmi.product.sku: 1GR55LA#AC8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892239/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Information type changed from Public Security to Public -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 Ca
[Kernel-packages] [Bug 1874374] Re: thinkbook 14-iil elan touchpad does not work
*** This bug is a duplicate of bug 1853277 *** https://bugs.launchpad.net/bugs/1853277 Just to follow up here... This bug is not a duplicate of #1853277. It is a duplicate of #1861610, which recently had a resolution. See comment 66 there, but be aware that the sed line had a bug that was fixed in comment 96 -- 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/1874374 Title: thinkbook 14-iil elan touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Here is the output of cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.0/0003:062A:4C01.0001/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input6 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse Consumer Control" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse System Control" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=c000 10 0 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=9 B: ABS=100 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input10 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input11 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor=000
[Kernel-packages] [Bug 1886234] Re: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory.
I tried putting that parameter in grub after quiet splash, but I still get the exact same error. -- 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/1886234 Title: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory. Status in linux package in Ubuntu: Confirmed Bug description: After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and turning the VM off, I see this in dmesg: [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, widening DMA allocations [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config. [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6 [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1 [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config. [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on [ 4680.392669] sysfs: cannot create duplicate filename '/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1' [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G OE 5.4.0-40-generic #44-Ubuntu [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 1409 05/12/2020 [ 4680.392674] Call Trace: [ 4680.392681] dump_stack+0x6d/0x9a [ 4680.392684] sysfs_warn_dup.cold+0x17/0x35 [ 4680.392685] sysfs_create_dir_ns+0xb8/0xd0 [ 4680.392687] kobject_add_internal+0xbd/0x2b0 [ 4680.392688] kobject_add+0x7e/0xb0 [ 4680.392692] device_add+0x132/0x6b0 [ 4680.392696] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392702] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392706] snd_device_register_all+0x33/0x50 [snd] [ 4680.392709] snd_card_register+0x62/0x1b0 [snd] [ 4680.392712] ? snd_hwdep_new+0xfe/0x146 [snd_hwdep] [ 4680.392715] snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth] [ 4680.392717] snd_emux_register+0x11a/0x190 [snd_emux_synth] [ 4680.392719] ? 0xc1065000 [ 4680.392721] ? sf_sample_new+0x20/0x20 [snd_emux_synth] [ 4680.392723] snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth] [ 4680.392725] really_probe+0x2b3/0x3e0 [ 4680.392726] driver_probe_device+0xbc/0x100 [ 4680.392728] __device_attach_driver+0x71/0xd0 [ 4680.392729] ? driver_allows_async_probing+0x50/0x50 [ 4680.392731] bus_for_each_drv+0x84/0xd0 [ 4680.392732] __device_attach+0xe1/0x160 [ 4680.392734] device_initial_probe+0x13/0x20 [ 4680.392735] bus_probe_device+0x8f/0xa0 [ 4680.392737] device_add+0x3c7/0x6b0 [ 4680.392740] ? __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392742] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392745] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392748] snd_device_register_all+0x33/0x50 [snd] [ 4680.392751] snd_card_register+0x62/0x1b0 [snd] [ 4680.392753] ? snd_seq_device_new+0xd0/0x126 [snd_seq_device] [ 4680.392758] snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1] [ 4680.392761] local_pci_probe+0x48/0x80 [ 4680.392763] pci_device_probe+0x10f/0x1b0 [ 4680.392765] really_probe+0x159/0x3e0 [ 4680.392766] driver_probe_device+0xbc/0x100 [ 4680.392767] __device_attach_driver+0x71/0xd0 [ 4680.392769] ? driver_allows_async_probing+0x50/0x50 [ 4680.392770] bus_for_each_drv+0x84/0xd0 [ 4680.392771] __device_attach+0xe1/0x160 [ 4680.392773] device_attach+0x10/0x20 [ 4680.392775] bus_rescan_devices_helper+0x39/0x80 [ 4680.392777] drivers_probe_store+0x36/0x60 [ 4680.392778] bus_attr_store+0x27/0x30 [ 4680.392780] sysfs_kf_write+0x3e/0x50 [ 4680.392782] kernfs_fop_write+0xda/0x1b0 [ 4680.392784] __vfs_write+0x1b/0x40 [ 4680.392785] vfs_write+0xb9/0x1a0 [ 4680.392786] ksys_write+0x67/0xe0 [ 4680.392788] __x64_sys_write+0x1a/0x20 [ 4680.392790] do_syscall_64+0x57/0x190 [ 4680.392793] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 4680.392794] RIP: 0033:0x7f52456222cf [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48 [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 0001 [ 4680.392798] RAX: ffda RBX: 000c RCX: 7f52456222cf [ 4680.392799] RDX: 000c RSI: 7f5230062f50 RDI: 000
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@gannon1 I follow the concept. I tried first using vmware workstation, mostly just cause I already had it installed for another purpose, but unfortunately no luck there. Vmware abstracts the underlying hardware and windows doesn't even see it as a realtek audio device. I also shared the problem of not being able to get samsung update installed, but I used your driver download you posted and it did install, but sadly I can't get speaker sound even with the driver in wmware... So, I will see if I can find some time this weekend to get qemu going. One thought on your other thread... if you suspend or reboot the entire VM then you will see tons of traffic as it communicates with every hardware device. Perhaps instead you could just go into device manager and then disable and re-enable the audio device specifically while tracing. Seems like it would greatly reduce the search data, assuming it actually issues the needed command during a disable... just a thought... -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsi
[Kernel-packages] [Bug 1892547] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1892547 Title: [0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) [0.172444] ACPI Exception: Could not find/resolve named package element: OC07 (20170831/dspkginit-381) Status in linux package in Ubuntu: Confirmed Bug description: [0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xilion 1667 F pulseaudio CurrentDesktop: LXDE Date: Fri Aug 21 22:15:54 2020 HibernationDevice: RESUME=UUID=3a74be02-d33e-4932-8d91-4d1fa8672def InstallationDate: Installed on 2018-06-18 (795 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: lono wireless extensions. enp0s29f7u2 no wireless extensions. enp1s3no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=4ed73824-614c-4c5a-a4ca-782b0ed7ace2 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.173.19 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.name: P5GPL-X SE 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.:bvr0301:bd06/09/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5GPL-XSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892547/+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 1892547] [NEW] [ 0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) [ 0.172444] ACPI Exception: Could not find/resolve named p
Public bug reported: [0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xilion 1667 F pulseaudio CurrentDesktop: LXDE Date: Fri Aug 21 22:15:54 2020 HibernationDevice: RESUME=UUID=3a74be02-d33e-4932-8d91-4d1fa8672def InstallationDate: Installed on 2018-06-18 (795 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: lono wireless extensions. enp0s29f7u2 no wireless extensions. enp1s3no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=4ed73824-614c-4c5a-a4ca-782b0ed7ace2 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.173.19 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.name: P5GPL-X SE 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.:bvr0301:bd06/09/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5GPL-XSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- 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/1892547 Title: [0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) [0.172444] ACPI Exception: Could not find/resolve named package element: OC07 (20170831/dspkginit-381) Status in linux package in Ubuntu: Confirmed Bug description: [0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xilion 1667 F pulseaudio CurrentDesktop: LXDE Date: Fri Aug 21 22:15:54 2020 HibernationDevice: RESUME=UUID=3a74be02-d33e-4932-8d91-4d1fa8672def InstallationDate: Installed on 2018-06-18 (795 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: lono wireless extensions. enp0s29f7u2 no wireless extensions. enp1s3no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=4ed73824-614c-4c5a-a4ca-782b0ed7ace2 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.173.19 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.name: P5GPL-X SE 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.:bvr0301:bd06/09/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5GPL-XSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net U
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
Seeing this bug on 20.10 groovy system. ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) ... Removing old bcmwl-6.30.223.271+bdcom DKMS files... -- Deleting module version: 6.30.223.271+bdcom completely from the DKMS tree. -- Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-42-generic Building for architecture x86_64 Building initial module for 5.4.0-42-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Confirmed Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1892546] [NEW] Novalink (mkvterm command failure)
Public bug reported: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-187036 severity-critical targetmilestone-inin16046 ** Tags added: architecture-ppc64le bugnameltc-187036 severity-critical targetmilestone-inin16046 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1892546 Title: Novalink (mkvterm command failure) Status in linux package in Ubuntu: New Bug description: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892546/+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 1892546] [NEW] Novalink (mkvterm command failure)
You have been subscribed to a public bug: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-187036 severity-critical targetmilestone-inin16046 -- Novalink (mkvterm command failure) https://bugs.launchpad.net/bugs/1892546 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations
Thx a lot Ursula - I've updated the tags ... ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Connections from later-level SMC (protocol) versions to an SMC- enabled server on Linux hang. * Later-level versions of SMC (although backwards-compatible) present a higher version number and use larger messages during the CLC handshake. * The solution to avoid such hangs is to introduce toleration for later version numbers, and support CLC messages of arbitrary length. [Fix] * fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 fb4f79264c0f "net/smc: tolerate future SMCD versions" [Test Case] * Requires two IBM z13/z13s GA2 or LinuxONE Rockhopper/Emperor systems with RoCE Express adapter v2(.1) for SMC-D usage. * One system needs to run the initial SMC-D version, the other a newer version. * Establish a connection between both system and monitor/verify if it's reliable or if it hangs. [Regression Potential] * The regression can be considered as medium to low: * Since SMC-D is a pretty special way of doing shared memory communications and not that wide-spread. * However, the code that is changed is common code. * But the patch is straight forward and only modifies /net/smc/smc_clc.c and /net/smc/smc_clc.h * It largely bumps limits (allows larger messages), adds a check and introduces toleration, rather than changing control or flow. [Other] * The above fix is currently in 'linux-next' and tagged with next-20200709. * It is still assumed that it gets accepted for 5.8. * However, since this is not guaranteed this SRU request is for focal and groovy - to make sure that no potential regressions are introduced in case the patch will not end up in 5.8. __ Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+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 1882088] Comment bridged from LTC Bugzilla
--- Comment From ursula.br...@de.ibm.com 2020-08-21 14:10 EDT--- My tests have been successful. Fix is validated. -- 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/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Connections from later-level SMC (protocol) versions to an SMC- enabled server on Linux hang. * Later-level versions of SMC (although backwards-compatible) present a higher version number and use larger messages during the CLC handshake. * The solution to avoid such hangs is to introduce toleration for later version numbers, and support CLC messages of arbitrary length. [Fix] * fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 fb4f79264c0f "net/smc: tolerate future SMCD versions" [Test Case] * Requires two IBM z13/z13s GA2 or LinuxONE Rockhopper/Emperor systems with RoCE Express adapter v2(.1) for SMC-D usage. * One system needs to run the initial SMC-D version, the other a newer version. * Establish a connection between both system and monitor/verify if it's reliable or if it hangs. [Regression Potential] * The regression can be considered as medium to low: * Since SMC-D is a pretty special way of doing shared memory communications and not that wide-spread. * However, the code that is changed is common code. * But the patch is straight forward and only modifies /net/smc/smc_clc.c and /net/smc/smc_clc.h * It largely bumps limits (allows larger messages), adds a check and introduces toleration, rather than changing control or flow. [Other] * The above fix is currently in 'linux-next' and tagged with next-20200709. * It is still assumed that it gets accepted for 5.8. * However, since this is not guaranteed this SRU request is for focal and groovy - to make sure that no potential regressions are introduced in case the patch will not end up in 5.8. __ Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+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 1711407] Re: unregister_netdevice: waiting for lo to become free
Bug also happens on 5.4.0-42-generic. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal -- 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/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+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 1768211] Re: norton setup
http://id.indonesiayp.com/company/839674/BacaduluTop https://www.semrush.com/user/187932785/ https://patch.com/users/ustman-kurma https://yellow.place/en/bacadulu-top-tasikmalaya-indonesia https://id.gravatar.com/bacadulutop https://www.intensedebate.com/people/bacadulu https://www.sbnation.com/users/bacadulutop https://bacadulutop.listal.com/ https://jobs.thelocal.com/app/e/#job/5ebc32105852916df590b689 https://www.soundclick.com/member/default.cfm?memberID=7016265 https://disqus.com/by/bacadulutop/ https://www.kongregate.com/accounts/bacadulutop https://pbase.com/bacadulutop https://www.deviantart.com/bacadulutop https://imageshack.com/user/bacadulutop https://www.quora.com/profile/Baca-Dulutop https://about.me/dulutop https://issuu.com/bacadulutop?issuu_product=header&issuu_subproduct=publisher-home&issuu_context=link&issuu_cta=profile https://issuu.com/bacadulutop?issuu_product=header&issuu_subproduct=account&issuu_context=link&issuu_cta=profile http://cappyzeb.freeyellow.com/01/album/gallery04/details.php?image_id=3 https://participer.valdemarne.fr/profiles/bacadulutop/timeline https://participation.lillemetropole.fr/profiles/bacadulutop/timeline https://forums.beyondunreal.com/members/bacadulutop.79368/ https://bacadulutop.demo.xwiki.com/xwiki/bin/view/Main/ https://bacadulutop.demo.xwiki.com/xwiki/bin/view/XWiki/BacaDulutop?category=profile https://forum.laleggepertutti.it/User-bacadulutop https://forum.laleggepertutti.it/User-bacadulutop https://nianow.com/bacadulutop https://mastodon.acc.sunet.se/web/accounts/102936 https://myspace.com/bacadulutop https://dribbble.com/bacadulutop/about https://www.behance.net/bacadulutop https://www.theverge.com/users/Toni%2520Antonio https://visual.ly/users/bacadulutop/ https://visual.ly/users/bacadulutop/portfolio https://loop.frontiersin.org/people/981782/overview https://8tracks.com/bacadulutop https://www.magcloud.com/user/bacadulutop https://express.yudu.com/profile/index https://www.dead.net/member/bacadulutop https://www.warriorforum.com/members/bacadulutop.html https://nianow.com/users/bacadulutop https://www.onrpg.com/boards/members/1964358-bacadulutop https://forums.hostsearch.com/member.php?185100-bacadulutop https://www.openstreetmap.org/user/bacadulutop https://trello.com/bacadulutop https://trello.com/c/J0rQCksP/3-sujana-blog-review-blog https://community.linksys.com/t5/user/viewprofilepage/user-id/1169550 https://weheartit.com/bacadulutop https://www.aeriagames.com/user/bacadulutop/ http://billion7.com/people/bacadulutop https://triberr.com/bacadulutop http://www.authorstream.com/bacadulutop/ https://triberr.com/bacadulutop?resend=true https://www.huntingnet.com/forum/members/bacadulutop.html https://www.slideshare.net/BacaDuluTOP https://id.scribd.com/user/513251650/bacadulutop https://www.4shared.com/u/yhpr8bck/fa8676206.html https://www.smashwords.com/profile/view/bacadulutop https://www.wattpad.com/user/ustmankurma https://www.patreon.com/user?u=35975849 https://www.wondercms.com/community/memberlist.php?mode=viewprofile&u=3550 https://speechdebate.binghamton.edu/Users/6071/Profile/baca-dulutop/ http://club.kedo.gov.cn/home.php?mod=space&uid=544553&do=profile&from=space https://projects.co.id/public/browse_users/view/84841d/bacadulutop http://io.telkomuniversity.ac.id/forum/account/bacadulutop/ -- 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/1768211 Title: norton setup Status in linux package in Ubuntu: Invalid Bug description: Online Norton Help and Support by PC Planet PCPlanet's Certified Technicians can help you scan, detect, and remove all types of viruses and malware in your computer. Our techies have years of experience and the expertise in providing support for antivirus and fixing computer virus problems online through remote connection. Our support services are available through phone, chat and email. Just call us at 1-888-406-4114 to chat with a certified expert and get instant support for Norton Antivirus to make your computer virus free.http://pcplanet247.com/www-norton-com-setup//";>Norton Support Get Started http://pcplanet247.com/www-norton-com-setup//";>Norton Support http://pcplanet247.com/www-norton-com-setup//";>Norton Support 2016 is a version of Norton Setup productivity suite came after Norton 2013. This version is available for PCs (such as Norton Security & 360 2016) and Macs (such as Norton Delux & Premier Edition 2016 for Mac). Along with all the features of previous versions, Norton includes additional ribbon buttons, enhanced collaboration, mentions, new & improved connection options, publish to docs.com, publish to power BI, researcher, suggest a feature, text highlighter, zoom for Norton and staying in the loop. To get Norton 2016, you need to buy, download, install and then activate it. To perform these processes, there is a series of steps that needs to be followed. Yo
[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla
--- Comment From ursula.br...@de.ibm.com 2020-08-21 12:42 EDT--- Yes, it helped. Thx! I am now running kernel 5.4.0-44-generic and started verification. -- 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/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Connections from later-level SMC (protocol) versions to an SMC- enabled server on Linux hang. * Later-level versions of SMC (although backwards-compatible) present a higher version number and use larger messages during the CLC handshake. * The solution to avoid such hangs is to introduce toleration for later version numbers, and support CLC messages of arbitrary length. [Fix] * fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 fb4f79264c0f "net/smc: tolerate future SMCD versions" [Test Case] * Requires two IBM z13/z13s GA2 or LinuxONE Rockhopper/Emperor systems with RoCE Express adapter v2(.1) for SMC-D usage. * One system needs to run the initial SMC-D version, the other a newer version. * Establish a connection between both system and monitor/verify if it's reliable or if it hangs. [Regression Potential] * The regression can be considered as medium to low: * Since SMC-D is a pretty special way of doing shared memory communications and not that wide-spread. * However, the code that is changed is common code. * But the patch is straight forward and only modifies /net/smc/smc_clc.c and /net/smc/smc_clc.h * It largely bumps limits (allows larger messages), adds a check and introduces toleration, rather than changing control or flow. [Other] * The above fix is currently in 'linux-next' and tagged with next-20200709. * It is still assumed that it gets accepted for 5.8. * However, since this is not guaranteed this SRU request is for focal and groovy - to make sure that no potential regressions are introduced in case the patch will not end up in 5.8. __ Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+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 1889992] Re: Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens
It locked up again. This time I let it sit there in the frozen state for ~5 minutes before powering off. It was so frozen that it did not respond to attempts to SSH in. This time the logs show more systemd- udevd logs at the end. The new logs are attached. ** Attachment added: "journalctl -b -1 (tail end of the logs)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889992/+attachment/5403529/+files/another_crash.log -- 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/1889992 Title: Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens Status in linux package in Ubuntu: Incomplete Bug description: I just did a fresh first-time install of Ubuntu on a Dell Inspirion 14 with no modifications apart from installing Canon printer drivers and no 3rd party peripherals. The desktop freezes spontaneously. When it freezes, the display freezes including the mouse pointer, and all keystrokes are unresponsive (can't even do ctrl-alt-F3 to get a tty). Forced power off is the only possible action. I think this is irrelevent, but I'll mention that (I think) the lockup only happens when I'm using VLC to play MythTV-served videos from the LAN. Nothing else is running.. not even a browser. I'm simply watching a video and out of the blue it hangs. After rebooting, I play the same video I was watching just before the hang, and finish watching without a freeze up. Which means there's no relation to the video data. $ inxi -Fxz System:Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Portable System: Dell product: Inspiron 14-3452 v: 4.0.7 serial: Mobo: Dell model: 0625M8 v: A00 serial: UEFI: Dell v: 4.0.7 date: 04/26/2016 Battery: ID-1: BAT0 charge: 33.6 Wh condition: 33.6/41.4 Wh (81%) model: Samsung SD DELL 07G075A status: Full CPU: Topology: Dual Core model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont rev: 3 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400 Speed: 1377 MHz min/max: 480/2160 MHz Core speeds (MHz): 1: 1034 2: 1139 Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.Org 1.19.2 driver: i915 resolution: 1280x800~60Hz OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-42-generic Network: Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be v: kernel port: e000 bus ID: 01:00.0 IF: wlp1s0 state: up mac: Drives:Local Storage: total: 29.12 GiB used: 8.75 GiB (30.0%) ID-1: /dev/mmcblk0 model: HBG4e size: 29.12 GiB Partition: ID-1: / size: 28.05 GiB used: 8.74 GiB (31.2%) fs: ext4 dev: /dev/mmcblk0p2 Sensors: System Temperatures: cpu: 52.0 C mobo: 47.0 C Fan Speeds (RPM): cpu: 3181 Info: Processes: 199 Uptime: 41m Memory: 1.85 GiB used: 891.8 MiB (46.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.17 inxi: 3.0.38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889992/+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 1889384] Re: ASPM not enabled on child devices behind VMD controller
** Tags added: originate-from-1889754 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1889384 Title: ASPM not enabled on child devices behind VMD controller Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: ASPM of VMD devices is not automatically enabled even it's said capable in its Link Capabilities Register. $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1831 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-29 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19 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.6.0-1020-oem N/A linux-backports-modules-5.6.0-1020-oem N/A linux-firmware 1.187.2 Tags: focal Uname: Linux 5.6.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.5.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1889384/+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 1830151] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1830151
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1830151
Title:
ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on
B-hwe P9
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
This test has passed with Cosmic kernel on the same node ("baltar"),
but not with the 4.18 kernel on Bionic.
selftests: ebb: cycles_test
test: cycles
tags: git_version:unknown
EBB Handler is at 0x10004170
ebb_state:
ebb_count = 10
spurious = 0
negative = 0
no_overflow = 0
pmc[1] count = 0x2843f
pmc[2] count = 0x0
pmc[3] count = 0x0
pmc[4] count = 0x0
pmc[5] count = 0x0
pmc[6] count = 0x0
HW state:
MMCR0 0x8400 FC PMAE
MMCR2 0x
EBBHR 0x10004170
BESCR 0x8000 GE
PMC1 0x4000
PMC2 0x
PMC3 0x
PMC4 0x
PMC5 0x00028b3f
PMC6 0x0002ac80
SIAR 0x100035d4
Trace buffer dump:
address 0x71a628a2
tail 0x71a628a201f6
size 1048576
overflow false
Content:
[0]: counter = 1
[1]: register SPRN_MMCR0 = 0x8080
[2]: register SPRN_PMC1 = 0x8004
[3]: counter = 2
[4]: register SPRN_MMCR0 = 0x8080
[5]: register SPRN_PMC1 = 0x8004
[6]: counter = 3
[7]: register SPRN_MMCR0 = 0x8080
[8]: register SPRN_PMC1 = 0x8004
[FAIL] Test FAILED on line 52
[9]: counter = 4
[10]: register SPRN_MMCR0 = 0x8080
[11]: register SPRN_PMC1 = 0x8004
[12]: counter = 5
[13]: register SPRN_MMCR0 = 0x8080
[14]: register SPRN_PMC1 = 0x8004
[15]: counter = 6
[16]: register SPRN_MMCR0 = 0x8080
[17]: register SPRN_PMC1 = 0x8004
[18]: counter = 7
[19]: register SPRN_MMCR0 = 0x8080
[20]: register SPRN_PMC1 = 0x8004
[21]: counter = 8
[22]: register SPRN_MMCR0 = 0x8080
[23]: register SPRN_PMC1 = 0x8004
[24]: counter = 9
[25]: register SPRN_MMCR0 = 0x8080
[26]: register SPRN_PMC1 = 0x8004
[27]: counter = 10
[28]: register SPRN_MMCR0 = 0x8080
[29]: register SPRN_PMC1 = 0x8004
[30]: register SPRN_PMC1 = 0x4417
PMC1 count (0x2843f) above upper limit 0x283e8 (+0x57)
failure: cycles
not ok 1..3 selftests: ebb: cycles_test [FAIL]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830151/+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 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed
Removing bootloader tasks, as the kernel has loaded successfully. ** No longer affects: grub2 (Ubuntu) ** No longer affects: syslinux (Ubuntu) -- 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/1886769 Title: [ 0.00] Initramfs unpacking failed: Decoding failed Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Download MATE Groovy daily (sha256sum = 7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 ) 2. Insert ISO into VirtualBox with EFI enabled 3. Boot VM Expected results: * VM boots normally Actual results: * VM hangs during early boot with message [ 0.00] Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886769/+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 1830151] Re: ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on B-hwe P9
We do see this failing on recent ADT testing on PowerPC with Focal
kernel in this cycle (didn't see this anywhere else), re-open this bug
to get it fixed in the right way.
** Changed in: linux (Ubuntu)
Status: Fix Released => New
** Changed in: ubuntu-kernel-tests
Status: Fix Released => New
** Tags added: 5.4 focal
--
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/1830151
Title:
ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on
B-hwe P9
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Bug description:
This test has passed with Cosmic kernel on the same node ("baltar"),
but not with the 4.18 kernel on Bionic.
selftests: ebb: cycles_test
test: cycles
tags: git_version:unknown
EBB Handler is at 0x10004170
ebb_state:
ebb_count = 10
spurious = 0
negative = 0
no_overflow = 0
pmc[1] count = 0x2843f
pmc[2] count = 0x0
pmc[3] count = 0x0
pmc[4] count = 0x0
pmc[5] count = 0x0
pmc[6] count = 0x0
HW state:
MMCR0 0x8400 FC PMAE
MMCR2 0x
EBBHR 0x10004170
BESCR 0x8000 GE
PMC1 0x4000
PMC2 0x
PMC3 0x
PMC4 0x
PMC5 0x00028b3f
PMC6 0x0002ac80
SIAR 0x100035d4
Trace buffer dump:
address 0x71a628a2
tail 0x71a628a201f6
size 1048576
overflow false
Content:
[0]: counter = 1
[1]: register SPRN_MMCR0 = 0x8080
[2]: register SPRN_PMC1 = 0x8004
[3]: counter = 2
[4]: register SPRN_MMCR0 = 0x8080
[5]: register SPRN_PMC1 = 0x8004
[6]: counter = 3
[7]: register SPRN_MMCR0 = 0x8080
[8]: register SPRN_PMC1 = 0x8004
[FAIL] Test FAILED on line 52
[9]: counter = 4
[10]: register SPRN_MMCR0 = 0x8080
[11]: register SPRN_PMC1 = 0x8004
[12]: counter = 5
[13]: register SPRN_MMCR0 = 0x8080
[14]: register SPRN_PMC1 = 0x8004
[15]: counter = 6
[16]: register SPRN_MMCR0 = 0x8080
[17]: register SPRN_PMC1 = 0x8004
[18]: counter = 7
[19]: register SPRN_MMCR0 = 0x8080
[20]: register SPRN_PMC1 = 0x8004
[21]: counter = 8
[22]: register SPRN_MMCR0 = 0x8080
[23]: register SPRN_PMC1 = 0x8004
[24]: counter = 9
[25]: register SPRN_MMCR0 = 0x8080
[26]: register SPRN_PMC1 = 0x8004
[27]: counter = 10
[28]: register SPRN_MMCR0 = 0x8080
[29]: register SPRN_PMC1 = 0x8004
[30]: register SPRN_PMC1 = 0x4417
PMC1 count (0x2843f) above upper limit 0x283e8 (+0x57)
failure: cycles
not ok 1..3 selftests: ebb: cycles_test [FAIL]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830151/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Bionic verification:
$ apt changelog bcache-tools | head -10
bcache-tools (1.0.8-2ubuntu0.18.04.1) bionic; urgency=medium
[ Ryan Harper ]
* Add helper script to read bcache devs superblock (LP: #1861941)
-- Rafael David Tinoco Wed, 05 Aug 2020
17:44:05 -0300
bcache-tools (1.0.8-2build1) artful; urgency=medium
$ dpkg-query -f '${Package}###${Version}\n' -W 'bcache-tools'
bcache-tools###1.0.8-2ubuntu0.18.04.1
$ sudo ./test-bcache.sh
/mnt is a mountpoint
/dev/bcache0: 2 bytes were erased at offset 0x0438 (ext4): 53 ef
writing 1 to /sys/class/block/bcache0/bcache/stop
writing 1 to /sys/fs/bcache/60412675-9103-47b0-9794-91fcfb12d50d/stop
/dev/vdc: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a
45 ca 82 65 f5 7f 48 ba 6d 81
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.0173157 s, 606 MB/s
/dev/vdb: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a
45 ca 82 65 f5 7f 48 ba 6d 81
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.00634546 s, 1.7 GB/s
UUID: c3758ea3-0e2c-42e3-bb77-da27292d2476
Set UUID: b2b21f55-3599-461a-b162-8377d85fbc34
version:0
nbuckets: 2048
block_size: 1
bucket_size:1024
nr_in_set: 1
nr_this_dev:0
first_bucket: 1
UUID: f4001b7e-386e-4ca3-a5e0-d53f100d156f
Set UUID: b2b21f55-3599-461a-b162-8377d85fbc34
version:1
block_size: 1
data_offset:16
/dev/vdc
tee: /sys/fs/bcache/register: Invalid argument
/dev/vdb
tee: /sys/fs/bcache/register: Invalid argument
total 0
drwxr-xr-x 2 root root 60 Aug 21 14:03 .
drwxr-xr-x 3 root root 60 Aug 21 14:03 ..
lrwxrwxrwx 1 root root 13 Aug 21 14:03 f4001b7e-386e-4ca3-a5e0-d53f100d156f ->
../../bcache0
Creating filesystems on bcache0
mke2fs 1.44.1 (24-Mar-2018)
Discarding device blocks: done
Creating filesystem with 262142 4k blocks and 65536 inodes
Filesystem UUID: 4ade91a9-6176-4a93-a34f-158fa08d0091
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
mounting bcache0 to /mnt
total 0
drwxr-xr-x 2 root root 60 Aug 21 14:03 .
drwxr-xr-x 3 root root 60 Aug 21 14:03 ..
lrwxrwxrwx 1 root root 13 Aug 21 14:03 f4001b7e-386e-4ca3-a5e0-d53f100d156f ->
../../bcache0
Everything OK
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
Status in bcache-tools package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Fix Released
Status in bcache-tools source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Won't Fix
Status in bcache-tools source package in Focal:
Fix Released
Status in systemd source package in Focal:
In Progress
Bug description:
SRU TEAM: The last 2 commits show a summary for the merges/changes
I added some specific (to Bionic) notes in the template.
Thanks!
[Impact]
* bcache-tools udev created symlinks might disappear when other udev
events are processed for the same devices.
* after mkfs.XXX in /dev/bcacheY you might face a condition where
/dev/bcache/by-{uuid,label}/zzz symlinks are gone.
* /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
devices can be addressed by their UUIDs and not the ordering they were
assembled (MAAS depends on this feature, for example).
* it was also discussed in this bug that systemd-udev should *not*
populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
backing devices. this was turned into a discussion whether blkid
should report those or not, and this discussion "died" after sometime.
This last item is what the systemd update is all about: to disallow
/dev/disk/by-XXX/ creation for bcache backing devices (a simple
change that will reduce end users confusion).
[Test Case]
* The reproducer script is here:
https://paste.ubuntu.com/p/37KGy2Smnp/
* Bionic can't reproduce the issue with the 18.04 kernel, nor with
the HWE kernel. Nevertheless, it is preferable that Bionic also do the
same thing: to read bcache superblock and feed environment for
/dev/bcache/by-{uuid,label} symlinks creation.
[Regression Potential]
* We are not depending on bcache device udev events any more when
creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
depe
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
Removed spurious grub task. ** No longer affects: grub2 (Ubuntu) ** No longer affects: grub2 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags added: originate-from-1892498 -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver
[Kernel-packages] [Bug 1891405] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380
It has been a week since I installed the new firmware from the PPA, and there have been no dropouts whatsoever. Thanks again for the assistance! -- 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/1891405 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge
[Kernel-packages] [Bug 1889992] Re: Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens
Immediately after a crash and forced poweroff, I ran "journalctl -b -1", which I've pasted below (minus the huge amount of systemd-udevd logs which are likely irrelevant). The freeze always happens in VLC, and indeed the logs show VLC failures at the end of the logs. I should also note that I'm using glitchy cheap chinese bluetooth speakers. No matter what device connects to these speakers (phones and various laptops), the sound often dies and I have to disconnect and reconnect the bluetooth session to recover. I doubt that's related but mention it for completeness. When VLC can bring down the whole platform, that seems like a serious problem with the kernel. Regardless of how badly an app like VLC behaves, it shouldn't be able to freeze the whole system. --- Aug 21 08:53:40 hostname kernel: microcode: microcode updated early to revision 0x368, date = 2019-04-23 Aug 21 08:53:40 hostname kernel: Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 (Ubuntu 5.4.0-42.46-generic 5.4.44) Aug 21 08:53:40 hostname kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=(redacted) ro quiet splash vt.handoff=7 Aug 21 08:53:40 hostname kernel: KERNEL supported cpus: Aug 21 08:53:40 hostname kernel: Intel GenuineIntel Aug 21 08:53:40 hostname kernel: AMD AuthenticAMD Aug 21 08:53:40 hostname kernel: Hygon HygonGenuine Aug 21 08:53:40 hostname kernel: Centaur CentaurHauls Aug 21 08:53:40 hostname kernel: zhaoxin Shanghai Aug 21 08:53:40 hostname kernel: x86/fpu: x87 FPU will use FXSAVE (...) [copious systemd-udevd logs snipped] Aug 21 09:19:11 hostname systemd-udevd[4206]: value '[dmi/id]sys_vendor' is 'Dell Inc.' Aug 21 09:19:11 hostname systemd-udevd[4205]: ext4_inode_cache(357:console-setup.service): Device (SEQNUM=7613, ACTION=remove) processed Aug 21 09:19:11 hostname systemd-udevd[4205]: ext4_inode_cache(357:console-setup.service): sd-device-monitor: Passed 164 byte to netlink monitor Aug 21 09:19:11 hostname systemd-udevd[4206]: ext4_inode_cache(1161:NetworkManager-dispatcher.service): Device (SEQNUM=7614, ACTION=remove) processed Aug 21 09:19:11 hostname systemd-udevd[4206]: ext4_inode_cache(1161:NetworkManager-dispatcher.service): sd-device-monitor: Passed 177 byte to netlink monitor Aug 21 09:19:14 hostname systemd-udevd[325]: Cleanup idle workers Aug 21 09:19:14 hostname systemd-udevd[4205]: Unload module index Aug 21 09:19:14 hostname systemd-udevd[4205]: Unloaded link configuration context. Aug 21 09:19:14 hostname systemd-udevd[4206]: Unload module index Aug 21 09:19:14 hostname systemd-udevd[4206]: Unloaded link configuration context. Aug 21 09:19:14 hostname systemd-udevd[325]: Worker [4205] exited Aug 21 09:19:14 hostname systemd-udevd[325]: Worker [4206] exited Aug 21 09:19:23 hostname vlc.desktop[2577]: [5591dba78700] main audio output error: too low audio sample frequency (0) Aug 21 09:19:23 hostname vlc.desktop[2577]: [7fb34d0176b0] main decoder error: failed to create audio output Aug 21 09:19:23 hostname vlc.desktop[2577]: [7fb34c009260] ts demux error: libdvbpsi error (PSI decoder): TS discontinuity (received 11, expected 10) for PID 0 Aug 21 09:19:23 hostname vlc.desktop[2577]: [7fb34d01d6b0] main decoder error: buffer deadlock prevented Aug 21 09:19:23 hostname vlc.desktop[2577]: [7fb34d0176b0] main decoder error: buffer deadlock prevented Aug 21 09:19:34 hostname pkexec[4257]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Aug 21 09:19:34 hostname pkexec[4257]: blee: Executing command [USER=root] [TTY=unknown] [CWD=/home/blee] [COMMAND=/usr/lib/update-notifier/package-system-locked] Aug 21 09:19:35 hostname vlc.desktop[2577]: [5591dba78700] main audio output error: too low audio sample frequency (0) Aug 21 09:19:35 hostname vlc.desktop[2577]: [7fb38101ca10] main decoder error: failed to create audio output Aug 21 09:19:35 hostname vlc.desktop[2577]: [7fb3800050e0] ts demux error: libdvbpsi error (PSI decoder): TS discontinuity (received 11, expected 10) for PID 0 Aug 21 09:19:35 hostname vlc.desktop[2577]: [7fb38100b580] main decoder error: buffer deadlock prevented Aug 21 09:19:35 hostname vlc.desktop[2577]: [7fb38101ca10] main decoder error: buffer deadlock prevented Aug 21 09:19:41 hostname vlc.desktop[2577]: [5591dba78700] main audio output error: too low audio sample frequency (0) Aug 21 09:19:41 hostname vlc.desktop[2577]: [7fb35d018870] main decoder error: failed to create audio output Aug 21 09:19:41 hostname vlc.desktop[2577]: [7fb35c003480] ts demux error: libdvbpsi error (PSI decoder): TS discontinuity (received 11, expected 10) for PID 0 Aug 21 09:19:42 hostname vlc.desktop[2577]: [7fb35c006f30] main decoder error: buffer deadlock prevented Aug 21 09:19:42 hostname vlc.desktop[2577]: [7fb35d018870] main decoder error: buffer dead
[Kernel-packages] [Bug 1892001] Autopkgtest regression report (zfs-linux/0.7.5-1ubuntu16.10)
All autopkgtests for the newly accepted zfs-linux (0.7.5-1ubuntu16.10) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxd/3.0.3-0ubuntu1~18.04.1 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#zfs-linux
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892001
Title:
zfs-dkms fails to build on arm64 with PREEMPTION and BLK_CGROUP
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Bionic:
Fix Committed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Groovy:
Fix Released
Bug description:
[Impact]
On arm64 with PREEMPTION and BLK_CGROUP enabled,
preempt_schedule_notrace is being pulled in which is a GPL-only
function so the DKMS build fails:
DKMS make.log for zfs-0.8.3 for kernel 5.4.0-1015-raspi (aarch64)
Tue Aug 18 06:30:17 UTC 2020
./scripts/make_gitrev.sh
/bin/bash: ./scripts/make_gitrev.sh: No such file or directory
make: [Makefile:1512: gitrev] Error 127 (ignored)
make all-recursive
make[1]: Entering directory '/var/lib/dkms/zfs/0.8.3/build'
Making all in module
make[2]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module'
list='icp lua'; for targetdir in $list; do \
make -C $targetdir; \
done
make[3]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module/icp'
mkdir -p api core spi io os algs algs/aes algs/edonr algs/modes algs/sha1
algs/sha2 algs/skein asm-x86_64 asm-x86_64/aes asm-x86_64/modes asm-x86_64/sha1
asm-x86_64/sha2 asm-i386 asm-generic
make[3]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module/icp'
make[3]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module/lua'
mkdir -p setjmp
make[3]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module/lua'
make -C /lib/modules/5.4.0-1015-raspi/build M=`pwd` CONFIG_ZFS=m modules
make[3]: Entering directory '/usr/src/linux-headers-5.4.0-1015-raspi'
CC [M] /var/lib/dkms/zfs/0.8.3/build/module/avl/avl.o
CC [M] /var/lib/dkms/zfs/0.8.3/build/module/nvpair/nvpair.o
CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/qat_compress.o
CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/qat_crypt.o
CC [M]
/var/lib/dkms/zfs/0.8.3/build/module/zfs/vdev_raidz_math_aarch64_neon.o
CC [M]
/var/lib/dkms/zfs/0.8.3/build/module/zfs/vdev_raidz_math_aarch64_neonx2.o
LD [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/zfs.o
Building modules, stage 2.
MODPOST 8 modules
FATAL: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol
'preempt_schedule_notrace'
make[4]: *** [scripts/Makefile.modpost:94: __modpost] Error 1
make[3]: *** [Makefile:1647: modules] Error 2
make[3]: Leaving directory '/usr/src/linux-headers-5.4.0-1015-raspi'
make[2]: *** [Makefile:30: modules] Error 2
make[2]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module'
make[1]: *** [Makefile:807: all-recursive] Error 1
make[1]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build'
make: *** [Makefile:676: all] Error 2
Note that Ubuntu currently doesn't support/provide a preemptible arm64
kernel so this hasn't been a problem so far.
[Test Case]
Install zfs-dkms on an arm64 system that has a PREEMPT kernel
installed.
[Fix]
Redefine preempt_schedule_notrace() to preempt_schedule() in the ZFS
module (only for arm64 and if PREEMPTION and BLK_CGROUP are both
enabled). preempt_schedule() is not a GPL symbol.
[Regression Potential]
Per comment in the kernel source, preempt_schedule_notrace() is
required when tracing is enabled. As long as tracing is not enabled,
this 'fix' should not cause any issues. Problems due to this change
could show up as kernel splats like:
===
[ INFO: suspicious RCU usage. ]
3.10.0-rc2+ #1 Not tainted
---
include/linux/rcupdate.h:771 rcu_read_lock() used illegally while idle!
other info that might help us debug this:
RCU used illegally from idle CPU! rcu_scheduler_active = 1, debug_locks
= 0
RCU used illegally from extended quiescent state!
2 locks held by cc1/63645:
#0: (&rq->lock){-.-.-.}, at: [] __schedule+0xed/0x9b0
#1: (rcu_read_lock){.+.+..}, at: []
cpuacct_charge+0x5/0x1f0
CPU: 1 PID: 63645 Comm: cc1 Not tainted 3.10.0-rc2+ #1 [loadavg: 40.57
27.55 13.39 25/277 64369]
Hardware name: Gigabyte Technology Co., Ltd.
GA-MA78GM-S2H/GA-MA78GM-S2H, BIOS F12a 04/23/2010
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
** Also affects: kunpeng920 Importance: Undecided Status: New ** Changed in: kunpeng920 Status: New => Incomplete -- 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/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0:
[Kernel-packages] [Bug 1892483] Re: Synaptics TouchPad not getting detected
apport information ** Tags added: apport-collected focal ** Description changed: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.6 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-08-18 (3 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: linux (not installed) + Tags: focal + Uname: Linux 5.8.2-050802-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to focal on 2020-08-19 (1 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892483/+attachment/5403414/+files/ProcCpuinfoMinimal.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/1892483 Title: Synaptics TouchPad not getting detected Status in linux package in Ubuntu: Incomplete Bug description: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) Tags: focal Uname: Linux 5.8.2-050802-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2020-08-19 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+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 1892483] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1892483/+attachment/5403415/+files/ProcEnviron.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/1892483 Title: Synaptics TouchPad not getting detected Status in linux package in Ubuntu: Incomplete Bug description: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) Tags: focal Uname: Linux 5.8.2-050802-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2020-08-19 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+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 1892419] Re: Displayport is not working
Here is the file ** Attachment added: "drm-status.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1892419/+attachment/5403413/+files/drm-status.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/1892419 Title: Displayport is not working Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Can't get dysplayport to recognize. It is not the cable since I tested it on another PC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 16:54:01 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1993] InstallationDate: Installed on 2020-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP ProBook 650 G1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=adbe32f1-2fcd-4bb7-b8d0-7e8db010d123 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L77 Ver. 01.32 dmi.board.name: 1993 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.asset.tag: 5CG5203T6Z dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL77Ver.01.32:bd03/25/2015:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ProBook 650 G1 dmi.product.sku: K4L00UT#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892419/+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 1891585] Re: alsa/sof: support 1 and 3 dmics
Hello Hui, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: Triaged => Fix Committed -- 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/1891585 Title: alsa/sof: support 1 and 3 dmics Status in HWE Next: Triaged Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Status in linux-firmware source package in Groovy: Fix Released Bug description: This is for linux-firmware: [Impact] On a Dell tigerlake laptop, the sof driver fails to detect the dmic, it alwasys report 0 dmics on the machine. So users doesn't have internal mic to use. [Fix] Intel provides 2 new topology files to us, they could support 1 dmic and 3 dmics. [Test Case] Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in the linux-firmware, the sof driver could detect the dmic and users have a workable internal mic after booting up. [Regression Risk] This is adding 2 new topology files, not changing anything on current sof-firmware, so the regression posibility is very low. This is for linux kernel: [Impact] On a Dell tigerlake laptop, the sof driver fails to detect the dmic, it alwasys report 0 dmics on the machine. So users doesn't have internal mic to use. [Fix] Intel write a patch to fix this issue, if NHLT table returns 1 or 3 dmics, the sof driver will not fail like before, it can support 1 or 3 dmics after applying this patch. [Test Case] Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in the linux-firmware, the sof driver could detect the dmic and users have a workable internal mic after booting up. [Regression Risk] This patch adds new support for 1 and 3 dmics, it doesn't change anything on existing functions, so the regression posibility is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1891585/+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 1892001] Re: zfs-dkms fails to build on arm64 with PREEMPTION and BLK_CGROUP
Hello Juerg, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: zfs-linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1892001 Title: zfs-dkms fails to build on arm64 with PREEMPTION and BLK_CGROUP Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: [Impact] On arm64 with PREEMPTION and BLK_CGROUP enabled, preempt_schedule_notrace is being pulled in which is a GPL-only function so the DKMS build fails: DKMS make.log for zfs-0.8.3 for kernel 5.4.0-1015-raspi (aarch64) Tue Aug 18 06:30:17 UTC 2020 ./scripts/make_gitrev.sh /bin/bash: ./scripts/make_gitrev.sh: No such file or directory make: [Makefile:1512: gitrev] Error 127 (ignored) make all-recursive make[1]: Entering directory '/var/lib/dkms/zfs/0.8.3/build' Making all in module make[2]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module' list='icp lua'; for targetdir in $list; do \ make -C $targetdir; \ done make[3]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module/icp' mkdir -p api core spi io os algs algs/aes algs/edonr algs/modes algs/sha1 algs/sha2 algs/skein asm-x86_64 asm-x86_64/aes asm-x86_64/modes asm-x86_64/sha1 asm-x86_64/sha2 asm-i386 asm-generic make[3]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module/icp' make[3]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module/lua' mkdir -p setjmp make[3]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module/lua' make -C /lib/modules/5.4.0-1015-raspi/build M=`pwd` CONFIG_ZFS=m modules make[3]: Entering directory '/usr/src/linux-headers-5.4.0-1015-raspi' CC [M] /var/lib/dkms/zfs/0.8.3/build/module/avl/avl.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/nvpair/nvpair.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/qat_compress.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/qat_crypt.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/vdev_raidz_math_aarch64_neon.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/vdev_raidz_math_aarch64_neonx2.o LD [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/zfs.o Building modules, stage 2. MODPOST 8 modules FATAL: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'preempt_schedule_notrace' make[4]: *** [scripts/Makefile.modpost:94: __modpost] Error 1 make[3]: *** [Makefile:1647: modules] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-5.4.0-1015-raspi' make[2]: *** [Makefile:30: modules] Error 2 make[2]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module' make[1]: *** [Makefile:807: all-recursive] Error 1 make[1]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build' make: *** [Makefile:676: all] Error 2 Note that Ubuntu currently doesn't support/provide a preemptible arm64 kernel so this hasn't been a problem so far. [Test Case] Install zfs-dkms on an arm64 system that has a PREEMPT kernel installed. [Fix] Redefine preempt_schedule_notrace() to preempt_schedule() in the ZFS module (only for arm64 and if PREEMPTION and BLK_CGROUP are both enabled). preempt_schedule() is not a GPL symbol. [Regression Potential] Per comment in the kernel source, preempt_schedule_notrace() is required when tracing is enabled. As long as tracing is not enabled, this 'fix' should not cause any issues. Problems due to this change could show up
[Kernel-packages] [Bug 1892001] Please test proposed package
Hello Juerg, or anyone else affected, Accepted zfs-linux into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.7.5-1ubuntu16.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1892001 Title: zfs-dkms fails to build on arm64 with PREEMPTION and BLK_CGROUP Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: [Impact] On arm64 with PREEMPTION and BLK_CGROUP enabled, preempt_schedule_notrace is being pulled in which is a GPL-only function so the DKMS build fails: DKMS make.log for zfs-0.8.3 for kernel 5.4.0-1015-raspi (aarch64) Tue Aug 18 06:30:17 UTC 2020 ./scripts/make_gitrev.sh /bin/bash: ./scripts/make_gitrev.sh: No such file or directory make: [Makefile:1512: gitrev] Error 127 (ignored) make all-recursive make[1]: Entering directory '/var/lib/dkms/zfs/0.8.3/build' Making all in module make[2]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module' list='icp lua'; for targetdir in $list; do \ make -C $targetdir; \ done make[3]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module/icp' mkdir -p api core spi io os algs algs/aes algs/edonr algs/modes algs/sha1 algs/sha2 algs/skein asm-x86_64 asm-x86_64/aes asm-x86_64/modes asm-x86_64/sha1 asm-x86_64/sha2 asm-i386 asm-generic make[3]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module/icp' make[3]: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module/lua' mkdir -p setjmp make[3]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module/lua' make -C /lib/modules/5.4.0-1015-raspi/build M=`pwd` CONFIG_ZFS=m modules make[3]: Entering directory '/usr/src/linux-headers-5.4.0-1015-raspi' CC [M] /var/lib/dkms/zfs/0.8.3/build/module/avl/avl.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/nvpair/nvpair.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/qat_compress.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/qat_crypt.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/vdev_raidz_math_aarch64_neon.o CC [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/vdev_raidz_math_aarch64_neonx2.o LD [M] /var/lib/dkms/zfs/0.8.3/build/module/zfs/zfs.o Building modules, stage 2. MODPOST 8 modules FATAL: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'preempt_schedule_notrace' make[4]: *** [scripts/Makefile.modpost:94: __modpost] Error 1 make[3]: *** [Makefile:1647: modules] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-5.4.0-1015-raspi' make[2]: *** [Makefile:30: modules] Error 2 make[2]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module' make[1]: *** [Makefile:807: all-recursive] Error 1 make[1]: Leaving directory '/var/lib/dkms/zfs/0.8.3/build' make: *** [Makefile:676: all] Error 2 Note that Ubuntu currently doesn't support/provide a preemptible arm64 kernel so this hasn't been a problem so far. [Test Case] Install zfs-dkms on an arm64 system that has a PREEMPT kernel installed. [Fix] Redefine preempt_schedule_notrace() to preempt_schedule() in the ZFS module (only for arm64 and if PREEMPTION and BLK_CGROUP are both enabled). preempt_schedule() is not a GPL symbol. [Regression Potential] Per comment in the kernel source, preempt_schedule_notrace() is required when tracing is enabled. As long as tracing is not enabled, this 'fix' should not cause any issues. Problems due to this change could show up as kernel splats like: === [ INFO: suspicious RCU usage. ] 3.10.0-rc2+ #1 Not tainted --
[Kernel-packages] [Bug 1892347] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403412/+files/WifiSyslog.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send
[Kernel-packages] [Bug 1892347] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403403/+files/CurrentDmesg.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to s
[Kernel-packages] [Bug 1892347] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403410/+files/ProcModules.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to sen
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Had to login on different interface (ib0) and unload and load hns3 module to get primary network up. Then I could run apport-collect 1892347. -- 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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send ma
[Kernel-packages] [Bug 1892347] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403409/+files/ProcInterrupts.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5)
[Kernel-packages] [Bug 1892347] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403406/+files/ProcCpuinfo.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to sen
[Kernel-packages] [Bug 1892347] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403408/+files/ProcEnviron.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to sen
[Kernel-packages] [Bug 1892347] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403407/+files/ProcCpuinfoMinimal.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF fail
[Kernel-packages] [Bug 1892347] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403411/+files/UdevDb.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox m
[Kernel-packages] [Bug 1892347] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403404/+files/Lspci.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox mes
[Kernel-packages] [Bug 1892347] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403405/+files/Lsusb.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/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox mes
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
apport information ** Tags added: apport-collected ** Description changed: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.280295] hns3 :7d:00.0: inform reset to vf(3) failed -5! [80001.305621] hns3 :7d:00.0 enp125s0f0: link down [80001.413473] hns3 :7d:00.0: prepare wait ok [80001.523836] hns3 :7d:00.0: The firmware version is 01092806 [80001.530925] hns3 :7d:00.0: Reset done, hclge driver ini
[Kernel-packages] [Bug 1892483] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1892483 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1892483 Title: Synaptics TouchPad not getting detected Status in linux package in Ubuntu: Incomplete Bug description: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+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 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations
Hi, please let me recommend a different approach to get the kernel from proposed installed: # the package 'software-properties-common' contains the 'add-apt-repository' tool and should be installed by default these days, but anyway: $ sudo apt install software-properties-common # enable the proposed section of the Ubuntu archive: $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed restricted main universe" # the above should trigger an archive index update automatically these days, but anyway: $ sudo apt update # will see several kernel related packages: $ apt list --upgradable | grep -i ^linux-image linux-headers-generic/focal-proposed,focal-proposed 5.4.0.44.48 s390x [upgradable from: 5.4.0.42.46] linux-image-generic/focal-proposed,focal-proposed 5.4.0.44.48 s390x [upgradable from: 5.4.0.42.46] linux-libc-dev/focal-proposed,focal-proposed 5.4.0-44.48 s390x [upgradable from: 5.4.0-42.46] linux-source-5.4.0/focal-proposed,focal-proposed 5.4.0-44.48 all [upgradable from: 5.4.0-42.46] linux-source/focal-proposed,focal-proposed 5.4.0.44.48 all [upgradable from: 5.4.0.42.46] linux-tools-common/focal-proposed,focal-proposed 5.4.0-44.48 all [upgradable from: 5.4.0-42.46] linux-tools-generic/focal-proposed,focal-proposed 5.4.0.44.48 s390x [upgradable from: 5.4.0.42.46] # you can now update to the new kernel packages (aka install them) in different way: # 1) just install the package that's there (and trust that it's the latest version): $ sudo apt install --install-recommends linux-image-generic ... # 2) or by explicitly specifying the version number: $ sudo apt install --install-recommends linux-image-generic=4.15.0.114.102 # 3) or (and probably easiest) upgrading everything to the latest available level in proposed: $ sudo apt -y -q full-upgrade ... # you may see messages like these: ┌───┤ Pending kernel upgrade ├┐ │ │ │ Newer kernel available │ │ │ │ The currently running kernel version is 5.4.0-42-generic which is not │ │ the expected kernel version . │ │ │ │ Restarting the system to load the new kernel will not be handled│ │ automatically, so you should consider rebooting.│ │ │ │ │ │ │ └─┘ ┌┤ Daemons using outdated libraries ├─┐ │ │ │ │ │ Which services should be restarted? │ │ │ │[ ] dbus.service │ │[ ] libvirtd.service │ │[ ] systemd-logind.service │ │[ ] unattended-upgrades.service │ │ │ │ │ │ │ │ │ └─┘ # that just remind you about the needed restart to make the new kernel take effect: # old active: $ uname -a Linux s1lp15 5.4.0-42-generic #46 SMP Thu Jul 16 12:06:43 UTC 2020 s390x s390x s390x GNU/Linux $ sudo reboot exit $ ssh ubuntu@zlin42 ... # new active: $ uname -a Linux s1lp15 5.4.0-44-generic #48-Ubuntu SMP Tue Aug 11 06:37:25 UTC 2020 s390x s390x s390x GNU/Linux # if the kernel source package was installed too, you can even quickly double-check if the patch from this particular LP bug is in by looking up (grep) the LP bug number:: $ dpkg -l | grep "^.. linux-source*" ii linux-source 5.4.0.44.48 all Linux kernel source with Ubuntu patches ii linux-source-5.4.05.4.0-44.48 all Linux kernel source for version 5.4.0 with Ubuntu patches $ apt changelog linux-source-5.4.0 | grep -C2 1882088 * [UBUNTU 20.04] smc: SMC connections hang with later-level implementations (LP: #1882088) - net/smc: tolerate future SMCD versions You can now do the verification ... Hope this helps! -- You received this bug notification b
[Kernel-packages] [Bug 1861925] Re: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255
Oh, is there a way to try out that patch? if yes how? -- 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/1861925 Title: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255 Status in Pop!_OS: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, I have a acer aspire a315-41 laptop, it has BIOS 1.15, Ubuntu 19.10, Kernel stock 5.3, and 5.5.0. I have a problem with the Backlight. I can not control. According to: https://wiki.ubuntu.com/Kernel/Debugging/Backlight It is : Backlight control does not work, but there are entries in /sys/class/backlight. The problem is as far I could find: sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat brightness 135 sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat actual_brightness 43500 sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat max_brightness 255 The brightness read from the HW is not in the range, and when I change the brightness by the keys the value in the brightness file changes too, but the actual_brightness is stuck at the value 43500... I have tried all the steps mentioned in https://wiki.ubuntu.com/Kernel/Debugging/Backlight Actually I have tried all these kernel startup parameter variants without luck: GRUB_CMDLINE_LINUX_DEFAULT="" #GRUB_CMDLINE_LINUX_DEFAULT="video.use_native_backlight=1" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=" #GRUB_CMDLINE_LINUX_DEFAULT="video.use_bios_initial_backlight=0" #GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dcfeaturemask=0x4 amdgpu.abmlevel=2" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=video amdgpu.abmlevel=1" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=Linux acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=video" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" I guess the fwts has found also this as an error: autobrightness: Automated LCD brightness test. Test 1 of 2: Test for maximum and actual brightness. PASSED: Test 1, Maximum brightness for amdgpu_bl0 is 255 which is sane. FAILED [HIGH] BrightnessOutofRange: Test 1, Actual brightness for amdgpu_bl0 not in range 0..255. Test 2 of 2: Change actual brightness. FAILED [MEDIUM] BrightnessMismatch: Test 2, 256 brightness levels did not match the brightnesss level just set for backlight amdgpu_bl0. The failed brightness levels were: 0-255. It would be great if someone could help set the HW brightness back to the normal range. If you need any more debug files please let me know! Thanks, Regards, Sandor To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1861925/+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 1892483] Re: Synaptics TouchPad not getting detected
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+attachment/5403386/+files/lspci-vnvn.log -- 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/1892483 Title: Synaptics TouchPad not getting detected Status in linux package in Ubuntu: New Bug description: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+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 1892483] Re: Synaptics TouchPad not getting detected
** Attachment added: "xinput" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+attachment/5403387/+files/xinput -- 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/1892483 Title: Synaptics TouchPad not getting detected Status in linux package in Ubuntu: New Bug description: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+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 1892483] [NEW] Synaptics TouchPad not getting detected
Public bug reported: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1892483/+attachment/5403385/+files/devices -- 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/1892483 Title: Synaptics TouchPad not getting detected Status in linux package in Ubuntu: New Bug description: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+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 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
Oh I see, so this would not have happened with the official dkms package. Thanks. In that case yes, wont-fix. ** Changed in: backport-iwlwifi-dkms (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: backport-iwlwifi-dkms (Ubuntu Bionic) Assignee: Stefan Bader (smb) => (unassigned) -- 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/1892163 Title: Major networking regression linux-image-5.4.0-42-generic Status in backport-iwlwifi-dkms package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Bionic: Won't Fix Status in linux source package in Bionic: Invalid Status in backport-iwlwifi-dkms source package in Focal: Invalid Status in linux source package in Focal: Invalid Bug description: When booting into linux-image-5.4.0-42-generic networking grinds to a halt. It is 1x times slower than usual. Selecting an older kernel like linux-image-5.3.0-62-generic makes networking normal again. Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 Date: Wed Aug 19 11:11:51 2020 InstallationDate: Installed on 2019-11-19 (273 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1892163/+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 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E/F
Affecting Focal P8 as well Note that you will have to review it directly on jenkins, the whole test suite terminates at the ftracetest ** Summary changed: - [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E + [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E/F ** Tags added: 5.4 focal sru-20200810 -- 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/1888332 Title: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E/F Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node) # selftests: powerpc/dscr: dscr_inherit_exec_test # test: dscr_inherit_exec_test # tags: git_version:unknown # Parent DSCR 1 was not inherited over exec (kernel value) # Child didn't exit cleanly # failure: dscr_inherit_exec_test not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888332/+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 1888334] Re: [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E/F
Affecting Focal P8 as well Note that you will have to review it directly on jenkins, the whole test suite terminates at the ftracetest ** Summary changed: - [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E + [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E/F ** Tags added: 5.4 focal sru-20200810 -- 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/1888334 Title: [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E/F Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (skipped with P9 node) # selftests: powerpc/tm: tm-resched-dscr # test: tm_resched_dscr # tags: git_version:unknown # Binding to cpu 8 # main test running as pid 142637 # Check DSCR TM context switch: FAIL # failure: tm_resched_dscr not ok 1 selftests: powerpc/tm: tm-resched-dscr # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888334/+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 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
For the one available in Bionic, version 7906-0ubuntu4~18.04.2 latest updated for bug 1886911, it compiles, but no ko will be installed. -- 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/1892163 Title: Major networking regression linux-image-5.4.0-42-generic Status in backport-iwlwifi-dkms package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Status in backport-iwlwifi-dkms source package in Focal: Invalid Status in linux source package in Focal: Invalid Bug description: When booting into linux-image-5.4.0-42-generic networking grinds to a halt. It is 1x times slower than usual. Selecting an older kernel like linux-image-5.3.0-62-generic makes networking normal again. Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 Date: Wed Aug 19 11:11:51 2020 InstallationDate: Installed on 2019-11-19 (273 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1892163/+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 1888339] Re: [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E
Affecting Focal P8 as well Note that you will have to review it directly on jenkins, the whole test suite terminates at the ftracetest ** Tags added: 5.4 focal ** Summary changed: - [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E + [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E/F ** Tags removed: 5.4 focal ** Tags added: sru-20200810 -- 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/1888339 Title: [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E/F Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node) # selftests: powerpc/ptrace: ptrace-tar # test: ptrace_tar # tags: git_version:f21e446-dirty # [User Write (Running)] TAR: 10 PPR: 4 DSCR: 100 # [User Read (Running)] TAR: 20 PPR: 8 DSCR: 0 # [Ptrace Read (Running)]TAR: 10 PPR: 4 DSCR: 100 # [Ptrace Write (Running)] TAR: 20 PPR: 8 DSCR: 200 # failure: ptrace_tar not ok 4 selftests: powerpc/ptrace: ptrace-tar # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888339/+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 1869032] Re: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8
Eoan EOL, closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869032 Title: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: Issue found on P8 node modoc with Eoan (5.3.0-43.36) (Note that this test has passed with P9 node baltar without any traces in syslog) The ubuntu_kernel_selftests hangs: 15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack 15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # Opening 127.0.0.1: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening in6addr_any: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # selftests: net: tls 15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected status (4) == 0 (0) 15:17:26 DEBUG| [stdout] # Alarm clock 15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351 (And test continues) It looks like it's the selftests: net: tls that's causing this issue. If you ssh to the node, the following trace could be found in dmesg: Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Oops: Exception in kernel mode, sig: 4 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270 REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic) MSR: 9288b033 CR: 28002862 XER: 2000 CFAR: c000dfc4 IRQMASK: 0 GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 GPR04: c00f5afc c00fc97839b8 GPR08: c00f5afc c00ff9a13780 GPR12: 88002462 c00eb380 GPR16: 0ac875961368 0ac875960d38 0ac875960d90 GPR20: 7c6b4ef0 c00e3996dc48 GPR24: c04a9d70 ea60 GPR28: c00c0398c740 cab32e70 c00f7ecebd00 NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] Call Trace: [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] (unreliable) [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140 [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70 [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50 [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0 [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280 [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0 [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0 [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0 [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130 [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0 [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170 [c00fc9783e20] [c000b388] system_call+0x5c/0x70 Instruction dump: <> ---[ end trace 8961ea39a6f2dd08 ]--- BUG: Kernel NULL pointer dereference at 0x Faulting instruction address: 0xc020bd74 Oops: Kernel access of bad area, sig: 11 [#2] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_m
[Kernel-packages] [Bug 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
Thanks, You-Sheng and Hui, I would suggest (and maybe that is what you meant) to use dkms (remove or uninstall for the 5.4 kernel version) to drop the built dkms module from the 5.4 kernel as a first test. That way it is available for any older kernel as long as they are kept. If this works and it is unlikely to have to go back to 5.3, then it is better to completely remove the backport driver. Otherwise it gets rebuild/installed for every kernel update. I would also take back (at least for now) the wont-fix status for the dkms package. With the 5.4 kernel being the latest HWE kernel for Bionic, we should see whether we can make it not compiling for 5.4. ** Changed in: backport-iwlwifi-dkms (Ubuntu Bionic) Status: Won't Fix => Triaged ** Changed in: backport-iwlwifi-dkms (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: backport-iwlwifi-dkms (Ubuntu Bionic) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1892163 Title: Major networking regression linux-image-5.4.0-42-generic Status in backport-iwlwifi-dkms package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Status in backport-iwlwifi-dkms source package in Focal: Invalid Status in linux source package in Focal: Invalid Bug description: When booting into linux-image-5.4.0-42-generic networking grinds to a halt. It is 1x times slower than usual. Selecting an older kernel like linux-image-5.3.0-62-generic makes networking normal again. Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 Date: Wed Aug 19 11:11:51 2020 InstallationDate: Installed on 2019-11-19 (273 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1892163/+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 1891998] Re: Fix non-working Goodix touchpad after system sleep
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1891998 Title: Fix non-working Goodix touchpad after system sleep Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] After system sleep, Goodix touchpad doesn't work anymore. [Fix] Add a delay after issuing SET_POWER_ON command. [Test] With the patch applied, Goodix touchpad still works after system sleep. [Regression Potential] The original delay between SET_POWER_ON and RESET was increaed to 60ms, so the the driver becomes much more forgiving on power management. Hence I am not seeing any major potential regression risk here. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1891998/+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 1892386] Re: test_bpf in net from ubuntu_kernel_selftests ADT failure with xenial/linux s390x
*** This bug is a duplicate of bug 1868243 *** https://bugs.launchpad.net/bugs/1868243 ** This bug has been marked a duplicate of bug 1868243 ld_abs+vlan_push/pop from test_bpf in ubuntu_bpf_jit will fail on X s390x -- 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/1892386 Title: test_bpf in net from ubuntu_kernel_selftests ADT failure with xenial/linux s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: Testing failed with xenial/linux 4.4.0-189.219 on s390x: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200813_225543_d8951@/log.gz Another issue with this testcase has been fixed recently by bug 1879752, however this is still failing on s390x (it passes on the other arches now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892386/+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 1892010] Re: [SRU] Fix acpi backlight issue on some thinkpads
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1892010 Title: [SRU] Fix acpi backlight issue on some thinkpads Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Bug description: [Impact] On some ThinkPads, the BIOS reported invalid acpi backlight implement . Then backlight can't be changed because OS use acpi backlight by default. [Fix] Check acpi backlight mode, disable it if invalid. [Test Case] Verified on 3 models of thinkpad include Intel/NV/AMD GPU with positive results. [Regression Potential] Low Most ThinkPads now use native backlight control by default. Check the false acpi mode correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1892010/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
That should be a regression introduced in bug 1861451, which is to allow gathering information as root under non-gui env. -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Committed Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: Updated Description to match SRU requirements for bionic [Impact] linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. [Test Case] 1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. [Regression Potential] Very limited, as we are just adding a symlink from linux-firmware to the linux source package hook. this change has been available in Focal and Groovy without problem Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
https://bugzilla.kernel.org/show_bug.cgi?id=206411#c9 stated it may relate to the power sequence of a specific platform. I have also RTL8822BE installed, but it works on every Focal/Groovy + 5.4.0-42/5.7-rc1/5.8.0-16/5.9-rc1 combination. -- 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/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Confirmed Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]---
