[Kernel-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1862813] Re: xenial/linux-oracle: 4.15.0-1033.36~16.04.1 -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 kernel-stable-master-bug: 1862814 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Testing - phase-changed: Wednesday, 12. February 2020 14:02 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 07:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff variant: debs -- 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/1862813 Title: xenial/linux-oracle: 4.15.0-1033.36~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: 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 kernel-stable-master-bug: 1862814 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Friday, 14. February 2020 07:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862813/+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 1862813] Re: xenial/linux-oracle: 4.15.0-1033.36~16.04.1 -proposed tracker
4.15.0-1033.36~16.04.1 - oracle Regression test CMPL, RTB. Issue to note in oracle (amd64): ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) pcid (bug 1827979) pmu (bug 1853797) port80 (bug 1748105) vmx (bug 1821394) vmx_apic_passthrough_thread (bug 1822309) vmx_hlt_with_rvi_test (bug 1822308) ubuntu_ltp_syscalls - move_pages12 (bug 1831043) on some instance quotactl04 (bug 1854153) statx05 (bug 1798524) pkey01 (bug 1849093) Skipped / blacklisted: * ubuntu_ltp ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1862813 Title: xenial/linux-oracle: 4.15.0-1033.36~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: 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 kernel-stable-master-bug: 1862814 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Friday, 14. February 2020 07:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862813/+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 1862312] Re: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel
Xenial 4.15, Xenial 4.15 Oracle all green.
thank you!
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Changed in: ubuntu-kernel-tests
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862312
Title:
Segmentation fault (kernel oops) with memory-hotplug in
ubuntu_kernel_selftests on Bionic kernel
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
It looks like memory-hotplug test in ubuntu_kernel_selftests will
trigger this issue.
This issue cannot be reproduced with the kernel in -updates, but can
be reproduced quite easily with the proposed kernel (X-4.15 Oracle
4.15.0-1032.35~16.04.1).
This was spotted on the following kernels (for now):
* X-oracle-4.15
* B
* B-oracle-4.15
It's not very easy to spot this as the jenkins job will just hang and you
won't see the test result on the report page,
for example 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 client._record_indent now set to 1
05:06:37 DEBUG| Persistent state client.unexpected_reboot deleted
05:06:37 INFO | START ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1580792797localtime=Feb 04
05:06:37
05:06:37 DEBUG| Persistent state client._record_indent now set to 2
05:06:37 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_kvm_unit_tests.emulator', 'ubuntu_kvm_unit_tests.emulator')
05:06:37 DEBUG| Running 'kvm-ok'
05:06:37 DEBUG| [stdout] INFO: /dev/kvm exists
05:06:37 DEBUG| [stdout] KVM acceleration can be used
05:06:37 DEBUG| Running 'ppc64_cpu --smt=off'
Build was aborted
Check the syslog, there is a call trace before the test_bpf and after page
offline:
[ 1195.321441] Offlined Pages 4096
[ 1195.335056] Offlined Pages 4096
[ 1195.354614] Offlined Pages 4096
[ 1198.491967] Offlined Pages 4096
[ 1199.457587] Injecting error (-12) to MEM_GOING_ONLINE
[ 1200.473838] [ cut here ]
[ 1200.473841] kernel BUG at
/build/linux-CWyQTi/linux-4.15.0/kernel/rcu/sync.c:128!
[ 1200.473909] Oops: Exception in kernel mode, sig: 5 [#1]
[ 1200.473953] LE SMP NR_CPUS=2048 NUMA PowerNV
[ 1200.473999] 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 joydev
input_leds mac_hid idt_89hpesx opal_prd ofpart at24 cmdlinepart powernv_flash
ipmi_powernv uio_pdrv_genirq uio mtd ipmi_devintf ibmpowernv ipmi_msghandler
sch_fq_codel vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure
scsi_transport_sas ast i2c_algo_bit hid_generic ttm drm_kms_helper
[ 1200.474641] syscopyarea usbhid sysfillrect sysimgblt hid fb_sys_fops
crct10dif_vpmsum crc32c_vpmsum drm i40e aacraid [last unloaded: test_bpf]
[ 1200.474792] CPU: 12 PID: 139071 Comm: mem-on-off-test Not tainted
4.15.0-87-generic #87-Ubuntu
[ 1200.474894] NIP: c01a8490 LR: c01a8478 CTR:
c026c5e0
[ 1200.474981] REGS: c00c830ff7c0 TRAP: 0700 Not tainted
(4.15.0-87-generic)
[ 1200.475084] MSR: 9282b033
CR: 28222888 XER: 2004
[ 1200.475219] CFAR: c001940c SOFTE: 1
[ 1200.475219] GPR00: c01a8434 c00c830ffa40 c172c900
0001
[ 1200.475219] GPR04: 01f0 c00c7a4d2480 28228882
c001e730
[ 1200.475219] GPR08: 000ff9a1 0001
c00c61bab790
[ 1200.475219] GPR12: 2000 cfa88400 058d97936070
[ 1200.475219] GPR16: 058d6b6e9690 058d6b776ab0 058d6b7a8204
058d6b776ae8
[ 1200.475219] GPR20: 058d6b7ad5d8 0001
7fffd1cb80e4
[ 1200.475219] GPR24: 7fffd1cb80e0 c1763428 c15f6ba8
00
[Kernel-packages] [Bug 1862824] Re: bionic/linux: 4.15.0-88.88 -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: Wednesday, 12. February 2020 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff trackers: bionic/linux-aws: bug 1862808 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1862810 bionic/linux-ibm-gt: bug 1862812 bionic/linux-kvm: bug 1862811 bionic/linux-oem: bug 1863072 bionic/linux-oracle: bug 1862814 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1862803 bionic/linux/pc-lowlatency-kernel: bug 1862804 xenial/linux-azure: bug 1862818 xenial/linux-gcp: bug 1862821 xenial/linux-hwe: bug 1862823 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/1862824 Title: bionic/linux: 4.15.0-88.88 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released 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: Wednesday, 12. February 2020 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff trackers: bionic/linux-aws: bug 1862808 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1862810 bionic/linux-ibm-gt: bug 1862812 bionic/linux-kvm: bug 1862811 bionic/linux-oem: bug 1863072 bionic/linux-oracle: bug 1862814 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1862803 bionic/linux/pc-lowlatency-kernel: bug 1862804 xenial/linux-azure: bug 1862818 xenial/linux-gcp: bug 1862821 xenial/linux-hwe: bug 1862823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862824/+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 1862312] Re: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel
Bionic 4.15 amd64, ppc64 are good.
Checking Xenial 4.15
--
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:
Segmentation fault (kernel oops) with memory-hotplug in
ubuntu_kernel_selftests on Bionic kernel
Status in ubuntu-kernel-tests:
Fix Committed
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Bug description:
It looks like memory-hotplug test in ubuntu_kernel_selftests will
trigger this issue.
This issue cannot be reproduced with the kernel in -updates, but can
be reproduced quite easily with the proposed kernel (X-4.15 Oracle
4.15.0-1032.35~16.04.1).
This was spotted on the following kernels (for now):
* X-oracle-4.15
* B
* B-oracle-4.15
It's not very easy to spot this as the jenkins job will just hang and you
won't see the test result on the report page,
for example 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 client._record_indent now set to 1
05:06:37 DEBUG| Persistent state client.unexpected_reboot deleted
05:06:37 INFO | START ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1580792797localtime=Feb 04
05:06:37
05:06:37 DEBUG| Persistent state client._record_indent now set to 2
05:06:37 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_kvm_unit_tests.emulator', 'ubuntu_kvm_unit_tests.emulator')
05:06:37 DEBUG| Running 'kvm-ok'
05:06:37 DEBUG| [stdout] INFO: /dev/kvm exists
05:06:37 DEBUG| [stdout] KVM acceleration can be used
05:06:37 DEBUG| Running 'ppc64_cpu --smt=off'
Build was aborted
Check the syslog, there is a call trace before the test_bpf and after page
offline:
[ 1195.321441] Offlined Pages 4096
[ 1195.335056] Offlined Pages 4096
[ 1195.354614] Offlined Pages 4096
[ 1198.491967] Offlined Pages 4096
[ 1199.457587] Injecting error (-12) to MEM_GOING_ONLINE
[ 1200.473838] [ cut here ]
[ 1200.473841] kernel BUG at
/build/linux-CWyQTi/linux-4.15.0/kernel/rcu/sync.c:128!
[ 1200.473909] Oops: Exception in kernel mode, sig: 5 [#1]
[ 1200.473953] LE SMP NR_CPUS=2048 NUMA PowerNV
[ 1200.473999] 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 joydev
input_leds mac_hid idt_89hpesx opal_prd ofpart at24 cmdlinepart powernv_flash
ipmi_powernv uio_pdrv_genirq uio mtd ipmi_devintf ibmpowernv ipmi_msghandler
sch_fq_codel vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure
scsi_transport_sas ast i2c_algo_bit hid_generic ttm drm_kms_helper
[ 1200.474641] syscopyarea usbhid sysfillrect sysimgblt hid fb_sys_fops
crct10dif_vpmsum crc32c_vpmsum drm i40e aacraid [last unloaded: test_bpf]
[ 1200.474792] CPU: 12 PID: 139071 Comm: mem-on-off-test Not tainted
4.15.0-87-generic #87-Ubuntu
[ 1200.474894] NIP: c01a8490 LR: c01a8478 CTR:
c026c5e0
[ 1200.474981] REGS: c00c830ff7c0 TRAP: 0700 Not tainted
(4.15.0-87-generic)
[ 1200.475084] MSR: 9282b033
CR: 28222888 XER: 2004
[ 1200.475219] CFAR: c001940c SOFTE: 1
[ 1200.475219] GPR00: c01a8434 c00c830ffa40 c172c900
0001
[ 1200.475219] GPR04: 01f0 c00c7a4d2480 28228882
c001e730
[ 1200.475219] GPR08: 000ff9a1 0001
c00c61bab790
[ 1200.475219] GPR12: 2000 cfa88400 058d97936070
[ 1200.475219] GPR16: 058d6b6e9690 058d6b776ab0 058d6b7a8204
058d6b776ae8
[ 1200.475219] GPR20: 058d6b7ad5d8 0001
7fffd1cb80e4
[ 1200.475219] GPR24: 7fffd1cb80e0 c1763428 c15f6ba8
[ 1200.475219] GPR28: 0020 c15f6bb0
c15f6ba8
[ 1200.476036] NIP [c01a8490] rcu_sync_enter+0xa0/0x1e0
[ 1200.476124] LR [c01a8478] rcu_sync_enter+0x8
[Kernel-packages] [Bug 1861295] Re: Bluetooth not working
Did the wifi also stop working? -- 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/1861295 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 19.10 on this Macbook Pro a couple of weeks ago. Bluetooth was working during the first days, but now it won't work anymore. Here is the output of dmesg | grep -i blue, showing some errors that might be interesting: > dmesg | grep -i blue [1.562871] usb 1-3: Product: Bluetooth USB Host Controller [2.104835] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0003/input/input10 [2.164582] hid-generic 0003:05AC:8290.0003: input,hidraw2: USB HID v1.11 Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input0 [2.164685] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0004/input/input11 [2.164761] hid-generic 0003:05AC:8290.0004: input,hidraw3: USB HID v1.11 Mouse [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input1 [3.605086] Bluetooth: Core ver 2.22 [3.605103] Bluetooth: HCI device and connection manager initialized [3.605107] Bluetooth: HCI socket layer initialized [3.605109] Bluetooth: L2CAP socket layer initialized [3.605112] Bluetooth: SCO socket layer initialized [5.720427] Bluetooth: hci0: command 0x0c03 tx timeout [6.637120] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.637122] Bluetooth: BNEP filters: protocol multicast [6.637126] Bluetooth: BNEP socket layer initialized [ 13.876494] Bluetooth: hci0: BCM: Reset failed (-110) 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/controlC2: maurizio 1377 F pulseaudio /dev/snd/controlC0: maurizio 1377 F pulseaudio /dev/snd/controlC1: maurizio 1377 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 14:16:01 2020 InstallationDate: Installed on 2020-01-23 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Apple Inc. MacBookPro12,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=adc45397-ab6d-4a20-8795-b9e7f3d733b6 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/30/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 188.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr188.0.0.0.0:bd10/30/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861295/+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 1862824] Re: bionic/linux: 4.15.0-88.88 -proposed tracker
4.15.0-88.88 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted (bug 1821390) vmx (bug 1821394) ubuntu_ltp - proc01 (bug 1829849) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_xfstests_btrfs - btrfs/187 timeout ubuntu_xfstests_ext4 - timed out on generic/430 test (bug 1755999) ubuntu_xfstests_xfs - timed out on generic/430 test (bug 1755999) 51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) function traceon/off triggers in ftace (bug 1837040) ubuntu_kvm_unit_tests - gicv3-ipi and gicv3-active failed on Moonshot (bug 1790825) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - move_pages12 (bug 1831043) ubuntu_lxc - failed to fetch GPG key 52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) test_maps failed (bug 1837386) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) TRACE_syscall.ptrace_syscall_errno in seccomp (bug 1829359) TRACE_syscall.ptrace_syscall_faked in seccomp (bug 1829363) ubuntu_kvm_unit_tests - vmexit_* on i386 (bug 1822235) vmexit_ipi on i386 (bug 1822235) ubuntu_ltp - proc01 (bug 1829849) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) 52 / 56 tests were run, missing: ubuntu_boot, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_fan_smoke_test - failed to fetch file from ports.ubuntu.com, probably FW issue ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) TRACE_syscall.ptrace_syscall_errno in seccomp (bug 1829359) TRACE_syscall.ptrace_syscall_faked in seccomp (bug 1829363) dscr_sysfs_test in powerpc/dscr (bug 1813136) subpage_prot in powerpc/mm (bug 1813140) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - move_pages12 (bug 1831043) ubuntu_lxc - failed to fetch GPG key ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) 53 / 56 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P9): hwclock - hwclock test failed on PowerPC due to 0.x sec difference (bug 1802233) ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_fan_smoke_test - failed to fetch file from ports.ubuntu.com, probably FW issue ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) dscr_sysfs_test in powerpc/dscr (bug 1813136) subpage_prot in powerpc/mm (bug 1813140) ubuntu_ltp - proc01 (bug 1829849) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) ubuntu_ltp_syscalls - move_pages12 (bug 1831043) ubuntu_lxc - failed to fetch GPG key ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) Issue to note in s390x (KVM): ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_cts_kernel - test is a bit flaky (bug 1837536) ubuntu_kernel_selftests - TRACE_syscall in seccomp (bug 1812824) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuacct_100_100 (bug 1829978) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) ubuntu_ltp_syscalls - add_key01 (bug 1862878) msgstress03 (bug 1797341) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_kernel_selftests - TRACE_syscall in seccomp (bug 1812824) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) ubuntu_ltp_syscalls - add_key01 (bug 1862878) ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is defined (bug 1788574) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) Issue to note in s390x (zVM): ubuntu_bpf - test_maps failed (bug 183738
[Kernel-packages] [Bug 1829359] Re: TRACE_syscall.ptrace_syscall_errno in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Won't Fix ** Tags added: sru-20200127 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829359 Title: TRACE_syscall.ptrace_syscall_errno in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Won't Fix Bug description: This test will fail on Bionic / Cosmic PowerPC: [ RUN ] TRACE_syscall.ptrace_syscall_errno seccomp_bpf.c:1826:TRACE_syscall.ptrace_syscall_errno:Expected -(-3) (3) == (*__errno_location ()) (38) TRACE_syscall.ptrace_syscall_errno: Test failed at step #13 This test will pass on PowerPC with Disco kernel. As this issue can be reproduced with the upsteam kernel tree, so it looks like a kernel issue instead of a test case issue to me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 16 09:48:18 2019 ProcLoadAvg: 0.38 0.64 0.48 1/1316 6114 ProcLocks: 1: POSIX ADVISORY WRITE 1767 00:17:402 0 EOF 2: POSIX ADVISORY WRITE 3941 00:17:825 0 EOF 3: FLOCK ADVISORY WRITE 3492 00:17:390 0 EOF 4: FLOCK ADVISORY WRITE 3947 00:17:820 0 EOF 5: POSIX ADVISORY WRITE 3872 00:17:799 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-20-generic (buildd@bos02-ppc64el-019) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21~18.04.1-Ubuntu SMP Wed May 8 08:51:08 UTC 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861344] Re: uvcvideo: IPEVO Ziggi-HD document camera stops working on kernel 4.4.0-171
There are many USB/UVC commits between these two versions. Please run a kernel bisection: $ sudo apt build-dep linux $ git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial $ cd linux $ git bisect start $ git bisect good Ubuntu-4.4.0-170.199 $ git bisect bad Ubuntu-4.4.0-171.200 $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1861344 Title: uvcvideo: IPEVO Ziggi-HD document camera stops working on kernel 4.4.0-171 Status in linux package in Ubuntu: Incomplete Bug description: I have a IPEVO Ziggi-HD document camera (1778:0207) that refuses to operate on kernel 4.4.0-171 or newer. On such kernels, uvcvideo fails with the kernel message 'uvcvideo: No streaming interface found for terminal 2' and no `/dev/videoX` device is created. The camera operates correctly on kernel 4.4.0-170. Ubuntu release: 16.04.6 LTS Attached in a tarball: * a relevant /var/log/syslog fragment captured when device plugged in * `cat /proc/version_signature` * `sudo lspci -vnvn` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829363] Re: TRACE_syscall.ptrace_syscall_faked in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Won't Fix ** Tags added: sru-20200127 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829363 Title: TRACE_syscall.ptrace_syscall_faked in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Won't Fix Bug description: This test will fail on Bionic / Cosmic PowerPC: [ RUN ] TRACE_syscall.ptrace_syscall_faked seccomp_bpf.c:1837:TRACE_syscall.ptrace_syscall_faked:Expected 45000 (45000) == syscall(207) (18446744073709551615) TRACE_syscall.ptrace_syscall_faked: Test failed at step #13 [ FAIL ] TRACE_syscall.ptrace_syscall_faked This test will pass on PowerPC with Disco kernel. As this issue can be reproduced with the upsteam kernel tree, so it looks like a kernel issue instead of a test case issue to me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 16 09:59:19 2019 ProcLoadAvg: 0.07 0.40 0.68 1/1315 7583 ProcLocks: 1: POSIX ADVISORY WRITE 1767 00:17:402 0 EOF 2: POSIX ADVISORY WRITE 3941 00:17:825 0 EOF 3: FLOCK ADVISORY WRITE 3492 00:17:390 0 EOF 4: FLOCK ADVISORY WRITE 3947 00:17:820 0 EOF 5: POSIX ADVISORY WRITE 3872 00:17:799 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-20-generic (buildd@bos02-ppc64el-019) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21~18.04.1-Ubuntu SMP Wed May 8 08:51:08 UTC 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 0) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: Sound(ALSA) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1858299] Re: This laptop contains a touchpadwhich is not recognized.
https://lkml.org/lkml/2020/2/14/68 -- 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/1858299 Title: This laptop contains a touchpadwhich is not recognized. Status in linux package in Ubuntu: Confirmed Bug description: This laptop contains a touchpad which is not recognized. The laptop is the Trekstore Surfbook E11B. 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 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deathmetal 1119 F pulseaudio CurrentDesktop: LXQt Date: Sat Jan 4 23:09:34 2020 InstallationDate: Installed on 2020-01-04 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TREKSTOR SURFBOOK E11B ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7 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: 08/30/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BIOS_V1.1.5 dmi.board.asset.tag: Default string dmi.board.name: Gemini_Lake_Celeron_V01 dmi.board.vendor: TS_EMDOOR dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Surfbook dmi.product.name: SURFBOOK E11B dmi.product.sku: NFCN4SW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858299/+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 1862840] Re: [Bionic] i915 incomplete fix for CVE-2019-14615
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862840
Title:
[Bionic] i915 incomplete fix for CVE-2019-14615
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Gregory Herrero reported that the proof-of-concept for CVE-2019-14615
indicates that the information leak is not fixed in the Bionic 4.15
kernel as indicated by USN-4255-1:
https://usn.ubuntu.com/4255-1/
This only affects Ubuntu's 4.15 kernel series. Xenial (4.4), Disco
(5.0), Eoan (5.3), and Focal (5.4) are not affected by this incomplete
fix issue.
I've verified this by testing each Ubuntu release with the proof-of-
concept. I then tested vanilla 4.15 with commit bc8a76a152c5
("drm/i915/gen9: Clear residual context state on context switch")
applied, which is the fix for CVE-2019-14615, and verified that the
proof-of-concept showed that the info leak was still possible. I then
tested vanilla 4.16 with commit bc8a76a152c5 applied to verify that
the proof-of-concept showed that the info leak was fixed.
After bisecting changes to the DRM subsystem as well as the i915
driver, it looks like commit d2b4b97933f5 ("drm/i915: Record the
default hw state after reset upon load") as well as its prerequisites
are necessary to fully fix CVE-2019-14615 in 4.15 based kernels.
[Test Case]
A proof-of-concept for CVE-2019-14615 became available once the issue
was made public. It can be found here:
https://github.com/HE-Wenjian/iGPU-Leak
Steps to use the proof-of-concept:
$ git clone https://github.com/HE-Wenjian/iGPU-Leak.git
# In one terminal
$ cd iGPU-Leak/demo/SLM_Leak/
$ ./run_victim.sh
# In another terminal
$ cd iGPU-Leak/demo/SLM_Leak/
$ ./run_attacker.sh
# In the terminal running run_attacker.sh, ensure that all data dumped
# to the terminal is zeros and that there is no non-zero data. You'll
# have to closely monitor the script for a minute or so to ensure that
# the information leak is not possible.
[Regression Potential]
High as the changes are complex in comparison to the typical SRU.
However, the bulk of the change is to the initialization stages of the
driver and we're just pulling back changes that landed in 4.16-rc1 to
our 4.15 kernel. I don't see any later Fixes tags that reference the
needed commits.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862840/+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 1861197] Re: eoan/linux-raspi2: 5.3.0-1018.20 -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 kernel-stable-master-bug: 1861214 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Testing - phase-changed: Tuesday, 04. February 2020 14:47 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 06:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-raspi2-5.3: bug 1861196 eoan/linux-raspi2/pi-kernel: bug 1861194 variant: debs -- 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/1861197 Title: eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Friday, 14. February 2020 06:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-raspi2-5.3: bug 1861196 eoan/linux-raspi2/pi-kernel: bug 1861194 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861197/+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 1861197] Re: eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: Rpi2b-armhf: https://certification.canonical.com/hardware/201906-27188/submission/160435/ Rpi3b-arm64: https://certification.canonical.com/hardware/201811-26649/submission/160926/ Rpi3b-armhf: https://certification.canonical.com/hardware/201811-26649/submission/160428/ Rpi3a+-arm64: https://certification.canonical.com/hardware/201901-26785/submission/160907/ Rpi3a+-armhf: https://certification.canonical.com/hardware/201901-26785/submission/160425/ Rpi3b+-arm64: https://certification.canonical.com/hardware/201810-26542/submission/160925/ Rpi3b+-armhf: https://certification.canonical.com/hardware/201810-26542/submission/160424/ Rpi4b-1g-arm64: https://certification.canonical.com/hardware/201911-27471/submission/161070/ Rpi4b-1g-armhf: https://certification.canonical.com/hardware/201910-27407/submission/161071/ Rpi4b-2g-arm64: https://certification.canonical.com/hardware/201911-27507/submission/161068/ Rpi4b-2g-armhf: https://certification.canonical.com/hardware/201911-27506/submission/161074/ Rpi4b-4g-arm64: https://certification.canonical.com/hardware/201911-27456/submission/161072/ Rpi4b-4g-armhf: https://certification.canonical.com/hardware/201911-27455/submission/161073/ CM3-arm64: https://certification.canonical.com/hardware/201711-25992/submission/161193/ CM3-armhf: https://certification.canonical.com/hardware/201711-25992/submission/160423/ CM3+-arm64: https://certification.canonical.com/hardware/201908-27277/submission/160918/ CM3+-armhf: https://certification.canonical.com/hardware/201908-27277/submission/160421/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- 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/1861197 Title: eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Friday, 14. February 2020 06:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-raspi2-5.3: bug 1861196 eoan/linux-raspi2/pi-kernel: bug 1861194 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861197/+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 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Kai-Heng Feng, please note that after I installed Qubes, I never ever had the problem again. It may be useful in the debug process, and maybe the way Xen, PCIe and Linux work together in Qubes can give a hint on what's happening. Thank you for all your help to this day. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Relea
[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -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 kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 13. February 2020 10:16 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- 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/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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 kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 13. February 2020 10:16 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+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 1853219] Re: [CML-H] Add intel_thermal_pch driver support Comet Lake -H
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853219
Title:
[CML-H] Add intel_thermal_pch driver support Comet Lake -H
Status in intel:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-osp1 package in Ubuntu:
New
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
In Progress
Status in linux source package in Eoan:
Fix Committed
Status in linux-oem-osp1 source package in Eoan:
New
Status in linux source package in Focal:
In Progress
Status in linux-oem-osp1 source package in Focal:
New
Bug description:
[SRU Justification]
[Impact]
Missing thermal_zone info for Intel PCH on Comet Lake (CML) platform.
[Fix]
Commit 35709c4ee772 ("thermal: intel: intel_pch_thermal: Add Comet Lake
(CML) platform support") from v5.6-rc1 to be backported.
[Test Case]
Check if sysfs thermal zone entry of type "pch_cometlake" exists:
$ cat /sys/class/thermal/thermal_zone*/type | grep pch_cometlake
[Regression Potential]
Low. This affects only CML platforms.
== original description ==
Description
Add intel_thermal_pch driver support Comet Lake -H
Target Release: 20.04
Target Kernel: 5.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1853219/+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
Please submit the patch to upstream so we can backport it. https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1862498 Title: Nuvision NES11 needs silead touchscreen quirks Status in linux package in Ubuntu: Incomplete 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 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -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 kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 13. February 2020 10:16 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- 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/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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 kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 13. February 2020 10:16 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+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 1862429] Re: Eoan update: upstream stable patchset 2020-02-07
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862429 Title: Eoan update: upstream stable patchset 2020-02-07 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-07 Ported from the following upstream stable releases: v4.19.98, v5.4.14 from git://git.kernel.org/ ARM: dts: meson8: fix the size of the PMU registers clk: qcom: gcc-sdm845: Add missing flag to votable GDSCs dt-bindings: reset: meson8b: fix duplicate reset IDs ARM: dts: imx6q-dhcom: fix rtc compatible clk: Don't try to enable critical clocks if prepare failed ASoC: msm8916-wcd-digital: Reset RX interpolation path after use iio: buffer: align the size of scan bytes to size of the largest element USB: serial: simple: Add Motorola Solutions TETRA MTP3xxx and MTP85xx USB: serial: option: Add support for Quectel RM500Q USB: serial: opticon: fix control-message timeouts USB: serial: option: add support for Quectel RM500Q in QDL mode USB: serial: suppress driver bind attributes USB: serial: ch341: handle unbound port at reset_resume USB: serial: io_edgeport: handle unbound ports on URB completion USB: serial: io_edgeport: add missing active-port sanity check USB: serial: keyspan: handle unbound ports USB: serial: quatech2: handle unbound ports scsi: fnic: fix invalid stack access scsi: mptfusion: Fix double fetch bug in ioctl ASoC: msm8916-wcd-analog: Fix selected events for MIC BIAS External1 ASoC: msm8916-wcd-analog: Fix MIC BIAS Internal1 ARM: dts: imx6q-dhcom: Fix SGTL5000 VDDIO regulator connection ALSA: dice: fix fallback from protocol extension into limited functionality ALSA: seq: Fix racy access for queue timer in proc read ALSA: usb-audio: fix sync-ep altsetting sanity check arm64: dts: allwinner: a64: olinuxino: Fix SDIO supply regulator Fix built-in early-load Intel microcode alignment block: fix an integer overflow in logical block size ARM: dts: am571x-idk: Fix gpios property to have the correct gpio number ptrace: reintroduce usage of subjective credentials in ptrace_has_cap() usb: core: hub: Improved device recognition on remote wakeup x86/resctrl: Fix an imbalance in domain_remove_cpu() x86/CPU/AMD: Ensure clearing of SME/SEV features is maintained x86/efistub: Disable paging at mixed mode entry drm/i915: Add missing include file x86/resctrl: Fix potential memory leak perf hists: Fix variable name's inconsistency in hists__for_each() macro perf report: Fix incorrectly added dimensions as switch perf data file mm/shmem.c: thp, shmem: fix conflict of above-47bit hint address and PMD alignment mm: memcg/slab: call flush_memcg_workqueue() only if memcg workqueue is valid btrfs: rework arguments of btrfs_unlink_subvol btrfs: fix invalid removal of root ref btrfs: do not delete mismatched root refs btrfs: fix memory leak in qgroup accounting mm/page-writeback.c: avoid potential division by zero in wb_min_max_ratio() ARM: dts: imx6q-icore-mipi: Use 1.5 version of i.Core MX6DL ARM: dts: imx7: Fix Toradex Colibri iMX7S 256MB NAND flash support net: stmmac: 16KB buffer must be 16 byte aligned net: stmmac: Enable 16KB buffer size mm/huge_memory.c: thp: fix conflict of above-47bit hint address and PMD alignment arm64: dts: agilex/stratix10: fix pmu interrupt numbers bpf: Fix incorrect verifier simulation of ARSH under ALU32 cfg80211: fix deadlocks in autodisconnect work cfg80211: fix memory leak in cfg80211_cqm_rssi_update cfg80211: fix page refcount issue in A-MSDU decap netfilter: fix a use-after-free in mtype_destroy() netfilter: arp_tables: init netns pointer in xt_tgdtor_param struct netfilter: nft_tunnel: fix null-attribute check netfilter: nf_tables: remove WARN and add NLA_STRING upper limits netfilter: nf_tables: store transaction list locally while requesting module netfilter: nf_tables: fix flowtable list del corruption NFC: pn533: fix bulk-message timeout batman-adv: Fix DAT candidate selection on little endian systems macvlan: use skb_reset_mac_header() in macvlan_queue_xmit() hv_netvsc: Fix memory leak when removing rndis device net: dsa: tag_qca: fix doubled Tx statistics net: hns: fix soft
[Kernel-packages] [Bug 1861710] Re: Eoan update: upstream stable patchset 2020-02-03
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861710 Title: Eoan update: upstream stable patchset 2020-02-03 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-03 Ported from the following upstream stable releases: v4.19.94, v5.4.9 from git://git.kernel.org/ nvme_fc: add module to ops template to allow module references nvme-fc: fix double-free scenarios on hw queues drm/amdgpu: add check before enabling/disabling broadcast mode drm/amdgpu: add cache flush workaround to gfx8 emit_fence drm/amd/display: Fixed kernel panic when booting with DP-to-HDMI dongle iio: adc: max9611: Fix too short conversion time delay PM / devfreq: Fix devfreq_notifier_call returning errno PM / devfreq: Set scaling_max_freq to max on OPP notifier error PM / devfreq: Don't fail devfreq_dev_release if not in list afs: Fix afs_find_server lookups for ipv4 peers afs: Fix SELinux setting security label on /afs RDMA/cma: add missed unregister_pernet_subsys in init failure rxe: correctly calculate iCRC for unaligned payloads scsi: lpfc: Fix memory leak on lpfc_bsg_write_ebuf_set func scsi: qla2xxx: Drop superfluous INIT_WORK of del_work scsi: qla2xxx: Don't call qlt_async_event twice scsi: qla2xxx: Fix PLOGI payload and ELS IOCB dump length scsi: qla2xxx: Configure local loop for N2N target scsi: qla2xxx: Send Notify ACK after N2N PLOGI scsi: qla2xxx: Ignore PORT UPDATE after N2N PLOGI scsi: iscsi: qla4xxx: fix double free in probe drm/nouveau: Move the declaration of struct nouveau_conn_atom up a bit usb: gadget: fix wrong endpoint desc net: make socket read/write_iter() honor IOCB_NOWAIT afs: Fix creation calls in the dynamic root to fail with EOPNOTSUPP md: raid1: check rdev before reference in raid1_sync_request func s390/cpum_sf: Adjust sampling interval to avoid hitting sample limits s390/cpum_sf: Avoid SBD overflow condition in irq handler IB/mlx4: Follow mirror sequence of device add during device removal IB/mlx5: Fix steering rule of drop and count xen-blkback: prevent premature module unload xen/balloon: fix ballooned page accounting without hotplug enabled ALSA: hda/realtek - Add Bass Speaker and fixed dac for bass speaker ALSA: hda/realtek - Enable the bass speaker of ASUS UX431FLC ALSA: hda - fixup for the bass speaker on Lenovo Carbon X1 7th gen taskstats: fix data-race netfilter: nft_tproxy: Fix port selector on Big Endian ALSA: ice1724: Fix sleep-in-atomic in Infrasonic Quartet support code ALSA: usb-audio: fix set_format altsetting sanity check ALSA: hda/realtek - Add headset Mic no shutup for ALC283 drm/sun4i: hdmi: Remove duplicate cleanup calls MIPS: Avoid VDSO ABI breakage due to global register variable media: pulse8-cec: fix lost cec_transmit_attempt_done() call media: cec: CEC 2.0-only bcast messages were ignored media: cec: avoid decrementing transmit_queue_sz if it is 0 media: cec: check 'transmit_in_progress', not 'transmitting' mm/zsmalloc.c: fix the migrated zspage statistics. memcg: account security cred as well to kmemcg mm: move_pages: return valid node id in status if the page is already on the target node pstore/ram: Write new dumps to start of recycled zones locks: print unsigned ino in /proc/locks dmaengine: Fix access to uninitialized dma_slave_caps compat_ioctl: block: handle Persistent Reservations compat_ioctl: block: handle BLKREPORTZONE/BLKRESETZONE ata: libahci_platform: Export again ahci_platform_able_phys() ata: ahci_brcm: Fix AHCI resources management ata: ahci_brcm: Add missing clock management during recovery ata: ahci_brcm: BCM7425 AHCI requires AHCI_HFLAG_DELAY_ENGINE libata: Fix retrieving of active qcs gpiolib: fix up emulated open drain outputs riscv: ftrace: correct the condition logic in function graph tracer rseq/selftests: Fix: Namespace gettid() for compatibility with glibc 2.30 tracing: Fix lock inversion in trace_event_enable_tgid_record() tracing: Avoid memory leak in process_system_preds() tracing: Have the histogram compare functions convert to u64 first tracing: Fix endianness bug in histogram trigger apparmor: fix aa_xattrs_match()
[Kernel-packages] [Bug 1862418] Re: Disco update: upstream stable patchset 2020-02-07
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862418 Title: Disco update: upstream stable patchset 2020-02-07 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-07 Ported from the following upstream stable releases: v4.19.98, v5.4.14 from git://git.kernel.org/ ARM: dts: meson8: fix the size of the PMU registers clk: qcom: gcc-sdm845: Add missing flag to votable GDSCs dt-bindings: reset: meson8b: fix duplicate reset IDs ARM: dts: imx6q-dhcom: fix rtc compatible clk: Don't try to enable critical clocks if prepare failed ASoC: msm8916-wcd-digital: Reset RX interpolation path after use iio: buffer: align the size of scan bytes to size of the largest element USB: serial: simple: Add Motorola Solutions TETRA MTP3xxx and MTP85xx USB: serial: option: Add support for Quectel RM500Q USB: serial: opticon: fix control-message timeouts USB: serial: option: add support for Quectel RM500Q in QDL mode USB: serial: suppress driver bind attributes USB: serial: ch341: handle unbound port at reset_resume USB: serial: io_edgeport: handle unbound ports on URB completion USB: serial: io_edgeport: add missing active-port sanity check USB: serial: keyspan: handle unbound ports USB: serial: quatech2: handle unbound ports scsi: fnic: fix invalid stack access scsi: mptfusion: Fix double fetch bug in ioctl ASoC: msm8916-wcd-analog: Fix selected events for MIC BIAS External1 ASoC: msm8916-wcd-analog: Fix MIC BIAS Internal1 ARM: dts: imx6q-dhcom: Fix SGTL5000 VDDIO regulator connection ALSA: dice: fix fallback from protocol extension into limited functionality ALSA: seq: Fix racy access for queue timer in proc read ALSA: usb-audio: fix sync-ep altsetting sanity check arm64: dts: allwinner: a64: olinuxino: Fix SDIO supply regulator Fix built-in early-load Intel microcode alignment block: fix an integer overflow in logical block size ARM: dts: am571x-idk: Fix gpios property to have the correct gpio number ptrace: reintroduce usage of subjective credentials in ptrace_has_cap() usb: core: hub: Improved device recognition on remote wakeup x86/resctrl: Fix an imbalance in domain_remove_cpu() x86/CPU/AMD: Ensure clearing of SME/SEV features is maintained x86/efistub: Disable paging at mixed mode entry drm/i915: Add missing include file x86/resctrl: Fix potential memory leak perf hists: Fix variable name's inconsistency in hists__for_each() macro perf report: Fix incorrectly added dimensions as switch perf data file mm/shmem.c: thp, shmem: fix conflict of above-47bit hint address and PMD alignment mm: memcg/slab: call flush_memcg_workqueue() only if memcg workqueue is valid btrfs: rework arguments of btrfs_unlink_subvol btrfs: fix invalid removal of root ref btrfs: do not delete mismatched root refs btrfs: fix memory leak in qgroup accounting mm/page-writeback.c: avoid potential division by zero in wb_min_max_ratio() ARM: dts: imx6q-icore-mipi: Use 1.5 version of i.Core MX6DL ARM: dts: imx7: Fix Toradex Colibri iMX7S 256MB NAND flash support net: stmmac: 16KB buffer must be 16 byte aligned net: stmmac: Enable 16KB buffer size mm/huge_memory.c: make __thp_get_unmapped_area static mm/huge_memory.c: thp: fix conflict of above-47bit hint address and PMD alignment arm64: dts: agilex/stratix10: fix pmu interrupt numbers bpf: Fix incorrect verifier simulation of ARSH under ALU32 cfg80211: fix deadlocks in autodisconnect work cfg80211: fix memory leak in cfg80211_cqm_rssi_update cfg80211: fix page refcount issue in A-MSDU decap netfilter: fix a use-after-free in mtype_destroy() netfilter: arp_tables: init netns pointer in xt_tgdtor_param struct netfilter: nft_tunnel: fix null-attribute check netfilter: nf_tables: remove WARN and add NLA_STRING upper limits netfilter: nf_tables: store transaction list locally while requesting module netfilter: nf_tables: fix flowtable list del corruption NFC: pn533: fix bulk-message timeout batman-adv: Fix DAT candidate selection on little endian systems macvlan: use skb_reset_mac_header() in macvlan_queue_xmit() hv_netvsc: Fix memory leak when removing rndis device net: ds
[Kernel-packages] [Bug 1862059] Re: Disco update: upstream stable patchset 2020-02-05
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862059 Title: Disco update: upstream stable patchset 2020-02-05 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-05 Ported from the following upstream stable releases: v4.19.96, v5.4.12, v4.19.97, v5.4.13 from git://git.kernel.org/ chardev: Avoid potential use-after-free in 'chrdev_open()' i2c: fix bus recovery stop mode timing usb: chipidea: host: Disable port power only if previously enabled ALSA: usb-audio: Apply the sample rate quirk for Bose Companion 5 ALSA: hda/realtek - Add new codec supported for ALCS1200A ALSA: hda/realtek - Set EAPD control to default for ALC222 ALSA: hda/realtek - Add quirk for the bass speaker on Lenovo Yoga X1 7th gen kernel/trace: Fix do not unregister tracepoints when register sched_migrate_task fail tracing: Have stack tracer compile when MCOUNT_INSN_SIZE is not defined tracing: Change offset type to s32 in preempt/irq tracepoints HID: Fix slab-out-of-bounds read in hid_field_extract HID: uhid: Fix returning EPOLLOUT from uhid_char_poll HID: hid-input: clear unmapped usages Input: add safety guards to input_set_keycode() Input: input_event - fix struct padding on sparc64 drm/sun4i: tcon: Set RGB DCLK min. divider based on hardware model drm/fb-helper: Round up bits_per_pixel if possible drm/dp_mst: correct the shifting in DP_REMOTE_I2C_READ can: kvaser_usb: fix interface sanity check can: gs_usb: gs_usb_probe(): use descriptors of current altsetting can: mscan: mscan_rx_poll(): fix rx path lockup when returning from polling to irq mode can: can_dropped_invalid_skb(): ensure an initialized headroom in outgoing CAN sk_buffs gpiolib: acpi: Turn dmi_system_id table into a generic quirk table gpiolib: acpi: Add honor_wakeup module-option + quirk mechanism staging: vt6656: set usb_set_intfdata on driver fail. USB: serial: option: add ZLP support for 0x1bc7/0x9010 usb: musb: fix idling for suspend after disconnect interrupt usb: musb: Disable pullup at init usb: musb: dma: Correct parameter passed to IRQ handler staging: comedi: adv_pci1710: fix AI channels 16-31 for PCI-1713 staging: rtl8188eu: Add device code for TP-Link TL-WN727N v5.21 serdev: Don't claim unsupported ACPI serial devices tty: link tty and port before configuring it as console tty: always relink the port mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf scsi: bfa: release allocated memory in case of error rtl8xxxu: prevent leaking urb HID: hiddev: fix mess in hiddev_open() USB: Fix: Don't skip endpoint descriptors with maxpacket=0 phy: cpcap-usb: Fix error path when no host driver is loaded phy: cpcap-usb: Fix flakey host idling and enumerating of devices netfilter: arp_tables: init netns pointer in xt_tgchk_param struct netfilter: conntrack: dccp, sctp: handle null timeout argument netfilter: ipset: avoid null deref when IPSET_ATTR_LINENO is present tpm: Handle negative priv->response_len in tpm_common_read() pstore/ram: Regularize prz label allocation lifetime USB-PD tcpm: bad warning+size, PPS adapters staging: vt6656: correct return of vnt_init_registers. staging: vt6656: limit reg output to block size arm64: Implement copy_thread_tls arm: Implement copy_thread_tls parisc: Implement copy_thread_tls riscv: Implement copy_thread_tls xtensa: Implement copy_thread_tls um: Implement copy_thread_tls staging: vt6656: remove bool from vnt_radio_power_on ret rpmsg: char: release allocated memory UBUNTU: upstream stable to v4.19.96, v5.4.12 hidraw: Return EPOLLOUT from hidraw_poll HID: hidraw: Fix returning EPOLLOUT from hidraw_poll HID: hidraw, uhid: Always report EPOLLOUT ethtool: reduce stack usage with clang fs/select: avoid clang stack usage warning f2fs: check if file namelen exceeds max value iwlwifi: dbg_ini: fix memory leak in alloc_sgtable iwlwifi: pcie: fix memory leaks in iwl_pcie_ctxt_info_gen3_init rtc: mt6397: fix alarm register overwrite RDMA/bnxt_re: Avoid freeing MR resources if dereg fails RDMA/bnxt_re: Fix Send Work Entry state check while polling completions
[Kernel-packages] [Bug 1862528] Re: Thomson NEO14A-4SL64 touchpad does not work
The IRQ information is from BIOS, please try updating the BIOS. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1862528 Title: Thomson NEO14A-4SL64 touchpad does not work Status in linux package in Ubuntu: Incomplete 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 1861929] Re: Eoan update: upstream stable patchset 2020-02-04
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861929 Title: Eoan update: upstream stable patchset 2020-02-04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-04 Ported from the following upstream stable releases: v4.19.95, v5.4.10, v5.4.11 from git://git.kernel.org/ USB: dummy-hcd: use usb_urb_dir_in instead of usb_pipein USB: dummy-hcd: increase max number of devices to 32 bpf: Fix passing modified ctx to ld/abs/ind instruction regulator: fix use after free issue ASoC: max98090: fix possible race conditions locking/spinlock/debug: Fix various data races netfilter: ctnetlink: netns exit must wait for callbacks libtraceevent: Fix lib installation with O= x86/efi: Update e820 with reserved EFI boot services data to fix kexec breakage ASoC: Intel: bytcr_rt5640: Update quirk for Teclast X89 efi/gop: Return EFI_NOT_FOUND if there are no usable GOPs efi/gop: Return EFI_SUCCESS if a usable GOP was found efi/gop: Fix memory leak in __gop_query32/64() ARM: dts: imx6ul: imx6ul-14x14-evk.dtsi: Fix SPI NOR probing ARM: vexpress: Set-up shared OPP table instead of individual for each CPU netfilter: uapi: Avoid undefined left-shift in xt_sctp.h netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets netfilter: nf_tables: validate NFT_SET_ELEM_INTERVAL_END netfilter: nf_tables: validate NFT_DATA_VALUE after nft_data_init() ARM: dts: BCM5301X: Fix MDIO node address/size cells selftests/ftrace: Fix multiple kprobe testcase ARM: dts: Cygnus: Fix MDIO node address/size cells spi: spi-cavium-thunderx: Add missing pci_release_regions() ASoC: topology: Check return value for soc_tplg_pcm_create() ARM: dts: bcm283x: Fix critical trip point bpf, mips: Limit to 33 tail calls spi: spi-ti-qspi: Fix a bug when accessing non default CS ARM: dts: am437x-gp/epos-evm: fix panel compatible samples: bpf: Replace symbol compare of trace_event samples: bpf: fix syscall_tp due to unused syscall powerpc: Ensure that swiotlb buffer is allocated from low memory btrfs: Fix error messages in qgroup_rescan_init bpf: Clear skb->tstamp in bpf_redirect when necessary bnx2x: Do not handle requests from VFs after parity bnx2x: Fix logic to get total no. of PFs per engine cxgb4: Fix kernel panic while accessing sge_info net: usb: lan78xx: Fix error message format specifier parisc: add missing __init annotation rfkill: Fix incorrect check to avoid NULL pointer dereference ASoC: wm8962: fix lambda value regulator: rn5t618: fix module aliases iommu/iova: Init the struct iova to fix the possible memleak kconfig: don't crash on NULL expressions in expr_eq() perf/x86/intel: Fix PT PMI handling fs: avoid softlockups in s_inodes iterators net: stmmac: Do not accept invalid MTU values net: stmmac: xgmac: Clear previous RX buffer size net: stmmac: RX buffer size must be 16 byte aligned net: stmmac: Always arm TX Timer at end of transmission start s390/purgatory: do not build purgatory with kcov, kasan and friends drm/exynos: gsc: add missed component_del s390/dasd/cio: Interpret ccw_device_get_mdc return value correctly s390/dasd: fix memleak in path handling error case block: fix memleak when __blk_rq_map_user_iov() is failed parisc: Fix compiler warnings in debug_core.c llc2: Fix return statement of llc_stat_ev_rx_null_dsap_xid_c (and _test_c) hv_netvsc: Fix unwanted rx_table reset powerpc/vcpu: Assume dedicated processors as non-preempt powerpc/spinlocks: Include correct header for static key gtp: fix bad unlock balance in gtp_encap_enable_socket macvlan: do not assume mac_header is set in macvlan_broadcast() net: dsa: mv88e6xxx: Preserve priority when setting CPU port. net: stmmac: dwmac-sun8i: Allow all RGMII modes net: stmmac: dwmac-sunxi: Allow all RGMII modes net: usb: lan78xx: fix possible skb leak pkt_sched: fq: do not accept silly TCA_FQ_QUANTUM sch_cake: avoid possible divide by zero in cake_enqueue() sctp: free cmd->obj.chunk for the unprocessed SCTP_CMD_REPLY tcp: fix "old stuff" D-SACK causing SACK to be treated as D-SACK vxlan: fix tos value before xmit vlan: fix memory
[Kernel-packages] [Bug 1862639] Re: Touch pad not seen with kernel > 5.0.0-23
Would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1862639 Title: Touch pad not seen with kernel > 5.0.0-23 Status in linux package in Ubuntu: Incomplete Bug description: Not sure Xorg is the right team, please reroute if not. Teclast F5 touch pad not seen Not seen with kernel 5.3.0-38 , neither 5.4.-15 (ubuntu,kubuntu,mint) but working like a charm with 5.0.0-23 and with kubuntu 18.04 live. Command issued with 5.0.0-23 kernel: xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ 2.4G Wireless Optical Mouse id=8[slave pointer (2)] ⎜ ↳ Goodix Capacitive TouchScreen id=10 [slave pointer (2)] ⎜ ↳ HTIX5288:00 0911:5288 Touchpadid=11 [slave pointer (2)] ---> not seen with new kernels (1)** ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Video Bus id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ USB Camera: USB Cameraid=9 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Goodix Capacitive TouchScreen id=15 [slave keyboard (3)] (**1) ---> despite grub.conf modifcation with i8042.nopnp neither i8042.notimeout,i8042.nomux described at https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Mon Feb 10 15:20:20 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TECLAST F5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=f459c555-b0c2-4e3f-9b81-08010853e2f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2019 dmi.bios.vendor: TECLAST dmi.bios.version: TECLAST13x.WX111J.NLGAUHP08 dmi.board.asset.tag: Default string dmi.board.name: F5 dmi.board.vendor: TECLAST dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnTECLAST:bvrTECLAST13x.WX111J.NLGAUHP08:bd08/21/2019:svnTECLAST:pnF5:pvrDefaultstring:rvnTECLAST:rnF5:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: F5 dmi.product.sku: S5K7_A1 dmi.product.version: Default string dmi.sys.vendor: TECLAST version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg
[Kernel-packages] [Bug 1862227] Re: Eoan update: upstream stable patchset 2020-02-06
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862227 Title: Eoan update: upstream stable patchset 2020-02-06 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-06 Ported from the following upstream stable releases: v4.19.96, v5.4.12, v4.19.97, v5.4.13 from git://git.kernel.org/ chardev: Avoid potential use-after-free in 'chrdev_open()' i2c: fix bus recovery stop mode timing usb: chipidea: host: Disable port power only if previously enabled ALSA: usb-audio: Apply the sample rate quirk for Bose Companion 5 ALSA: hda/realtek - Add new codec supported for ALCS1200A ALSA: hda/realtek - Set EAPD control to default for ALC222 ALSA: hda/realtek - Add quirk for the bass speaker on Lenovo Yoga X1 7th gen kernel/trace: Fix do not unregister tracepoints when register sched_migrate_task fail tracing: Have stack tracer compile when MCOUNT_INSN_SIZE is not defined tracing: Change offset type to s32 in preempt/irq tracepoints HID: Fix slab-out-of-bounds read in hid_field_extract HID: uhid: Fix returning EPOLLOUT from uhid_char_poll HID: hid-input: clear unmapped usages Input: add safety guards to input_set_keycode() Input: input_event - fix struct padding on sparc64 drm/sun4i: tcon: Set RGB DCLK min. divider based on hardware model drm/fb-helper: Round up bits_per_pixel if possible drm/dp_mst: correct the shifting in DP_REMOTE_I2C_READ can: kvaser_usb: fix interface sanity check can: gs_usb: gs_usb_probe(): use descriptors of current altsetting can: mscan: mscan_rx_poll(): fix rx path lockup when returning from polling to irq mode can: can_dropped_invalid_skb(): ensure an initialized headroom in outgoing CAN sk_buffs gpiolib: acpi: Add Terra Pad 1061 to the run_edge_events_on_boot_blacklist gpiolib: acpi: Turn dmi_system_id table into a generic quirk table gpiolib: acpi: Add honor_wakeup module-option + quirk mechanism staging: vt6656: set usb_set_intfdata on driver fail. USB: serial: option: add ZLP support for 0x1bc7/0x9010 usb: musb: fix idling for suspend after disconnect interrupt usb: musb: Disable pullup at init usb: musb: dma: Correct parameter passed to IRQ handler staging: comedi: adv_pci1710: fix AI channels 16-31 for PCI-1713 staging: rtl8188eu: Add device code for TP-Link TL-WN727N v5.21 serdev: Don't claim unsupported ACPI serial devices tty: link tty and port before configuring it as console tty: always relink the port mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf scsi: bfa: release allocated memory in case of error rtl8xxxu: prevent leaking urb HID: hiddev: fix mess in hiddev_open() USB: Fix: Don't skip endpoint descriptors with maxpacket=0 phy: cpcap-usb: Fix error path when no host driver is loaded phy: cpcap-usb: Fix flakey host idling and enumerating of devices netfilter: arp_tables: init netns pointer in xt_tgchk_param struct netfilter: conntrack: dccp, sctp: handle null timeout argument netfilter: ipset: avoid null deref when IPSET_ATTR_LINENO is present powercap: intel_rapl: add NULL pointer check to rapl_mmio_cpu_online() tpm: Handle negative priv->response_len in tpm_common_read() rtc: sun6i: Add support for RTC clocks on R40 drm/i915: Add Wa_1408615072 and Wa_1407596294 to icl,ehl drm/i915: Add Wa_1407352427:icl,ehl IB/hfi1: Adjust flow PSN with the correct resync_psn pstore/ram: Regularize prz label allocation lifetime staging: vt6656: Fix non zero logical return of, usb_control_msg usb: ohci-da8xx: ensure error return on variable error is set USB-PD tcpm: bad warning+size, PPS adapters staging: vt6656: correct return of vnt_init_registers. staging: vt6656: limit reg output to block size iommu/vt-d: Fix adding non-PCI devices to Intel IOMMU arm64: Move __ARCH_WANT_SYS_CLONE3 definition to uapi headers arm64: Implement copy_thread_tls arm: Implement copy_thread_tls parisc: Implement copy_thread_tls riscv: Implement copy_thread_tls xtensa: Implement copy_thread_tls powerpc: convert to copy_thread_tls clone3: ensure copy_thread_tls is implemented um: Implement copy_thread_tls staging: vt6656: remove bool from
[Kernel-packages] [Bug 1861918] Re: Disco update: upstream stable patchset 2020-02-04
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861918 Title: Disco update: upstream stable patchset 2020-02-04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-04 Ported from the following upstream stable releases: v4.19.95, v5.4.10, v5.4.11 from git://git.kernel.org/ USB: dummy-hcd: use usb_urb_dir_in instead of usb_pipein USB: dummy-hcd: increase max number of devices to 32 bpf: Fix passing modified ctx to ld/abs/ind instruction regulator: fix use after free issue ASoC: max98090: fix possible race conditions locking/spinlock/debug: Fix various data races netfilter: ctnetlink: netns exit must wait for callbacks libtraceevent: Fix lib installation with O= x86/efi: Update e820 with reserved EFI boot services data to fix kexec breakage ASoC: Intel: bytcr_rt5640: Update quirk for Teclast X89 efi/gop: Return EFI_NOT_FOUND if there are no usable GOPs efi/gop: Return EFI_SUCCESS if a usable GOP was found efi/gop: Fix memory leak in __gop_query32/64() ARM: dts: imx6ul: imx6ul-14x14-evk.dtsi: Fix SPI NOR probing ARM: vexpress: Set-up shared OPP table instead of individual for each CPU netfilter: uapi: Avoid undefined left-shift in xt_sctp.h netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets netfilter: nf_tables: validate NFT_SET_ELEM_INTERVAL_END netfilter: nf_tables: validate NFT_DATA_VALUE after nft_data_init() ARM: dts: BCM5301X: Fix MDIO node address/size cells selftests/ftrace: Fix multiple kprobe testcase ARM: dts: Cygnus: Fix MDIO node address/size cells spi: spi-cavium-thunderx: Add missing pci_release_regions() ASoC: topology: Check return value for soc_tplg_pcm_create() ARM: dts: bcm283x: Fix critical trip point bpf, mips: Limit to 33 tail calls spi: spi-ti-qspi: Fix a bug when accessing non default CS ARM: dts: am437x-gp/epos-evm: fix panel compatible samples: bpf: Replace symbol compare of trace_event samples: bpf: fix syscall_tp due to unused syscall powerpc: Ensure that swiotlb buffer is allocated from low memory btrfs: Fix error messages in qgroup_rescan_init bpf: Clear skb->tstamp in bpf_redirect when necessary bnx2x: Do not handle requests from VFs after parity bnx2x: Fix logic to get total no. of PFs per engine cxgb4: Fix kernel panic while accessing sge_info net: usb: lan78xx: Fix error message format specifier parisc: add missing __init annotation rfkill: Fix incorrect check to avoid NULL pointer dereference ASoC: wm8962: fix lambda value regulator: rn5t618: fix module aliases iommu/iova: Init the struct iova to fix the possible memleak kconfig: don't crash on NULL expressions in expr_eq() perf/x86/intel: Fix PT PMI handling fs: avoid softlockups in s_inodes iterators net: stmmac: Do not accept invalid MTU values net: stmmac: xgmac: Clear previous RX buffer size net: stmmac: RX buffer size must be 16 byte aligned net: stmmac: Always arm TX Timer at end of transmission start s390/purgatory: do not build purgatory with kcov, kasan and friends drm/exynos: gsc: add missed component_del s390/dasd/cio: Interpret ccw_device_get_mdc return value correctly s390/dasd: fix memleak in path handling error case block: fix memleak when __blk_rq_map_user_iov() is failed parisc: Fix compiler warnings in debug_core.c llc2: Fix return statement of llc_stat_ev_rx_null_dsap_xid_c (and _test_c) hv_netvsc: Fix unwanted rx_table reset powerpc/vcpu: Assume dedicated processors as non-preempt powerpc/spinlocks: Include correct header for static key PCI/switchtec: Read all 64 bits of part_event_bitmap gtp: fix bad unlock balance in gtp_encap_enable_socket macvlan: do not assume mac_header is set in macvlan_broadcast() net: dsa: mv88e6xxx: Preserve priority when setting CPU port. net: stmmac: dwmac-sun8i: Allow all RGMII modes net: stmmac: dwmac-sunxi: Allow all RGMII modes net: usb: lan78xx: fix possible skb leak pkt_sched: fq: do not accept silly TCA_FQ_QUANTUM sch_cake: avoid possible divide by zero in cake_enqueue() sctp: free cmd->obj.chunk for the unprocessed SCTP_CMD_REPLY tcp: fix "old stuff" D-SACK causing SACK to be treated as D-
[Kernel-packages] [Bug 1862639] Re: Touch pad not seen with kernel > 5.0.0-23
Leimar, the issue you filed is different to this one. -- 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/1862639 Title: Touch pad not seen with kernel > 5.0.0-23 Status in linux package in Ubuntu: Incomplete Bug description: Not sure Xorg is the right team, please reroute if not. Teclast F5 touch pad not seen Not seen with kernel 5.3.0-38 , neither 5.4.-15 (ubuntu,kubuntu,mint) but working like a charm with 5.0.0-23 and with kubuntu 18.04 live. Command issued with 5.0.0-23 kernel: xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ 2.4G Wireless Optical Mouse id=8[slave pointer (2)] ⎜ ↳ Goodix Capacitive TouchScreen id=10 [slave pointer (2)] ⎜ ↳ HTIX5288:00 0911:5288 Touchpadid=11 [slave pointer (2)] ---> not seen with new kernels (1)** ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Video Bus id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ USB Camera: USB Cameraid=9 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Goodix Capacitive TouchScreen id=15 [slave keyboard (3)] (**1) ---> despite grub.conf modifcation with i8042.nopnp neither i8042.notimeout,i8042.nomux described at https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Mon Feb 10 15:20:20 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TECLAST F5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=f459c555-b0c2-4e3f-9b81-08010853e2f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2019 dmi.bios.vendor: TECLAST dmi.bios.version: TECLAST13x.WX111J.NLGAUHP08 dmi.board.asset.tag: Default string dmi.board.name: F5 dmi.board.vendor: TECLAST dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnTECLAST:bvrTECLAST13x.WX111J.NLGAUHP08:bd08/21/2019:svnTECLAST:pnF5:pvrDefaultstring:rvnTECLAST:rnF5:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: F5 dmi.product.sku: S5K7_A1 dmi.product.version: Default string dmi.sys.vendor: TECLAST version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862639/+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 1783880] Re: ltp-syscalls: fallocate05 fails with btrfs on ppc64el
fallocate05 passed on P8/P9 Bionic (4.15.0-88.88): <<>> tag=fallocate05 stime=1581659795 cmdline="fallocate05" contacts="" analysis=exit <<>> incrementing stop tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop0' tst_device.c:282: INFO: Skipping $LTP_DEV size 256MB, requested size 512MB tst_device.c:88: INFO: Found free device 1 '/dev/loop1' tst_supported_fs_types.c:59: INFO: Kernel supports ext2 tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:59: INFO: Kernel supports ext3 tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:59: INFO: Kernel supports ext4 tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:59: INFO: Kernel supports xfs tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist tst_supported_fs_types.c:59: INFO: Kernel supports btrfs tst_supported_fs_types.c:43: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:59: INFO: Kernel supports vfat tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported tst_test.c:1278: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s fallocate05.c:62: CONF: fallocate() not supported: EOPNOTSUPP (95) tst_test.c:1278: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext3 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s fallocate05.c:62: CONF: fallocate() not supported: EOPNOTSUPP (95) tst_test.c:1278: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext4 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate05.c:77: PASS: write() wrote 65536 bytes fallocate05.c:99: INFO: fallocate()d 0 extra blocks on full FS fallocate05.c:110: PASS: fallocate() on full FS fallocate05.c:126: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) fallocate05.c:132: PASS: write() tst_test.c:1278: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate05.c:77: PASS: write() wrote 1048576 bytes fallocate05.c:99: INFO: fallocate()d 0 extra blocks on full FS fallocate05.c:110: PASS: fallocate() on full FS fallocate05.c:126: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) fallocate05.c:132: PASS: write() tst_test.c:1278: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill
[Kernel-packages] [Bug 1862259] Re: Bionic update: upstream stable patchset 2020-02-06
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862259 Title: Bionic update: upstream stable patchset 2020-02-06 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-06 Ported from the following upstream stable releases: v4.14.167, v4.19.98 from git://git.kernel.org/ dt-bindings: reset: meson8b: fix duplicate reset IDs clk: Don't try to enable critical clocks if prepare failed ASoC: msm8916-wcd-analog: Fix selected events for MIC BIAS External1 ALSA: seq: Fix racy access for queue timer in proc read Fix built-in early-load Intel microcode alignment block: fix an integer overflow in logical block size ARM: dts: am571x-idk: Fix gpios property to have the correct gpio number iio: buffer: align the size of scan bytes to size of the largest element USB: serial: simple: Add Motorola Solutions TETRA MTP3xxx and MTP85xx USB: serial: option: Add support for Quectel RM500Q USB: serial: opticon: fix control-message timeouts USB: serial: option: add support for Quectel RM500Q in QDL mode USB: serial: suppress driver bind attributes USB: serial: ch341: handle unbound port at reset_resume USB: serial: io_edgeport: add missing active-port sanity check USB: serial: keyspan: handle unbound ports USB: serial: quatech2: handle unbound ports scsi: fnic: fix invalid stack access scsi: mptfusion: Fix double fetch bug in ioctl ptrace: reintroduce usage of subjective credentials in ptrace_has_cap() usb: core: hub: Improved device recognition on remote wakeup x86/resctrl: Fix an imbalance in domain_remove_cpu() x86/efistub: Disable paging at mixed mode entry perf hists: Fix variable name's inconsistency in hists__for_each() macro perf report: Fix incorrectly added dimensions as switch perf data file mm/shmem.c: thp, shmem: fix conflict of above-47bit hint address and PMD alignment btrfs: fix memory leak in qgroup accounting mm/page-writeback.c: avoid potential division by zero in wb_min_max_ratio() net: stmmac: 16KB buffer must be 16 byte aligned net: stmmac: Enable 16KB buffer size USB: serial: io_edgeport: use irqsave() in USB's complete callback USB: serial: io_edgeport: handle unbound ports on URB completion mm/huge_memory.c: make __thp_get_unmapped_area static mm/huge_memory.c: thp: fix conflict of above-47bit hint address and PMD alignment arm64: dts: agilex/stratix10: fix pmu interrupt numbers cfg80211: fix page refcount issue in A-MSDU decap netfilter: fix a use-after-free in mtype_destroy() netfilter: arp_tables: init netns pointer in xt_tgdtor_param struct NFC: pn533: fix bulk-message timeout batman-adv: Fix DAT candidate selection on little endian systems macvlan: use skb_reset_mac_header() in macvlan_queue_xmit() hv_netvsc: Fix memory leak when removing rndis device net: dsa: tag_qca: fix doubled Tx statistics net: hns: fix soft lockup when there is not enough memory net: usb: lan78xx: limit size of local TSO packets net/wan/fsl_ucc_hdlc: fix out of bounds write on array utdm_info ptp: free ptp device pin descriptors properly r8152: add missing endpoint sanity check tcp: fix marked lost packets not being retransmitted xen/blkfront: Adjust indentation in xlvbd_alloc_gendisk cw1200: Fix a signedness bug in cw1200_load_firmware() arm64: dts: meson-gxl-s905x-khadas-vim: fix gpio-keys-polled node cfg80211: check for set_wiphy_params tick/sched: Annotate lockless access to last_jiffies_update Revert "arm64: dts: juno: add dma-ranges property" reiserfs: fix handling of -EOPNOTSUPP in reiserfs_for_each_xattr scsi: esas2r: unlock on error in esas2r_nvram_read_direct() scsi: qla4xxx: fix double free bug scsi: bnx2i: fix potential use after free scsi: target: core: Fix a pr_debug() argument scsi: qla2xxx: Fix qla2x00_request_irqs() for MSI scsi: qla2xxx: fix rports not being mark as lost in sync fabric scan scsi: core: scsi_trace: Use get_unaligned_be*() perf probe: Fix wrong address verification regulator: ab8500: Remove SYSCLKREQ from enum ab8505_regulator_id ARM: dts: meson8: fix the size of the PMU registers LSM: generalize flag passing to security_capable drm/i915: Add missing in
[Kernel-packages] [Bug 1861934] Re: Bionic update: upstream stable patchset 2020-02-04
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861934 Title: Bionic update: upstream stable patchset 2020-02-04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-04 Ported from the following upstream stable releases: v4.14.165, v4.19.96, v4.14.166, v4.19.97 from git://git.kernel.org/ chardev: Avoid potential use-after-free in 'chrdev_open()' usb: chipidea: host: Disable port power only if previously enabled ALSA: usb-audio: Apply the sample rate quirk for Bose Companion 5 ALSA: hda/realtek - Add new codec supported for ALCS1200A ALSA: hda/realtek - Set EAPD control to default for ALC222 kernel/trace: Fix do not unregister tracepoints when register sched_migrate_task fail tracing: Have stack tracer compile when MCOUNT_INSN_SIZE is not defined HID: Fix slab-out-of-bounds read in hid_field_extract HID: uhid: Fix returning EPOLLOUT from uhid_char_poll can: gs_usb: gs_usb_probe(): use descriptors of current altsetting can: mscan: mscan_rx_poll(): fix rx path lockup when returning from polling to irq mode can: can_dropped_invalid_skb(): ensure an initialized headroom in outgoing CAN sk_buffs gpiolib: acpi: Turn dmi_system_id table into a generic quirk table gpiolib: acpi: Add honor_wakeup module-option + quirk mechanism staging: vt6656: set usb_set_intfdata on driver fail. USB: serial: option: add ZLP support for 0x1bc7/0x9010 usb: musb: fix idling for suspend after disconnect interrupt usb: musb: Disable pullup at init usb: musb: dma: Correct parameter passed to IRQ handler staging: comedi: adv_pci1710: fix AI channels 16-31 for PCI-1713 HID: hid-input: clear unmapped usages Input: add safety guards to input_set_keycode() drm/fb-helper: Round up bits_per_pixel if possible drm/dp_mst: correct the shifting in DP_REMOTE_I2C_READ staging: rtl8188eu: Add device code for TP-Link TL-WN727N v5.21 tty: link tty and port before configuring it as console tty: always relink the port mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf scsi: bfa: release allocated memory in case of error rtl8xxxu: prevent leaking urb arm64: cpufeature: Avoid warnings due to unused symbols HID: hiddev: fix mess in hiddev_open() USB: Fix: Don't skip endpoint descriptors with maxpacket=0 phy: cpcap-usb: Fix error path when no host driver is loaded phy: cpcap-usb: Fix flakey host idling and enumerating of devices netfilter: arp_tables: init netns pointer in xt_tgchk_param struct netfilter: ipset: avoid null deref when IPSET_ATTR_LINENO is present ALSA: hda/realtek - Add quirk for the bass speaker on Lenovo Yoga X1 7th gen tracing: Change offset type to s32 in preempt/irq tracepoints serdev: Don't claim unsupported ACPI serial devices netfilter: conntrack: dccp, sctp: handle null timeout argument UBUNTU: upstream stable to v4.14.165, v4.19.96 hidraw: Return EPOLLOUT from hidraw_poll HID: hidraw: Fix returning EPOLLOUT from hidraw_poll HID: hidraw, uhid: Always report EPOLLOUT ethtool: reduce stack usage with clang fs/select: avoid clang stack usage warning arm64: don't open code page table entry creation arm64: mm: Change page table pointer name in p[md]_set_huge() arm64: Enforce BBM for huge IO/VMAP mappings arm64: Make sure permission updates happen for pmd/pud media: usb:zr364xx:Fix KASAN:null-ptr-deref Read in zr364xx_vidioc_querycap wimax: i2400: fix memory leak wimax: i2400: Fix memory leak in i2400m_op_rfkill_sw_toggle iwlwifi: dbg_ini: fix memory leak in alloc_sgtable rtc: mt6397: fix alarm register overwrite RDMA/bnxt_re: Fix Send Work Entry state check while polling completions ASoC: stm32: spdifrx: fix inconsistent lock state ASoC: stm32: spdifrx: fix race condition in irq handler gpio: zynq: Fix for bug in zynq_gpio_restore_context API iommu: Remove device link to group on failure gpio: Fix error message on out-of-range GPIO in lookup table hsr: reset network header when supervision frame is created cifs: Adjust indentation in smb2_open_file btrfs: simplify inode locking for RWF_NOWAIT RDMA/mlx5: Return proper error value RDMA/srpt: Report the SCSI
[Kernel-packages] [Bug 1861739] Re: Bionic update: upstream stable patchset 2020-02-03
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861739 Title: Bionic update: upstream stable patchset 2020-02-03 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-03 Ported from the following upstream stable releases: v4.14.164, v4.19.95 from git://git.kernel.org/ USB: dummy-hcd: use usb_urb_dir_in instead of usb_pipein USB: dummy-hcd: increase max number of devices to 32 locking/spinlock/debug: Fix various data races netfilter: ctnetlink: netns exit must wait for callbacks libtraceevent: Fix lib installation with O= x86/efi: Update e820 with reserved EFI boot services data to fix kexec breakage efi/gop: Return EFI_NOT_FOUND if there are no usable GOPs efi/gop: Return EFI_SUCCESS if a usable GOP was found efi/gop: Fix memory leak in __gop_query32/64() ARM: vexpress: Set-up shared OPP table instead of individual for each CPU netfilter: uapi: Avoid undefined left-shift in xt_sctp.h netfilter: nf_tables: validate NFT_SET_ELEM_INTERVAL_END ARM: dts: Cygnus: Fix MDIO node address/size cells spi: spi-cavium-thunderx: Add missing pci_release_regions() ASoC: topology: Check return value for soc_tplg_pcm_create() ARM: dts: bcm283x: Fix critical trip point bpf, mips: Limit to 33 tail calls ARM: dts: am437x-gp/epos-evm: fix panel compatible samples: bpf: Replace symbol compare of trace_event samples: bpf: fix syscall_tp due to unused syscall powerpc: Ensure that swiotlb buffer is allocated from low memory bnx2x: Do not handle requests from VFs after parity bnx2x: Fix logic to get total no. of PFs per engine net: usb: lan78xx: Fix error message format specifier rfkill: Fix incorrect check to avoid NULL pointer dereference ASoC: wm8962: fix lambda value regulator: rn5t618: fix module aliases kconfig: don't crash on NULL expressions in expr_eq() perf/x86/intel: Fix PT PMI handling fs: avoid softlockups in s_inodes iterators net: stmmac: Do not accept invalid MTU values net: stmmac: RX buffer size must be 16 byte aligned s390/dasd/cio: Interpret ccw_device_get_mdc return value correctly s390/dasd: fix memleak in path handling error case block: fix memleak when __blk_rq_map_user_iov() is failed parisc: Fix compiler warnings in debug_core.c llc2: Fix return statement of llc_stat_ev_rx_null_dsap_xid_c (and _test_c) hv_netvsc: Fix unwanted rx_table reset bpf: Fix passing modified ctx to ld/abs/ind instruction PCI/switchtec: Read all 64 bits of part_event_bitmap gtp: fix bad unlock balance in gtp_encap_enable_socket macvlan: do not assume mac_header is set in macvlan_broadcast() net: dsa: mv88e6xxx: Preserve priority when setting CPU port. net: stmmac: dwmac-sun8i: Allow all RGMII modes net: stmmac: dwmac-sunxi: Allow all RGMII modes net: usb: lan78xx: fix possible skb leak pkt_sched: fq: do not accept silly TCA_FQ_QUANTUM USB: core: fix check for duplicate endpoints USB: serial: option: add Telit ME910G1 0x110a composition sctp: free cmd->obj.chunk for the unprocessed SCTP_CMD_REPLY tcp: fix "old stuff" D-SACK causing SACK to be treated as D-SACK vxlan: fix tos value before xmit vlan: vlan_changelink() should propagate errors net: sch_prio: When ungrafting, replace with FIFO vlan: fix memory leak in vlan_dev_set_egress_priority regulator: fix use after free issue ASoC: max98090: fix possible race conditions netfilter: nf_tables: validate NFT_DATA_VALUE after nft_data_init() ARM: dts: BCM5301X: Fix MDIO node address/size cells bpf: Clear skb->tstamp in bpf_redirect when necessary parisc: add missing __init annotation iommu/iova: Init the struct iova to fix the possible memleak powerpc/spinlocks: Include correct header for static key ARM: dts: imx6ul: use nvmem-cells for cpu speed grading UBUNTU: upstream stable to v4.14.164, v4.19.95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861739/+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 1863019] Re: Bionic update: upstream stable patchset 2020-02-12
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863019 Title: Bionic update: upstream stable patchset 2020-02-12 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-12 Ported from the following upstream stable releases: v4.14.168, v4.19.99 from git://git.kernel.org/ xfs: Sanity check flags of Q_XQUOTARM call mfd: intel-lpss: Add default I2C device properties for Gemini Lake powerpc/archrandom: fix arch_get_random_seed_int() tipc: fix wrong timeout input for tipc_wait_for_cond() mt7601u: fix bbp version check in mt7601u_wait_bbp_ready crypto: sun4i-ss - fix big endian issues drm/sti: do not remove the drm_bridge that was never added drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset() ALSA: hda: fix unused variable warning apparmor: don't try to replace stale label in ptrace access check PCI: iproc: Remove PAXC slot check to allow VF support drm/hisilicon: hibmc: Don't overwrite fb helper surface depth IB/rxe: replace kvfree with vfree IB/hfi1: Add mtu check for operational data VLs ALSA: usb-audio: update quirk for B&W PX to remove microphone staging: comedi: ni_mio_common: protect register write overflow pwm: lpss: Release runtime-pm reference from the driver's remove callback drm/sun4i: hdmi: Fix double flag assignation mlxsw: reg: QEEC: Add minimum shaper fields NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks pcrypt: use format specifier in kobject_add exportfs: fix 'passing zero to ERR_PTR()' warning drm/dp_mst: Skip validating ports during destruction, just ref net: phy: Fix not to call phy_resume() if PHY is not attached IB/rxe: Fix incorrect cache cleanup in error flow staging: bcm2835-camera: Abort probe if there is no camera switchtec: Remove immediate status check after submitting MRPC command pinctrl: sh-pfc: r8a7740: Add missing REF125CK pin to gether_gmii group pinctrl: sh-pfc: r8a7740: Add missing LCD0 marks to lcd0_data24_1 group pinctrl: sh-pfc: r8a7791: Remove bogus ctrl marks from qspi_data4_b group pinctrl: sh-pfc: r8a7791: Remove bogus marks from vin1_b_data18 group pinctrl: sh-pfc: sh73a0: Add missing TO pin to tpu4_to3 group pinctrl: sh-pfc: r8a7794: Remove bogus IPSR9 field pinctrl: sh-pfc: sh7734: Add missing IPSR11 field pinctrl: sh-pfc: r8a77995: Remove bogus SEL_PWM[0-3]_3 configurations pinctrl: sh-pfc: sh7269: Add missing PCIOR0 field pinctrl: sh-pfc: sh7734: Remove bogus IPSR10 value vxlan: changelink: Fix handling of default remotes Input: nomadik-ske-keypad - fix a loop timeout test clk: highbank: fix refcount leak in hb_clk_init() clk: qoriq: fix refcount leak in clockgen_init() clk: socfpga: fix refcount leak clk: samsung: exynos4: fix refcount leak in exynos4_get_xom() clk: imx6q: fix refcount leak in imx6q_clocks_init() clk: imx6sx: fix refcount leak in imx6sx_clocks_init() clk: imx7d: fix refcount leak in imx7d_clocks_init() clk: vf610: fix refcount leak in vf610_clocks_init() clk: armada-370: fix refcount leak in a370_clk_init() clk: kirkwood: fix refcount leak in kirkwood_clk_init() clk: armada-xp: fix refcount leak in axp_clk_init() clk: mv98dx3236: fix refcount leak in mv98dx3236_clk_init() clk: dove: fix refcount leak in dove_clk_init() MIPS: BCM63XX: drop unused and broken DSP platform device IB/usnic: Fix out of bounds index check in query pkey RDMA/ocrdma: Fix out of bounds index check in query pkey RDMA/qedr: Fix out of bounds index check in query pkey drm/shmob: Fix return value check in shmob_drm_probe arm64: dts: apq8016-sbc: Increase load on l11 for SDCARD spi: cadence: Correct initialisation of runtime PM RDMA/iw_cxgb4: Fix the unchecked ep dereference drm/etnaviv: NULL vs IS_ERR() buf in etnaviv_core_dump() media: s5p-jpeg: Correct step and max values for V4L2_CID_JPEG_RESTART_INTERVAL kbuild: mark prepare0 as PHONY to fix external module build crypto: brcm - Fix some set-but-not-used warning crypto: tgr192 - fix unaligned memory access ASoC: imx-sgtl5000: put of nodes if finding codec fails IB/iser: Pass the correct number of entries for dma mapped SGL rtc: cmos: ignore bogus century b
[Kernel-packages] [Bug 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi
Maybe try this? https://techtablets.com/forum/topic/how-to-disable- secure-boot-for-xiaomi-mi-notebook-air/ -- 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: Incomplete 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 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi
Marked as Incomplete for request in comment #2 ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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: Incomplete 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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Please test this kernel: https://people.canonical.com/~khfeng/lp1860754/ -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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
Re: [Kernel-packages] [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
There are no extensions or scripts that I have installed to handle the backlight. I did not include acpi_backlight=vendor as a kernel parameter at the same time as i915.enable_dpcd_backlight=1. The only kernel parameters currently are "i915.enable_dpcd_backlight=1 quiet splash". Should I try both backlight parameters at the same time? On Thu, Feb 13, 2020 at 10:05 PM Kai-Heng Feng wrote: > What if acpi_backlight=vendor is removed? Is there any extension or > script installed to handle the backlight? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > 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: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > 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-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor 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: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > -- 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/1860303 Title: Backlight brightness cannot be adjusted using keys Status in linux package in Ubuntu: Incomplete Bug description: I cannot adjust the screen brightness using the keyboard keys or changing /sys/call/backlight/intel_backlight/brightness values. I've only been able to adjust the backlight using xrandr. Followed bug report on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and attached files. Additional information: 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change the screen brightness 2. video.use_bios_initial_backlight=0 does not enable brightness to be changed 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work and on one boot "y"s were being continuously typed without any keys being depressed. It was odd. 4. video.use_native_backlight=1 does not enabel brightness to be changed 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no impact ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignatu
[Kernel-packages] [Bug 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi
There is no such options in the bios. -- 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: Incomplete 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 1746340] Re: Samsung SSD corruption (fsck needed)
Can you please attach `sudo nvme id-ctrl /dev/nvme0`? -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=0ca062da-7e8f-425a-88
[Kernel-packages] [Bug 1861192] Re: disco/linux: 5.0.0-41.45 -proposed tracker
Also I can't find this kernel in proposed repository, I suppose this is expected(since already EOL). linux-generic: Installed: 5.0.0.40.42 Candidate: 5.0.0.40.42 Version table: *** 5.0.0.40.42 500 500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.0.0.38.40 500 500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu disco-security/main amd64 Packages 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages -- 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: Invalid 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: Fix Released 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: Ready for Testing phase-changed: Friday, 14. February 2020 05:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-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 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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 1783880] Re: ltp-syscalls: fallocate05 fails with btrfs on ppc64el
** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Cosmic) Status: Invalid => Won't Fix -- 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/1783880 Title: ltp-syscalls: fallocate05 fails with btrfs on ppc64el Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Won't Fix Bug description: This affects at least bionic and cosmic proposed kernels. This affects only ppc64el. My guess is the reason is the page size. In fact, changing the fallocate size to 64KiB, the test works. tst_test.c:1079: INFO: Testing on btrfs tst_mkfs.c:83: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:61: INFO: write(): ENOSPC fallocate05.c:62: PASS: write() wrote 32768 bytes fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC fallocate05.c:78: BROK: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE): ENOSPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783880/+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 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
** Tags added: sru-20200127 -- 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/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: New Status in linux source package in Disco: New Status in linux-azure source package in Disco: New Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+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 + phase: Ready for Testing + phase-changed: Friday, 14. February 2020 05:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-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 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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: Invalid 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: Fix Released 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: Ready for Testing phase-changed: Friday, 14. February 2020 05:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-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 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi
s/dibbled/disabled/ -- 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 1861192] Re: disco/linux: 5.0.0-41.45 -proposed tracker
Ubuntu 19.04 is already EOL. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Invalid 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: Fix Released 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: Ready for Testing phase-changed: Friday, 14. February 2020 05:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-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 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi
Secure Boot has to be dibbled in the BIOS. -- 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 1862313] Re: Support Headset Mic on HP cPC
** Changed in: linux (Ubuntu Eoan) Status: Confirmed => Fix Released -- 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/1862313 Title: Support Headset Mic on HP cPC Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Incomplete Status in linux-oem source package in Focal: Won't Fix Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] Two HP workstations can't detect headset microphone. [Fix] Apply vendor-specific coefficient to enable headset mic detection. [Test] Plug headset and see if the mic gets detected. Headset mic gets detected correctly after applying the patch. [Regression Potential] Low. The fix matches to very specific machines, so all other systems are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862313/+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 1862865] 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 1862865
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986]
[Kernel-packages] [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
What if acpi_backlight=vendor is removed? Is there any extension or script installed to handle the backlight? -- 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/1860303 Title: Backlight brightness cannot be adjusted using keys Status in linux package in Ubuntu: Incomplete Bug description: I cannot adjust the screen brightness using the keyboard keys or changing /sys/call/backlight/intel_backlight/brightness values. I've only been able to adjust the backlight using xrandr. Followed bug report on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and attached files. Additional information: 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change the screen brightness 2. video.use_bios_initial_backlight=0 does not enable brightness to be changed 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work and on one boot "y"s were being continuously typed without any keys being depressed. It was odd. 4. video.use_native_backlight=1 does not enabel brightness to be changed 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no impact 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: jaredy 1649 F pulseaudio /dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 19 19:51:45 2020 InstallationDate: Installed on 2020-01-03 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13t-aw100 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-26-generic root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash acpi_backlight=vendor 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: 11/15/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13t-aw100 dmi.product.sku: 6YG70AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+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 1850439] Re: No sound on ASUS UX534FT
Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: Sound(ALSA) Probably need a quirk to enable the codec. -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
** Package changed: linux-meta-5.4 (Ubuntu Focal) => linux (Ubuntu
Focal)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02
[Kernel-packages] [Bug 1862263] Re: test_sysctl in bpf from ubuntu_kernel_selftests make net test fails to build on eoan
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862263
Title:
test_sysctl in bpf from ubuntu_kernel_selftests make net test fails to
build on eoan
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Fix Committed
Bug description:
== SRU Justification ==
Commit 7541c87c ("bpf: Allow narrow loads of bpf_sysctl fields with
offset > 0") applied to Eoan tree via stable-update process brought a
member called "seek" to tools/testing/selftests/bpf/test_sysctl.c:
.seek = 4,
However we don't have the commit that declares it, so the compilation
failed with:
test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named
‘seek’
181 | .seek = 4,
| ^~~~
== Fix ==
* d895a0f1 ("bpf: fix accessing bpf_sysctl.file_pos on s390")
Only Eoan is affected.
== Test ==
Patch tested against the affected kernels, the bpf test can be built
without any issue.
== Regression Potential ==
Low, changes limited to testing tools.
==Original Bug Report ==
test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named ‘seek’
181 | .seek = 4,
|^~~~
This affects all arches. Kernel 5.3.0-40.32.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862263/+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 1860041] Re: shiftfs: prevent lower dentries from going negative during unlink
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860041
Title:
shiftfs: prevent lower dentries from going negative during unlink
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
SRU Justification
Impact: All non-special files (For shiftfs this only includes fifos
and - for this case - unix sockets - since we don't allow character
and block devices to be created.) go through shiftfs_open() and have
their dentry pinned through this codepath preventing it from going
negative. But fifos don't use the shiftfs fops but rather use the
pipefifo_fops which means they do not go through shiftfs_open() and
thus don't have their dentry pinned that way. Thus, the lower dentries
for such files can go negative on unlink causing segfaults. The
following C program can be used to reproduce the crash:
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
struct stat stat;
unlink("./bbb");
int ret = mknod("./bbb", S_IFIFO|0666, 0);
if (ret < 0)
exit(1);
int fd = open("./bbb", O_RDWR);
if (fd < 0)
exit(2);
if (unlink("./bbb"))
exit(4);
fstat(fd, &stat);
return 0;
}
Fix: Similar to ecryptfs we need to dget() the lower dentry before
calling vfs_unlink() on it and dput() it afterwards.
Regression Potential: Limited to shiftfs.
Test Case: Compiled a kernel with the fix and used the reproducer
above to verify that the kernel cannot be crashed anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860041/+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 1862865] [NEW] i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
You have been subscribed to a public bug:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at
0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8
31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef
be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01
80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8
31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef
be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01
80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:17 dharkan kernel: [71072.575930] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:19 dharkan kernel: [71074.591922] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:21 dharkan kernel: [71076.575911] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:23 dharkan kernel: [71078.591901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:25 dharkan kernel: [71080.575883] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:
[Kernel-packages] [Bug 1862885] Re: Sometimes can't adjust brightness on Dell AIO
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862885 Title: Sometimes can't adjust brightness on Dell AIO Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux source package in Focal: Fix Committed Bug description: [Impact] We already added retry on the backlight driver, but the scalar have to take some time to activate panel during booting up, and 2 seconds seem doesn't enough. So, it sometimes fails to get the response from scalar. [Fix] Enlarge the retry time from 2 seconds to 5 seconds. We didn't observe the response time longer than 3 seconds, but to be more confident, enlarge the value to 5 seconds. [Test] Verified on new Dell AIO platform. [Regression Potential] Low, increase the retry times doesn't hurt anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862885/+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 1799497] Re: 4.15 kernel hard lockup about once a week
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799497
Title:
4.15 kernel hard lockup about once a week
Status in linux package in Ubuntu:
Incomplete
Status in zram-config package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in zram-config source package in Bionic:
Confirmed
Bug description:
== SRU Justification ==
When using zram (as installed and configured with the zram-config package)
systems can lockup after about a week of use. This occurs because of
a hang in a lock in zram.
== Test Case ==
Run stress-ng --brk 0 --stack 0 in a Bionic amd64 server VM with 1GM of
memory, 16 CPU threads and zram-config installed. Without the fix the
kernel will hang in a spinlock after 1-2 hours of run time. With the fix,
the hang does not occur. Testing shows that with the fix, 5 x 16 CPU hours
of stress testing with stress-ng works fine without the lockup occurring.
== The fix ==
Upstream commit c4d6c4cc7bfd ("zram: correct flag name of ZRAM_ACCESS") as
a prerequisite followed by a minor context wiggle backport of the fix with
commit 3c9959e02547 ("zram: fix lockdep warning of free block handling").
== Regression Potential ==
This touches the zram locking, so the core zram driver is affected. However
the fixes are backports from 5.0, so the fixes have had a fair amount of
testing in later kernels.
My main server has been running into hard lockups about once a week
ever since I switched to the 4.15 Ubuntu 18.04 kernel.
When this happens, nothing is printed to the console, it's effectively
stuck showing a login prompt. The system is running with panic=1 on
the cmdline but isn't rebooting so the kernel isn't even processing
this as a kernel panic.
As this felt like a potential hardware issue, I had my hosting
provider give me a completely different system, different motherboard,
different CPU, different RAM and different storage, I installed that
system on 18.04 and moved my data over, a week later, I hit the issue
again.
We've since also had a LXD user reporting similar symptoms here also on
varying hardware:
https://github.com/lxc/lxd/issues/5197
My system doesn't have a lot of memory pressure with about 50% of free
memory:
root@vorash:~# free -m
totalusedfree shared buff/cache
available
Mem: 31819 17574 402 513 13842
13292
Swap: 159092687 13222
I will now try to increase console logging as much as possible on the
system in the hopes that next time it hangs we can get a better idea
of what happened but I'm not too hopeful given the complete silence on
the console when this occurs.
System is currently on:
Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
But I've seen this since the GA kernel on 4.15 so it's not a recent
regression.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 23 16:12 seq
crw-rw 1 root audio 116, 33 Oct 23 16:12 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse:
Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with
exit code 1: Cannot stat file /proc/22822/fd/10: Permission denied
Cannot stat file /proc/22831/fd/10: Permission denied
DistroRelease: Ubuntu 18.04
HibernationDevice:
RESUME=none
CRYPTSETUP=n
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard
and Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel Corporation S1200SP
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0
panic=1 verbose console=tty0 console=ttyS0,115200n8
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Unam
[Kernel-packages] [Bug 1860657] Re: Prevent arm64 guest from accessing host debug registers
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860657 Title: Prevent arm64 guest from accessing host debug registers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] Guests could access host debug/PMU registers. This could happen very briefly before they are first preempted. This only affects arm64 CPUs that support virtualization. [Regression potential] This could break virtualization or guest access to PMU registers. [Test case] A guest has been run with a host with the patched kernel. perf top has been run on the guest. Using uvtool: host$ sudo apt install uvtool qemu-efi-aarch64 host$ uvt-kvm create test release=eoan arch=arm64 host$ uvt-kvm ssh test guest$ sudo perf top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860657/+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 1861973] Re: run_afpackettests in ubuntu_kernel_selftests failed with "./in_netns.sh: Permission denied"
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861973 Title: run_afpackettests in ubuntu_kernel_selftests failed with "./in_netns.sh: Permission denied" Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux-signed package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-signed source package in Xenial: Invalid Bug description: This issue begins with my fix in bug 1853375, the newly created in_netns.sh script got file permission with: new file mode 100755 However, it lost the executable property when downloaded by the test case: -rw-r--r-- 1 root root 298 Feb 5 07:41 in_netns.sh If you do a manual chmod this test will pass without any issue. This commit can be found here in Xenial tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h =master-next&id=df9283329019ce48157c84fcd06c61204139abb7 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: User Name 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Wed Feb 5 07:27:33 2020 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1861973/+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 1862114] Re: pty03 from pty in ubuntu_ltp failed on Eoan
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862114 Title: pty03 from pty in ubuntu_ltp failed on Eoan Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: == Justification == The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL pointer dereference: [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020 [ 951.309960] #PF: supervisor write access in kernel mode [ 951.312130] #PF: error_code(0x0002) - not-present page [ 951.314227] PGD 0 P4D 0 [ 951.315278] Oops: 0002 [#1] SMP PTI [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic #15-Ubuntu [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50 [ 951.352494] Call Trace: [ 951.353244] slip_write_wakeup+0x25/0x30 [slip] [ 951.354600] tty_wakeup+0x5b/0x70 [ 951.355539] pty_unthrottle+0x19/0x30 [ 951.356560] tty_unthrottle+0x42/0x60 [ 951.357566] __tty_perform_flush+0x87/0x90 [ 951.358768] n_tty_ioctl_helper+0xcc/0x150 [ 951.359955] n_tty_ioctl+0x2d/0x100 [ 951.360930] tty_ioctl+0x3c0/0x8e0 [ 951.361882] ? __switch_to_asm+0x34/0x70 [ 951.363049] ? __switch_to_asm+0x40/0x70 [ 951.364191] ? __switch_to_asm+0x34/0x70 [ 951.365261] ? __switch_to_asm+0x40/0x70 [ 951.366382] ? __switch_to_asm+0x34/0x70 [ 951.367452] ? __switch_to_asm+0x40/0x70 [ 951.368523] ? __switch_to_asm+0x34/0x70 [ 951.369693] ? __switch_to_asm+0x40/0x70 [ 951.370829] ? __switch_to_asm+0x34/0x70 [ 951.371923] ? __switch_to_asm+0x40/0x70 [ 951.372998] ? __switch_to_asm+0x34/0x70 [ 951.374097] ? __switch_to_asm+0x40/0x70 [ 951.375183] ? __switch_to_asm+0x34/0x70 [ 951.376288] ? __switch_to_asm+0x40/0x70 [ 951.377390] ? __switch_to+0x110/0x470 [ 951.378863] do_vfs_ioctl+0x407/0x670 [ 951.380269] ? __schedule+0x2eb/0x740 [ 951.381761] ksys_ioctl+0x67/0x90 [ 951.383076] __x64_sys_ioctl+0x1a/0x20 [ 951.384510] do_syscall_64+0x57/0x190 [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9 == Fixes == Indicated by the test case, this issue can be fixed by: * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and close with RCU) This patch can be cherry-picked into all of our kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/ Tested on KVM nodes and the patched kernels work as expected, there will be no more kernel null pointer dereference issue, and the test can finish properly. == Regression potential == Low, changes limited to two specific drivers for serial line TTY. This issue can be reproduced quite easily and the patched kernels show positive results. == Original Bug Report == startup='Thu Feb 6 02:45:23 2020' tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s pty03.c:101: INFO: Creating PTY with SLIP line discipline Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0 This is a new test case, so it's not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862114/+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 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
Correcting comment #3, this is the correct patch commit 39d1e3340c73e8f7eb1d6a8cae561c255ca7b1b0 Author: Tudor Ambarus Date: Thu Nov 7 08:41:51 2019 + mtd: spi-nor: Fix clearing of QE bit on lock()/unlock() -- 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/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver 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 Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+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 1862252] Re: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** 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 -- kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 - phase: Packaging - phase-changed: Thursday, 13. February 2020 14:45 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 14. February 2020 04:11 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building 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/1862252 Title: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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 -- kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Holding before Promote to Proposed phase-changed: Friday, 14. February 2020 04:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862252/+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 1863086] Re: unkillable process (kernel NULL pointer dereference)
I cannot reproduce this. I compiled the reproducer program and tested on a Eoan VM running in KVM, with the same 5.3.0-29-generic kernel: ubuntu@ubuntu:~$ ./socktest Segmentation fault (core dumped) ubuntu@ubuntu:~$ tail /var/log/kern.log Feb 14 04:00:41 ubuntu kernel: [ 134.951620] socktest[1598]: segfault at 21 ip 55892e4cb2a3 sp 7ffed8905de0 error 6 in socktest[55892e4cb000+1000] Feb 14 04:00:41 ubuntu kernel: [ 134.951634] Code: 48 8d 4d e0 8b 45 dc ba 10 00 00 00 48 89 ce 89 c7 e8 71 fe ff ff 8b 45 dc be 0a 00 00 00 89 c7 e8 52 fe ff ff b8 21 00 00 00 00 21 00 00 00 b8 00 00 00 00 48 8b 4d f8 64 48 33 0c 25 28 00 ubuntu@ubuntu:~$ ps ax | grep socktest 1602 pts/0S+ 0:00 grep --color=auto socktest ubuntu@ubuntu:~$ uname -rv 5.3.0-29-generic #31-Ubuntu SMP Fri Jan 17 17:27:26 UTC 2020 The segfault happens as expected, but there is no null pointer dereference and no stack trace in dmesg. The process is terminated and I can still bind to port 6000 with netcat. I see that you have Virtual Box kernel modules loaded. Can you try reproduce this on a fresh Eoan VM with no Virtual Box drivers installed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863086 Title: unkillable process (kernel NULL pointer dereference) Status in linux package in Ubuntu: Confirmed Bug description: If process that listens socket on any port crashes (segmentation fault) it becomes unkillable. Kill command does not kill this process. Port that listen crashed process never be freed. journalctl shows error: Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000] Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 0020 Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0 Feb 13 13:28:09 vbun04 kernel: Oops: [#1] SMP NOPTI Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G OE 5.3.0-29-generic #31-Ubuntu Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: 9d4b76995100 RCX: 1afc Feb 13 13:28:09 vbun04 kernel: RDX: RSI: b464c2c5fc68 RDI: Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 R09: b464c2c5fbe0 Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11: R12: 9d4b7b3df540 Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14: R15: b9f15920 Feb 13 13:28:09 vbun04 kernel: FS: 7f6c91911540() GS:9d4b7db0() knlGS: Feb 13 13:28:09 vbun04 kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 CR4: 000606e0 Feb 13 13:28:09 vbun04 kernel: Call Trace: Feb 13 13:28:09 vbun04 kernel: ? wake_up_state+0x10/0x20 Feb 13 13:28:09 vbun04 kernel: ? __send_signal+0x1eb/0x3f0 Feb 13 13:28:09 vbun04 kernel: get_signal+0x159/0x880 Feb 13 13:28:09 vbun04 kernel: do_signal+0x34/0x280 Feb 13 13:28:09 vbun04 kernel: ? bad_area+0x47/0x50 Feb 13 13:28:09 vbun04 kernel: exit_to_usermode_loop+0xbf/0x160 Feb 13 13:28:09 vbun04 kernel: prepare_exit_to_usermode+0x77/0xa0 Feb 13 13:28:09 vbun04 kernel: retint_user+0x8/0x8 Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: RCX: 7f6c918424eb Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a RDI: 0003 Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08: R09: 7f6c919331f0 Feb 13 13:28:09 vbun04 kernel: R10: R11: 0
[Kernel-packages] [Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Fix Released 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 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
SNOR_F_HAS_16BIT_SR is defined in this patch commit adf1092fa838e870813f2ac152973af311d8ae02 Author: Jungseung Lee Date: Mon Dec 2 15:35:06 2019 +0900 mtd: spi-nor: Support TB selection using SR bit 6 There are some flashes to use bit 6 of status register for Top/Bottom (TB). Use top/bottom bit variable instead of fixed value and support this case. -- 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/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver 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 Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+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
Re: [Kernel-packages] [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
This kernel parameter does make the backlight respond to keyboard input, as well as manually changing the brightness values in `/sys/class/backlight/intel_backlight/brightness`. However the behavior is odd. Adjusting the brightness using the keyboard results in erratic changes rather than a smooth change in brightness. The brightness settings appear to range between 655 and 65535 in `/sys/class/backlight/intel_backlight/brightness` when using the keyboard keys. However, the max screen brightness appears to be at 2047 when manually setting a brightness value in `/sys/class/backlight/intel_backlight/brightness`. On Thu, Feb 13, 2020 at 12:30 AM Kai-Heng Feng wrote: > Does kernel parameter "i915.enable_dpcd_backlight=1" help? > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > 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: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > 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-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor 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: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > -- 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/1860303 Title: Backlight brightness cannot be adjusted using keys Status in linux package in Ubuntu: Incomplete Bug description: I cannot adjust the screen brightness using the keyboard keys or changing /sys/call/backlight/intel_backlight/brightness values. I've only been able to adjust the backlight using xrandr. Followed bug report on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and attached files. Additional information: 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change the screen brightness 2. video.use_bios_initial_backlight=0 does not enable brightness to be changed 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work and on one boot "y"s were being continuously typed without any keys being depr
[Kernel-packages] [Bug 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -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 kernel-stable-master-bug: 1862824 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Testing - phase-changed: Tuesday, 11. February 2020 13:26 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 03:40 UTC reason: - certification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1861135 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1861136 Title: bionic/linux-snapdragon: 4.15.0-1072.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 kernel-stable-master-bug: 1862824 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Signoff phase-changed: Friday, 14. February 2020 03:40 UTC reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1861135 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861136/+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 1862818] Re: xenial/linux-azure: 4.15.0-1071.76 -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 kernel-stable-master-bug: 1862824 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Testing - phase-changed: Wednesday, 12. February 2020 15:58 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 03:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- stakeholder signoff not verified security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff trackers: trusty/linux-azure: bug 1862816 xenial/linux-azure/azure-kernel: bug 1862815 variant: debs -- 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/1862818 Title: xenial/linux-azure: 4.15.0-1071.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: 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 kernel-stable-master-bug: 1862824 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Friday, 14. February 2020 03:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff trackers: trusty/linux-azure: bug 1862816 xenial/linux-azure/azure-kernel: bug 1862815 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862818/+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 1862818] Re: xenial/linux-azure: 4.15.0-1071.76 -proposed tracker
No outstanding ADT regressions. ** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released -- 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/1862818 Title: xenial/linux-azure: 4.15.0-1071.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: 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 kernel-stable-master-bug: 1862824 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Friday, 14. February 2020 03:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff trackers: trusty/linux-azure: bug 1862816 xenial/linux-azure/azure-kernel: bug 1862815 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862818/+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 1861214] Re: eoan/linux: 5.3.0-40.32 -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:42 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 03:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1862398 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 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/1861214 Title: eoan/linux: 5.3.0-40.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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: Signoff phase-changed: Friday, 14. February 2020 03:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1862398 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861214/+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 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: https://certification.canonical.com/hardware/201901-26783/submission/161078/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1861136 Title: bionic/linux-snapdragon: 4.15.0-1072.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 kernel-stable-master-bug: 1862824 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Signoff phase-changed: Friday, 14. February 2020 03:40 UTC reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1861135 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861136/+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 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Tuesday, 11. February 2020 16:43 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862213 Title: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Friday, 14. February 2020 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862213/+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 1861300] Re: Data Corruption with Sil 3114 and 3124 controlleurs
Ok, if disabling NCQ solves the issue we need to fix it in the kernel. -- 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 1861214] Re: eoan/linux: 5.3.0-40.32 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/Q9MvidMW/292-eoan-linux- image-530-40-generic-530-4032 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861214 Title: eoan/linux: 5.3.0-40.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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: Signoff phase-changed: Friday, 14. February 2020 03:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1862398 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861214/+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 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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: In Progress 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: Fix Released 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 trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 bionic/linux-gcp: bug 1862213 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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 1862405] Re: bionic/linux-azure: 5.0.0-1032.34 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Testing - phase-changed: Tuesday, 11. February 2020 16:44 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress replaces: bug 1861182 trackers: bionic/linux-azure/azure-kernel: bug 1862404 variant: debs -- 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/1862405 Title: bionic/linux-azure: 5.0.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Friday, 14. February 2020 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff replaces: bug 1861182 trackers: bionic/linux-azure/azure-kernel: bug 1862404 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862405/+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 1863092] Re: Testing node with B-FIPS will complain "Unknown error executing apt-key"
I found this was caused by libgcrypt20 / libgcrypt20-hmac package in FIPS proposed, will update the bug description ** Also affects: libgcrypt20 (Ubuntu) Importance: Undecided Status: New ** Description changed: B-FIPS testing node will complain about "Unknown error executing apt- key" when running the apt update command. + $ sudo apt update + Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease + Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease + Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease + Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease + Hit:5 https://private-ppa.launchpad.net/ubuntu-advantage/fips-proposed/ubuntu bionic InRelease + Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease + Unknown error executing apt-key + + This is caused by the libgcrypt20 / libgcrypt20-hmac package in FIPS + proposed pocket. + + Steps to reproduce: + 1. Deploy a Bionic node, run apt update + 2. Enable FIPS proposed, upgrade libgcrypt20 / libgcrypt20-hmac package + 3. run apt update + + You will see this failure in step 3. + + This issue does not exist in X-FIPS. - Not sure what's the cause. ** Description changed: B-FIPS testing node will complain about "Unknown error executing apt- key" when running the apt update command. $ sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease - Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease - Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease - Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease + Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease + Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease + Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:5 https://private-ppa.launchpad.net/ubuntu-advantage/fips-proposed/ubuntu bionic InRelease - Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease - Unknown error executing apt-key + Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease + Unknown error executing apt-key - This is caused by the libgcrypt20 / libgcrypt20-hmac package in FIPS - proposed pocket. + This is caused by the libgcrypt20 / libgcrypt20-hmac package + (1.8.1-4ubuntu1.fips.2.3) in FIPS proposed pocket. Steps to reproduce: 1. Deploy a Bionic node, run apt update - 2. Enable FIPS proposed, upgrade libgcrypt20 / libgcrypt20-hmac package + 2. Enable FIPS proposed, upgrade libgcrypt20 / libgcrypt20-hmac package 3. run apt update You will see this failure in step 3. - This issue does not exist in X-FIPS. -- 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/1863092 Title: Testing node with B-FIPS will complain "Unknown error executing apt- key" Status in ubuntu-kernel-tests: New Status in libgcrypt20 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: B-FIPS testing node will complain about "Unknown error executing apt- key" when running the apt update command. $ sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:5 https://private-ppa.launchpad.net/ubuntu-advantage/fips-proposed/ubuntu bionic InRelease Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease Unknown error executing apt-key This is caused by the libgcrypt20 / libgcrypt20-hmac package (1.8.1-4ubuntu1.fips.2.3) in FIPS proposed pocket. Steps to reproduce: 1. Deploy a Bionic node, run apt update 2. Enable FIPS proposed, upgrade libgcrypt20 / libgcrypt20-hmac package 3. run apt update You will see this failure in step 3. This issue does not exist in X-FIPS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1863092/+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
5 remaining unverified issues. LP #1846148 LP #1858815 LP #1857413 LP #1859522 LP #1854401 3 hardware-related, 2 CVE-related. All are low risk, and some not easily verifiable. Setting VT to fix-released ** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: In Progress 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: Fix Released 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 trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 bionic/linux-gcp: bug 1862213 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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 1862459] Re: ubuntu 18 screen flicker/blink
Thanks for the bug report. I can see two possible problems here that might relate to screen flicker: * The i915 kernel driver crashed, in intel_modeset_init * Xorg is using probably the wrong driver 'intel'. It should be using the modesetting driver on a modern system like yours. Please try removing that wrong driver: sudo apt remove xserver-xorg-video-intel or just try logging into "Ubuntu on Wayland" instead. Maybe it's some combination of the above two issues. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-intel (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/1862459 Title: ubuntu 18 screen flicker/blink Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Ubuntu screen flicker /blinking on start laptop every time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Sat Feb 8 20:50:43 2020 DistUpgraded: 2019-06-27 23:49:46,134 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1574 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-27 (225 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jun 27 18:02:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862459/+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 1862459] [NEW] ubuntu 18 screen flicker/blink
You have been subscribed to a public bug: Ubuntu screen flicker /blinking on start laptop every time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Sat Feb 8 20:50:43 2020 DistUpgraded: 2019-06-27 23:49:46,134 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1574 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-27 (225 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jun 27 18:02:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- ubuntu 18 screen flicker/blink https://bugs.launchpad.net/bugs/1862459 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862253] Re: focal/linux-kvm-5.4: 5.4.0-1001.1 -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 kernel-stable-master-bug: 1862255 packages: main: linux-kvm-5.4 meta: linux-meta-kvm-5.4 phase: Ready for Promote to Proposed phase-changed: Thursday, 13. February 2020 14:16 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review 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/1862253 Title: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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 kernel-stable-master-bug: 1862255 packages: main: linux-kvm-5.4 meta: linux-meta-kvm-5.4 phase: Ready for Promote to Proposed phase-changed: Thursday, 13. February 2020 14:16 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862253/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Just checked again and it seems neither upstream Linux nor upstream PulseAudio have landed this yet. Perhaps they don't know about it or have lost track of the patches. To get the ball rolling, anyone affected please open new upstream bugs in both: Linux: https://bugzilla.kernel.org/ PulseAudio: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and then tell us the new bug IDs. If the Ubuntu kernel team is listening then maybe they can help with this. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 bionic/linux-gke-5.0: bug 1861187 - bionic/linux-oem-osp1: bug 1861178, bug 1863082 + bionic/linux-oem-osp1: bug 1863082 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: In Progress 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 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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 1862398] Re: eoan/linux-azure: 5.3.0-1013.14 -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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 12. February 2020 01:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff trackers: bionic/linux-azure-5.3: bug 1862397 variant: debs -- 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/1862398 Title: eoan/linux-azure: 5.3.0-1013.14 -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: Invalid 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 12. February 2020 01:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff trackers: bionic/linux-azure-5.3: bug 1862397 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862398/+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)
@Paolo, To check if ucm files getting loaded, what I know is to check the pusleaudio's log. -- 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 1861199] Re: eoan/linux-aws: 5.3.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Testing - phase-changed: Tuesday, 04. February 2020 14:53 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 00:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1861198 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1861199 Title: eoan/linux-aws: 5.3.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Friday, 14. February 2020 00:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-aws-5.3: bug 1861198 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861199/+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 1861197] Re: eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861214 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 04. February 2020 14:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2-5.3: bug 1861196 eoan/linux-raspi2/pi-kernel: bug 1861194 variant: debs -- 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/1861197 Title: eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 04. February 2020 14:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-raspi2-5.3: bug 1861196 eoan/linux-raspi2/pi-kernel: bug 1861194 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861197/+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 1861206] Re: eoan/linux-kvm: 5.3.0-1010.11 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861214 packages: main: linux-kvm meta: linux-meta-kvm - phase: Testing - phase-changed: Monday, 03. February 2020 19:33 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 00:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1861206 Title: eoan/linux-kvm: 5.3.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Friday, 14. February 2020 00:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861206/+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 1861208] Re: eoan/linux-oracle: 5.3.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Testing - phase-changed: Tuesday, 04. February 2020 16:06 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 00:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1861207 variant: debs -- 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/1861208 Title: eoan/linux-oracle: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Friday, 14. February 2020 00:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-oracle-5.3: bug 1861207 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861208/+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 1862398] Re: eoan/linux-azure: 5.3.0-1013.14 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 12. February 2020 01:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1862397 variant: debs -- 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/1862398 Title: eoan/linux-azure: 5.3.0-1013.14 -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: Invalid 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 12. February 2020 01:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff trackers: bionic/linux-azure-5.3: bug 1862397 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862398/+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 1861214] Re: eoan/linux: 5.3.0-40.32 -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:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1862398 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 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/1861214 Title: eoan/linux: 5.3.0-40.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1862398 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861214/+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 1861205] Re: eoan/linux-gcp: 5.3.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Tuesday, 04. February 2020 16:05 UTC + phase: Signoff + phase-changed: Friday, 14. February 2020 00:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1861202 bionic/linux-gke-5.3: bug 1861204 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1861205 Title: eoan/linux-gcp: 5.3.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Friday, 14. February 2020 00:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-gcp-5.3: bug 1861202 bionic/linux-gke-5.3: bug 1861204 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861205/+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 1861214] Re: eoan/linux: 5.3.0-40.32 -proposed tracker
Only outstanding issues are laptop/hardware related and the addition of some new modules. Verification isn't strictly necessary for those. Setting VT to Fix released. ** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861214 Title: eoan/linux: 5.3.0-40.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1862398 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861214/+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
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+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)
@Paolo, Just remove "Headset" from all LENOVO-*.conf, change that line to cset "name='Mic Boost Volume' 2" reboot -- 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 1851068] Re: laptop does not wakeup after suspend (when lid off). Need to had reset
I switch to ubuntu 20.04 running kernel 5.4.0-17. I have the same issue when closing the lid, using pm-suspend or systemctl suspend. -- 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/1851068 Title: laptop does not wakeup after suspend (when lid off). Need to had reset Status in linux package in Ubuntu: Confirmed Bug description: When lid off. The laptop goes to unusual suspend mode. When raising the lid. Cannot turn laptop on. Cannot even log remotely using ssh. My laptop is hp spectre-15, i7-9750h with nvidia gtx 1650 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 Uname: Linux 5.4.0-050400rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:14:29 2019 InstallationDate: Installed on 2019-10-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dror 1529 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-31 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 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-21-generic root=UUID=ad8d697c-17a2-4ab1-97ac-a1f665546354 ro acpi_osi=! "acpi_osi=Windows 2015" nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-21-generic N/A linux-backports-modules-5.3.0-21-generic N/A linux-firmware1.183.1 Tags: wayland-session eoan Uname: Linux 5.3.0-21-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: 10/14/2019 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863E dmi.board.vendor: HP dmi.board.version: 53.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd10/14/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863E:rvr53.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV29AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851068/+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 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
Hi Dean -- I built a test kernel with the 5.3 patch from the gitlab bug, please give it a spin to see if it fixes your issue. https://people.canonical.com/~sforshee/lp1853044/5.3.0-40.32+lp1853044v202002131655/ Thanks! ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1853044 Title: 5.3.0-23-generic causes fans to spin when idle Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to 5.3.0-23-generic the fans in my machine don't stop running. They always sound like something is utilizing CPU - even with no applications running after boot. If I boot back to 5.3.0-19-generic it's fine. My microcode version is reported as 0xd4 and iucode-tool reports: iucode-tool: system has processor(s) with signature 0x000506e3 Let me know if you need anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 2898 F pulseaudio /dev/snd/pcmC2D0p: dean 2898 F...m pulseaudio /dev/snd/controlC0: dean 2898 F pulseaudio /dev/snd/controlC1: dean 2898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:03:34 2019 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (482 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+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 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters
You mean I should try an older version? Then I think I should try v5.0.x first. As you can see, it takes time to reproduce it again. I don't know how to intentionally reproduce it. -- 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/1860793 Title: [amdgpu] Severe freezes that begin with minor stutters Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: It starts with very subtle stuttering that you notice when moving windows around, then keeps getting worse and worse until it starts freezing the UI for many seconds. I could only reproduce it twice in a couple of days. The applications open at the time are usually Atom, Firefox, Hexchat, GNOME Files and occasionally Eye of GNOME. I checked resource consumption at the time of the stutters. Memory consumption was about 50% of 8GB, while the swap partition was nearly full (after a long gaming session). Storage device is a SATA SSD. During the stutters and freezes, CPU usage is normal. Through the process list of System Monitor I cannot see any application overusing resources. Temperatures are also normal. One potentially problematic hardware device is the GPU: AMD RX 560 4GB (open source AMDGPU). Its temperature and fan speed were also normal at the time. I know my system is capable of handling this workload. Also, this is only reproducible on Ubuntu 19.10 Eoan with GNOME. The LTS version of Ubuntu (18.04.3) is unaffected. I have used it for months before switching to the latest non-LTS version. What I've tried to stop the freezes: - Closed all running applications and waited. It didn't improve the situation, so I restarted my user session. The freezes continued, so I performed a system reboot, which finally helped normalize things. I did not try to reproduce this on the Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 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 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 11:13:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860793/+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
