[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests
** Tags added: sru-20200127 ** Tags added: oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1824228 Title: ept test fails in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: New Status in linux-kvm source package in Disco: New Status in linux-oracle source package in Disco: New Status in linux-azure source package in Eoan: New Status in linux-kvm source package in Eoan: New Status in linux-oracle source package in Eoan: New Bug description: Reproducible: Yes, Series: cosmic Kernel: "linux-azure 4.18.0-1015.15" Steps: 1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd /tmp/tmp.RcwfbGP5Ou enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: ept_access_test_not_present Test suite: ept_access_test_read_only Test suite: ept_access_test_write_only Test suite: ept_access_test_read_write Test suite: ept_access_test_execute_only Test suite: ept_access_test_read_execute Test suite: ept_access_test_write_execute Test suite: ept_access_test_read_write_execute Test suite: ept_access_test_reserved_bits Test suite: ept_access_test_ignored_bits Test suite: ept_access_test_paddr_not_present_ad_disabled Test suite: ept_access_test_paddr_not_present_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_only_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312 Test suite: ept_access_test_paddr_read_only_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_write Test suite: ept_access_test_paddr_read_write_execute Test suite: ept_access_test_paddr_read_execute_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312 EPT_VLT_RD
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
** Description changed: [Bug Description] hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: split hclge_reset() into preparing and rebuilding part net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vector net: hns3: re-organize vector handle net: hns3: add trace event support for HNS3 driver update 0120 net: hns3: pad the short frame before sending to the hardware - [Status] - (In Progress): net: hns3: support tx-scatter-gather-fraglist feature - (In Progress): net: hns3: add support for configuring VF MAC from the host - (In Progress): net: hns3: add support for configuring bandwidth of VF on the host - (In Progress): net: hns3: add support for setting VF trust - (In Progress): net: hns3: add support for spoof check setting - (In Progress): net: hns3: add support for setting VF link status on the host - (In Progress): net: hns3: make array tick_array static, makes object smaller + (Fix committed): net: hns3: support tx-scatter-gather-fraglist feature + (Fix committed): net: hns3: add support for configuring VF MAC from the host + (Fix committed): net: hns3: add support for configuring bandwidth of VF on the host + (Fix committed): net: hns3: add
[Kernel-packages] [Bug 1855668] Re: lockdown on power
The commit "a356646a56857c2e5ad875beec734d7145ecd49a" is upstream with 5.5 and named "tracing: Do not create directories if lockdown is in affect". Looking this up in focal master-next tells me that it was indeed picked-up, but under commit "ce5fac3cf42b": tracing: Do not create directories if lockdown is in affect. It's actually in since 5.4.0-13. Since we still have 5.4.0.12 in the focal release pocket, I can't set it to Fix Released, yet - need to wait until 5.4.0.14 migrates from proposed to release. -- 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/1855668 Title: lockdown on power Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Michael Ranweiler - 2019-11-11 08:50:51 == For 20.04 testing/inclusion. The ubuntu kernel team has a ppa here for testing: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable Test results will follow... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+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 1855668] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2020-02-10 01:28 EDT--- I tried this out with the latest kernel in proposed. It looks like the -14 kernel picked up commit a356646a56857c2e5ad875beec734d7145ecd49a and that got rid of the warns. I tired access to /dev/mem and got correct results. -- 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/1855668 Title: lockdown on power Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Michael Ranweiler - 2019-11-11 08:50:51 == For 20.04 testing/inclusion. The ubuntu kernel team has a ppa here for testing: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable Test results will follow... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+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 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error
Patch sent. https://lists.ubuntu.com/archives/kernel- team/2020-February/107343.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/1859744 Title: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04 series: New Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] Because of out-of-order execution about some CPU architecture, In this debug stage we find Completing spi interrupt enable -> prodrucing TXEI interrupt -> running "interrupt_transfer" function will prior to set "dw->rx and dws->rx_end" data, so this patch add memory barrier to enable dw->rx and dw->rx_end to be visible and solve to send SPI data error. eg: it will fix to this following low possibility error in testing environment which using SPI control to connect TPM Modules kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Steps to Reproduce] 1) enable ima and tpm 2)reboot this system 3) [Actual Results] kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Expected Results] ok [Reproducibility] low probabilities [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859744/+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 1861972] Re: [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE kernel branch
Patches sent. https://lists.ubuntu.com/archives/kernel- team/2020-February/107343.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/1861972 Title: [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] hns3 patchset have merged into mainline 5.4rc7 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] (Fix committed) net: hns3: cleanup some coding style issue (In progress) net: hns3: remove redundant print on ENOMEM (In progress) net: hns3: delete unnecessary blank line and space for cleanup (In progress) net: hns3: rewrite a log in hclge_put_vector() (In progress) net: hns3: refine the input parameter 'size' for snprintf() (In progress) net: hns3: move duplicated macro definition into header (In progress) net: hns3: set VF's default reset_type to HNAE3_NONE_RESET (In progress) net: hns3: do not reuse pfmemalloc pages (In progress) net: hns3: limit the error logging in the hns3_clean_tx_ring() (In progress) net: hns3: replace snprintf with scnprintf in hns3_update_strings (In progress) net: hns3: replace snprintf with scnprintf in hns3_dbg_cmd_read (Fix committed) net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861972/+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 1859743] Re: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform
Patch sent. https://lists.ubuntu.com/archives/kernel- team/2020-February/107343.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/1859743 Title: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04 series: New Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-19.10 series: New Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] this patch gets tpm eventlog information such as device boot status,event guid and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog" functions to get it for ARM64 platorm. [Steps to Reproduce] 1) ls -l /sys/kernel/security/tpm0/binary_bios_measurements 2) 3) [Actual Results] '/sys/kernel/security/tpm0/binary_bios_measurements' no such file or directory [Expected Results] ok [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859743/+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 1861165] Re: bionic/linux: 4.15.0-87.87 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 03. February 2020 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1862013 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1862408 - xenial/linux-gcp: bug 1862224, bug 1861160 + xenial/linux-gcp: bug 1861160, bug 1862224 xenial/linux-hwe: bug 1861164 variant: debs -- 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/1861165 Title: bionic/linux: 4.15.0-87.87 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 03. February 2020 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1862013 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1862408 xenial/linux-gcp: bug 1861160, bug 1862224 xenial/linux-hwe: bug 1861164 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861165/+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 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch
Patches sent. https://lists.ubuntu.com/archives/kernel- team/2020-February/107343.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/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+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 1861192] Re: disco/linux: 5.0.0-41.45 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 30. January 2020 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 - bionic/linux-gcp: bug 1861184, bug 1862213 + bionic/linux-gcp: bug 1862213, bug 1861184 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1861178 bionic/linux-oracle-5.0: bug 1861190 variant: debs -- 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/1861192 Title: disco/linux: 5.0.0-41.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 30. January 2020 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 bionic/linux-gcp: bug 1862213, bug 1861184 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1861178 bionic/linux-oracle-5.0: bug 1861190 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861192/+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 1860910] Re: ELAN Touchpad not working on Lenovo Thinkbook with Ubuntu 18.04 and 19.10
This issue should be the duplicated as: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277 If you don't want to change ACPI, please wait for LENOVO's new BIOS. -- 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/1860910 Title: ELAN Touchpad not working on Lenovo Thinkbook with Ubuntu 18.04 and 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I bought a Lenovo Thinkbook (Intel i5 10th generation) Model- 20RV00BNIH just last week. I bought a DOS machine and put ubuntu 18.04 on it, the touchpad hasnt been working ever since. I checked with Win 10, and the touchpad works, so it is not a hardware issue. Then I upgraded to ubuntu 19.10. Kernel is 5.3.0-26-generic #28-Ubuntu SMP Lots of posts on ubuntuforums indicate that 18.10 onwards should fix this issue. They also claim that Kernel 4.18 onwards should fix this issue, but looks like they dont, at least for me. I tried the following. Did not help. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825996 edit /etc/modprobe.d/blacklist.conf add "blacklist i2c_i801" in the blacklist.conf sudo update-initramfs -u reboot When I do a sudo acpidump | grep -C3 ELAN, I get the following 33230: 0F 00 03 04 49 4E 54 31 70 0A 20 49 44 41 44 A4 INT1p. IDAD. 33240: 84 53 42 46 53 53 42 46 49 00 5B 82 4D 0D 54 50 .SBFSSBFI.[.M.TP 33250: 44 32 08 5F 41 44 52 00 08 49 44 41 44 00 08 48 D2._ADR..IDAD..H 33260: 49 44 32 00 08 5F 48 49 44 0D 45 4C 41 4E 30 36 ID2.._HID.ELAN06 33270: 32 46 00 08 5F 43 49 44 0D 50 4E 50 30 43 35 30 2F.._CID.PNP0C50 33280: 00 08 5F 55 49 44 01 14 46 04 5F 44 53 4D 04 A0 .._UID..F._DSM.. 33290: 37 93 68 11 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 7.h... yields nothing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nanditha 1320 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 17:48:17 2020 InstallationDate: Installed on 2020-01-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=1bd35570-763f-4f7e-ae06-6b141cfb7a44 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN22WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN22WW:bd10/23/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrNODPK:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860910/+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 1862567] Re: [SRU][B/OEM-B] Fix multitouch support on some devices
** Changed in: linux-oem (Ubuntu) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-oem (Ubuntu Bionic) Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1862567 Title: [SRU][B/OEM-B] Fix multitouch support on some devices Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: Confirmed Bug description: [Impact] Some LG touchscreens reported themselves as generic touch devices, actually it is multitouch devices. Even after adding IDs in hid-multitouch, hid-generic will bind the device still. multitouch features are not supported. [Fix] commit e04a0442 make hid-generic work nicely with other drivers like hid-multitouch. If other drivers match the devices, hid-generic will step back. This patch will benefit many devices to support their own drivers without adding IDs. [Test] Verified on LG/ELAN/RAYDIUM touchscreens with positive results. [Regression Potential] Medium. commit e04a0442 is included by 4.16 kernel, only bionic kernel should be applied. This commit is based on the other 3 patches, mostly changes are moving codes to hid-quirk.c. Backports are during to the other backports patches, these changes are moved to hid-quirk.c too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862567/+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 1860910] Re: ELAN Touchpad not working on Lenovo Thinkbook with Ubuntu 18.04 and 19.10
Any response from this, from other than a bot? My new Laptop Thinkbook i5 10th gen laptop's touchpad is not working. Lenovo said that they do not support ubuntu, and cannot help here. They cannot replace it with an older 8th gen laptop (on which the touchpad driver is available with ubuntu). Quick fix pls? This is urgent. -- 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/1860910 Title: ELAN Touchpad not working on Lenovo Thinkbook with Ubuntu 18.04 and 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I bought a Lenovo Thinkbook (Intel i5 10th generation) Model- 20RV00BNIH just last week. I bought a DOS machine and put ubuntu 18.04 on it, the touchpad hasnt been working ever since. I checked with Win 10, and the touchpad works, so it is not a hardware issue. Then I upgraded to ubuntu 19.10. Kernel is 5.3.0-26-generic #28-Ubuntu SMP Lots of posts on ubuntuforums indicate that 18.10 onwards should fix this issue. They also claim that Kernel 4.18 onwards should fix this issue, but looks like they dont, at least for me. I tried the following. Did not help. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825996 edit /etc/modprobe.d/blacklist.conf add "blacklist i2c_i801" in the blacklist.conf sudo update-initramfs -u reboot When I do a sudo acpidump | grep -C3 ELAN, I get the following 33230: 0F 00 03 04 49 4E 54 31 70 0A 20 49 44 41 44 A4 INT1p. IDAD. 33240: 84 53 42 46 53 53 42 46 49 00 5B 82 4D 0D 54 50 .SBFSSBFI.[.M.TP 33250: 44 32 08 5F 41 44 52 00 08 49 44 41 44 00 08 48 D2._ADR..IDAD..H 33260: 49 44 32 00 08 5F 48 49 44 0D 45 4C 41 4E 30 36 ID2.._HID.ELAN06 33270: 32 46 00 08 5F 43 49 44 0D 50 4E 50 30 43 35 30 2F.._CID.PNP0C50 33280: 00 08 5F 55 49 44 01 14 46 04 5F 44 53 4D 04 A0 .._UID..F._DSM.. 33290: 37 93 68 11 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 7.h... yields nothing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nanditha 1320 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 17:48:17 2020 InstallationDate: Installed on 2020-01-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=1bd35570-763f-4f7e-ae06-6b141cfb7a44 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN22WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN22WW:bd10/23/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrNODPK:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860910/+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 1851969] Re: Kernel 5.0.0-31 or another 5 kernel problem with Realtek RTL8111/8168/8411 Download Speed
[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/1851969 Title: Kernel 5.0.0-31 or another 5 kernel problem with Realtek RTL8111/8168/8411 Download Speed Status in linux package in Ubuntu: Expired Bug description: Many problem s with download speed reduced problem. Not occurs at 4.18 kernels or kernel below 5 versions. I tried most updated like Kernel 5.3. Not works too. Device: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Modules working at 4.18 kernel: r8169 86016 0 mii16384 1 r8169 Temporary using fixed 4.18 kernel. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851969/+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 1862101] Re: ubuntu_zfs_fstest / ubuntu_zfs_xfs_generic failed to build on Focal 5.4
Test passed with Focal now, thank you! ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- 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/1862101 Title: ubuntu_zfs_fstest / ubuntu_zfs_xfs_generic failed to build on Focal 5.4 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Bug description: The test build will failed because of unmet dependencies of zfsutils- linux and zfs-dkms package apt-get install --yes --force-yes build-essential gdb git gcc zfsutils-linux stdout: Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.8ubuntu1). gcc is already the newest version (4:9.2.1-3.1ubuntu1). gdb is already the newest version (9.0.90.20200117-0ubuntu1). git is already the newest version (1:2.25.0-1ubuntu1). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: zfsutils-linux : Breaks: zfs-dkms (< 0.8.3-1ubuntu2) stderr: W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862101/+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 1862567] Re: [SRU][B/OEM-B] Fix multitouch support on some devices
** Description changed: [Impact] Some LG touchscreens reported themselves as generic touch devices, actually it is multitouch devices. Even after adding IDs in hid-multitouch, hid-generic will bind the device still. multitouch features are not supported. [Fix] commit e04a0442 make hid-generic work nicely with other drivers like hid-multitouch. If other drivers match the devices, hid-generic will step back. This patch will benefit many devices to support their own drivers without adding IDs. [Test] Verified on LG/ELAN/RAYDIUM touchscreens with positive results. [Regression Potential] Medium. commit e04a0442 is included by 4.16 kernel, only bionic kernel should be applied. This commit is based on the other 3 patches, mostly changes are moving codes to hid-quirk.c. + Backports are during to the other backports patches, these changes are moved to + hid-quirk.c too. -- 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/1862567 Title: [SRU][B/OEM-B] Fix multitouch support on some devices Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: New Bug description: [Impact] Some LG touchscreens reported themselves as generic touch devices, actually it is multitouch devices. Even after adding IDs in hid-multitouch, hid-generic will bind the device still. multitouch features are not supported. [Fix] commit e04a0442 make hid-generic work nicely with other drivers like hid-multitouch. If other drivers match the devices, hid-generic will step back. This patch will benefit many devices to support their own drivers without adding IDs. [Test] Verified on LG/ELAN/RAYDIUM touchscreens with positive results. [Regression Potential] Medium. commit e04a0442 is included by 4.16 kernel, only bionic kernel should be applied. This commit is based on the other 3 patches, mostly changes are moving codes to hid-quirk.c. Backports are during to the other backports patches, these changes are moved to hid-quirk.c too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862567/+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 1847937] Re: 'gpu has fallen off the bus' after return from suspend
I upgraded my kernel to 5.4.18 and the issue is still appearing for me. $ uname -a Linux pop-os 5.4.18-050418-generic #202002051737 SMP Wed Feb 5 22:42:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ nvidia-detector nvidia-driver-440 -- 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/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Triaged Bug description: With this message the only way to resume work is to reboot the system using power button. With kernel linux-image-5.3.0-13-generic everything is OK. Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still happens in linux-image-5.3.0-18-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: player 4451 F pulseaudio /dev/snd/controlC1: player 4451 F pulseaudio /dev/snd/controlC0: player 4451 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 14 01:27:04 2019 HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e MachineType: LENOVO 20BG0016US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current loglevel=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago) WifiSyslog: dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.sku: LENOVO_MT_20BG dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+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 1862567] 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 1862567 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 ** Changed in: linux (Ubuntu Bionic) 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/1862567 Title: [SRU][B/OEM-B] Fix multitouch support on some devices Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: New Bug description: [Impact] Some LG touchscreens reported themselves as generic touch devices, actually it is multitouch devices. Even after adding IDs in hid-multitouch, hid-generic will bind the device still. multitouch features are not supported. [Fix] commit e04a0442 make hid-generic work nicely with other drivers like hid-multitouch. If other drivers match the devices, hid-generic will step back. This patch will benefit many devices to support their own drivers without adding IDs. [Test] Verified on LG/ELAN/RAYDIUM touchscreens with positive results. [Regression Potential] Medium. commit e04a0442 is included by 4.16 kernel, only bionic kernel should be applied. This commit is based on the other 3 patches, mostly changes are moving codes to hid-quirk.c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862567/+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 1861837] Re: machine doesn't come up after suspend and re-opening the lid
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Hello Edwin, Here is more information on the issue we are seeing wrt dropped packets and other connectivity issues with this NIC. The problem is *only* seen when the second port on the NIC is chosen as the active interface of a active-backup configuration. So on the "bad" system with the interfaces: enp94s0f0 -> when chosen as active, all OK enp94s0f1d1 -> when chosen as active, not OK I'll see if the reporters can confirm that on the "good" systems, there was no problem when the second interface is active. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested
[Kernel-packages] [Bug 1862567] [NEW] [SRU][B/OEM-B] Fix multitouch support on some devices
Public bug reported: [Impact] Some LG touchscreens reported themselves as generic touch devices, actually it is multitouch devices. Even after adding IDs in hid-multitouch, hid-generic will bind the device still. multitouch features are not supported. [Fix] commit e04a0442 make hid-generic work nicely with other drivers like hid-multitouch. If other drivers match the devices, hid-generic will step back. This patch will benefit many devices to support their own drivers without adding IDs. [Test] Verified on LG/ELAN/RAYDIUM touchscreens with positive results. [Regression Potential] Medium. commit e04a0442 is included by 4.16 kernel, only bionic kernel should be applied. This commit is based on the other 3 patches, mostly changes are moving codes to hid-quirk.c. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) 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/1862567 Title: [SRU][B/OEM-B] Fix multitouch support on some devices Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: New Bug description: [Impact] Some LG touchscreens reported themselves as generic touch devices, actually it is multitouch devices. Even after adding IDs in hid-multitouch, hid-generic will bind the device still. multitouch features are not supported. [Fix] commit e04a0442 make hid-generic work nicely with other drivers like hid-multitouch. If other drivers match the devices, hid-generic will step back. This patch will benefit many devices to support their own drivers without adding IDs. [Test] Verified on LG/ELAN/RAYDIUM touchscreens with positive results. [Regression Potential] Medium. commit e04a0442 is included by 4.16 kernel, only bionic kernel should be applied. This commit is based on the other 3 patches, mostly changes are moving codes to hid-quirk.c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862567/+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 1861330] Re: Battery status unknown on Lenovo X1 Carbon Extreme Gen 2
** Tags added: champagne -- 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/1861330 Title: Battery status unknown on Lenovo X1 Carbon Extreme Gen 2 Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo X1 Carbon Extreme Gen 2. When I first installed Focal on it battery status was working however its now stuck at 59% even though its been charging for days. $ cat /sys/class/power_supply/BAT0/status Unknown $ cat /sys/class/power_supply/BAT0/capacity 59 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lee4054 F pulseaudio /dev/snd/controlC1: lee4054 F pulseaudio /dev/snd/controlC0: lee4054 F pulseaudio /dev/snd/pcmC0D0p: lee4054 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-29 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220) MachineType: LENOVO 20QVCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=/dev/mapper/samsung--ssd-ROOT ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861330/+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 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen
** Description changed: + [Impact] + There are 2 physical speakers on the X1 7th, and one is Bass speaker + and connect to a DAC which doesn't have volume control on it. + + [Fix] + adjust that speaker to connect to a DAC which has volume control + capability. + + + [Test Case] + adjust the output volume from UI and play sound from speaker. + + + [Regression Risk] + Low, these change is specific to 2 lenovo machines. + + On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in speakers, the volume is either off or on, there's no gradation in volume when I move the slider up or down. If I enable Over-Amplification than there's gradation in volume when I turn the volume up past 100%, but not for 0-100%. This problem does not occur with a headset plugged into the 3.5mm jack. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jik3746 F pulseaudio - /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jik3746 F pulseaudio + /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:07:44 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.3.0-12-generic N/A - linux-backports-modules-5.3.0-12-generic N/A - linux-firmware1.182 + linux-restricted-modules-5.3.0-12-generic N/A + linux-backports-modules-5.3.0-12-generic N/A + linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO -- 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/1845677 Title: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen Status in linux package in Ubuntu: Confirmed Bug description: [Impact] There are 2 physical speakers on the X1 7th, and one is Bass speaker and connect to a DAC which doesn't have volume control on it. [Fix] adjust that speaker to connect to a DAC which has volume control capability. [Test Case] adjust the output volume from UI and play sound from speaker. [Regression Risk] Low, these change is specific to 2 lenovo machines. On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in speakers, the volume is either off or on, there's no gradation in volume when I move the slider up or down. If I enable Over-Amplification than there's gradation in volume when I turn the volume up past 100%, but not for 0-100%. This problem does not occur with a headset plugged into the 3.5mm jack. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:07:44 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182
[Kernel-packages] [Bug 1862563] [NEW] nvidia optimus vulkan layer is placed in the wrong directory
Public bug reported: The vulkan layer file that is provided with the nvidia driver to control which vulkan device appears as device 0 in hybrid configurations is installed in the wrong location with the current packages, preventing it from working. It currently goes to: /usr/share/vulkan/icd.d/nvidia_layers.json and it should go to: /usr/share/vulkan/implicit_layer.d/nvidia_layers.json Manually moving the file allows the layer to work. ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Package changed: nvidia-graphics-drivers-375 (Ubuntu) => nvidia- graphics-drivers-440 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1862563 Title: nvidia optimus vulkan layer is placed in the wrong directory Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: The vulkan layer file that is provided with the nvidia driver to control which vulkan device appears as device 0 in hybrid configurations is installed in the wrong location with the current packages, preventing it from working. It currently goes to: /usr/share/vulkan/icd.d/nvidia_layers.json and it should go to: /usr/share/vulkan/implicit_layer.d/nvidia_layers.json Manually moving the file allows the layer to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1862563/+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 1856045] Re: capabilities set with setcap are not honoured
Well this is a consequence of this upstream change in iproute2: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?h=v4.16.0=ba2fc55b99f8363c80ce36681bc1ec97690b66f5. Upstream discussion, such as it is, of the patch appears to be here: https://lore.kernel.org/netdev/20180327162419.8962-1-bl...@debian.org/ Probably the next step is to email the netdev list about this. Is that something you would be interested in doing? You are probably better able to explain your use case than I am! ** Changed in: iproute2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1856045 Title: capabilities set with setcap are not honoured Status in iproute2 package in Ubuntu: Triaged Status in iproute2 source package in Eoan: Confirmed Bug description: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+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 1856045] Re: capabilities set with setcap are not honoured
** Package changed: libcap2 (Ubuntu) => iproute2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1856045 Title: capabilities set with setcap are not honoured Status in iproute2 package in Ubuntu: New Status in iproute2 source package in Eoan: Confirmed Bug description: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+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 1856045] Re: capabilities set with setcap are not honoured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1856045 Title: capabilities set with setcap are not honoured Status in iproute2 package in Ubuntu: New Status in iproute2 source package in Eoan: Confirmed Bug description: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+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 1861070] Re: Raspberry Pi 4B: USB OTG is not working
** Description changed: + [Impact] + On the RPI4B board, the usb-c power port could also work as a USB + OTG mode, but we set the dwc2 driver to the host mode + unconditionally, now set it to dual_role mode, then it could work + in host/otg/peripheal mode. + + [Fix] + Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n + + + [Test Case] + set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, + and isnmod the g_ether or g_cdc, on the host machine, we could see + RPI4B work as a usb device. + + Because physical port limitation, could test dr_mode=host. + + [Regression Risk] + Low, our eoan kernel choose dwc_otg driver for this port by default, + very very few users will choose dwc2 driver, and the dwc2 driver is + not enabled by default in our kernel. + + And bug reporter and I already tested that the peripheral mode works + after this change. + + I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi2 package in Ubuntu: Triaged Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by
[Kernel-packages] [Bug 1856045] [NEW] capabilities set with setcap are not honoured
You have been subscribed to a public bug: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Affects: iproute2 (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan id-5dfbada861bbb0737ab3648f -- capabilities set with setcap are not honoured https://bugs.launchpad.net/bugs/1856045 You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 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 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
Thanks. It sounds like the problem is either in Xorg or in the kernel. Please log into "Ubuntu on Wayland" or install 'weston' and try that. We need to know if the same bug occurs in a Wayland compositor without any Xorg server running. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => xorg-server (Ubuntu) ** 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/1862281 Title: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: If I run a thermal transition test script (30 seconds stress-ng, 30 seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably crashes, usually in the first couple of runs and almost 100% of the time by run 6. This appears to be hardware-linked, but not due to a specific piece of bad hardware: I have swapped literally every piece of hardware in the system. It shows up (while running the script at the end): - On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard. - On both an AMD Ryzen 5 3600 and 3600X CPU. - With one or two sticks of RAM. I've tested both sticks individually, in more than one mainboard slot. - Regardless of whether the mainboard is in/attached to a case. - Regardless of whether there is an m.2 SSD installed or I'm running off a live Kubuntu 19.10 USB stick with no hard disk attached. - Regardless of which of two mice I use (an old Logitech one, or a GTX 133 Gaming mouse). - Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU. - Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases). - Regardless of whether I'm using KDE or XFCE. - Regardless of whether I'm using the default KDE DM or switch to GDM3 and set WaylandEnable=false. - Regardless of whether I use the default 5.3.0-29-generic kernel or 5.4.17-050417-generic. - Regardless of whether I go directly into the graphical environment or start in runlevel 3 and then manually run startx. - Regardless of whether it's on the rising or falling edge of the stress-script's temperature changes. - Regardless of bios version on the X570 mainboard (the one it shipped with, or the newest one released in January 2020). - Regardless of whether XMP is on or off in the bios. - Regardless of whether I use the default or set global c-state to "control = disabled" in the bios. - Regardless of whether I add processor.max_cstate=5 idle=halt in grub. - Regardless of whether or not speakers are plugged in. - Regardless of whether I'm using a USB port that is directly on the motherboard or is on the front of the case. - Regardless of which monitor it is attached to. It doesn't show up: - On an old i7-4771 machine I have, also running Kubuntu 19.10, while running the test script. - When I use a mouse remotely with ssh -Y [ip of the machine I am reporting this from] xeyes, while running the test script. - When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle, including under saturated network load, while running the test script. - During stress tests of the GPU, CPU, etc. Tools like memtest, mprime, Unigine Superposition, repeated kernel compiles, etc run stably overnight. - When the system is entirely idle aside from mouse movement. - When I start in runlevel 3 and run the same test script, using the mouse with gpm. - Running the same test script without mouse movement: this was stable overnight, then crashed within a couple of minutes of moving the mouse. It shows up with load other than the stress-ng+sleep script too, but much less reliably - I'm writing this bug report on the relevant machine, with firefox open. Crashes occur at least once a week under these conditions, but not frequently. Crashes occur with sensor-reported CPU temperatures of 32 to 41 degrees Celsius. Nothing is overheating, and the system is stable at much higher temperatures under sustained stress tests. The symptoms of the crash: the display stops updating and the system does not respond to any further input, including via the network or magic sysrq key. There is nothing related to it in syslog or journalctl, including when I'm running journalctl -f at the time of the crash. The test script: #!/bin/bash for x in {1..1} do echo "Run $x at `date`" stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief sleep 30 done ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.4.17-050417-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2
[Kernel-packages] [Bug 1856908] Re: Sometimes my Lenovo v310 freezes completely while playing music
Sounds promising. Kernel 4.15 has the bug and 4.20 onward does not. We really just need to figure out exactly which version fixed it. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1856908 Title: Sometimes my Lenovo v310 freezes completely while playing music Status in linux package in Ubuntu: Confirmed Bug description: $lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $uname -a Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux audacious: 3.6.2-2 What happened: Sometimes my Lenovo v310 freezes completely while playing music (Audacious). This is something i found in syslog. Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here ] Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active) Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 at /build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev serio_raw snd_seq media wmi_bmof snd_seq_device Dec 19 03:01:53 localhost kernel: [12615.594456] intel_wmi_thunderbolt snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: kworker/u8:0 Tainted: G OE4.15.0-73-generic #82~16.04.1-Ubuntu Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, BIOS 0ZCN30WW 12/08/2016 Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound intel_atomic_commit_work [i915] Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 0010:intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 EFLAGS: 00010286 Dec 19 03:01:53 localhost kernel: [12615.594969] RAX: RBX: a06e2a00 RCX: 97e63a28 Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 0082 RDI: 0202 Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: fffa734938d0 R09: Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 0367 R12: a06c56299000 Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: a06c5629f000 R15: a06e2a00 Dec 19 03:01:53 localhost kernel: [12615.594997] FS: () GS:a06e3ec0() knlGS: Dec 19 03:01:53 localhost kernel: [12615.595003] CS: 0010 DS: ES: CR0: 80050033 Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 000210a0a001 CR4: 003626f0 Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace: Dec 19 03:01:53 localhost kernel: [12615.595197] ? intel_pre_plane_update+0x12f/0x190 [i915] Dec 19 03:01:53 localhost kernel: [12615.595371] intel_update_crtc+0x75/0xa0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595526] skl_update_crtcs+0x1a9/0x1f0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595663] intel_atomic_commit_tail+0x3c8/0xe00 [i915] Dec 19 03:01:53 localhost kernel: [12615.595676] ? __switch_to+0x9b/0x4e0 Dec 19 03:01:53 localhost kernel: [12615.595687] ? __switch_to_asm+0x35/0x70 Dec 19 03:01:53 localhost kernel: [12615.595819] intel_atomic_commit_work+0x12/0x20 [i915] Dec 19 03:01:53 localhost kernel: [12615.595830] process_one_work+0x14d/0x410 Dec 19 03:01:53 localhost kernel: [12615.595839] worker_thread+0x4b/0x460 Dec 19 03:01:53 localhost kernel: [12615.595853] kthread+0x105/0x140 Dec 19 03:01:53 localhost
[Kernel-packages] [Bug 1862312] Re: Bionic powerpc hang with ubuntu_kernel_selftests (kernel oops)
This issue can be found on node modoc with Bionic as well [ 1148.018124] Injecting error (-12) to MEM_GOING_ONLINE [ 1148.019950] Injecting error (-12) to MEM_GOING_ONLINE [ 1148.021889] Injecting error (-12) to MEM_GOING_ONLINE [ 1149.494309] [ cut here ] [ 1149.494314] kernel BUG at /build/linux-CWyQTi/linux-4.15.0/kernel/rcu/sync.c:128! [ 1149.494330] Oops: Exception in kernel mode, sig: 5 [#1] [ 1149.494333] LE SMP NR_CPUS=2048 NUMA PowerNV [ 1149.494338] Modules linked in: memory_notifier_error_inject notifier_error_inject overlay veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter binfmt_misc leds_powernv powernv_op_panel uio_pdrv_genirq uio ipmi_powernv ipmi_devintf powernv_rng ibmpowernv ipmi_msghandler vmx_crypto sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: test_bpf] [ 1149.494411] CPU: 44 PID: 140088 Comm: mem-on-off-test Not tainted 4.15.0-87-generic #87-Ubuntu [ 1149.494416] NIP: c01a8490 LR: c01a8478 CTR: c026c5e0 [ 1149.494421] REGS: c00f06d677c0 TRAP: 0700 Not tainted (4.15.0-87-generic) [ 1149.494425] MSR: 90010282b033 CR: 28222888 XER: 2000 [ 1149.494435] CFAR: c001940c SOFTE: 1 [ 1149.494435] GPR00: c01a8434 c00f06d67a40 c172c900 0001 [ 1149.494435] GPR04: 01f0 001ffdd1 0092c39e6cf7 [ 1149.494435] GPR08: 001ffdd1 0001 c00f09be9390 [ 1149.494435] GPR12: 2200 cfa9e400 0b644f99e4d0 [ 1149.494435] GPR16: 0b6422f19690 0b6422fa6ab0 0b6422fd8204 0b6422fa6ae8 [ 1149.494435] GPR20: 0b6422fdd5d8 0001 7fffd94fe1a4 [ 1149.494435] GPR24: 7fffd94fe1a0 c1763428 c15f6ba8 [ 1149.494435] GPR28: 0020 c15f6bb0 fff9 c15f6ba8 [ 1149.494482] NIP [c01a8490] rcu_sync_enter+0xa0/0x1e0 [ 1149.494487] LR [c01a8478] rcu_sync_enter+0x88/0x1e0 [ 1149.494490] Call Trace: [ 1149.494495] [c00f06d67a40] [c00f06d67aa0] 0xc00f06d67aa0 (unreliable) [ 1149.494503] [c00f06d67ab0] [c01889a8] percpu_down_write+0x38/0x140 [ 1149.494510] [c00f06d67b00] [c039fa6c] online_pages+0x1fc/0x440 [ 1149.494517] [c00f06d67bd0] [c08a7320] memory_subsys_online+0x180/0x250 [ 1149.494524] [c00f06d67c60] [c0879f54] device_online+0x84/0x120 [ 1149.494530] [c00f06d67ca0] [c08a7ee8] store_mem_state+0xb8/0x180 [ 1149.494535] [c00f06d67ce0] [c08744bc] dev_attr_store+0x3c/0x60 [ 1149.494541] [c00f06d67d00] [c04ae254] sysfs_kf_write+0x64/0x90 [ 1149.494546] [c00f06d67d20] [c04acf2c] kernfs_fop_write+0x1ac/0x240 [ 1149.494552] [c00f06d67d70] [c03e147c] __vfs_write+0x3c/0x70 [ 1149.494557] [c00f06d67d90] [c03e16d8] vfs_write+0xd8/0x220 [ 1149.494562] [c00f06d67de0] [c03e1a38] SyS_write+0x78/0x140 [ 1149.494568] [c00f06d67e30] [c000b288] system_call+0x5c/0x70 [ 1149.494572] Instruction dump: [ 1149.494575] 409e00b0 7c2004ac 3920 3861 913f0008 4be70f85 6000 2fbe [ 1149.494582] 3920 419e000c 7f9c0034 5789d97e <0b09> 4092008c 813f0038 3d42fffb [ 1149.494590] ---[ end trace 45d06205be58a4bd ]--- [ 1149.495015] ** Summary changed: - P9 node baltar hang with ubuntu_kernel_selftests (kernel oops) + Bionic powerpc hang with ubuntu_kernel_selftests (kernel oops) -- 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/1862312 Title: Bionic powerpc hang with ubuntu_kernel_selftests (kernel oops) Status in linux package in Ubuntu: Incomplete Bug description: It looks like some test inside the ubuntu_kernel_selftests has triggered this issue, the jenkins job "sru-misc__B_ppc64el- generic__using_baltar__for_kernel" hung at the same spot (the beginning of the KVM unit test) for two out of two attempts: 05:06:37 INFO | GOODubuntu_kvm_unit_tests.setup ubuntu_kvm_unit_tests.setup timestamp=1580792797localtime=Feb 04 05:06:37 completed successfully 05:06:37 INFO | END GOODubuntu_kvm_unit_tests.setup ubuntu_kvm_unit_tests.setup timestamp=1580792797localtime=Feb 04 05:06:37 05:06:37 DEBUG| Persistent state
[Kernel-packages] [Bug 1862559] 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 1862559 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: eoan -- 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/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in linux package in Ubuntu: Incomplete Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862559/+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 1862559] [NEW] ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
Public bug reported: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in linux package in Ubuntu: New Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit:
Re: [Kernel-packages] [Bug 1856908] Re: Sometimes my Lenovo v310 freezes completely while playing music
Sorry, I didn’t answer for a long time. The results of my tests surprised me a bit: - kernel 5.5.2 works fine, even though I had to recompile the VirtualBox kernel module with GCC 9 - kernel 5.3.18 works fine - kernel 4.20.17 works fine - kernel 4.15.0.87 (last updates) run into the same problem as before: Feb 10 03:30:19 localhost kernel: [32746.808522] [ cut here ] Feb 10 03:30:19 localhost kernel: [32746.808525] WARN_ON(fbc->active) Feb 10 03:30:19 localhost kernel: [32746.808735] WARNING: CPU: 3 PID: 14663 at /build/linux-hwe-LVnYcm/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 intel_fbc_enable+0x3ed/0x570 [i915] Feb 10 03:30:19 localhost kernel: [32746.808738] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm rfcomm bnep zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rtsx_usb_ms memstick uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 iwlmvm mac80211 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_hda_codec_realtek snd_soc_sst_ipc snd_soc_acpi snd_hda_codec_generic snd_soc_core intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel kvm snd_hda_codec irqbypass snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel pcbc snd_pcm snd_seq_midi snd_seq_midi_event aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_rawmidi intel_cstate intel_rapl_perf Feb 10 03:30:19 localhost kernel: [32746.808808] snd_seq joydev snd_seq_device snd_timer input_leds wmi_bmof intel_wmi_thunderbolt serio_raw snd btusb btrtl btbcm btintel soundcore iwlwifi bluetooth ecdh_generic cfg80211 shpchp mei_me mei intel_pch_thermal ideapad_laptop sparse_keymap acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrfs xor zstd_compress raid6_pq hid_generic i915 i2c_algo_bit rtsx_usb_sdmmc drm_kms_helper usbhid syscopyarea sysfillrect sysimgblt rtsx_usb hid fb_sys_fops psmouse r8169 ahci drm mii libahci wmi video Feb 10 03:30:19 localhost kernel: [32746.808870] CPU: 3 PID: 14663 Comm: kworker/u8:0 Tainted: P OE4.15.0-87-generic #87~16.04.1-Ubuntu Feb 10 03:30:19 localhost kernel: [32746.808873] Hardware name: LENOVO 80SY/, BIOS 0ZCN30WW 12/08/2016 Feb 10 03:30:19 localhost kernel: [32746.808996] Workqueue: events_unbound intel_atomic_commit_work [i915] Feb 10 03:30:19 localhost kernel: [32746.809112] RIP: 0010:intel_fbc_enable+0x3ed/0x570 [i915] Feb 10 03:30:19 localhost kernel: [32746.809116] RSP: 0018:b11005aa7cb0 EFLAGS: 00010286 Feb 10 03:30:19 localhost kernel: [32746.809121] RAX: RBX: 8e19a9fe RCX: Feb 10 03:30:19 localhost kernel: [32746.809124] RDX: 0014 RSI: 9675bc34 RDI: 0246 Feb 10 03:30:19 localhost kernel: [32746.809127] RBP: b11005aa7d00 R08: fffa8539e412 R09: Feb 10 03:30:19 localhost kernel: [32746.809130] R10: b11005aa7c88 R11: 037a R12: 8e17f22e5000 Feb 10 03:30:19 localhost kernel: [32746.809133] R13: 8e19b0efdb00 R14: 8e193ab5a800 R15: 8e19a9fe Feb 10 03:30:19 localhost kernel: [32746.809138] FS: () GS:8e19bed8() knlGS: Feb 10 03:30:19 localhost kernel: [32746.809142] CS: 0010 DS: ES: CR0: 80050033 Feb 10 03:30:19 localhost kernel: [32746.809145] CR2: e120e000 CR3: 000143a0a005 CR4: 003626e0 Feb 10 03:30:19 localhost kernel: [32746.809148] Call Trace: Feb 10 03:30:19 localhost kernel: [32746.809262] ? intel_pre_plane_update+0x12f/0x190 [i915] Feb 10 03:30:19 localhost kernel: [32746.809371] intel_update_crtc+0x75/0xa0 [i915] Feb 10 03:30:19 localhost kernel: [32746.809477] skl_update_crtcs+0x1a9/0x1f0 [i915] Feb 10 03:30:19 localhost kernel: [32746.809596] intel_atomic_commit_tail+0x3c8/0xe00 [i915] Feb 10 03:30:19 localhost kernel: [32746.809607] ? __switch_to+0x9b/0x4e0 Feb 10 03:30:19 localhost kernel: [32746.809616] ? __switch_to_asm+0x35/0x70 Feb 10 03:30:19 localhost kernel: [32746.809720] intel_atomic_commit_work+0x12/0x20 [i915] Feb 10 03:30:19 localhost kernel: [32746.809729] process_one_work+0x14d/0x410 Feb 10 03:30:19 localhost kernel: [32746.809736] worker_thread+0x4b/0x460 Feb 10 03:30:19 localhost kernel: [32746.809742] kthread+0x105/0x140 Feb 10 03:30:19 localhost kernel: [32746.809749] ? process_one_work+0x410/0x410 Feb 10 03:30:19 localhost kernel: [32746.809754] ? kthread_bind+0x40/0x40 Feb 10 03:30:19 localhost kernel: [32746.809762] ret_from_fork+0x35/0x40 Feb 10 03:30:19 localhost kernel: [32746.809767] Code: 4a 03 00 00 00 0f 84 55 01 00 00 80 bb ca 2c 00 00 00 0f 84 1c ff ff ff 48 c7 c6 5e 44 6e c0 48 c7 c7 44 44 6e c0 e8 a3 00 83 d4 <0f> 0b e9 02 ff ff ff 3d 00 08 00 00 ba 00 08 00 00 0f 4f c2 e9 Feb 10 03:30:19 localhost kernel: [32746.809838] ---[ end trace 82e85d01278b82eb ]--- Do not know, is it
[Kernel-packages] [Bug 1803179]
(In reply to Matthias Fulz from comment #161) > I'm just using bumblebee and do not blacklist nvidia modules. > > This is my /etc/bumblebee/xorg.conf.nvidia > > Section "ServerLayout" > Identifier "Layout0" > Option "AutoAddDevices" "true" > Option "AutoAddGPU" "false" > EndSection > > Section "Device" > Identifier "DiscreteNvidia" > Driver "nvidia" > VendorName "NVIDIA Corporation" > > > Option "NoLogo" "true" > Option "UseEDID" "false" > Option "AllowEmptyInitialConfiguration" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "DiscreteNvidia" > EndSection > > And I'm just using an additional systemd service for powertop > /etc/systemd/system/powertop.service: > > [Unit] > Description=PowerTOP auto tune > > [Service] > Type=idle > Environment="TERM=dumb" > ExecStart=/usr/bin/bash -c "sleep 30 && /usr/bin/powertop --auto-tune && > sleep 10 && echo 'on' > '/sys/bus/usb/devices/1-1/power/control'" > > [Install] > WantedBy=multi-user.target > > Then I've everything ready and can use: > primusrun > optirum > > for nvidia GPU stuff. For the unloading of the modules after the use I'm > using the following scripts: > > /usr/local/bin/primusrun > > #!/bin/bash > > trap unload 1 2 3 6 > > unload() { > /usr/bin/lsmod | grep nvidia > /dev/null 2>&1 > if [ $? -eq 0 ] > then > echo "unloading nvidia modules ..." > sleep 2 > /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1 > if [ $? -eq 0 ] > then > sudo /usr/bin/rmmod nvidia_modeset > fi > sudo /usr/bin/rmmod nvidia > echo "finished." > fi > } > > primusrun $@ > unload > > /usr/local/bin/optirun > > #!/bin/bash > > trap unload 1 2 3 6 > > unload() { > /usr/bin/lsmod | grep nvidia > /dev/null 2>&1 > if [ $? -eq 0 ] > then > echo "unloading nvidia modules ..." > sleep 2 > /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1 > if [ $? -eq 0 ] > then > sudo /usr/bin/rmmod nvidia_modeset > fi > sudo /usr/bin/rmmod nvidia > echo "finished." > fi > } > > optirun $@ > unload > > That's it for me. > > In addition for powersavings I'm using TLP with quite default settings. > > Offloading inside the nvidia drivers is just not really helpful afaik :) > > Hope that helps. Cheers! I'll see what I can do there :) Thank you so much for all the help -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15
[Kernel-packages] [Bug 1803179]
(In reply to Matthias Fulz from comment #159) > Yep the problem is bbswitch. Just deinstall it, make sure the power mode for > nvidia gpu and hdmi sound are set to auto and unload the nvidia & > nvidia_modeset modules. > > bbswitch will still lead to the lockups, if used. Awesome! Blacklisting the modules, then setting runtime power management to auto for everything in powertop put the power usage down to about 8W. Loading the modules back up again manually puts the power usage back up, and unloading them back down, without having to use bbswitch at all. Do you know if it's possible to, with an X session that started up without the nvidia modules loaded, then turn those modules on and use that GPU with "__NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia "$@"" (the PRIME render offload in the recent drivers). I've so far not had any success :( -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+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 1803179]
I'm just using bumblebee and do not blacklist nvidia modules. This is my /etc/bumblebee/xorg.conf.nvidia Section "ServerLayout" Identifier "Layout0" Option "AutoAddDevices" "true" Option "AutoAddGPU" "false" EndSection Section "Device" Identifier "DiscreteNvidia" Driver "nvidia" VendorName "NVIDIA Corporation" Option "NoLogo" "true" Option "UseEDID" "false" Option "AllowEmptyInitialConfiguration" EndSection Section "Screen" Identifier "Screen0" Device "DiscreteNvidia" EndSection And I'm just using an additional systemd service for powertop /etc/systemd/system/powertop.service: [Unit] Description=PowerTOP auto tune [Service] Type=idle Environment="TERM=dumb" ExecStart=/usr/bin/bash -c "sleep 30 && /usr/bin/powertop --auto-tune && sleep 10 && echo 'on' > '/sys/bus/usb/devices/1-1/power/control'" [Install] WantedBy=multi-user.target Then I've everything ready and can use: primusrun optirum for nvidia GPU stuff. For the unloading of the modules after the use I'm using the following scripts: /usr/local/bin/primusrun #!/bin/bash trap unload 1 2 3 6 unload() { /usr/bin/lsmod | grep nvidia > /dev/null 2>&1 if [ $? -eq 0 ] then echo "unloading nvidia modules ..." sleep 2 /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1 if [ $? -eq 0 ] then sudo /usr/bin/rmmod nvidia_modeset fi sudo /usr/bin/rmmod nvidia echo "finished." fi } primusrun $@ unload /usr/local/bin/optirun #!/bin/bash trap unload 1 2 3 6 unload() { /usr/bin/lsmod | grep nvidia > /dev/null 2>&1 if [ $? -eq 0 ] then echo "unloading nvidia modules ..." sleep 2 /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1 if [ $? -eq 0 ] then sudo /usr/bin/rmmod nvidia_modeset fi sudo /usr/bin/rmmod nvidia echo "finished." fi } optirun $@ unload That's it for me. In addition for powersavings I'm using TLP with quite default settings. Offloading inside the nvidia drivers is just not really helpful afaik :) Hope that helps. -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
Recent updates (kernel I guess) seem to have fixed this for me. Drivers are loaded and being used, laptop goes to sleep and wakes up fine. jonpad@jonpad-laptop ~ $ uname -a Linux jonpad-laptop 5.4.0-12-generic #15-Ubuntu SMP Tue Jan 21 15:12:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux jonpad@jonpad-laptop ~ $ sudo journalctl | grep "PM: suspend" | tail -2 Feb 10 08:16:25 jonpad-laptop kernel: PM: suspend entry (s2idle) Feb 10 09:39:04 jonpad-laptop kernel: PM: suspend exit jonpad@jonpad-laptop ~ $ nvidia-detector nvidia-driver-440 jonpad@jonpad-laptop ~ $ sudo lsmod | grep -i nvidia nvidia_uvm954368 0 nvidia_drm 45056 3 nvidia_modeset 1114112 2 nvidia_drm nvidia 20422656 79 nvidia_uvm,nvidia_modeset drm_kms_helper184320 2 nvidia_drm,i915 drm 487424 20 drm_kms_helper,nvidia_drm,i915 ipmi_msghandler 106496 2 ipmi_devintf,nvidia -- 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/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Triaged Bug description: With this message the only way to resume work is to reboot the system using power button. With kernel linux-image-5.3.0-13-generic everything is OK. Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still happens in linux-image-5.3.0-18-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: player 4451 F pulseaudio /dev/snd/controlC1: player 4451 F pulseaudio /dev/snd/controlC0: player 4451 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 14 01:27:04 2019 HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e MachineType: LENOVO 20BG0016US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current loglevel=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago) WifiSyslog: dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.sku: LENOVO_MT_20BG dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+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 1803179]
Additional information: The on is for my logitech receiver as it is annoying like hell when powersavings are enabled for it. Will need to move the mouse for 2s before it*s working again. And the sleep is needed to be able to have all the hardware available before powertop will change the modes. -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+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 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Hi Mohammad, Can you double check that you tested with the 4.15.0-87-generic kernel from -proposed with the following uname string? 4.15.0-87-generic #87-Ubuntu SMP Fri Jan 31 19:32:37 UTC 2020 You can verify that the patches have landed in the kernel by looking at the git tree: Checkout the code, switch to 4.15.0-87-generic tag: $ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git $ git checkout Ubuntu-4.15.0-87.87 Look at the git log history for the commits: $ git log --oneline --grep "net/mlx5e: Rx, Fixup skb checksum for packets with tail padding" d1a32cb24dfe net/mlx5e: Rx, Fixup skb checksum for packets with tail padding $ git log --oneline --grep "net/mlx5e: Rx, Fix checksum calculation for new hardware" 786fb87b8f55 net/mlx5e: Rx, Fix checksum calculation for new hardware Look at what version they are tagged in: $ git describe --contains d1a32cb24dfe Ubuntu-4.15.0-87.87~459 $ git describe --contains 786fb87b8f55 Ubuntu-4.15.0-87.87~458 Looking at the commits themselves: $ git show d1a32cb24dfe https://paste.ubuntu.com/p/yWs3tBqywK/ $ git show 786fb87b8f55 https://paste.ubuntu.com/p/byj34bPFjZ/ Note that: - d1a32cb24dfe in the Ubuntu Bionic tree is 0aa1d18615c163f92935b806dcaff9157645233a upstream. - 786fb87b8f55 in the Ubuntu Bionic tree is db849faa9bef993a1379dc510623f750a72fa7ce upstream. I cross checked the backported commits with the upstream ones again, and they appear correct. Can you please re-rest and double check you are running the 4.15.0-87-generic kernel from -proposed? Thanks, Matthew -- 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/1854842 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1854842 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, there is a kernel splat when sending large IP packets which have padding at the end. enp6s0f0: hw csum failure CPU: 19 PID: 0 Comm: swapper/19 Not tainted 4.15.0-72-generic Call Trace: dump_stack+0x63/0x8e netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xbc/0xd0 nf_ip_checksum+0xc3/0xf0 icmp_error+0x27d/0x310 [nf_conntrack_ipv4] nf_conntrack_in+0x15a/0x510 [nf_conntrack] ? __skb_checksum+0x68/0x330 ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xc0 ? skb_send_sock+0x50/0x50 ip_rcv+0x301/0x360 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x432/0xb80 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xe0 napi_gro_receive+0xc5/0xf0 mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core] ? enqueue_task_rt+0x1b4/0x2e0 mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] net_rx_action+0x140/0x3a0 __do_softirq+0xe4/0x2d4 irq_exit+0xc5/0xd0 do_IRQ+0x86/0xe0 common_interrupt+0x8c/0x8c This bug is a further attempt to fix these splats, as there has been previous fixes in LP #1840854 and a series of commits which landed in 4.15.0-67 (LP #1847155) as a part of upstream -stable patches. This bug will also fix the same problems on the new Mellanox CX6 and Bluefield hardware, which has been enabled already via previous upstream -stable patches which landed in LP #1847155. [Fix] This particular issue was fixed for Mellanox series 5 drivers in the following commits: commit 0aa1d18615c163f92935b806dcaff9157645233a Author: Saeed Mahameed Date: Tue Mar 12 00:24:52 2019 -0700 Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding This commit required a minor backport. This commit was selected for upstream -stable in 4.19.76 and 5.0.10. This commit appears to be omitted from "Bionic update: upstream stable patchset 2019-10-07", which is LP #1847155, probably due to requiring a backport. commit db849faa9bef993a1379dc510623f750a72fa7ce Author: Saeed Mahameed Date: Fri May 3 13:14:59 2019 -0700 Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware This commit required a minor backport. This commit was selected for upstream -stable in 5.1.21 and 5.2.4. This commit has already been applied to the disco kernel, as part of stable updates. [Testcase] The following scapy script will reproduce this issue. Run from the machine with the Mellanox series 5 NIC: 1)
[Kernel-packages] [Bug 1854887] Re: cifs: DFS Caching feature causing problems traversing multi-tier DFS setups
Verification for eoan, via the Bionic 5.3 HWE kernel. The customer installed 5.3.0-40-generic #32~18.04.1-Ubuntu to their bionic machine, and mounted their multi-tier cifs share: @:~$ uname -rv 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 @:~$ cd /mnt/share/ @:/mnt/share$ ll total 8 drwxrwxrwx 2 root root 4096 Dec 4 13:36 ./ drwxr-xr-x 3 root root 4096 Dec 4 13:36 ../ @:/mnt/share$ cd / @:/$ sudo mount -v -t cifs //company.com/folders/Country/ -o defaults,user= /mnt/share Password for @//company.com/folders/Country/: *** mount.cifs kernel mount options: ip=,unc=\\company.com\folders,user=,prefixpath=Country/,pass=*** @:/$ cd /mnt/share/ @:/mnt/share$ ll total 4 drwxr-xr-x 2 root root 0 Oct 18 2017 ./ drwxr-xr-x 3 root root 4096 Dec 4 13:36 ../ drwxr-xr-x 2 root root 0 Feb 5 15:39 / drwxr-xr-x 2 root root 0 Feb 4 17:09 / @:/mnt/share$ cd / @:/mnt/share/$ The cifs share mounted successfully, and the user was able to access files in the share. I'm happy to mark this as verified. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1854887 Title: cifs: DFS Caching feature causing problems traversing multi-tier DFS setups Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1854887 [Impact] There is a problem where kernels 5.0-rc1 and onwards cannot mount a multi tier cifs DFS setup, while kernels 4.20 and below can mount the share fine. The DFS tiering structure looks like this: Domain virtual DFS (i.e. \\company.com\folders\share) |-- Domain controller DFS (i.e. \\regional-dc.company.com\folders\share) |-- Regional DFS Server (i.e. \\regional-dfs.company.com\folders\share) |-- Actual file server (i.e. \\regional-svr.company.com\share) On the 5.x series kernels, after getting the DFS referrals list through to the Regional DFS Server, which responds with the correct server/share, instead of going to the Actual file server, the kernel backtracks from the Regional DFS Server back to the Domain controller and requests the share there. Of course, this share does not exist on the Domain controller, as it only exists on the Actual file server, and the connection dies. We have collected a packet capture, and the flow looks like this: Legend: -- DC = Domain Controller / Domain DFS Root RDC = Regional Domain Controller / Domain DFS Root RDS = Regional DFS Server AFS = Actual File Server 4.18.0-21-generic Ubuntu kernel - Good Host: request/response DC: company.com\folders DC: Referral List RDC:start convo RDC:\Folders\Country\ referral RDC:\Folders\Country\ referral RDS:start convo RDS:\Root\Country\ RDS:STATUS_PATH_NOT_COVERED RDS:request referrals RDS:Referral List AFS:convo started AFS:\ AFS:Good response 5.0.0-26-generic Ubuntu kernel - Bad Host: request/response DC: company.com\folders RDC:start convo RDC:\Folders\Country\ RDC:STATUS_PATH_NOT_COVERED RDS:start convo RDS:\Root\Country\ RDS:STATUS_PATH_NOT_COVERED RDC:\Root\Country\ RDC:STATUS_PATH_NOT_COVERED From there the debugging output was more or less the same between the two kernel versions, until the problematic area: Linux 4.18: Full log: https://paste.ubuntu.com/p/D9XwBbvTXc/ Status code returned 0xc257 STATUS_PATH_NOT_COVERED fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc257 to POSIX err -66 fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\ fs/cifs/smb2ops.c: smb2_get_dfs_refer path <\\Root\Country\> fs/cifs/misc.c: num_referrals: 1 dfs flags: 0x2 ... fs/cifs/dns_resolve.c: dns_resolve_server_name_to_ip: resolved: to fs/cifs/connect.c: Username: XXX // mounts the share successfully Linux 5.0: Full log: https://paste.ubuntu.com/p/9sXPj7WMQv/ Status code returned 0xc257 STATUS_PATH_NOT_COVERED fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc257 to POSIX err -66 fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\ fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\ fs/cifs/dfs_cache.c: do_dfs_cache_find: search path: \\Root\Country\ fs/cifs/dfs_cache.c: do_dfs_cache_find: cache miss fs/cifs/dfs_cache.c: do_dfs_cache_find: DFS referral request for \\Root\Country\ fs/cifs/smb2ops.c:
[Kernel-packages] [Bug 1803179]
Yep the problem is bbswitch. Just deinstall it, make sure the power mode for nvidia gpu and hdmi sound are set to auto and unload the nvidia & nvidia_modeset modules. bbswitch will still lead to the lockups, if used. -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+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 1847937] Re: 'gpu has fallen off the bus' after return from suspend
If I might add to this issue; I also have an XPS15, GTX 1650 and Ubuntu and POP!Os both trigger the issue (kernel 5.3.0-7625-generic). I also have deep as mem_sleep and use s2idle. I have tried the following parameters without succcess: $ sudo kernelstub -a "rcutree.rcu_idle_gp_delay=1 acpi_osi=! acpi_osi='Linux'" $ sudo kernelstub -a "pcie_acpi=off" (In combination and alone) I have also tried forcing persistence with the driver which also did not work. Here is another thread in mint forums https://forums.linuxmint.com/viewtopic.php?p=1728952=d2f654dfa1082400eeea98c9fbf01918#p1728952 The added parameters seems to work for them, but I could not resolve the issue. Nvidia driver is also at the latest version. -- 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/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Triaged Bug description: With this message the only way to resume work is to reboot the system using power button. With kernel linux-image-5.3.0-13-generic everything is OK. Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still happens in linux-image-5.3.0-18-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: player 4451 F pulseaudio /dev/snd/controlC1: player 4451 F pulseaudio /dev/snd/controlC0: player 4451 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 14 01:27:04 2019 HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e MachineType: LENOVO 20BG0016US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current loglevel=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago) WifiSyslog: dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.sku: LENOVO_MT_20BG dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+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 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
@Jastria Rahmat (ijash) have you updated the firmware ( UEFI firmware update to CJCN24WW [2]) type > xinput is the device shown there? -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+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 1861330] Re: Battery status unknown on Lenovo X1 Carbon Extreme Gen 2
I've only ever run Focal on this laptop. When I first installed(end of December 2019) the battery level worked. I was using it while plugged in for a few weeks and recently noticed that the battery level stopped working. According to [1] this laptop is certified pre-install for Ubuntu. [1] https://certification.ubuntu.com/hardware/201906-27150 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1861330 Title: Battery status unknown on Lenovo X1 Carbon Extreme Gen 2 Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo X1 Carbon Extreme Gen 2. When I first installed Focal on it battery status was working however its now stuck at 59% even though its been charging for days. $ cat /sys/class/power_supply/BAT0/status Unknown $ cat /sys/class/power_supply/BAT0/capacity 59 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lee4054 F pulseaudio /dev/snd/controlC1: lee4054 F pulseaudio /dev/snd/controlC0: lee4054 F pulseaudio /dev/snd/pcmC0D0p: lee4054 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-29 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220) MachineType: LENOVO 20QVCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=/dev/mapper/samsung--ssd-ROOT ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861330/+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 1803179]
(In reply to Matthias Fulz from comment #157) > Yep the actual arch kernel is working fine here, including these patches: > Linux omega 5.5.2-arch1-1 #1 SMP PREEMPT Tue, 04 Feb 2020 18:56:18 + > x86_64 GNU/Linux > > Best Powerconsumption so far 6-7W normal working (wlan, 25% display, > browsing, etc.) > > No lockups anymore, using bumblebee (primusrun, optirun) just need to > manually unload the nvidia modules afterwards, which I've included in simple > scripts. > > Thanks at all for this :) I'm currently using the vanilla kernel and still run into the lockups I mentioned above. Do I need to apply patches myself? Or is it just the stuff I'm using (eg I only use bbswitch, on top of optimus-manager)? Sorry if this is a little asking the obvious, just had this problem for a while now and not sure how to deal with it. -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+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 1803179]
Yep the actual arch kernel is working fine here, including these patches: Linux omega 5.5.2-arch1-1 #1 SMP PREEMPT Tue, 04 Feb 2020 18:56:18 + x86_64 GNU/Linux Best Powerconsumption so far 6-7W normal working (wlan, 25% display, browsing, etc.) No lockups anymore, using bumblebee (primusrun, optirun) just need to manually unload the nvidia modules afterwards, which I've included in simple scripts. Thanks at all for this :) -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+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 988799]
https://jessynaija.org/mp3-download/naija-songs -- 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/988799 Title: Precise freezes under heavy i/o Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Whilst creating a VM with 20 GB persistent HD and my system froze until the disk was created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gema 2526 F pulseaudio /dev/snd/controlC0: gema 2526 F pulseaudio /dev/snd/controlC1: gema 2526 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,104383c4,0010' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 16 Mono: Capture 12 [75%] [24.00dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Thu Apr 26 11:59:11 2012 HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: lono wireless extensions. virbr0no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago) dmi.bios.date: 03/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/988799/+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 1861165] Re: bionic/linux: 4.15.0-87.87 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 03. February 2020 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1862013 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1862408 - xenial/linux-gcp: bug 1861160, bug 1862224 + xenial/linux-gcp: bug 1862224, bug 1861160 xenial/linux-hwe: bug 1861164 variant: debs -- 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/1861165 Title: bionic/linux: 4.15.0-87.87 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 03. February 2020 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1862013 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1862408 xenial/linux-gcp: bug 1862224, bug 1861160 xenial/linux-hwe: bug 1861164 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861165/+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 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
I forgot to tell that I tried the following kernel parameters one by one with no luck: noapic, pci=routeirq, pci=noacpi, acpi=off. -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
** Attachment added: "lsusb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+attachment/5326692/+files/lsusb -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
** Attachment added: "interrupts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+attachment/5326690/+files/interrupts -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: disco -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+attachment/5326691/+files/lspci -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+attachment/5326688/+files/dmesg -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
** Attachment added: "dmidecode" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+attachment/5326689/+files/dmidecode -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+attachment/5326693/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1862528] [NEW] Thomson NEO14A-4SL64 touchpad does not work
Public bug reported: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: disco -- 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Thomson NEO14A-4SL64 touchpad does not work: I tested this with a live Ubuntu 19.10 and a live Linux Mint 19.3 with the same result. I could not use "ubuntu-bug" because I could not connect via Ethernet (no Ethernet on this device) nor Wi-Fi (does not work). The attached files come from the live Linux Mint 19.3 with Linux 5.0. These lines from dmesg seem interesting: [ 69.353090] i2c_hid i2c-SYNA3602:00: HID over i2c has not been provided an Int IRQ [ 69.353269] i2c_hid: probe of i2c-SYNA3602:00 failed with error -22 I could no find useful setting in the BIOS, and Thomson does not seem to provide BIOS update for this device. Regards, Yvan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862528/+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 1861192] Re: disco/linux: 5.0.0-41.45 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 30. January 2020 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 - bionic/linux-gcp: bug 1862213, bug 1861184 + bionic/linux-gcp: bug 1861184, bug 1862213 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1861178 bionic/linux-oracle-5.0: bug 1861190 variant: debs -- 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/1861192 Title: disco/linux: 5.0.0-41.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 30. January 2020 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 bionic/linux-gcp: bug 1861184, bug 1862213 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1861178 bionic/linux-oracle-5.0: bug 1861190 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861192/+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 1803179]
Are these patches included in kernel 5.5.2? I blacklist nvidia modules on boot, and "echo 'OFF' | sudo tee /proc/acpi/bbswitch" (which succeeds) followed by lspci also produces a freeze on my machine. Without the call to bbswitch, the freeze does not happen, but my idle power usage is at 25-30W, instead of the ~11 that occurs if I do invoke bbswitch. I'm running Arch, with the 5.5.2 kernel. Hardware is an Intel i7-8750H and NVidia GTX 1070M, and my kernel parameters are "root=/dev/nvme0n1p5 rw add_efi_memmap initrd=intel-ucode.img initrd=initramfs-%v.img nopti intel_iommu=on iommu=on sysrq_always_enabled=1". -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+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 620074]
https://jessynaija.org/mp3-download/naija-songs -- 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/620074 Title: Thrashing turns system unusable Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Thrashing on Ubuntu seems to make it almost impossible to interact with the system. It can be minutes before any interaction has an effect, including remote connections. This means that if a program either misbehaves or simply needs more memory than available RAM, it might be hard or impossible to stop it, either locally or remotely. This can be both an annoyance and a security threat (since a process without elevated privileges can effectively hang the system). It is not hard to make a system go into thrashing, especially if it is low on memory (that's probably true in general, not only of Ubuntu). On my ASUS netbook running Ubuntu 10.04, with only 1GB RAM, thrashing can occur as easily as running both Chromium (which is a bit of a memory hog) and the Resynthesizer plugin in the GIMP at the same time. Running these programs plus another memory-intensive program like Mathematica can generate thrashing even when 2GB or 4GB of physical memory are available. I am including a short C++ program that allocates and accesses a large amount of memory, guaranteeing thrashing will occur on any system. Using this or any other memory-intensive program, the steps required to reproduce the condition I described are 1. Start one or more memory-intensive programs. 2. As RAM is filled, paging will start, and if the programs try to access the memory that has been swapped out, thrashing occurs. What happens? - Interactivity with the system drops to almost zero. Mouse barely moves, keyboard interaction has huge delays (tens of seconds), starting a terminal or switching to one if one is already open can take minutes, as is the case with remote (e.g. SSH) connections. What I would expect/want to happen? - The system should keep interactivity levels high at all times. While I'm not at all an expert on this, I would think this could be achieved by either not allowing paging out of essential user-interface elements, or more generally by giving processes that generate a lot of page faults comparatively lower priority than other processes, especially processes that are just starting, or are part of the user interface. To use the included program, compile with g++ -o bug bug.cc and run with ./bug where is the amount of memory in MB to be allocated. One can run several instances of the program at the same time, to compete for memory. One can use top, free or the System Monitor to check when RAM is completely filled, and thrashing starts. PS: This seems to be a long-standing issue with Linux, it's not limited to the current version of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.39 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tibi 1596 F pulseaudio /dev/snd/pcmC0D0p: tibi 1596 F...m pulseaudio /dev/snd/controlC1: tibi 1596 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21' Mixer name : 'Nvidia MCP78 HDMI' Components : 'HDA:10ec0888,10250153,00100202 HDA:10de0002,10de0101,0010' Controls : 37 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x8da'/'USB Device 0x46d:0x8da at usb-:00:04.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:08da' Controls : 3 Simple ctrls : 2 Date: Wed Aug 18 13:01:30 2010 HibernationDevice: RESUME=UUID=9464cfb9-e39a-46ab-bf3a-01a7f2194ab1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: eMachines EL1210-09 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=93f3d657-74ac-4853-acab-704f74ab4cd0 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.1 RfKill: SourcePackage: linux dmi.bios.date: 09/23/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: R01-A0 dmi.board.name: WMCP78M dmi.board.vendor: eMachines dmi.chassis.asset.tag: 00 dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias:
[Kernel-packages] [Bug 1834875] Re: cloud-init growpart race with udev
> Ah, no I think this might be along right lines: udev is calling blkid > on the _partition_ of course, so it can probe for filesystem etc without > looking at the partition table. After it's done that, it does look for > the partition table so it can read the ID_PART_ENTRY_* values from it, > but if it fails to load the partition table it just gives up and still > returns success. Ah so this was in the right direction, but not completely right: the failure is not in reading the partition table of the disk being probed, but failing to figure out which entry in that table corresponds to the partition being probed: Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: LOWPROBE: trying to convert devno 0x811 to partition Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: LOWPROBE: searching by offset/size Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: LOWPROBE: not found partition for device Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: LOWPROBE: parts: end probing for partition entry [nothing] The function of interest in libblkid here is blkid_partlist_devno_to_partition, which (unless some apis have very misleading names) is reading the offset and size of the partition from sysfs. What must be happening here is that udev sees the disk being closed by gdisk and somehow runs the builting blkid command on the partition before the kernel has been informed of the resize of the partition. And indeed, we can see when the kernel notices this: Feb 06 00:37:43 test-xrdpdnvfctsofyygmzan kernel: EXT4-fs (sdb1): resizing filesystem from 548091 to 7836155 blocks Feb 06 00:37:44 test-xrdpdnvfctsofyygmzan kernel: EXT4-fs (sdb1): resized filesystem to 7836155 At least a second later. (In passing_journalctl_output.txt, this message is printed before udev even gets the inotify event about sdb being closed). So there's always a race here but I don't know why we only see this on Azure with newer releases. A proper fix would be to get sgdisk to call partx_resize_partition before closing the disk but it would also be interesting to see why it takes so long to get to that part sometimes. growpart is too much shell for me, but maybe it's possible to get it to run partx under strace and get the output of that out somehow? -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and
[Kernel-packages] [Bug 1861300] Re: Data Corruption with Sil 3114 and 3124 controlleurs
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1861300 Title: Data Corruption with Sil 3114 and 3124 controlleurs Status in linux package in Ubuntu: Confirmed Bug description: Silicon Image 3114 and 3124 seem to have data corruption at writing data (particularly with big files or when the writing concern lot of files). I used a PCI card with the Sil 3114 chip; when copying files and directories from a HDD to an other, data corruption appears and seems to be random in files. But every checks about the computer (RAM, HDD ...) have gone right. Don't know what happening really, but I supposed that the module which control the Sil 3114 (and so the Sil 3124, cause this module was written from the 3114's module) contain a bug. I've tried to enable the Sil 3114 module's option called "slow_down" which should solve some "problems", no difference with and without this option activated. The Sil 3124 module's doesn't have this option. Drives connected to Sil3124 controller seems to be affected by data corruption when at least 2 process attempts to writing at the same drive (obviously not in the same directory nor the same file), against Sil3114 which the bug seems to appears anytime. I have already posted a question : https://unix.stackexchange.com/questions/564067/file-corruption- between-2-hdd with more precisions about what have done until now. Now i use a PCI card based on the Sil 3124 controller, seems to have the same data corruption issue as the Sil 3114, but less pronounced (less often). Running Ubuntu 16.04 server i386 with Linux Kernel 4.4.211. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861300/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I opened a similar bug for focal, we need to put the alsa-ucm-conf and alsa-topology-conf to the focal image. This is the bug link: https://bugs.launchpad.net/ubuntu/+source/alsa- lib/+bug/1862505 -- 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/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi
I did not find how to boot unsigned kernels on Xiaomi RedmiBook 14 :( -- 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/1860552 Title: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi Status in linux-firmware package in Ubuntu: New Bug description: Running Linux RedmiBook 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci reports the device 01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) dmesg shows following messages when modprobe ath10_pci [ 35.405479] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 35.677189] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 11ad:0847 [ 35.677191] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 35.677655] ath10k_pci :01:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [ 35.741238] ath10k_pci :01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 from ath10k/QCA6174/hw3.0/board-2.bin [ 35.741396] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a [ 35.813765] ath10k_pci :01:00.0: unsupported HTC service id: 1536 [ 36.237594] ath10k_pci :01:00.0: htt version request timed out [ 36.237601] ath10k_pci :01:00.0: failed to setup htt: -110 [ 36.317707] ath10k_pci :01:00.0: could not init core (-110) [ 36.317770] ath10k_pci :01:00.0: could not probe fw (-110) as a result no wifi no networks visible and no connection possible ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.3 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 22 16:26:03 2020 Dependencies: InstallationDate: Installed on 2020-01-20 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1860552/+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 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default
registered sponsor team -- 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/1862505 Title: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology- conf to focal image by default Status in alsa-lib package in Ubuntu: New Bug description: Before the alsa-lib-1.2.1 the ucm and topology conf files are in the alsa-lib, when we install the alsa-lib/libasound2, they are installed together with alsa-lib. But from 1.2.1 they are separated from the alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should install the ucm and topology too, otherwise those machines need ucm and topology will not work anymore, users have to install these two packages manually. Two packages we need to put into the focal image are: alsa-ucm-conf 1.2.1.2-2 alsa-topology-conf 1.2.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+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 1862505] [NEW] alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default
Public bug reported: Before the alsa-lib-1.2.1 the ucm and topology conf files are in the alsa-lib, when we install the alsa-lib/libasound2, they are installed together with alsa-lib. But from 1.2.1 they are separated from the alsa- lib, and in the focal, we choose the 1.2.1.2 version, we should install the ucm and topology too, otherwise those machines need ucm and topology will not work anymore, users have to install these two packages manually. Two packages we need to put into the focal image are: alsa-ucm-conf 1.2.1.2-2 alsa-topology-conf 1.2.1-2 ** Affects: alsa-lib (Ubuntu) Importance: High Status: New ** Changed in: alsa-lib (Ubuntu) Importance: Undecided => High -- 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/1862505 Title: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology- conf to focal image by default Status in alsa-lib package in Ubuntu: New Bug description: Before the alsa-lib-1.2.1 the ucm and topology conf files are in the alsa-lib, when we install the alsa-lib/libasound2, they are installed together with alsa-lib. But from 1.2.1 they are separated from the alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should install the ucm and topology too, otherwise those machines need ucm and topology will not work anymore, users have to install these two packages manually. Two packages we need to put into the focal image are: alsa-ucm-conf 1.2.1.2-2 alsa-topology-conf 1.2.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+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 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920 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/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+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 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04
Found the problem in the kernel, our focal kernel introduced a patch from stable kernel, that patch make the sof driver not work, either we revert this patch or we need to backport more patches instead of only this one: Author: Ranjani Sridharan Date: Mon Nov 4 14:48:12 2019 -0800 ASoC: SOF: topology: set trigger order for FE DAI link BugLink: https://bugs.launchpad.net/bugs/1858428 [ Upstream commit 5eee2b3f60065a2530d13f28e771be48b989eb4c ] Set trigger order for FE DAI links to SND_SOC_DPCM_TRIGGER_POST to trigger the BE DAI's before the FE DAI's. This prevents the xruns seen on playback pipelines using the link DMA. Signed-off-by: Ranjani Sridharan Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191104224812.3393-3-ranjani.sridha...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Seth Forshee -- 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/1860697 Title: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both output and input, does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 12:00:01 2020 InstallationDate: Installed on 2019-09-06 (139 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20QDCTO1WW ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago) dmi.bios.date: 12/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+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 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch
2 more patches also needed for clean cherry-pick crypto: hisilicon - still no need to check return value of debugfs_create functions crypto: hisilicon/sec2 - Use atomics instead of __sync -- 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/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+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 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/upstream-kernel Status: New => Fix Released ** Changed in: kunpeng920/upstream-kernel Milestone: None => linux-v5.6 ** Changed in: kunpeng920/ubuntu-20.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: None => ubuntu-18.04.5 ** Changed in: kunpeng920/ubuntu-20.04 Milestone: None => ubuntu-20.04-ga ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+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 1861972] Re: [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/upstream-kernel Status: New => Fix Released ** Changed in: kunpeng920/upstream-kernel Milestone: None => linux-v5.6 ** Description changed: [Bug Description] - hns3 patchset have merged into mainline 5.4rc7 kernel. + hns3 patchset have merged into mainline 5.4rc7 kernel. [Steps to Reproduce] - 1) - 2) - 3) + 1) + 2) + 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] - (Firmware version, kernel version, affected hardware, etc. if required): + (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] - - net: hns3: cleanup some coding style issue - net: hns3: remove redundant print on ENOMEM - net: hns3: delete unnecessary blank line and space for cleanup - net: hns3: rewrite a log in hclge_put_vector() - net: hns3: refine the input parameter 'size' for snprintf() - net: hns3: move duplicated macro definition into header - net: hns3: set VF's default reset_type to HNAE3_NONE_RESET - net: hns3: do not reuse pfmemalloc pages - net: hns3: limit the error logging in the hns3_clean_tx_ring() - net: hns3: replace snprintf with scnprintf in hns3_update_strings - net: hns3: replace snprintf with scnprintf in hns3_dbg_cmd_read - net: hns3: pad the short frame before sending to the hardware + (Fix committed) net: hns3: cleanup some coding style issue + (In progress) net: hns3: remove redundant print on ENOMEM + (In progress) net: hns3: delete unnecessary blank line and space for cleanup + (In progress) net: hns3: rewrite a log in hclge_put_vector() + (In progress) net: hns3: refine the input parameter 'size' for snprintf() + (In progress) net: hns3: move duplicated macro definition into header + (In progress) net: hns3: set VF's default reset_type to HNAE3_NONE_RESET + (In progress) net: hns3: do not reuse pfmemalloc pages + (In progress) net: hns3: limit the error logging in the hns3_clean_tx_ring() + (In progress) net: hns3: replace snprintf with scnprintf in hns3_update_strings + (In progress) net: hns3: replace snprintf with scnprintf in hns3_dbg_cmd_read + (Fix committed) net: hns3: pad the short frame before sending to the hardware ** Changed in: kunpeng920/ubuntu-20.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: None => ubuntu-18.04.5 ** Changed in: kunpeng920/ubuntu-20.04 Milestone: None => linux-v5.6 ** Changed in: kunpeng920/ubuntu-20.04 Milestone: linux-v5.6 => ubuntu-20.04-ga ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920 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/1861972 Title: [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] hns3 patchset have merged into mainline 5.4rc7 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] (Fix committed) net: hns3: cleanup some coding style issue (In progress) net: hns3: remove redundant print on ENOMEM (In progress) net: hns3: delete unnecessary blank line and space for cleanup (In progress) net: hns3: rewrite a log in hclge_put_vector() (In progress) net: hns3: refine the input parameter 'size' for snprintf() (In progress) net: hns3: move duplicated macro definition into header (In progress) net: hns3: set VF's default reset_type to HNAE3_NONE_RESET (In progress) net: hns3: do not reuse pfmemalloc pages (In progress) net: hns3: limit the error logging in the hns3_clean_tx_ring() (In progress) net: hns3: replace snprintf with scnprintf in hns3_update_strings (In progress) net: hns3: replace snprintf with scnprintf in hns3_dbg_cmd_read (Fix committed) net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1859743] Re: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-20.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1859743 Title: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04 series: New Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-19.10 series: New Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] this patch gets tpm eventlog information such as device boot status,event guid and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog" functions to get it for ARM64 platorm. [Steps to Reproduce] 1) ls -l /sys/kernel/security/tpm0/binary_bios_measurements 2) 3) [Actual Results] '/sys/kernel/security/tpm0/binary_bios_measurements' no such file or directory [Expected Results] ok [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859743/+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 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: New => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1859744 Title: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04 series: New Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] Because of out-of-order execution about some CPU architecture, In this debug stage we find Completing spi interrupt enable -> prodrucing TXEI interrupt -> running "interrupt_transfer" function will prior to set "dw->rx and dws->rx_end" data, so this patch add memory barrier to enable dw->rx and dw->rx_end to be visible and solve to send SPI data error. eg: it will fix to this following low possibility error in testing environment which using SPI control to connect TPM Modules kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Steps to Reproduce] 1) enable ima and tpm 2)reboot this system 3) [Actual Results] kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Expected Results] ok [Reproducibility] low probabilities [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859744/+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 1862498] Re: Nuvision NES11 needs silead touchscreen quirks
** Tags added: patch -- 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/1862498 Title: Nuvision NES11 needs silead touchscreen quirks Status in linux package in Ubuntu: Confirmed Bug description: I discovered that this model's touchscreen uses a Silead touchscreen which requires device specific quirks to calibrate the touchscreen so touch input will work correctly. I have prepared a patch to resolve the issue and have already confirmed that it does indeed allow the touchscreen to function correctly. I would appreciate it if this patch could be included in a future kernel build. Regarding the patch I have 2 versions of it because upstream changed the location of the relevant quirks table in 4.19 and newer kernels. You will want to use the 4.18- patch for older kernels and 4.19+ patch for newer kernels. They should apply just fine but they may have fuzzing because the tables have been modified between kernel releases. Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 804 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Nuvision NES11 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=ee704514-8ebd-4b87-9635-76538d639209 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1W6_I1101_G.069 dmi.board.asset.tag: Hampoo Reserved dmi.board.name: L1W6_I1101_G dmi.board.vendor: Nuvision dmi.board.version: Hampoo Reserved dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1W6_I1101_G.069:bd04/20/2018:svnNuvision:pnNES11:pvrHampooReserved:rvnNuvision:rnL1W6_I1101_G:rvrHampooReserved:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ApolloLake MRD dmi.product.name: NES11 dmi.product.sku: NES11 dmi.product.version: Hampoo Reserved dmi.sys.vendor: Nuvision To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862498/+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 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
I followed all steps Martina (cantappa) and "Apply this patch to dsdt.dsl". didn't explain on how to apply the patch. is it download the github file and replace the dsdt.dsl or add line or something, or replace to ELAN062F?? because i cant find any on generated dsdt.dsl. also while doing `cp dsdt.aml ssdt1.aml kernel/firmware/acpi` ssdt1.aml was not found. please elaborate.. -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+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 1862498] Re: Nuvision NES11 needs silead touchscreen quirks
** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862498 Title: Nuvision NES11 needs silead touchscreen quirks Status in linux package in Ubuntu: Confirmed Bug description: I discovered that this model's touchscreen uses a Silead touchscreen which requires device specific quirks to calibrate the touchscreen so touch input will work correctly. I have prepared a patch to resolve the issue and have already confirmed that it does indeed allow the touchscreen to function correctly. I would appreciate it if this patch could be included in a future kernel build. Regarding the patch I have 2 versions of it because upstream changed the location of the relevant quirks table in 4.19 and newer kernels. You will want to use the 4.18- patch for older kernels and 4.19+ patch for newer kernels. They should apply just fine but they may have fuzzing because the tables have been modified between kernel releases. Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 804 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Nuvision NES11 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=ee704514-8ebd-4b87-9635-76538d639209 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1W6_I1101_G.069 dmi.board.asset.tag: Hampoo Reserved dmi.board.name: L1W6_I1101_G dmi.board.vendor: Nuvision dmi.board.version: Hampoo Reserved dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1W6_I1101_G.069:bd04/20/2018:svnNuvision:pnNES11:pvrHampooReserved:rvnNuvision:rnL1W6_I1101_G:rvrHampooReserved:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ApolloLake MRD dmi.product.name: NES11 dmi.product.sku: NES11 dmi.product.version: Hampoo Reserved dmi.sys.vendor: Nuvision To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862498/+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 1862498] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1862498/+attachment/5326621/+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/1862498 Title: Nuvision NES11 needs silead touchscreen quirks Status in linux package in Ubuntu: Confirmed Bug description: I discovered that this model's touchscreen uses a Silead touchscreen which requires device specific quirks to calibrate the touchscreen so touch input will work correctly. I have prepared a patch to resolve the issue and have already confirmed that it does indeed allow the touchscreen to function correctly. I would appreciate it if this patch could be included in a future kernel build. Regarding the patch I have 2 versions of it because upstream changed the location of the relevant quirks table in 4.19 and newer kernels. You will want to use the 4.18- patch for older kernels and 4.19+ patch for newer kernels. They should apply just fine but they may have fuzzing because the tables have been modified between kernel releases. Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 804 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Nuvision NES11 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=ee704514-8ebd-4b87-9635-76538d639209 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1W6_I1101_G.069 dmi.board.asset.tag: Hampoo Reserved dmi.board.name: L1W6_I1101_G dmi.board.vendor: Nuvision dmi.board.version: Hampoo Reserved dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1W6_I1101_G.069:bd04/20/2018:svnNuvision:pnNES11:pvrHampooReserved:rvnNuvision:rnL1W6_I1101_G:rvrHampooReserved:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ApolloLake MRD dmi.product.name: NES11 dmi.product.sku: NES11 dmi.product.version: Hampoo Reserved dmi.sys.vendor: Nuvision To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862498/+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 1862498] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1862498/+attachment/5326622/+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/1862498 Title: Nuvision NES11 needs silead touchscreen quirks Status in linux package in Ubuntu: Confirmed Bug description: I discovered that this model's touchscreen uses a Silead touchscreen which requires device specific quirks to calibrate the touchscreen so touch input will work correctly. I have prepared a patch to resolve the issue and have already confirmed that it does indeed allow the touchscreen to function correctly. I would appreciate it if this patch could be included in a future kernel build. Regarding the patch I have 2 versions of it because upstream changed the location of the relevant quirks table in 4.19 and newer kernels. You will want to use the 4.18- patch for older kernels and 4.19+ patch for newer kernels. They should apply just fine but they may have fuzzing because the tables have been modified between kernel releases. Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 804 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Nuvision NES11 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=ee704514-8ebd-4b87-9635-76538d639209 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1W6_I1101_G.069 dmi.board.asset.tag: Hampoo Reserved dmi.board.name: L1W6_I1101_G dmi.board.vendor: Nuvision dmi.board.version: Hampoo Reserved dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1W6_I1101_G.069:bd04/20/2018:svnNuvision:pnNES11:pvrHampooReserved:rvnNuvision:rnL1W6_I1101_G:rvrHampooReserved:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ApolloLake MRD dmi.product.name: NES11 dmi.product.sku: NES11 dmi.product.version: Hampoo Reserved dmi.sys.vendor: Nuvision To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862498/+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