[Kernel-packages] [Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
I also have this problem on my X1C7 running Linux Mint 20 with kernel 5.4.0-42-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) 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/alsa-ucm-conf/+bug/1872108/+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 1892822] Re: Xenial update: 4.4.233 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + 4.4.233 upstream stable release + from git://git.kernel.org/ -4.4.233 upstream stable release -from git://git.kernel.org/ + + * xfs: don't call xfs_da_shrink_inode with NULL bp + * net: phy: mdio-bcm-unimac: fix potential NULL dereference in unimac_mdio_probe() + * media: rc: prevent memory leak in cx23888_ir_probe + * ath9k_htc: release allocated buffer if timed out + * ath9k: release allocated buffer if timed out + * nfs: Move call to security_inode_listsecurity into nfs_listxattr + * PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge + * drm/amdgpu: Prevent kernel-infoleak in amdgpu_info_ioctl() + * drm: hold gem reference until object is no longer accessed + * f2fs: check memory boundary by insane namelen + * f2fs: check if file namelen exceeds max value + * ARM: 8986/1: hw_breakpoint: Don't invoke overflow handler on uaccess watchpoints + * fbdev: Detect integer underflow at "struct fbcon_ops"->clear_margins. + * rds: Prevent kernel-infoleak in rds_notify_queue_get() + * net/x25: Fix x25_neigh refcnt leak when x25 disconnect + * net/x25: Fix null-ptr-deref in x25_disconnect + * sh: Fix validation of system call number + * net: lan78xx: add missing endpoint sanity check + * net: lan78xx: fix transfer-buffer memory leak + * mlxsw: core: Increase scope of RCU read-side critical section + * mac80211: mesh: Free ie data when leaving mesh + * nfc: s3fwrn5: add missing release on skb in s3fwrn5_recv_frame + * net: ethernet: ravb: exit if re-initialization fails in tx timeout + * Revert "i2c: cadence: Fix the hold bit setting" + * xen-netfront: fix potential deadlock in xennet_remove() + * x86/i8259: Use printk_deferred() to prevent deadlock + * random32: update the net random state on interrupt and activity + * ARM: percpu.h: fix build error + * random: fix circular include dependency on arm64 after addition of percpu.h + * random32: remove net_rand_state from the latent entropy gcc plugin + * random32: move the pseudo-random 32-bit definitions to prandom.h + * ext4: fix direct I/O read error + * USB: serial: qcserial: add EM7305 QDL product ID + * ALSA: seq: oss: Serialize ioctls + * Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt() + * Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt() + * Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt() + * vgacon: Fix for missing check in scrollback handling + * mtd: properly check all write ioctls for permissions + * net/9p: validate fds in p9_fd_open + * drm/nouveau/fbcon: fix module unload when fbcon init has failed for some reason + * cfg80211: check vendor command doit pointer before use + * igb: reinit_locked() should be called with rtnl_lock + * atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent + * tools lib traceevent: Fix memory leak in process_dynamic_array_len + * binder: Prevent context manager from incrementing ref 0 + * ipv4: Silence suspicious RCU usage warning + * ipv6: fix memory leaks on IPV6_ADDRFORM path + * Revert "vxlan: fix tos value before xmit" + * net: lan78xx: replace bogus endpoint lookup + * usb: hso: check for return value in hso_serial_common_create() + * vxlan: Ensure FDB dump is performed under RCU + * Smack: fix use-after-free in smk_write_relabel_self() + * tracepoint: Mark __tracepoint_string's __used + * udp: drop corrupt packets earlier to avoid data corruption + * gpio: fix oops resulting from calling of_get_named_gpio(NULL, ...) + * EDAC: Fix reference count leaks + * m68k: mac: Don't send IOP message until channel is idle + * m68k: mac: Fix IOP status/control register writes + * ARM: at91: pm: add missing put_device() call in at91_pm_sram_init() + * ARM: socfpga: PM: add missing put_device() call in socfpga_setup_ocram_self_refresh() + * drm/tilcdc: fix leak & null ref in panel_connector_get_modes + * Bluetooth: add a mutex lock to avoid UAF in do_enale_set + * fs/btrfs: Add cond_resched() for try_release_extent_mapping() stalls + * drm/radeon: Fix reference count
[Kernel-packages] [Bug 1892822] Re: Xenial update: 4.4.233 upstream stable release
The conflict in #2 is due to the change 43711a479c1eb38a6c4836e31fddd5599aa95884 "bcache: fix high CPU occupancy during journal" which was applied as part of https://bugs.launchpad.net/bugs/1784665. -- 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/1892822 Title: Xenial update: 4.4.233 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.233 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892822/+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 1892822] Re: Xenial update: 4.4.233 upstream stable release
Encountered minor conflict when applying: bcache: allocate meta data pages as compound pages in journal.c -- 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/1892822 Title: Xenial update: 4.4.233 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.233 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892822/+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 1892822] Re: Xenial update: 4.4.233 upstream stable release
Skipped: - xfs: don't call xfs_da_shrink_inode with NULL bp (applied already for CVE-2018-13094) - net: phy: mdio-bcm-unimac: fix potential NULL dereference in unimac_mdio_probe() (fixed already for CVE-2018-8043) ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-13094 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-8043 -- 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/1892822 Title: Xenial update: 4.4.233 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.233 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892822/+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 1892822] [NEW] Xenial update: 4.4.233 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.233 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892822 Title: Xenial update: 4.4.233 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.233 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892822/+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 1892422] 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 1892422 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 ** Tags added: 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/1892422 Title: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04 Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Bug description: After setting up pci pass through for a virtual function it did not show up as an interface in Ubuntu 20.04, it did however show up as a PCI device. After reverting back to 18.04 with exactly the same configuration the interface showed up as expected. Bellow is the configuration and output for both 18.04 and 20.04. virt-install --import --connect qemu:///system --name emsk8sm1 --ram 8192 --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio --disk cidata.img,device=cdrom,format=img --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04 --network bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea --hostdev 3b:02.5 --console pty,target_type=serial --graphics type=vnc,listen=0.0.0.0 --noautoconsole --autostart -v Configuration of 18.04 where the passthrough works Version Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [interface shows inside of vm ens6] 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: ens6: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff Configuration of 20.04 where the VF shows as a PCI device but does not show as an interface Version Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [ens 6 does not show as an interface} 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: tunl0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 4: sit0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892422/+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 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04
--- B - Host changed, Guest stayed --- In this case I think the biggest moving pieces are: 1. Host Kernel 2. Host qemu 3. Host libvirt (to a much smaller extend) We can do some A/B tests to sort things out. #1 install linux-generic-hwe-18.04 which will bring a 5.4 kernel to Bionic #2,#3 install new qemu/libvirt in Bionic via `sudo add-apt-repository cloud-archive:ussuri` That should end up in a matrix like kernel-old kernel-new qemu-old ? ? qemu-new ? ? Would be useful to know these. ** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892422 Title: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04 Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: After setting up pci pass through for a virtual function it did not show up as an interface in Ubuntu 20.04, it did however show up as a PCI device. After reverting back to 18.04 with exactly the same configuration the interface showed up as expected. Bellow is the configuration and output for both 18.04 and 20.04. virt-install --import --connect qemu:///system --name emsk8sm1 --ram 8192 --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio --disk cidata.img,device=cdrom,format=img --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04 --network bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea --hostdev 3b:02.5 --console pty,target_type=serial --graphics type=vnc,listen=0.0.0.0 --noautoconsole --autostart -v Configuration of 18.04 where the passthrough works Version Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [interface shows inside of vm ens6] 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: ens6: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff Configuration of 20.04 where the VF shows as a PCI device but does not show as an interface Version Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [ens 6 does not show as an interface} 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: tunl0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 4: sit0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892422/+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 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04
--- A - Host stayed, Guest changed --- If that is the case then we can mostly ignore the Host. Never the less knowing the details what is used in the host is helpful. As mentioned per your uname I assume you have `linux-kvm` used in the guest. That is meant as a reduced kernel for virtual environments. Chances now are high that: 1. the required intel module is no more built for this -kvm kernel 2. the required intel module is built but moved from the base to the extra modules In general please check (and report here) on both guests - lsmod (will show us if a module is missing on the guest without net) - lspci -v (will show us which driver is used - if any - on the passed through intel card. After we have above data, please try to install the kernel that isn't reduced. Should be: $ apt install linux-image-generic $ apt remove linux-image-kvm $ reboot Did the situation now resolve? Does the listing of lsmod and lspci now report an additional driver loaded compared to before? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892422 Title: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04 Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: After setting up pci pass through for a virtual function it did not show up as an interface in Ubuntu 20.04, it did however show up as a PCI device. After reverting back to 18.04 with exactly the same configuration the interface showed up as expected. Bellow is the configuration and output for both 18.04 and 20.04. virt-install --import --connect qemu:///system --name emsk8sm1 --ram 8192 --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio --disk cidata.img,device=cdrom,format=img --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04 --network bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea --hostdev 3b:02.5 --console pty,target_type=serial --graphics type=vnc,listen=0.0.0.0 --noautoconsole --autostart -v Configuration of 18.04 where the passthrough works Version Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [interface shows inside of vm ens6] 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: ens6: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff Configuration of 20.04 where the VF shows as a PCI device but does not show as an interface Version Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [ens 6 does not show as an interface} 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: tunl0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 4: sit0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892422/+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 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04
Hi Neil, thanks for the report. I haven't seen/heard about this particular issue yet, maybe it is related to the specific intel model and/or firmware version - so if you could derive that from the host and let us know that might be helpful (if someone can find a similar model to cross verify then). That applies to both cases below. It is not entirely clear from your report if: A) you have kept the host the same (if so please report what you used) and only switched the guest. B) you have used the same host in both cases and ONLY switched the guest between 18.04/20.04 ? Since your kernel versions have the -kvm suffix (A) is more likely, but let me guide you to the next steps for both. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892422 Title: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04 Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: After setting up pci pass through for a virtual function it did not show up as an interface in Ubuntu 20.04, it did however show up as a PCI device. After reverting back to 18.04 with exactly the same configuration the interface showed up as expected. Bellow is the configuration and output for both 18.04 and 20.04. virt-install --import --connect qemu:///system --name emsk8sm1 --ram 8192 --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio --disk cidata.img,device=cdrom,format=img --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04 --network bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea --hostdev 3b:02.5 --console pty,target_type=serial --graphics type=vnc,listen=0.0.0.0 --noautoconsole --autostart -v Configuration of 18.04 where the passthrough works Version Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [interface shows inside of vm ens6] 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: ens6: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff Configuration of 20.04 where the VF shows as a PCI device but does not show as an interface Version Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [ens 6 does not show as an interface} 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: tunl0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 4: sit0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892422/+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
Spotted on 4.15.0-114.115 as well. ** Summary changed: - [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E/F + [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F ** Tags added: 4.15 bionic ** Tags added: xenial -- 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 B/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
This failure can be found on .15.0-114.115 / 4.15.0-114.115~16.04.1 PowerPC as well ** Tags added: 4.15 bionic xenial ** Summary changed: - [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E/F + [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on B/E/F -- 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 B/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 1757143] Re: /proc/modules has Null references causing python parsing issues
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757143 Title: /proc/modules has Null references causing python parsing issues Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in plainbox-provider-checkbox package in Ubuntu: Fix Released Bug description: EDIT: this originally looked like some sort of regression in the module_resource script of plainbox-provider-resource, however, on diving in a bit it seems the root cause is that /proc/modules in 4.15 is different than in previous kernels. This is a line from 4.15's /proc/modules data: e1000e 249856 0 - Live 0x (null) And this is the same module info from 4.13: e1000e 249856 0 - Live 0x That null character at the end appears to be causing the script to choke. For that reason, because /proc/modules has somehow changed to include null references (0xNULL is invalid, where 0x000 is parsable), I've added a kernel task to this bug. Original Summary: I ran into this issue (and came across some further glitches) while running canonical-certification-server on Ubuntu Server 18.04 on s390x (having 16.04 full selected in canonical-certification-server user interface): $ /usr/lib/plainbox-provider-resource-generic/bin/module_resource Traceback (most recent call last): File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 73, in sys.exit(main()) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 62, in main for module in modules: File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 57, in get_modules yield get_module(line) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 49, in get_module "offset": int(offset, 16)} ValueError: invalid literal for int() with base 16: '0x' result file is attached to the ticket, as well as the console log ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1757143/+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 B/E/F
This failure can be found on 4.15.0-114.115 / 4.15.0-114.115~16.04.1 PowerPC as well ** Summary changed: - [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E/F + [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on B/E/F ** Tags added: 4.15 bionic xenial -- 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 B/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 1829359] Re: TRACE_syscall.ptrace_syscall_errno in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC
Passed on X-4.15.0-114.115~16.04.1 and B-4.15.0-114.115 PowerPC [ RUN ] TRACE_syscall.ptrace_syscall_errno [ OK ] TRACE_syscall.ptrace_syscall_errno Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829359 Title: TRACE_syscall.ptrace_syscall_errno in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Bug description: This test will fail on Bionic / Cosmic PowerPC: [ RUN ] TRACE_syscall.ptrace_syscall_errno seccomp_bpf.c:1826:TRACE_syscall.ptrace_syscall_errno:Expected -(-3) (3) == (*__errno_location ()) (38) TRACE_syscall.ptrace_syscall_errno: Test failed at step #13 This test will pass on PowerPC with Disco kernel. As this issue can be reproduced with the upsteam kernel tree, so it looks like a kernel issue instead of a test case issue to me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 16 09:48:18 2019 ProcLoadAvg: 0.38 0.64 0.48 1/1316 6114 ProcLocks: 1: POSIX ADVISORY WRITE 1767 00:17:402 0 EOF 2: POSIX ADVISORY WRITE 3941 00:17:825 0 EOF 3: FLOCK ADVISORY WRITE 3492 00:17:390 0 EOF 4: FLOCK ADVISORY WRITE 3947 00:17:820 0 EOF 5: POSIX ADVISORY WRITE 3872 00:17:799 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-20-generic (buildd@bos02-ppc64el-019) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21~18.04.1-Ubuntu SMP Wed May 8 08:51:08 UTC 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829359/+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 1829363] Re: TRACE_syscall.ptrace_syscall_faked in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC
Passed on X-4.15.0-114.115~16.04.1 and B-4.15.0-114.115 PowerPC [ RUN ] TRACE_syscall.ptrace_syscall_faked [ OK ] TRACE_syscall.ptrace_syscall_faked Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829363 Title: TRACE_syscall.ptrace_syscall_faked in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Bug description: This test will fail on Bionic / Cosmic PowerPC: [ RUN ] TRACE_syscall.ptrace_syscall_faked seccomp_bpf.c:1837:TRACE_syscall.ptrace_syscall_faked:Expected 45000 (45000) == syscall(207) (18446744073709551615) TRACE_syscall.ptrace_syscall_faked: Test failed at step #13 [ FAIL ] TRACE_syscall.ptrace_syscall_faked This test will pass on PowerPC with Disco kernel. As this issue can be reproduced with the upsteam kernel tree, so it looks like a kernel issue instead of a test case issue to me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 16 09:59:19 2019 ProcLoadAvg: 0.07 0.40 0.68 1/1315 7583 ProcLocks: 1: POSIX ADVISORY WRITE 1767 00:17:402 0 EOF 2: POSIX ADVISORY WRITE 3941 00:17:825 0 EOF 3: FLOCK ADVISORY WRITE 3492 00:17:390 0 EOF 4: FLOCK ADVISORY WRITE 3947 00:17:820 0 EOF 5: POSIX ADVISORY WRITE 3872 00:17:799 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-20-generic (buildd@bos02-ppc64el-019) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21~18.04.1-Ubuntu SMP Wed May 8 08:51:08 UTC 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 0) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829363/+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 1873809] Re: Make linux-kvm bootable in LXD VMs
We weren't planning to as the previous releases (xenial and bionic) did not have "-kvm" image and their default image includes an initrd making them boot just fine under LXD. So it's really just groovy+focal that we need before we can start using those images. focal has been taken care of so we're just waiting for linux-kvm to hit the release pocket on groovy before we can switch over to those. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Released Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - 00
[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E/F
This failure can be found on 4.15.0-114.115~16.04.1 PowerPC as well -- 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 1884900] Re: Touchpad 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/1884900 Title: Touchpad not working Status in linux package in Ubuntu: Expired Bug description: Dear Sir, I have updated ubuntu 18.04 to 20.04 in the last 4 days. My laptop's touchpad worked well in the last system, but when I have updated it to 20.04 then touchpad not working, when I started my laptop. I have use a mouse. When I have start my laptop with connected mouse then touchpad not work. but, when I have started a laptop without connected with mouse then touchpad worked. Solve this issue properly. Thank you... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spshubham 1767 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 12:53:16 2020 HibernationDevice: RESUME=UUID=473a994d-cd87-4373-94ae-e2ff8edce101 InstallationDate: Installed on 2020-06-18 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=13763414-9331-414c-b5ad-ef7d3fa37ff2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-20 (3 days ago) dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron3521:pvrA16:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884900/+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 1892746] Re: Ubuntu doesn't use Bluetooth headset when connected automatically
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1866194, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1866194 External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. -- 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/1892746 Title: Ubuntu doesn't use Bluetooth headset when connected automatically Status in bluez package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu connects to it automatically and my headset says "Connected!". But the audio still comes out of my PC's main speakers. I have to disconnect my headset in Bluetooth settings and re-connect it for the audio to go to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892746/+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 1885131] Re: Intel 7260 [8086:08b2] Subsystem [8086:c270] Wifi firmware issue and crash
[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/1885131 Title: Intel 7260 [8086:08b2] Subsystem [8086:c270] Wifi firmware issue and crash Status in linux package in Ubuntu: Expired Bug description: I have had my wifi adaptor crash a few times. Basically the wifi icon disappears and I'm off the network. I can't get it back until I reboot the laptop. However, it seems that there are issues reported in dmesg which indicate there are other firmware related issues. I'm on Ubunu Budgie 20.04 Ubuntu 5.4.0-37.41-generic 5.4.41 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pbulteel 2768 F pulseaudio /dev/snd/controlC0: pbulteel 2768 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 25 14:05:58 2020 InstallationDate: Installed on 2020-06-04 (20 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20ARS3C101 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fjtg3n@/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_fjtg3n ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: GJETA3WW (2.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARS3C101 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJETA3WW(2.53):bd08/26/2019:svnLENOVO:pn20ARS3C101:pvrThinkPadT440s:rvnLENOVO:rn20ARS3C101:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARS3C101 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885131/+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 1885128] Re: Touchpad not working and not visible in the list of devices
[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/1885128 Title: Touchpad not working and not visible in the list of devices Status in linux package in Ubuntu: Expired Bug description: My touchpad is not responsive on my computer. I couldnt find my touchpad when I executed cat /proc/bus/input/devices. Mine is a Thinkpad E450 model. This is the output from the command in the terminal: 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=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 U: Uniq= H: Handlers=kbd event1 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/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor=17aa Product=5054 Version=4101 N: Name="ThinkPad Extra Buttons" P: Phys=thinkpad_acpi/input0 S: Sysfs=/devices/platform/thinkpad_acpi/input/input5 U: Uniq= H: Handlers=rfkill kbd event3 B: PROP=0 B: EV=13 B: KEY=10040 0 1804 0 501000 0 1701b02102004 c000280041114000 10e 0 B: MSC=10 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/input6 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04f2 Product=b444 Version=0016 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-8/button S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-8/2-8:1.0/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input13 U: Uniq= H: Handlers=event11 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:1b.0/sound/card1/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor= Product=3825 Version=0111 N: Name=" USB OPTICAL MOUSE" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/0003::3825.0002/input/input20 U: Uniq= H: Handlers=mouse0 event13 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shivanand 3169 F pulseaudio /dev/snd/controlC0: shivanand 3169 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 18:25:50 2020 InstallationDate: Installed on 2018-11-29 (574 days ago) InstallationMedia: Ubuntu 18.10
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
I do not recommend that as a solution. The open source 'nouveau' driver generally causes more problems than it solves. And performance is significantly lower than the proprietary driver. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mutter/+bug/1855757/+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 1892746] Re: Ubuntu doesn't use Bluetooth headset when connected automatically
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1892746 Title: Ubuntu doesn't use Bluetooth headset when connected automatically Status in bluez package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu connects to it automatically and my headset says "Connected!". But the audio still comes out of my PC's main speakers. I have to disconnect my headset in Bluetooth settings and re-connect it for the audio to go to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892746/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
^^^ Daniel, I wrote that answer mostly for the bug you mentioned, but as I mentioned in my answer, it fixes the corrupted background bug as well. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mutter/+bug/1855757/+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 1892746] [NEW] Ubuntu doesn't use Bluetooth headset when connected automatically
You have been subscribed to a public bug: When I turn on my Bluetooth headset, Ubuntu connects to it automatically and my headset says "Connected!". But the audio still comes out of my PC's main speakers. I have to disconnect my headset in Bluetooth settings and re-connect it for the audio to go to it. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu doesn't use Bluetooth headset when connected automatically https://bugs.launchpad.net/bugs/1892746 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station
I have the same issue with my Cable Matters USB-C dual 4k DisplayPort docking station and HP Elitebook laptop. In my experience, it does not occur on every disconnect, however each time it does occur, it appears to be preceded by a kernel oops: [114032.828215] usb 2-1: USB disconnect, device number 50 [114032.828220] usb 2-1.3: USB disconnect, device number 51 [114032.828222] usb 2-1.3.2: USB disconnect, device number 58 [114032.828225] usb 2-1.3.2.1: USB disconnect, device number 59 [114032.829619] [drm] DM_MST: stopping TM on aconnector: 660e4f23 [id: 77] [114032.829741] [drm] DM_MST: Disabling connector: 5955f6aa [id: 95] [master: 660e4f23] [114032.829901] [ cut here ] [114032.829902] sysfs group 'power' not found for kobject 'i2c-11' [114032.829920] WARNING: CPU: 3 PID: 42300 at fs/sysfs/group.c:279 sysfs_remove_group+0x7c/0x80 [114032.829921] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm binfmt_misc rfcomm cmac algif_hash algif_skcipher af_alg cdc_ether usbnet snd_usb_audio snd_usbmidi_lib usbhid r8152 mii bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ecc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common bonding aufs evdi(OE) snd_hda_codec_conexant snd_hda_codec_generic overlay ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd iwlmvm nls_iso8859_1 soundcore mac80211 libarc4 edac_mce_amd iwlwifi kvm_amd ccp kvm hp_wmi joydev input_leds sparse_keymap serio_raw wmi_bmof hid_multitouch cfg80211 ucsi_acpi typec_ucsi ipmi_devintf k10temp ipmi_msghandler typec mac_hid hp_wireless sch_fq_codel v4l2loopback(OE) videodev mc parport_pc ppdev lp parport ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq [114032.829978] async_xor async_tx xor uas usb_storage raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic amdgpu crct10dif_pclmul crc32_pclmul amd_iommu_v2 ghash_clmulni_intel gpu_sched i2c_algo_bit ttm aesni_intel drm_kms_helper i2c_hid crypto_simd hid cryptd syscopyarea sysfillrect glue_helper psmouse sysimgblt nvme fb_sys_fops ahci i2c_piix4 drm libahci nvme_core r8169 realtek wmi video i2c_amd_mp2_plat i2c_amd_mp2_pci [114032.830005] CPU: 3 PID: 42300 Comm: kworker/3:0 Tainted: G OE 5.4.0-42-generic #46-Ubuntu [114032.830007] Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.10.00 01/03/2020 [114032.830019] Workqueue: events drm_dp_destroy_connector_work [drm_kms_helper] [114032.830023] RIP: 0010:sysfs_remove_group+0x7c/0x80 [114032.830026] Code: e7 e8 98 b9 ff ff 5b 41 5c 41 5d 5d c3 4c 89 e7 e8 e9 b4 ff ff eb c9 49 8b 55 00 48 8b 33 48 c7 c7 10 de b8 97 e8 6f 9f d1 ff <0f> 0b eb d8 0f 1f 44 00 00 48 85 f6 74 37 55 48 89 e5 41 55 41 54 [114032.830027] RSP: 0018:abccc0363c18 EFLAGS: 00010286 [114032.830029] RAX: RBX: 978f3c60 RCX: 0006 [114032.830030] RDX: 0007 RSI: 0086 RDI: 9a4d5fcd78c0 [114032.830032] RBP: abccc0363c30 R08: 0c98 R09: 0004 [114032.830032] R10: R11: 0001 R12: [114032.830034] R13: 9a4d135f9418 R14: c0369140 R15: c0369140 [114032.830036] FS: () GS:9a4d5fcc() knlGS: [114032.830037] CS: 0010 DS: ES: CR0: 80050033 [114032.830038] CR2: 55e429698c40 CR3: 00040af48000 CR4: 003406a0 [114032.830039] Call Trace: [114032.830047] dpm_sysfs_remove+0x59/0x60 [114032.830050] device_del+0x85/0x370 [114032.830055] cdev_device_del+0x1a/0x40 [114032.830058] i2cdev_detach_adapter+0x87/0xc0 [114032.830060] i2cdev_notifier_call+0x21/0x40 [114032.830064] notifier_call_chain+0x55/0x80 [114032.830067] blocking_notifier_call_chain+0x50/0x70 [114032.830070] device_del+0x7d/0x370 [114032.830072] device_unregister+0x1b/0x60 [114032.830075] i2c_del_adapter+0x238/0x300 [114032.830085] drm_dp_port_teardown_pdt+0x1f/0x40 [drm_kms_helper] [114032.830096] drm_dp_destroy_connector_work+0xa3/0x110 [drm_kms_helper] [114032.830100] process_one_work+0x1eb/0x3b0 [114032.830104] worker_thread+0x4d/0x400 [114032.830108] kthread+0x104/0x140 [114032.830111] ? process_one_work+0x3b0/0x3b0 [114032.830114] ? kthread_park+0x90/0x90 [114032.830118] ret_from_fork+0x22/0x40 [114032.830124] ---[ end trace 5a351113a270c4cc ]--- [114032.830211] [ cut here ] [114032.830213] sysfs group 'power' not found for kobject 'i2c-11' [114032.830228] WARNING: CPU: 3 PID: 42300 at fs/sysfs/group.c:279 sysfs_remove_group+0x7c/0x80 [114032.830229] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm binfmt_misc rfcomm cmac algif_hash algif_skcipher af_alg cdc_ether usbnet snd_usb_audio snd_usbmidi_lib usbhid r8152 mii bnep btusb
[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
N, please don't mark this as invalid. This is the most annoying notification on my wonderful Gnome desktop. It is so premature. First off, it thinks my MX Logitech keyboard is a mouse and secondly, it displays over and over long before the keyboard needs to be charged. I use this keyboard with 2 other operating systems and none of them have this issue. -- 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/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
^^^ That is bug 1892440. It is not relevant here. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mutter/+bug/1855757/+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 1892714] Re: Microphone not working on HP Omen 17
you need to remove "options snd-hda-intel dmic_detect=0", and upload a new dmesg with that removed. -- 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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@John Hoff > enable file... Can you re-attach? I don't see it. > Anyway, thoughts? Do you have any more clarity on how to replay the CORB commands? Take a look at this patch [1]. Use the CORB command recording to write a similar patch. It will contain a 2034-entry long array of hda_verb structs [2]. Each hda_verb contains {Node ID, Verb ID, Payload} Apply your patch, compile, and run. [1] https://github.com/tespeleta/linux/commit/761cca49e9153b7832fa3f887b875e5ad1517892 [2] https://github.com/torvalds/linux/blob/master/include/sound/hda_codec.h#L360-L364 -- 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, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marti
[Kernel-packages] [Bug 1892774] Re: Groovy update: v5.8.3 upstream stable release
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- 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/1892774 Title: Groovy update: v5.8.3 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.8.3 upstream stable release from git://git.kernel.org/ UBUNTU: [Config] update config for ARMADA_AP_CPU_CLK ALSA: hda/realtek - Fix unused variable warning smb3: warn on confusing error scenario with sec=krb5 SMB3: Fix mkdir when idsfromsid configured on mount genirq/affinity: Make affinity setting if activated opt-in genirq: Unlock irq descriptor after errors genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() PCI/ATS: Add pci_pri_supported() to check device or associated PF PCI: Add device even if driver attach failed PCI: qcom: Define some PARF params needed for ipq8064 SoC PCI: qcom: Add support for tx term offset for rev 2.1.0 btrfs: allow use of global block reserve for balance item deletion btrfs: free anon block device right after subvolume deletion btrfs: don't allocate anonymous block device for user invisible roots btrfs: preallocate anon block device at first phase of snapshot creation btrfs: ref-verify: fix memory leak in add_block_entry btrfs: only commit the delayed inode when doing a full fsync btrfs: stop incremening log_batch for the log root tree when syncing log btrfs: only commit delayed items at fsync if we are logging a directory btrfs: remove no longer needed use of log_writers for the log root tree btrfs: don't traverse into the seed devices in show_devname btrfs: pass checksum type via BTRFS_IOC_FS_INFO ioctl btrfs: open device without device_list_mutex btrfs: move the chunk_mutex in btrfs_read_chunk_tree btrfs: relocation: review the call sites which can be interrupted by signal btrfs: add missing check for nocow and compression inode flags btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree btrfs: return EROFS for BTRFS_FS_STATE_ERROR cases btrfs: sysfs: use NOFS for device creation btrfs: don't WARN if we abort a transaction with EROFS btrfs: fix race between page release and a fast fsync btrfs: don't show full path of bind mounts in subvol= btrfs: fix messages after changing compression level by remount btrfs: only search for left_info if there is no right_info in try_merge_free_space btrfs: inode: fix NULL pointer dereference if inode doesn't need compression btrfs: fix memory leaks after failure to lookup checksums during inode logging btrfs: trim: fix underflow in trim length to prevent access beyond device boundary btrfs: make sure SB_I_VERSION doesn't get unset by remount btrfs: fix return value mixup in btrfs_get_extent btrfs: check correct variable after allocation in btrfs_backref_iter_alloc arm64: dts: qcom: sc7180: Drop the unused non-MSA SID arm64: perf: Correct the event index in sysfs dt-bindings: iio: io-channel-mux: Fix compatible string in example code iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw() iio: imu: st_lsm6dsx: reset hw ts after resume xtensa: add missing exclusive access state management xtensa: fix xtensa_pmu_setup prototype cifs: Fix leak when handling lease break for cached root fid powerpc/ptdump: Fix build failure in hashpagetable.c powerpc: Allow 4224 bytes of stack expansion for the signal frame powerpc: Fix circular dependency between percpu.h and mmu.h pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH pinctrl: ingenic: Properly detect GPIO direction when configured for IRQ media: venus: fix multiple encoder crash media: vsp1: dl: Fix NULL pointer dereference on unbind net: ethernet: stmmac: Disable hardware multicast filter net: stmmac: dwmac1000: provide multicast filter fallback irqchip/loongson-liointc: Fix misuse of gc->mask_cache irqchip/gic-v4.1: Ensure accessing the correct RD when writing INVALLR pidfd: Add missing sock updates for pidfd_getfd() net/compat: Add missing sock updates for SCM_RIGHTS selftests/seccomp: Set NNP for TSYNC ESRCH flag test md/raid5: Fix Force reconstruct-write io stuck in degraded raid5 bcache: allocate meta data pages as compound pages bca
[Kernel-packages] [Bug 1885031] Re: supervisor write access in kernel mode
Looks like I still run into this. I am on 5.4.0-44-generic. See attached log ** Attachment added: "journal log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885031/+attachment/5404236/+files/journal_log_08242020.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/1885031 Title: supervisor write access in kernel mode Status in linux package in Ubuntu: Incomplete Bug description: machine froze. Only mouse could be moved. BUG: kernel NULL pointer dereference, address: Jun 24 18:56:43 MartoBeast kernel: #PF: supervisor write access in kernel mode Jun 24 18:56:43 MartoBeast kernel: #PF: error_code(0x0002) - not-present page Ubuntu 20.04 Linux MartoBeast 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martin 2649 F pulseaudio /dev/snd/controlC0: martin 2649 F pulseaudio /dev/snd/controlC2: martin 2649 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (199 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash acpi_enforce_resources=lax vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (61 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885031/+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 1830740] Re: [linux-azure] Delay during boot of some instance sizes
Cloud-init logs on an instance with accelerated networking (bionic) exhibiting this delay across reboot ** Attachment added: "cloud-init.tar" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5404235/+files/cloud-init.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830740 Title: [linux-azure] Delay during boot of some instance sizes Status in linux-azure package in Ubuntu: New Bug description: We are seeing a long delay, about 100s, when booting new E32s_v3 VMs. We don’t see this delay with smaller sized Ubuntu VMs(D2s and NC6 sizes). I attached a screen shot of the boot delay. You can see between 7.022911 and 101.325958 seconds there is no activity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+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 1757143] Re: /proc/modules has Null references causing python parsing issues
** Changed in: plainbox-provider-checkbox (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757143 Title: /proc/modules has Null references causing python parsing issues Status in linux package in Ubuntu: Invalid Status in plainbox-provider-checkbox package in Ubuntu: Fix Released Bug description: EDIT: this originally looked like some sort of regression in the module_resource script of plainbox-provider-resource, however, on diving in a bit it seems the root cause is that /proc/modules in 4.15 is different than in previous kernels. This is a line from 4.15's /proc/modules data: e1000e 249856 0 - Live 0x (null) And this is the same module info from 4.13: e1000e 249856 0 - Live 0x That null character at the end appears to be causing the script to choke. For that reason, because /proc/modules has somehow changed to include null references (0xNULL is invalid, where 0x000 is parsable), I've added a kernel task to this bug. Original Summary: I ran into this issue (and came across some further glitches) while running canonical-certification-server on Ubuntu Server 18.04 on s390x (having 16.04 full selected in canonical-certification-server user interface): $ /usr/lib/plainbox-provider-resource-generic/bin/module_resource Traceback (most recent call last): File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 73, in sys.exit(main()) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 62, in main for module in modules: File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 57, in get_modules yield get_module(line) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 49, in get_module "offset": int(offset, 16)} ValueError: invalid literal for int() with base 16: '0x' result file is attached to the ticket, as well as the console log ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757143/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@gannon1 disable file ** Attachment added: "Disable" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404232/+files/Disable -- 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, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: a
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@gannon1 enable file... -- 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, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Sym
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@gannon1 I am tracking what your saying concept wise. Here is a summary of what I did today, in part just to help me clarify my thoughts and in part so you can maybe correct any gaps and save me troubleshooting time :). - I have gone through all the documents in the wiki for QemuHDADump and as far as I can tell it is running as expected on my PC and creating good logs. I am able to see the logging happening in real-time and I get the frame binary files. I am also able to use his extract and format programs to "see" the data as text. As an example, the attached file named CORB has the final formatted output from disabling and re- enabling the realtek device in windows - Looking at the HDA spec, this seems to be the only detailed description of the CORB entries : HDA Spec CORB 32 bit format The controller generated (outbound) Verb format Bits 31:28 Codec Address Bits 27:20 Node ID Bits 19:0 Verb Payload It is not currently clear to me how to parse the "verb payload" or how to map these CORB values into anything useful. - Several of the documents you listed and your comments mention playing back or using the values to turn on the sound. I assume (maybe incorrectly), that we are trying to a) produce a list of HDA Verb commands that match each CORB entry to prove the sound turns on and then B) work to whittle down the list to the minimum required ones. Part B will be effort, but I think that will just be applied time once we achieve Part A. For Part A, again my assumption, we are trying to convert CORB values into the HDA Verb format : HDA Verb format The hwdep device name The widget NID The verb The parameter - Since I was stuck on what to do with the output from QemuHDADump, I went back and read the other articles more, specifically the BSD article. That author took a different approach and instead of using the QemuHDADump program, he just altered Qemu to give him more info in the output. His source code was available so I worked with that to try and replicate his results. I couldn't just use his common.c file directly because we are on different version of qemu, but I was able to modify the common.c file on my version of qemu, and then remake qemu successfully. So now, instead of just getting lines like this : 15469@1598294292.270884:vfio_region_write (:00:1f.3:region0+0x48, 0xad, 2) 15469@1598294292.270975:vfio_region_write (:00:1f.3:region0+0x20, 0x4000, 4) 15469@1598294292.270983:vfio_region_write (:00:1f.3:region0+0x5d, 0x1, 1) I get more information, like this : 15469@1598294292.272359:vfio_region_write (:00:1f.3:region0+0x5d, 0x1, 1) RIRBWP advance to 185, last WP 183 CORB caddr:0x9 nid:0x47 control:0x407 param:0x20 response:0x64756c63 (ex 0x6f466465) CORB caddr:0x0 nid:0x0 control:0x1 param:0xe6 response:0x65735572 (ex 0x544e4900) RIRBWP advance to 185, last WP 185 RIRBWP advance to 185, last WP 185 RIRBWP advance to 185, last WP 185 15469@1598294292.272436:vfio_region_write (:00:1f.3:region0+0x20, 0xc000, 4) CORBWP advance to 187, last WP 185 CORB[186] = 0x0 (caddr:0x0 nid:0x0 control:0x0 param:0x0) CORB[187] = 0x0 (caddr:0x0 nid:0x0 control:0x0 param:0x0) 15469@1598294292.272522:vfio_region_write (:00:1f.3:region0+0x48, 0xbb, 2) I think the most useful parts here are the CORB[] lines (for example) : CORB[218] = 0x9cac8480 (caddr:0x9 nid:0x4a control:0xc84 param:0x80) This would at least seem like it could be mapped to an HDA verbs, maybe like so sudo hda-verb /dev/snd/hwC0D0 0x4a 0xc84 0x80 - So with that change, I then recorded all the traffic during a re- enable of the realtek devices in windows (I will attach files named Enable and Disable). I then wrote a script to pull out the CORB[x] lines from the log and to produce a new script with all the mapped HDA Verbs. This generated 2034 HDA Verb commands (just on the re-enable of the windows realtek device... yikes... ) - Anyway, I ran the script of 2034 HDA Verb commands on my PC. No errors, but unfortunately no sounds came out of the speakers. Very likely I just mapped the values to my HDA verbs incorrectly, I am just guessing on how to do that, or possibly the specific action we need does not happen on a re-enable. Anyway, thoughts? Do you have any more clarity on how to replay the CORB commands? I can try this all again with a suspend and resume, but suspect that will be a lot of CORB values ** Attachment added: "CORB" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404231/+files/CORB -- 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 i
[Kernel-packages] [Bug 1887774] Re: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP
Since we have kernel 5.8 in groovy proposed, I'm updating the 'affecting groovy' entry to Fix Committed. ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- 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/1887774 Title: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification: == [Impact] * Linux kernel panics due to kernel page fault in IRQ context when running zfcp_erp_timeout_handler() calling zfcp_erp_notify(). [Fix] * 936e6b85da0476dd2edac7c51c68072da9fb4ba2 936e6b85da04 "scsi: zfcp: Fix panic on ERP timeout for previously dismissed ERP action" [Test Case] * Requires an IBM z13/z13s or LinuxONE Rockhopper/Emperor system (or newer) connected to zfcp capcble storage sub-system. * Initiate an (ERP) timeout (maybe by injection or by causing a slow recovery otherwise). * Monitor the system log for any kernel panics. [Regression Potential] * The regression can be considered as medium since the modification is platform specific / limited to s390x and again limited to the zfcp layer. * Within zfcp it's further limited to the error recovery procedure (ERP) of fcp and only touches zfcp_erp.c, means the code path is mainly active under error conditions. [Other] * The above fix is upstream accepted with v5.8-rc3, hence will make it's way to groovy with kernel 5.8. * Therefore this SRU request was submitted for bionic and focal only and not for groovy. __ Description: zfcp: Fix panic on ERP timeout for previously dismissed ERP Symptom: Linux kernel panic due to kernel page fault in IRQ context when running zfcp_erp_timeout_handler() calling zfcp_erp_notify(). Problem: Suppose that, for unrelated reasons, FSF requests on behalf of recovery are very slow and can run into the ERP timeout. In the case at hand, we did adapter recovery to a large degree. However due to the slowness a LUN open is pending so the corresponding fc_rport remains blocked. After fast_io_fail_tmo we trigger close physical port recovery for the port under which the LUN should have been opened. The new higher order port recovery dismisses the pending LUN open ERP action and dismisses the pending LUN open FSF request. Such dismissal decouples the ERP action from the pending corresponding FSF request by setting zfcp_fsf_req->erp_action to NULL (among other things) [zfcp_erp_strategy_check_fsfreq()]. If now the ERP timeout for the pending open LUN request runs out, we must not use zfcp_fsf_req->erp_action in the ERP timeout handler. This is a problem since v4.15 commit 75492a51568b ("s390/scsi: Convert timers to use timer_setup()"). Before that we intentionally only passed zfcp_erp_action as context argument to zfcp_erp_timeout_handler(). Note: The lifetime of the corresponding zfcp_fsf_req object continues until a (late) response or an (unrelated) adapter recovery. Solution: Just like the regular response path ignores dismissed requests [zfcp_fsf_req_complete() => zfcp_fsf_protstatus_eval() => return early] the ERP timeout handler now needs to ignore dismissed requests. So simply return early in the ERP timeout handler if the FSF request is marked as dismissed in its status flags. To protect against the race where zfcp_erp_strategy_check_fsfreq() dismisses and sets zfcp_fsf_req->erp_action to NULL after our previous status flag check, return early if zfcp_fsf_req->erp_action is NULL. After all, the former ERP action does not need to be woken up as that was already done as part of the dismissal above [zfcp_erp_action_dismiss()]. Upstream-ID: 936e6b85da0476dd2edac7c51c68072da9fb4ba2 -> kernel 5.8 Will be integrated by kernel 5.8 by groovy. Please check that this also be integrated into 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887774/+subscriptio
[Kernel-packages] [Bug 1891437] Re: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support
** Changed in: ubuntu-z-systems Status: New => Triaged -- 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/1891437 Title: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Committed Bug description: When a NVMe drive is assigned/hotplugged to a Linux LPAR then a bug is hit in lib/list_debug.c. And the device is not accessible, there is no /dev/ file and lspci does not report it also. [ 1681.564462] list_add double add: new=eed0f808, prev=eed0f808, next=4070a300. [ 1681.564489] [ cut here ] [ 1681.564490] kernel BUG at lib/list_debug.c:31! [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2 [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR) [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 (__list_add_valid+0x70/0xa8) [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 1681.564545] Krnl GPRS: 0040 0027 0058 0007 [ 1681.564546]3ffcadb4 03e0051a7ce0 [ 1681.564547]4070a300 eed0f808 eed0f808 4070a300 [ 1681.564548]f56a2000 40c2c788 3ffcadb4 03e0051a7bc8 [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl %r2,405d03ba 3ffcadae: c0e5ffdd30b1brasl %r14,3fb70f10 #3ffcadb4: af00mc 0,0 >3ffcadb8: b9040054lgr %r5,%r4 3ffcadbc: c02000302aadlarl %r2,405d0316 3ffcadc2: b9040041lgr %r4,%r1 3ffcadc6: c0e5ffdd30a5brasl %r14,3fb70f10 3ffcadcc: af00mc 0,0 [ 1681.564592] Call Trace: [ 1681.564594] [<3ffcadb8>] __list_add_valid+0x70/0xa8 [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8) [ 1681.564599] [<3faf2920>] zpci_create_device+0x60/0x1b0 [ 1681.564601] [<3faf704a>] zpci_event_availability+0x282/0x2f0 [ 1681.564605] [<40367848>] chsc_process_crw+0x2b8/0xa18 [ 1681.564607] [<4036f35c>] crw_collect_info+0x254/0x348 [ 1681.564610] [<3fb2a6ea>] kthread+0x14a/0x168 [ 1681.564613] [<403a55c0>] ret_from_fork+0x24/0x2c [ 1681.564614] Last Breaking-Event-Address: [ 1681.564618] [<3fb70f62>] printk+0x52/0x58 [ 1681.564620] ---[ end trace 7ea67c348aa67e14 ]--- uname: Linux t83lp49.lnxne.boe 5.8.0-rc1+ #2 SMP Thu Jun 18 12:38:02 CEST 2020 s390x s390x s390x GNU/Linux How to reproduce: 1. Unassign a NVMe drive in HMC from your LPAR 2. Reassign it to your LPAR again 3. dmesg This issue is fixed by the following upstream commit that is also CCed to stable so might be coming in over the stable pulls in parallel: 3047766bc6ec ("s390/pci: fix enabling a reserved PCI function") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891437/+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 1891437] Re: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support
The commit got upstream accepted with v5.8-rc5 and is with that part of groovy's proposed kernel 5.8: user@box:~/ubuntu-groovy-master-next$ git tag --contains 3047766bc6ec Ubuntu-5.8.0-13.14 Ubuntu-5.8.0-14.15 Ubuntu-5.8.0-15.16 Ubuntu-5.8.0-16.17 v5.8 v5.8-rc5 v5.8-rc6 v5.8-rc7 Hence updating status of groovy entry to Fix Committed. ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed -- 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/1891437 Title: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Committed Bug description: When a NVMe drive is assigned/hotplugged to a Linux LPAR then a bug is hit in lib/list_debug.c. And the device is not accessible, there is no /dev/ file and lspci does not report it also. [ 1681.564462] list_add double add: new=eed0f808, prev=eed0f808, next=4070a300. [ 1681.564489] [ cut here ] [ 1681.564490] kernel BUG at lib/list_debug.c:31! [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2 [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR) [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 (__list_add_valid+0x70/0xa8) [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 1681.564545] Krnl GPRS: 0040 0027 0058 0007 [ 1681.564546]3ffcadb4 03e0051a7ce0 [ 1681.564547]4070a300 eed0f808 eed0f808 4070a300 [ 1681.564548]f56a2000 40c2c788 3ffcadb4 03e0051a7bc8 [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl %r2,405d03ba 3ffcadae: c0e5ffdd30b1brasl %r14,3fb70f10 #3ffcadb4: af00mc 0,0 >3ffcadb8: b9040054lgr %r5,%r4 3ffcadbc: c02000302aadlarl %r2,405d0316 3ffcadc2: b9040041lgr %r4,%r1 3ffcadc6: c0e5ffdd30a5brasl %r14,3fb70f10 3ffcadcc: af00mc 0,0 [ 1681.564592] Call Trace: [ 1681.564594] [<3ffcadb8>] __list_add_valid+0x70/0xa8 [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8) [ 1681.564599] [<3faf2920>] zpci_create_device+0x60/0x1b0 [ 1681.564601] [<3faf704a>] zpci_event_availability+0x282/0x2f0 [ 1681.564605] [<40367848>] chsc_process_crw+0x2b8/0xa18 [ 1681.564607] [<4036f35c>] crw_collect_info+0x254/0x348 [ 1681.564610] [<3fb2a6ea>] kthread+0x14a/0x168 [ 1681.564613] [<403a55c0>] ret_from_fork+0x24/0x2c [ 1681.564614] Last Breaking-Event-Address: [ 1681.564618] [<3fb70f62>] printk+0x52/0x58 [ 1681.564620] ---[ end trace 7ea67c348aa67e14 ]--- uname: Linux t83lp49.lnxne.boe 5.8.0-rc1+ #2 SMP Thu Jun 18 12:38:02 CEST 2020 s390x s390x s390x GNU/Linux How to reproduce: 1. Unassign a NVMe drive in HMC from your LPAR 2. Reassign it to your LPAR again 3. dmesg This issue is fixed by the following upstream commit that is also CCed to stable so might be coming in over the stable pulls in parallel: 3047766bc6ec ("s390/pci: fix enabling a reserved PCI function") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-sys
[Kernel-packages] [Bug 1891032] Re: Brightness key freeze screen
0. install acpidbg - sudo apt install linux-tools-`uname -r` linux- tools-generic trigger and check which of the following cause screen freeze 1. sudo acpidbg -b "e EV5 1 0" ("2 0" for brightness down) 2. sudo acpidbg -b "e \_SB.PCI0.GFX0.BRT6 1 0" ("2 0" for brightness down) 3. sudo acpidbg -b "notify \_SB.PCI0.GFX0.LCD 0x86" (0x86 for brightness down) 4. echo 3 | sudo tee /sys/class/backlight/intel_backlight/brightness 5. echo 6 | sudo tee /sys/class/backlight/intel_backlight/brightness -- 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/1891032 Title: Brightness key freeze screen Status in linux package in Ubuntu: Incomplete Bug description: When I press the KEY_BRIGHTNESSDOWN or KEY_BRIGHTNESSUP the screen freeze for a few seconds. Sometimes it up/down brightness to max/min with just one press and the overlay get stuck in the screen. Maybe useful information: # evtest Event: time 1597066500.752632, -- SYN_REPORT Event: time 1597066502.755372, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86 Event: time 1597066502.755372, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 1 Event: time 1597066502.755372, -- SYN_REPORT Event: time 1597066502.761653, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86 Event: time 1597066502.761653, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 0 Event: time 1597066502.761653, -- SYN_REPORT Event: time 1597066521.533682, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85 Event: time 1597066521.533682, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 1 Event: time 1597066521.533682, -- SYN_REPORT Event: time 1597066521.542973, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85 Event: time 1597066521.542973, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 0 $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.2 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 10 10:44:20 2020 InstallationDate: Installed on 2018-07-23 (749 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 5558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=c78b51e8-c664-4dd2-8020-7bc5da6f2bc0 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-07-11 (29 days ago) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0R392V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0R392V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5558 dmi.product.sku: Inspiron 5558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891032/+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
Verified that the report from apport-2.20.9-0ubuntu7.17 from bionic- proposed includes the ProcFB details. Verification-done ** 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-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 1891032] Re: Brightness key freeze screen
please refer to https://wiki.archlinux.org/index.php/backlight for more info on /sys/class/backlight/ interfaces -- 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/1891032 Title: Brightness key freeze screen Status in linux package in Ubuntu: Incomplete Bug description: When I press the KEY_BRIGHTNESSDOWN or KEY_BRIGHTNESSUP the screen freeze for a few seconds. Sometimes it up/down brightness to max/min with just one press and the overlay get stuck in the screen. Maybe useful information: # evtest Event: time 1597066500.752632, -- SYN_REPORT Event: time 1597066502.755372, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86 Event: time 1597066502.755372, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 1 Event: time 1597066502.755372, -- SYN_REPORT Event: time 1597066502.761653, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86 Event: time 1597066502.761653, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 0 Event: time 1597066502.761653, -- SYN_REPORT Event: time 1597066521.533682, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85 Event: time 1597066521.533682, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 1 Event: time 1597066521.533682, -- SYN_REPORT Event: time 1597066521.542973, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85 Event: time 1597066521.542973, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 0 $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.2 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 10 10:44:20 2020 InstallationDate: Installed on 2018-07-23 (749 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 5558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=c78b51e8-c664-4dd2-8020-7bc5da6f2bc0 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-07-11 (29 days ago) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0R392V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0R392V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5558 dmi.product.sku: Inspiron 5558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891032/+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 1892774] [NEW] Groovy update: v5.8.3 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.8.3 upstream stable release from git://git.kernel.org/ UBUNTU: [Config] update config for ARMADA_AP_CPU_CLK ALSA: hda/realtek - Fix unused variable warning smb3: warn on confusing error scenario with sec=krb5 SMB3: Fix mkdir when idsfromsid configured on mount genirq/affinity: Make affinity setting if activated opt-in genirq: Unlock irq descriptor after errors genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() PCI/ATS: Add pci_pri_supported() to check device or associated PF PCI: Add device even if driver attach failed PCI: qcom: Define some PARF params needed for ipq8064 SoC PCI: qcom: Add support for tx term offset for rev 2.1.0 btrfs: allow use of global block reserve for balance item deletion btrfs: free anon block device right after subvolume deletion btrfs: don't allocate anonymous block device for user invisible roots btrfs: preallocate anon block device at first phase of snapshot creation btrfs: ref-verify: fix memory leak in add_block_entry btrfs: only commit the delayed inode when doing a full fsync btrfs: stop incremening log_batch for the log root tree when syncing log btrfs: only commit delayed items at fsync if we are logging a directory btrfs: remove no longer needed use of log_writers for the log root tree btrfs: don't traverse into the seed devices in show_devname btrfs: pass checksum type via BTRFS_IOC_FS_INFO ioctl btrfs: open device without device_list_mutex btrfs: move the chunk_mutex in btrfs_read_chunk_tree btrfs: relocation: review the call sites which can be interrupted by signal btrfs: add missing check for nocow and compression inode flags btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree btrfs: return EROFS for BTRFS_FS_STATE_ERROR cases btrfs: sysfs: use NOFS for device creation btrfs: don't WARN if we abort a transaction with EROFS btrfs: fix race between page release and a fast fsync btrfs: don't show full path of bind mounts in subvol= btrfs: fix messages after changing compression level by remount btrfs: only search for left_info if there is no right_info in try_merge_free_space btrfs: inode: fix NULL pointer dereference if inode doesn't need compression btrfs: fix memory leaks after failure to lookup checksums during inode logging btrfs: trim: fix underflow in trim length to prevent access beyond device boundary btrfs: make sure SB_I_VERSION doesn't get unset by remount btrfs: fix return value mixup in btrfs_get_extent btrfs: check correct variable after allocation in btrfs_backref_iter_alloc arm64: dts: qcom: sc7180: Drop the unused non-MSA SID arm64: perf: Correct the event index in sysfs dt-bindings: iio: io-channel-mux: Fix compatible string in example code iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw() iio: imu: st_lsm6dsx: reset hw ts after resume xtensa: add missing exclusive access state management xtensa: fix xtensa_pmu_setup prototype cifs: Fix leak when handling lease break for cached root fid powerpc/ptdump: Fix build failure in hashpagetable.c powerpc: Allow 4224 bytes of stack expansion for the signal frame powerpc: Fix circular dependency between percpu.h and mmu.h pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH pinctrl: ingenic: Properly detect GPIO direction when configured for IRQ media: venus: fix multiple encoder crash media: vsp1: dl: Fix NULL pointer dereference on unbind net: ethernet: stmmac: Disable hardware multicast filter net: stmmac: dwmac1000: provide multicast filter fallback irqchip/loongson-liointc: Fix misuse of gc->mask_cache irqchip/gic-v4.1: Ensure accessing the correct RD when writing INVALLR pidfd: Add missing sock updates for pidfd_getfd() net/compat: Add missing sock updates for SCM_RIGHTS selftests/seccomp: Set NNP for TSYNC ESRCH flag test md/raid5: Fix Force reconstruct-write io stuck in degraded raid5 bcache: allocate meta data pages as compound pages bcache: fix overflow in offset_to_stripe() bcache: avoid nr_stripes overflow in bcache_device_init() bcache: fix bio_{start,end}_io_acct with proper device bcache: use disk_{start,end}_io_acct() to count I/O for bcache device mac80211: fix misplaced while instead of if appletalk: Fix atalk_proc_init() return path driver core: Avoid binding drivers to dead devices MIPS: CPU#0 is not hotpluggable MIPS: qi_lb60: Fix routing to audio amplifier MIPS: SGI-IP27: always enable NUMA in Kconfig ext2: fix missing percpu_counter_inc khugepaged: collapse_pte_mapped_thp(
[Kernel-packages] [Bug 1891032] Re: Brightness key freeze screen
The flow of brightness hotkey is as follows key pressed -> ec triggers events -> bios/os performs a series of following functions -> ... -> ACPI EV5 -> ACPI BRT6 -> ACPI Notify LCD 0x86/0x87 -> ACPI VGA driver generates keycodes -> userspace write to /sys/class/backlight/intel_backlight/brightness It is possible to manually perform functions in ACPI EV5 and later. EV5 and later does not freeze screen, hardware and BIOS are likely to be blamed; otherwise, it is possible to further narrow down which parts break and identify the responsible drivers. -- 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/1891032 Title: Brightness key freeze screen Status in linux package in Ubuntu: Incomplete Bug description: When I press the KEY_BRIGHTNESSDOWN or KEY_BRIGHTNESSUP the screen freeze for a few seconds. Sometimes it up/down brightness to max/min with just one press and the overlay get stuck in the screen. Maybe useful information: # evtest Event: time 1597066500.752632, -- SYN_REPORT Event: time 1597066502.755372, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86 Event: time 1597066502.755372, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 1 Event: time 1597066502.755372, -- SYN_REPORT Event: time 1597066502.761653, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86 Event: time 1597066502.761653, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 0 Event: time 1597066502.761653, -- SYN_REPORT Event: time 1597066521.533682, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85 Event: time 1597066521.533682, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 1 Event: time 1597066521.533682, -- SYN_REPORT Event: time 1597066521.542973, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85 Event: time 1597066521.542973, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 0 $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.2 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 10 10:44:20 2020 InstallationDate: Installed on 2018-07-23 (749 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 5558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=c78b51e8-c664-4dd2-8020-7bc5da6f2bc0 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-07-11 (29 days ago) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0R392V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0R392V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5558 dmi.product.sku: Inspiron 5558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891032/+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 1887986] Re: Enable FUNCTION_PROFILER kernel config option for ppc64le
Starting to work on this SRU I figures out that this kernel config option is already enabled. I checked the config file that is created at kernel build time as well as the master-next trees of focal and groovy - and CONFIG_FUNCTION_PROFILER is enabled for all architectures, incl. ppc64el: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal $ uname -r 5.4.0-44-generic $ grep CONFIG_FUNCTION_PROFILER /boot/config-$(uname -r) CONFIG_FUNCTION_PROFILER=y $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 Codename: groovy $ uname -r 5.4.0-42-generic $ grep CONFIG_FUNCTION_PROFILER /boot/config-$(uname -r) CONFIG_FUNCTION_PROFILER=y $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 Codename: groovy $ uname -r 5.8.0-16-generic $ grep CONFIG_FUNCTION_PROFILER /boot/config-$(uname -r) CONFIG_FUNCTION_PROFILER=y user@box:~/ubuntu-focal-master-next/debian.master/config$ grep -R CONFIG_FUNCTION_PROFILER * annotations:CONFIG_FUNCTION_PROFILERpolicy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'i386': 'y', 'ppc64el': 'y', 's390x': 'y'}> config.common.ubuntu:CONFIG_FUNCTION_PROFILER=y user@box:~/ubuntu-groovy-master-next/debian.master/config$ grep -R CONFIG_FUNCTION_PROFILER * annotations:CONFIG_FUNCTION_PROFILERpolicy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 's390x': 'y'}> config.common.ubuntu:CONFIG_FUNCTION_PROFILER=y Is CONFIG_FUNCTION_PROFILER the only option you were looking for, or is/are there other options needed or is it not working for you (even if set)? Otherwise I would say there is nothing to do, since it's already configured like requested. ** Changed in: ubuntu-power-systems Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux (Ubuntu Groovy) 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/1887986 Title: Enable FUNCTION_PROFILER kernel config option for ppc64le Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: Please enable CONFIG_FUNCTION_PROFILER config option for ppc64le kernel. This option enables the ftrace function profiling in the kernel, it helps in getting the function profiling information such as hit count, time spend and other profiling details. Enabling this kernel config option should not have any performance impact unless the function profiling is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887986/+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 1890873] Re: no intel_backlight file
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890873 Title: no intel_backlight file Status in linux package in Ubuntu: Fix Released Bug description: i am a noob, can't find the intel_backlight 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: kira 1573 F pulseaudio /dev/snd/controlC1: kira 1573 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:32:31 2020 InstallationDate: Installed on 2020-08-01 (6 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 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-54 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=53af6216-e431-4dba-8753-614cbe9fa7ca ro nomodeset_ quiet splash video.use_native_backlight=1 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: 05/11/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.30 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Octavia_CFS dmi.board.vendor: CFL dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.30:bd05/11/2020:svnAcer:pnNitroAN515-54:pvrV1.30:rvnCFL:rnOctavia_CFS:rvrV1.30:cvnAcer:ct10:cvrV1.30: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-54 dmi.product.sku: dmi.product.version: V1.30 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890873/+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
Tested for bionic on arm64/am64 generic and amd64 with PREEMPT with ubuntu zfs tests - all OK. ** Tags added: verification-done-bionic -- 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 88010f78fcf8 816ae383 88010f78fd28 810b698d 88011c092548 0023d073 88011c092500 0001 88010f78fd60 8109d7c5 8109d645 Call Trace: [] dump_stack+0x19/0x1b [] lockdep_rcu_suspicious+0xfd/0x130 [] cpuacct_charge+0x185/0x1f0 [] ? cpuacct_charge+0x5/0x1f0 [] update_curr+0xec/0x240 [] put_prev_t
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Reading the initial bug report I see kolAflash said > nomodeset seems to be essential, but not sufficient. When I added nomodeset to /etc/default/grub ( GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" ) then I can boot without issues, but suspend does not work. To reiterate: * the TTY1 screen is not blank on boot * sleep works * suspend does not work - you get this bug Given this error in syslog: > kernel: [0.047848] You have booted with nomodeset. This means your GPU > drivers are DISABLED > kernel: [0.047849] Unless you actually understand what nomodeset does, > you should reboot without enabling it > [0.047849] Any video related functionality will be severely degraded, and > you may not even be able to suspend the system properly > [0.047849] Unless you actually understand what nomodeset does, you should > reboot without enabling it I tried a few things without nomodeset in grub options. In this case: * the default screen, TTY1, (CTRL-ALT-F1) is blank on boot (or has the HP logo only) * sleep works * suspend doesn't seem to work. If you leave the laptop in suspend mode for a long time it does not resume. The screen is black with just a white underscore on it. The last log lines in /var/log/syslog is systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[8263]: Suspending system... kernel: [ 9425.088936] PM: suspend entry (s2idle) As a workaround for the default screen being blank on boot, you can go to TTY2 (CTRL-ALT-F2), log in and run startx from the command prompt. Some tests: * This does not seem to be the same issue as https://bugzilla.kernel.org/show_bug.cgi?id=204241 because the following command works just fine. for i in $(seq 30); do sudo rtcwake -m mem -s 5; sleep 15; done * I've tried adding GRUB_GFXMODE=1920x1080 to /etc/default/grub but that doesn't seem to solve the issue with the screen on TTY1 being blank on boot. The commands pm-hibernate and pm-suspend give the errors in /var/log/syslog > [ 2566.154192] Lockdown: grep: hibernation is restricted; see man > kernel_lockdown.7 and nothing happens The command pm-powersave gives the same "hibernation is restricted" error in /var/log/syslog but the system goes blank and the is unresponsive. ** Bug watch added: Linux Kernel Bug Tracker #204241 https://bugzilla.kernel.org/show_bug.cgi?id=204241 -- 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/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searc
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
*** This bug is a duplicate of bug 1859756 *** https://bugs.launchpad.net/bugs/1859756 TLDR; ignore in-tree driver version strings, they don't really mean anything. I have no idea what the proprietary driver is or how it is versioned, so I can't speak to that. I can say that version strings for Linux drivers are pretty arbitrary. There's no clear waterline for when a driver should go from say 1.0 to 2.0 - at some point a driver maintainer just submits a patch to change that string using whatever criteria they use. There could be 1000s of code changes to a driver in between version changes. And there are likely many drivers out there that claim to be the same version but have drastically different features/fixes. Consider vendor trees, like Ubuntu. We will obviously start out w/ the same version of the driver as the upstream base kernel (v4.15 here), but we're possibly going to backport additional features (in early devel) and maintenance fixes (for ~10 years of support). And for hns3, we have applied many so far: $ git log --oneline v4.15..Ubuntu-4.15.0-114.115 drivers/net/ethernet/hisilicon/hns3 | wc -l 588 But should this change our driver version? If it did, what would that tell you? Our driver won't be the same as upstream's, Red Hat's, etc. All you can say is that it is the version that shipped with Ubuntu-4.15.0-114.115. If you want to know more, you can look at change control to see if it has the changes you are looking for. Now, that said, version strings may provide useful context for hardware manufacturers that provide out-of-tree drivers. They may provide regular driver releases that can be used with Ubuntu 18.04. In that case, they know what exactly was in version 1.0foo.3 and what issues would be fixed if you upgraded to 1.0foo.4 - but that's a different release model. -- 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 kunpeng920 ubuntu-18.04 series: 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 :
[Kernel-packages] [Bug 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start
Changes submitted to our SRU cycle for groovy, focal, bionic and xenial. Cover letter: https://lists.ubuntu.com/archives/kernel- team/2020-August/112922.html -- 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/1891224 Title: [Hyper-V] VSS and File Copy daemons intermittently fails to start Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in systemd source package in Groovy: Invalid Bug description: [Impact] We have most reliably reproduced this on a Standard_B1s in Azure in the North Europe region (>80% of the time). Tests in other regions/VM types do not show this failure as often (<1%). We have reproduced this in Xenial, Bionic, Focal, and Groovy. We saw an increase of test failures around a month ago. From the journal : Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start tim> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_vss.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V VSS Protocol Daemon. Aug 11 09:55:28 ubuntu systemd[1]: hv-vss-daemon.service: Job hv-vss-daemon.service/start failed with result 'dependency'. Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start fai> Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_fcopy.device: Job sys-devices-virtual-misc-vmbus\x21hv_fcopy.device/start> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_fcopy.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V File Copy Protocol Daemon. We've seen problems in the past with KVP daemons that looked very similar : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063 [Test Case] There two main scenarios that need to be tested: 1. Azure instances: - Just start an azure instance using our Ubuntu images and check the the status of the hv-vss-daemon and hv-fcopy-daemon services using systemctl. - If the issue is solved they shouldn't be listed as failed. 2. Local Hyper-V VM: - Create a local Hyper-V instance and enable the two systemd services if necessary (hv-vss-daemon and hv-fcopy-daemon) and reboot. - You can change the integration services that are enable to the guest. 1. With desktop integration and the backup feature disabled, the hv-fcopy-daemon and the hv-vss-daemon service, respectively should not be listed as failed. 2. With the same features enabled the services should start without errors. [Regression Potential] The major risk with a potential regression is that those systemd service units are shipped by a package produced by our generic kernels and not the linux-azure kernel. So in case of a regression we might need to re-spin the generic kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891224/+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 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start
** Description changed: + [Impact] + We have most reliably reproduced this on a Standard_B1s in Azure in the North Europe region (>80% of the time). Tests in other regions/VM types do not show this failure as often (<1%). We have reproduced this in Xenial, Bionic, Focal, and Groovy. We saw an increase of test failures around a month ago. From the journal : Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start tim> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_vss.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V VSS Protocol Daemon. Aug 11 09:55:28 ubuntu systemd[1]: hv-vss-daemon.service: Job hv-vss-daemon.service/start failed with result 'dependency'. Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start fai> Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_fcopy.device: Job sys-devices-virtual-misc-vmbus\x21hv_fcopy.device/start> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_fcopy.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V File Copy Protocol Daemon. + We've seen problems in the past with KVP daemons that looked very + similar : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063 - We've seen problems in the past with KVP daemons that looked very similar : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063 + + [Test Case] + + There two main scenarios that need to be tested: + + 1. Azure instances: + +- Just start an azure instance using our Ubuntu images and check the + the status of the hv-vss-daemon and hv-fcopy-daemon services using + systemctl. + +- If the issue is solved they shouldn't be listed as failed. + + 2. Local Hyper-V VM: + +- Create a local Hyper-V instance and enable the two systemd services + if necessary (hv-vss-daemon and hv-fcopy-daemon) and reboot. + +- You can change the integration services that are enable to the + guest. + + 1. With desktop integration and the backup feature disabled, the hv-fcopy-daemon and the hv-vss-daemon service, respectively should not be listed as failed. + 2. With the same features enabled the services should start without errors. + + + [Regression Potential] + + The major risk with a potential regression is that those systemd service + units are shipped by a package produced by our generic kernels and not + the linux-azure kernel. So in case of a regression we might need to re- + spin the generic kernels. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Invalid ** Changed in: systemd (Ubuntu Bionic) Status: New => Invalid ** Changed in: systemd (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- 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/1891224 Title: [Hyper-V] VSS and File Copy daemons intermittently fails to start Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in systemd source package in Groovy: Invalid Bug description: [Impact] We have most reliably reproduced this on a Standard_B1s in Azure in the North Europe region (>80% of the time). Tests in other regions/VM types do not show t
[Kernel-packages] [Bug 1892546] Comment bridged from LTC Bugzilla
--- Comment From tyr...@us.ibm.com 2020-08-24 12:34 EDT--- (In reply to comment #24) > It looks like the patch just got submitted to upstream (and landed in a > staging tree); but we usually need to wait for it's upstream acceptance - at > least to Torvalds tree or linux-next (to be sure that the patch is stable, > reviewed and community accepted). Understood, but is it possible to get a one-off/test kernel in the interim? We have cloud customer for whom this problem is causing intermittent outages. > > Am I got it right reading that this happens on PowerVM DLPARs, controlled by > PowerVC? Correct, but the problem isn't limited to that scenario. It can be recreated on any PowerVM LPAR, but hvcs is generally not used outside of PowerVC setups and as such that is where this got exposed. --- Comment From tyr...@us.ibm.com 2020-08-24 12:37 EDT--- (In reply to comment #25) > I saw that the tag 'targetmilestone-inin16046' is set, which points to 16.04 > as affected release. Is this the only affected Ubuntu release? This is the LTS that PowerVC uses, but as mentioned previously this issue effects all PowerVM LPARs should someone choose to use hvcs so it is desirable in any other releases that support PowerVM. -- 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 The Ubuntu-power-systems project: Triaged 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-power-systems/+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 1892001] Re: zfs-dkms fails to build on arm64 with PREEMPTION and BLK_CGROUP
Tested for focal on arm64/amd64 generic and with PREEMPT with ubuntu zfs tests - all OK. ** Tags added: verification-done-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/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 88010f78fcf8 816ae383 88010f78fd28 810b698d 88011c092548 0023d073 88011c092500 0001 88010f78fd60 8109d7c5 8109d645 Call Trace: [] dump_stack+0x19/0x1b [] lockdep_rcu_suspicious+0xfd/0x130 [] cpuacct_charge+0x185/0x1f0 [] ? cpuacct_charge+0x5/0x1f0 [] update_curr+0xec/0x240 [] put_prev_task_fai
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
*** This bug is a duplicate of bug 1859756 *** https://bugs.launchpad.net/bugs/1859756 Small comment; - Any reason why hns3 is not version 1.0.2 as the proprietary driver for 18.04.1 LTS kernel 4.15.0-29-generic? root@n012:~# find /lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3 -name "*.ko" -type f -exec modinfo {} \; | egrep -i -e "name|version|srcv" filename: /lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge.ko version:1.0.2 srcversion: C608A5D8EF6F248597CA9E5 name: hclge filename: /lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf.ko version:1.0.2 srcversion: 83B44FBC5FE1D6324B5F3D6 name: hclgevf filename: /lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hnae3.ko version:1.0.2 srcversion: 9097930440A454C1B6A0217 name: hnae3 filename: /lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hns3.ko version:1.0.2 srcversion: 0EF59799F6C1BB69074D893 name: hns3 -- 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 kunpeng920 ubuntu-18.04 series: 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(
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
*** This bug is a duplicate of bug 1859756 *** https://bugs.launchpad.net/bugs/1859756 Thanks Torel, 4.15.0-114.115 will be released to -update on August 31th according to kernel SRU schedule[1]. All you need to do is `sudo apt update;sudo apt upgrade` and you can use 4.15 kernel with fix. Set this bug as duplicate of bug 1859756 [1] https://kernel.ubuntu.com/ ** This bug has been marked a duplicate of bug 1859756 [hns3-0115] add 8 BD limit for tx flow -- 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 kunpeng920 ubuntu-18.04 series: 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=0x
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hey all, will we get backports of this to previous releases? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Released Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - FXSAVE_STATE - 3FF1C290 Find image based on IP(0x3
[Kernel-packages] [Bug 1892728] [NEW] ec2-hibinit-agent needs to properly initialize swap file
Public bug reported: With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return errors"), applied to v5.6-rc1, running swapon on a file that has holes returns an error (EINVAL); hibinit-agent is creating the swap file just using fallocate(), without touching the whole file by deafult, so there might be holes, swapon fails and hibernation cannot be performed. To prevent this problem we need to touch the swap file before using it and this can be done setting "touch-swap = True" in /etc/hibinit- config.cfg. The downside of this setting is that a new instance requires more time to be properly "initialized" the first time it boots due to the extra I/O required to touch the swap file (this additional I/O can be quite consistent in large instances, like c5.18xlarge for example), but I don't see a better way to make sure the file is all allocated without holes, so I guess we need to turn on this option if we want to use hibernation w/ kernels >= 5.6. ** Affects: ec2-hibinit-agent (Ubuntu) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1892728 Title: ec2-hibinit-agent needs to properly initialize swap file Status in ec2-hibinit-agent package in Ubuntu: New Bug description: With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return errors"), applied to v5.6-rc1, running swapon on a file that has holes returns an error (EINVAL); hibinit-agent is creating the swap file just using fallocate(), without touching the whole file by deafult, so there might be holes, swapon fails and hibernation cannot be performed. To prevent this problem we need to touch the swap file before using it and this can be done setting "touch-swap = True" in /etc/hibinit- config.cfg. The downside of this setting is that a new instance requires more time to be properly "initialized" the first time it boots due to the extra I/O required to touch the swap file (this additional I/O can be quite consistent in large instances, like c5.18xlarge for example), but I don't see a better way to make sure the file is all allocated without holes, so I guess we need to turn on this option if we want to use hibernation w/ kernels >= 5.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1892728/+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 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards
This bug seems still there on Ubuntu 18.04 with a Jabra Speak 410 USB conference speaker/microphone, see attached screenshot of the top-right menu. Note that the output seems to work both when selecting 'Analog Output' or 'Digital Output (S/PDIF)'. ** Attachment added: "jabra_410.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+attachment/5404156/+files/jabra_410.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1002952 Title: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards Status in alsa-lib package in Ubuntu: Confirmed Bug description: === Read me first === = Symptom = If you have a USB headset, or other USB device that does not have any S/PDIF output, but yet sometimes there is an extra device called "Digital Output (S/PDIF)" for that device, you're suffering from this bug. This bug is only for USB devices - if you have an invalid digital output for some other type of device, please file a separate bug instead. = Workaround = If you're affected, please try this workaround: first check the output of "aplay -l" (lowercase L), or "arecord -l" if it's an input device, and grab the first of two name in brackets: Example: card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio] here grab the name "Sennheiser USB Headset". Now edit the file /usr/share/alsa/cards/USB-Audio.conf (requires root permissions) Around line 40, you will find a line saying "Logitech USB Headset" 999 Add a new line after this line, so that there is now a new line called "Sennheiser USB Headset" 999 (including quotes, and replace "Sennheiser USB Headset" with whatever your particular card was named.) Save the file and reboot your computer for the changes to take effect. = Already known devices = These card names are already in 12.04: "Blue Snowball" "Logitech USB Headset" "Logitech Web Camera" These card names are on their way into 12.04: "Logitech Speaker Lapdesk N700" "Logitech Wireless Headset" "Plantronics USB Headset" "Sennheiser USB headset" If you have one of the above four, please help out by testing the proposed repository and report back in bug 987163. If your name is not listed above, please add a comment to this bug, including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo - they will be collected for a SRU later on, or at least make it into the next release of Ubuntu. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+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 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
The fix is waiting review https://code.launchpad.net/~giner/livecd- rootfs/+git/livecd-rootfs/+merge/388963 -- 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/1874453 Title: ubuntu/focal64 very slow to boot and reboots once Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=tty1 console=ttyS0 Subsequent boots are also slow but don't seem to have the extra reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 16:02 seq crw-rw 1 root audio 116, 33 May 7 16:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t:
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
For now you can easily fix this without any third-party applications by following these instructions: https://askubuntu.com/a/1269431/1119550 -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mutter/+bug/1855757/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@Mike, thanks for your help! I was able to submit the patch. Easier than I thought :-) FYI it ended up there: https://lkml.org/lkml/2020/8/24/977 -- 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, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio S
[Kernel-packages] [Bug 1892714] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404135/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404136/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404142/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404141/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404138/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404140/+files/RfKill.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404139/+files/PulseList.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404137/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404130/+files/Lspci-vt.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404132/+files/Lsusb-t.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] Re: Microphone not working on HP Omen 17
apport information ** Tags added: apport-collected focal ** Description changed: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: croraf 1940 F pulseaudio + /dev/snd/controlC0: croraf 1940 F pulseaudio + /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-11-16 (281 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: HP OMEN by HP Laptop 17-cb0xxx + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + 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 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/05/2019 + dmi.bios.vendor: AMI + dmi.bios.version: F.16 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 8603 + dmi.board.vendor: HP + dmi.board.version: 45.38 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP OMEN + dmi.product.name: OMEN by HP Laptop 17-cb0xxx + dmi.product.sku: 7NG00EA#BED + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404125/+files/AlsaInfo.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules:
[Kernel-packages] [Bug 1892714] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404131/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404127/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404126/+files/CRDA.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404134/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404129/+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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404128/+files/IwConfig.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1892714/+attachment/5404133/+files/Lsusb-v.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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1891502] Re: tpm tpm0: Error (28) sending savestate before suspend
Can confirm 5.9.0-rc1 did not work for me (following the instruction at https://wiki.ubuntu.com/Kernel/MainlineBuilds). I also experienced the same behavior where it worked the first time but not after that. -- 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/1891502 Title: tpm tpm0: Error (28) sending savestate before suspend Status in linux package in Ubuntu: Incomplete Bug description: Upon clicking suspend via Log Out... button in Xubuntu and also via systemctl suspend, the screen turns to black for 2 sec but then brings me back to log in screen instead of suspending. This was not an issue in 18.04. Currently on fresh install of 20.04.1. Aug 13 08:12:59 laptop kernel: [87528.628302] PM: suspend entry (s2idle) Aug 13 08:13:00 laptop kernel: [87529.250844] printk: Suspending console(s) (use no_console_suspend to debug) Aug 13 08:13:00 laptop kernel: [87529.250844] printk: Suspending console(s) (use no_console_suspend to debug) Aug 13 08:13:00 laptop kernel: [87529.555272] tpm tpm0: Error (28) sending savestate before suspend Aug 13 08:13:00 laptop kernel: [87529.555287] PM: __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x80 returns 28 Aug 13 08:13:00 laptop kernel: [87529.555292] PM: dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 28 Aug 13 08:13:00 laptop kernel: [87529.555296] PM: Device 00:01 failed to suspend: error 28 Aug 13 08:13:00 laptop kernel: [87529.929361] PM: Some devices failed to suspend, or early wake event detected Aug 13 08:13:01 laptop kernel: [87530.458095] PM: suspend exit Aug 13 08:13:01 laptop systemd[1]: systemd-suspend.service: Succeeded. 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: smrtalec 1174 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Aug 13 08:25:19 2020 InstallationDate: Installed on 2020-08-10 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Compaq 2510p Notebook PC PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bf5ecda3-8bba-45a8-8f73-038836aa1952 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: 11/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MSP Ver. F.30 dmi.board.name: 30C9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 75.28 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MSPVer.F.30:bd11/11/2011:svnHewlett-Packard:pnHPCompaq2510pNotebookPC:pvrF.30:rvnHewlett-Packard:rn30C9:rvrKBCVersion75.28:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 2510p Notebook PC dmi.product.sku: KR918UT#ABA dmi.product.version: F.30 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891502/+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 1892714] 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 1892714 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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] [NEW] Microphone not working on HP Omen 17
Public bug reported: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: New Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+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 1892714] [NEW] Microphone not working on HP Omen 17
You have been subscribed to a public bug: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Microphone not working on HP Omen 17 https://bugs.launchpad.net/bugs/1892714 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 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: change DFLT_CCERROR counter name
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Frank Heimes (fheimes) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Frank Heimes (fheimes) -- 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/1891454 Title: [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Committed Bug description: Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name Symptom: Counter name CCERROR is misleading. Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15. This counter counts completed DEFLATE instructions with exit code 0, 1 or 2. Since exit code 0 means success and exit code 1 or 2 indicate errors, change the counter name to avoid confusion. This counter is incremented each time the DEFLATE instruction completed regardless if an error was detected or not. Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR currently succeeds. After this patch has been applied the command does not work anymore. The file does not exist anymore. Use command # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH instead. Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef Component: kernel 5.8 Will be integrated into 20.10 by kernel 5.8 integration. Backport available for 20.04. To be checked for 18.04 and 16.04, update will be provided Here is the backported patch. The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change DFLT_CCERROR counter name") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+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
Tested 4.15.0-114-generic it works fine. Thx! -- 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 kunpeng920 ubuntu-18.04 series: 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
[Kernel-packages] [Bug 1889384] Re: ASPM not enabled on child devices behind VMD controller
** Tags added: originate-from-1890985 -- 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: Fix Committed 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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I guess my only request is that: if (EDID_version >= 1.4 && EDID_supports_10bit) then don't restrict "max bpc" endif ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/1890 Importance: Unknown Status: Unknown -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in Linux: Unknown Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install 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+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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/linux/+bug/1890772/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I guess my only request is that: if (EDID_version > 1.4 && EDID_supports_10bit) then don't restrict "max bpc" endif -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in Linux: Unknown Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install 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+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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/linux/+bug/1890772/+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
Folks, I've got Ubuntu mate 18.04 LTS and recently installed the updates which brought it upto Kernel 5.4.xxx This has definitely caused issues with my network speed. It has become extremely slow. Wifi using Fibre broadband 35Mbps.. Feels like browsing on a modem.. Is there a fix coming soon.. -- 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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
Thanks for understanding. There's an upstream bug discussing this similar issue, we can follow their effort there. https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890 https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Description changed: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` - Would like to open this bug to open discussion for enhancing user experience. + Would like to open this bug to open discussion for enhancing user + experience. + + existed upstream bug: + - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install 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+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install 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+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc]
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Hi Torel, No. please get the kernel debs from Ubuntu archive. Here are the steps 1) sudo apt-add-repository "deb http://ports.ubuntu.com/ubuntu-ports bionic-proposed main" 2) sudo apt update 3) sudo apt dist-upgrade Let me know if you need to manual install kernel debs and I can put those debs somewhere you can download. -- 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 kunpeng920 ubuntu-18.04 series: 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 [80
[Kernel-packages] [Bug 1892626] Re: [radeon] Random system freeze
No problem. Don't put your work at risk. We can leave this bug 'Incomplete' and it will stay that way for 60 days. Then if there are no further comments it will close automatically. -- 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/1892626 Title: [radeon] Random system freeze Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS x86_64 randomly freezing. Often when using browser (Firefox or Vivaldi) or email client (Thunderbird). Have to reboot to restart. Can occur several times a day. Didn't have problem with 18.04. 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: Regolith:GNOME-Flashback:GNOME Date: Sun Aug 23 14:08:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2020-06-14 (69 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-K 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.:bvr0903:bd10/25/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS 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 20.0.8-0ubuntu1~20.04.1 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/1892626/+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 1892626] Re: [radeon] Random system freeze
Appreciate your reply and link. I have not previously installed a new kernel. Having spent a small amount of time investigating this, it appears there are some risks updating to a mainline kernel. I'm in the middle of some fairly critical deadlines at the moment and would frankly rather save my work frequently and live with reboots than have to spend time recovering my system from some bad kernel update. If you want to close this completely understand. Again appreciate your time. NB - I did check additional drivers, it said 'no additional drivers available.' -- 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/1892626 Title: [radeon] Random system freeze Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS x86_64 randomly freezing. Often when using browser (Firefox or Vivaldi) or email client (Thunderbird). Have to reboot to restart. Can occur several times a day. Didn't have problem with 18.04. 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: Regolith:GNOME-Flashback:GNOME Date: Sun Aug 23 14:08:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2020-06-14 (69 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-K 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.:bvr0903:bd10/25/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS 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 20.0.8-0ubuntu1~20.04.1 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/1892626/+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
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => 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/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: Fix Committed 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 1892678] Re: Fix non-working USB devices plugged during system sleep
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => 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/1892678 Title: Fix non-working USB devices plugged during 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] Some USB devices aren't working if they are plugged under system sleep. [Fix] Consider xHCI PORTSC CAS bit over other conditions. [Test] Plug or re-plug USB devices during system sleep. USB devices always work after system resume. [Regression Potential] There could be devices that depends on the old (but wrong) behavior. However it's really unlikely and it's against xHCI spec, we can deal with those quirky devices if any. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1892678/+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 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
This bug affects me as well but in ubuntu 20.04. It's very annoying. I've open a question -> https://answers.launchpad.net/ubuntu/+question/692509 -- 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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1543 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communicatio
[Kernel-packages] [Bug 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1543 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, I
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Ike, Do you mean the 4.15.0-103 kernel in https://kernel.ubuntu.com/~ikepanhc/lp1859756/? Linux.-hwe 5.4 is not an option for me as it breaks parallel filesystem BeeGFS. -- 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 kunpeng920 ubuntu-18.04 series: 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.276