[Kernel-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
It's the same one as #1845810 so we can mark it as verified. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in linux package in Ubuntu: In Progress 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: New Bug description: === SRU Justification === [Impact] XPS 13 9350/9360 has unbearlbe headphone noise after recent kernel updates. [Fix] Lock Headphone Mic Boost level to 1 as an workaround to solve the issue. [Test] Plug a headphone to audio jack, the noise is really bad. After applying the patch the noise is gone. [Regression Potenial] Low. This change only targets to 2 systems, so it has limited impact. === Original Bug Report === Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654448/+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 1852304] Re: trusty/linux-aws: 4.4.0-1059.63 -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: 1852306 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 15. November 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED - 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1852304 Title: trusty/linux-aws: 4.4.0-1059.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Invalid 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: Incomplete Status in Kernel SRU Workflow security-signoff series: Invalid 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 Trusty: 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: 1852306 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 15. November 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852304/+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 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@Erik, Dave Jones is working on the flash-kernel, and I remember there is already a bug to track this issue. Let Dave answer your question. -- 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/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
PPA in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1854156 -- 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/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497457] ---[ end trace 87c55fce1375aae8 ]--- ProblemTy
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Patch added: "0001-UBUNTU-SAUCE-fix-API-change-since-4.4.0-170.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854156/+attachment/5308646/+files/0001-UBUNTU-SAUCE-fix-API-change-since-4.4.0-170.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600
[Kernel-packages] [Bug 1852296] Re: xenial/linux-aws: 4.4.0-1099.110 -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: 1852306 packages: main: linux-aws meta: linux-meta-aws - phase: Testing - phase-changed: Friday, 15. November 2019 11:46 UTC + phase: Signoff + phase-changed: Friday, 29. November 2019 07:26 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: xenial/linux-aws/aws-kernel: bug 1852295 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/1852296 Title: xenial/linux-aws: 4.4.0-1099.110 -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-aws package in Ubuntu: Invalid Status in linux-aws 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: 1852306 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Friday, 29. November 2019 07:26 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: xenial/linux-aws/aws-kernel: bug 1852295 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852296/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
Patch verified on both 4.4.0-169.198 and 4.4.0-170-199. Should work for all 4.4 generic kernels with or without net/flow_dissector patch backported. -- 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/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 20
[Kernel-packages] [Bug 1851810] Re: Some EFI systems fail to boot in efi_init() when booted via maas
Marked as verified based on apw's comments in IRC. ** Tags removed: verification-needed-bionic verification-needed-disco verification-needed-eoan ** Tags added: verification-done-bionic verification-done-disco verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851810 Title: Some EFI systems fail to boot in efi_init() when booted via maas Status in linux package in Ubuntu: In Progress 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: In Progress Bug description: [Impact] Cirtain EFI systems will no longer boot with updated versions of maas. They will still boot in BIOS compatibility mode where available. [Test Case] Affected systems have already been tested with this fix applied and now boot successfully in EFI mode. The key test is does any EFI based system boot with this applied. [Regression Potential] The change increased the headroom by a very small amount, an additional 8 slots. This is very unlikely to lead to additional failures. === When booting via newer versions of maas we use grub extensions to load additional files. This leads the kernel to panic in efi_main(): exit_boot() failed! efi_main() failed! This occurs because the EFI memory map is more fragmented. When we exit boot services that returns an updated memory map in a buffer we supply. This has to be large enough to contain the updated map. If the exit fails because of lack of map space we are dead in the water because the call to allocate memory is lost to us. We therefore add some headroom in the allocation to allow for any expansion during close. This headroom is insufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851810/+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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
@Kai-Heng: Is there something that needs to be done to verify this bug in -proposed? -- 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in linux package in Ubuntu: In Progress 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: New Bug description: === SRU Justification === [Impact] XPS 13 9350/9360 has unbearlbe headphone noise after recent kernel updates. [Fix] Lock Headphone Mic Boost level to 1 as an workaround to solve the issue. [Test] Plug a headphone to audio jack, the noise is really bad. After applying the patch the noise is gone. [Regression Potenial] Low. This change only targets to 2 systems, so it has limited impact. === Original Bug Report === Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654448/+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 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
No outstanding bugs needing verification. ** 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/1852306 Title: xenial/linux: 4.4.0-170.199 -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: Incomplete 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 package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+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 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@hui.wang, see #20 I had to set this again this morning on updating. Is this known? If not set I get this upon flash-kernel: erikcas@thuis:~$ sudo flash-kernel /usr/share/flash-kernel/functions: line 160: warning: command substitution: ignored null byte in input Unsupported platform. I set this (manually) some days ago on flashing 1013 kernel. It seems not to be persistent. If not known, is a seperate bug to be filed? -- 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/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1852306] Re: xenial/linux: 4.4.0-170.199 -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: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 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/1852306 Title: xenial/linux: 4.4.0-170.199 -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: Incomplete 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 package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+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 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -proposed tracker
** Tags added: regression-testing-passed -- 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/1852241 Title: bionic/linux-gcp: 5.0.0-1026.27~18.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-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852241/+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 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Stalled -- testing FAILED - security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1853900 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/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+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 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Stalled -- testing FAILED - security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 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/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.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-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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+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 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
Bug 1853944 resolved with Colin's patch. ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released ** Tags added: regression-testing-passed -- 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/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+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 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
Bug 1853944 resolved with Colin's patch. ** Tags added: regression-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => 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/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.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-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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+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 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.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: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 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/1852241 Title: bionic/linux-gcp: 5.0.0-1026.27~18.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-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852241/+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 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -proposed tracker
Bug 1853944 resolved with Colin's patch. ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released -- 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/1852241 Title: bionic/linux-gcp: 5.0.0-1026.27~18.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-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852241/+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 1854432] 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 1854432 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/1854432 Title: Fix MST support on Ice Lake Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Some HDMI and DP doesn't count as external monitor on ICL MST. [Fix] Fix external port MST check on Ice Lake. [Test] DP and HDMI ports can only mirror display. After applying this patch bot DP and HDMI ports can drive its own external display. [Regression Potential] Low. This fix targets Gen 11 and Gen 12 Intel graphics, older systems are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854432/+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 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -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: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+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 1852277] Re: bionic/linux-oracle: 4.15.0-1030.33 -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: 1854027 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 19:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1852275 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/1852277 Title: bionic/linux-oracle: 4.15.0-1030.33 -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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1854027 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 19:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1852275 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852277/+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 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray) -- 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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+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 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 09:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852275 Title: xenial/linux-oracle: 4.15.0-1030.33~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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 09:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+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 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray) -- 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/1852275 Title: xenial/linux-oracle: 4.15.0-1030.33~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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 09:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+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 1854432] [NEW] Fix MST support on Ice Lake
Public bug reported: [Impact] Some HDMI and DP doesn't count as external monitor on ICL MST. [Fix] Fix external port MST check on Ice Lake. [Test] DP and HDMI ports can only mirror display. After applying this patch bot DP and HDMI ports can drive its own external display. [Regression Potential] Low. This fix targets Gen 11 and Gen 12 Intel graphics, older systems are unaffected. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1853415 somerville ** Tags added: oem-priority originate-from-1853415 somerville -- 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/1854432 Title: Fix MST support on Ice Lake Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] Some HDMI and DP doesn't count as external monitor on ICL MST. [Fix] Fix external port MST check on Ice Lake. [Test] DP and HDMI ports can only mirror display. After applying this patch bot DP and HDMI ports can drive its own external display. [Regression Potential] Low. This fix targets Gen 11 and Gen 12 Intel graphics, older systems are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854432/+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 1852273] Re: bionic/linux-kvm: 4.15.0-1051.51 -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: 1854027 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - 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/1852273 Title: bionic/linux-kvm: 4.15.0-1051.51 -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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1854027 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852273/+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 1852277] Re: bionic/linux-oracle: 4.15.0-1030.33 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray) -- 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/1852277 Title: bionic/linux-oracle: 4.15.0-1030.33 -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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1854027 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 19:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1852275 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852277/+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 1854427] Re: installation failed
the installation hang, so no log can be produced -- 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/1854427 Title: installation failed Status in linux package in Ubuntu: Incomplete Bug description: The installation for ubuntu 18.04 and 19.10 failed on laptop called dc pro as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990 for ubuntu 16.04.03 and 16.04.06 (should have same problem on 04 and 05) on 18.04 the problem is the same as 16.04.03+ the moving 5 dots will stop and system hang on 19.10 it will eject the disk and print something like nouveau problem /dev/sr0 read problem squashfs problem I think the problem occured before that since the 5 dots stop moving and cdrom stopped then both restart then cdrom rejected and print out above message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854427/+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 1852253] Re: disco/linux: 5.0.0-37.40 -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, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 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/1852253 Title: disco/linux: 5.0.0-37.40 -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: Fix Released 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, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+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 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -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: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: regression-testing: Ongoing -- testing in progress - 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852266 Title: bionic/linux-oem: 4.15.0-1065.75 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+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 1852273] Re: bionic/linux-kvm: 4.15.0-1051.51 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray) -- 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/1852273 Title: bionic/linux-kvm: 4.15.0-1051.51 -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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1854027 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852273/+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 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray) -- 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/1852266 Title: bionic/linux-oem: 4.15.0-1065.75 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+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 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray) -- 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/1852253 Title: disco/linux: 5.0.0-37.40 -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: Fix Released 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, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+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 1852248] Re: disco/linux-oracle: 5.0.0-1008.13 -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: 1852253 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 15. November 2019 15:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1852247 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/1852248 Title: disco/linux-oracle: 5.0.0-1008.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-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 kernel-stable-master-bug: 1852253 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 15. November 2019 15:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1852247 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852248/+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 1852248] Re: disco/linux-oracle: 5.0.0-1008.13 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1852248 Title: disco/linux-oracle: 5.0.0-1008.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-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 kernel-stable-master-bug: 1852253 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 15. November 2019 15:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1852247 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852248/+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 1854427] 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 1854427 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/1854427 Title: installation failed Status in linux package in Ubuntu: Incomplete Bug description: The installation for ubuntu 18.04 and 19.10 failed on laptop called dc pro as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990 for ubuntu 16.04.03 and 16.04.06 (should have same problem on 04 and 05) on 18.04 the problem is the same as 16.04.03+ the moving 5 dots will stop and system hang on 19.10 it will eject the disk and print something like nouveau problem /dev/sr0 read problem squashfs problem I think the problem occured before that since the 5 dots stop moving and cdrom stopped then both restart then cdrom rejected and print out above message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854427/+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 1852245] Re: disco/linux-kvm: 5.0.0-1023.25 -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: 1852253 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 19:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - 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/1852245 Title: disco/linux-kvm: 5.0.0-1023.25 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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 kernel-stable-master-bug: 1852253 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 19:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852245/+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 1854006] Re: eoan/linux-raspi2: 5.3.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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: 1852232 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 26. November 2019 16:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: eoan/linux-raspi2/pi-kernel: bug 1854005 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/1854006 Title: eoan/linux-raspi2: 5.3.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 26. November 2019 16:54 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: eoan/linux-raspi2/pi-kernel: bug 1854005 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854006/+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 1852245] Re: disco/linux-kvm: 5.0.0-1023.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray) -- 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/1852245 Title: disco/linux-kvm: 5.0.0-1023.25 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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 kernel-stable-master-bug: 1852253 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 19:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852245/+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 1852244] Re: disco/linux-gcp: 5.0.0-1026.27 -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: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 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/1852244 Title: disco/linux-gcp: 5.0.0-1026.27 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 kernel-stable-master-bug: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852244/+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 1854427] [NEW] installation failed
Public bug reported: The installation for ubuntu 18.04 and 19.10 failed on laptop called dc pro as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990 for ubuntu 16.04.03 and 16.04.06 (should have same problem on 04 and 05) on 18.04 the problem is the same as 16.04.03+ the moving 5 dots will stop and system hang on 19.10 it will eject the disk and print something like nouveau problem /dev/sr0 read problem squashfs problem I think the problem occured before that since the 5 dots stop moving and cdrom stopped then both restart then cdrom rejected and print out above message ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854427 Title: installation failed Status in linux package in Ubuntu: New Bug description: The installation for ubuntu 18.04 and 19.10 failed on laptop called dc pro as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990 for ubuntu 16.04.03 and 16.04.06 (should have same problem on 04 and 05) on 18.04 the problem is the same as 16.04.03+ the moving 5 dots will stop and system hang on 19.10 it will eject the disk and print something like nouveau problem /dev/sr0 read problem squashfs problem I think the problem occured before that since the 5 dots stop moving and cdrom stopped then both restart then cdrom rejected and print out above message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854427/+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 1852244] Re: disco/linux-gcp: 5.0.0-1026.27 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1852244 Title: disco/linux-gcp: 5.0.0-1026.27 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 kernel-stable-master-bug: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852244/+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 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1852241 Title: bionic/linux-gcp: 5.0.0-1026.27~18.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-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: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852241/+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 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.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: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 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/1852241 Title: bionic/linux-gcp: 5.0.0-1026.27~18.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-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: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852241/+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 1852236] Re: disco/linux-aws: 5.0.0-1022.25 -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: 1852253 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1852235 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/1852236 Title: disco/linux-aws: 5.0.0-1022.25 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 kernel-stable-master-bug: 1852253 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1852235 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852236/+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 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
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 doesn’t work, $ git bisect old Otherwise, $ git bisect new Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850099 Title: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error message stating "Error: out of memory Press any key to continue..." After pressing a key, nothing changed. I left the room and came back to see that there was a kernel panic. I'll attach picture as I couldn't copy/paste the console output. Description: Ubuntu 19.10 Release: 19.10 linux-image-5.3.0-19-generic I expect the kernel to load without a panic. The kernel panicked. After rebooting and selecting an older kernel, I was able to boot and load the old kernel without issue (5.0.0-32-generic) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lost 1947 F pulseaudio CurrentDesktop: XFCE Date: Mon Oct 28 00:52:26 2019 HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626 InstallationDate: Installed on 2016-06-17 (1227 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0WVDX2 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr: dmi.product.family: Precision dmi.product.name: Precision 5510 dmi.product.sku: 06E5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+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 1852236] Re: disco/linux-aws: 5.0.0-1022.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1852236 Title: disco/linux-aws: 5.0.0-1022.25 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 kernel-stable-master-bug: 1852253 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1852235 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852236/+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 1854177] Re: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2
Thanks, Kyle These 2 commits should be merged in the next Ubuntu-kernel release. Please try when it is avaiaible. -- 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/1854177 Title: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2 Status in linux package in Ubuntu: Confirmed Bug description: Present testing has focused on closing the laptop lid and reopening it. The laptop suspends as expected and resumes as expected (existing ssh sessions start working again) except that the display remains black and calls such as `xset -display :0 dpms force on` hang. The screen remains blank sSometimes for a few minutes, sometimes for many. In the example log it was 10 minutes and a few seconds before the display turned back on. One time trying to capture a log of the recovery I gave up after 70 minutes. While the display is black `/var/log/Xorg.0.log` repeats the following lines once per second. [ 119.384] (WW) modeset(0): hotplug event: connector 86's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... [ 119.386] (II) modeset(0): EDID vendor "SDC", prod id 16705 [ 119.386] (II) modeset(0): Printing DDC gathered Modelines: [ 119.386] (II) modeset(0): Modeline "3840x2160"x0.0 545.12 3840 3888 3920 4160 2160 2164 2168 2184 +hsync -vsync (131.0 kHz eP) This stops when the display turns on and no other messages are logged. The journalctl log has a much longer repeated sequence of messages. I haven't confirmed exact matching of the whole repeated block but here's a snippet reporting a failure. Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Max Voltage Swing reached Nov 27 00:02:32 p1 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:86:eDP-1] Link Training failed at link rate = 54, lane count = 4 When the display turned back on I instead get the following success message. Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] clock recovery OK Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS3 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_start_link_train [i915]] Channel EQ done. DP Training successful I tested the mainline .deb package for 5.3.13 and it did not exhibit this issue. When I open the laptop lid after suspending by closing it the cursor reliably displays within about 1 second and the lock screen is shown within about another second. I further checked versions and the last mainline .deb to exhibit the issue is 5.3.11. 5.3.12 works well. Looking at the changelog for 5.3.12 showed the following two
[Kernel-packages] [Bug 1845869] Re: test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 ARM64
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845869 Title: test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 ARM64 Status in linux package in Ubuntu: Expired Bug description: Issue found on a Moonshot node with B-hwe-edge 5.3 kernel, test failed with: #13/p valid read map access into a read-only array 2 FAIL retval 65507 != -29 (run 1/1) verification time 41 usec stack depth 8 processed 14 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 This is the only test failing in this test suite: Summary: 1547 PASSED, 0 SKIPPED, 1 FAILED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845869/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Tags added: originate-from-1854420 -- 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/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497457] ---[ end trace 87c55fce1375aae8 ]--- ProblemType: Bug DistroRelease: Ub
[Kernel-packages] [Bug 1852233] Re: disco/linux-raspi2: 5.0.0-1023.24 -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: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED - 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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852233 Title: disco/linux-raspi2: 5.0.0-1023.24 -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: Incomplete 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 kernel-stable-master-bug: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852233/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
find -name *.html | while read manifest; do grep oem-wifi-intel- iwlwifi-.*-dkms $manifest -H; done | tee ~/oem-wifi-intel-iwlwifi- dkms.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-253
[Kernel-packages] [Bug 1852233] Re: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1852233 Title: disco/linux-raspi2: 5.0.0-1023.24 -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: Incomplete 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 kernel-stable-master-bug: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852233/+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 1854413] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854413 Title: Backlight adjustments shows OSD but does not change anything on Samsung OLED panel Status in linux package in Ubuntu: Confirmed Bug description: When running Ubuntu with linux-image-5.3.0-23-generic, mainline 5.3.13, or latest 5.4+ my Lenovo ThinkPad P1 Gen 2 with a Samsung OLED panel is unable to change the backlight brightness. The buttons trigger the on-screen display and move the bar but the actual display brightness does not change. With the kernel option i915.enable_dpcd_backlight=1 it does make the backlight change but erratically. For example moving through the range you get stuff like off, medium bright, dim, bright, medium, off. This does work in Ubuntu linux-image-4.15.0-1059-oem. It seems the following commits in particular make the difference. UBUNTU: SAUCE: i915: intel_dp_aux_backlight: Fix max backlight calculations https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/eoan/commit/?h=oem&id=ff39163c455f31005e2709a2006a7605b3d8a05f UBUNTU: SAUCE: drm/i915: customize DPCD brightness control for specific panel https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/eoan/commit/?h=oem&id=cf7286b44a6e27967f5ed134c4492dd17bde118a It has been explained to me that these OEM changes are unlikely to be directly ported into -generic images but it seems relevant to document the issue. I ported the above commits to the latest linux mainline kernel and am running that (other than while reporting this issue). This was in part because >= 5.3.12 fixes another issue with this hardware where the screen remains black after a resume (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177). I have filed https://bugzilla.kernel.org/show_bug.cgi?id=205699. https://github.com/altendky/linux/commit/395eb4b85f6a0f85061c0598247727de0d9316f6 https://github.com/altendky/linux/commit/c2dc38e6aadf3d979bea83e382a1b119574df7af Built with: git clean -fdx && cp /boot/config-5.3.0-23-generic .config && yes '' | make oldconfig && make clean && make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-altendky-backlight Note that the use of DEVICE_ID_ANY is likely bad and the correct ID for this panel should be identified. I wanted to first confirm it worked before bothering to figure out which ID was needed there and how to get it. I have naively ported these patches. While I have done embedded C for years and some hardware design... I am not familiar with Linux kernel development nor any details of controlling this hardware. 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 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: altendky 1381 F pulseaudio CurrentDesktop: KDE Date: Thu Nov 28 21:24:12 2019 InstallationDate: Installed on 2019-11-26 (2 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/lvm_group-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: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854413/+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 1845716] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne
*** This bug is a duplicate of bug 1827100 *** https://bugs.launchpad.net/bugs/1827100 A fix has been released for eoan under bug #1827100, and a fix for bionic is pending. ** This bug has been marked a duplicate of bug 1827100 bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1845716 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: Confirmed Bug description: - ProblemType: Package DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 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 Date: Fri Sep 27 23:20:40 2019 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2017-10-07 (720 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1845716/+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 1835197] Re: bcmwl dkms won't build on 5.1.x kernels (get_ds() -> KERNEL_DS)
*** This bug is a duplicate of bug 1827100 *** https://bugs.launchpad.net/bugs/1827100 A fix has been released to bionic-proposed under bug #1827100. ** This bug has been marked a duplicate of bug 1827100 bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1835197 Title: bcmwl dkms won't build on 5.1.x kernels (get_ds() -> KERNEL_DS) Status in bcmwl package in Ubuntu: Confirmed Bug description: bcmwl dkms won't build on 5.1.x kernels The problem is in use of kernel's get_ds() macro which was removed upstream: #define get_ds()(KERNEL_DS) Instead KERNEL_DS should be used directly. See this patch: https://nest.parrotsec.org/h0tw4t3r/broadcom-fork-5.1.0-kernel/commit/9661e61c6e42e33fb591976ec15461ad45b71104 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1835197/+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 1827100] Re: bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1
Tested bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5~18.04.1. The issue is resolved for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1827100 Title: bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Bionic: Fix Committed Status in bcmwl source package in Eoan: Fix Released Bug description: [Impact] The DKMS package won't work with new kernels on bionic. [Test case] Install and load the modules. [Regression potential] This might break the functioning of the module. --- Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/b/bcmwl/20190429_132741_e6057@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/b/bcmwl/20190429_124054_e6057@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1827100/+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 1854413] [NEW] Backlight adjustments shows OSD but does not change anything on Samsung OLED panel
Public bug reported: When running Ubuntu with linux-image-5.3.0-23-generic, mainline 5.3.13, or latest 5.4+ my Lenovo ThinkPad P1 Gen 2 with a Samsung OLED panel is unable to change the backlight brightness. The buttons trigger the on- screen display and move the bar but the actual display brightness does not change. With the kernel option i915.enable_dpcd_backlight=1 it does make the backlight change but erratically. For example moving through the range you get stuff like off, medium bright, dim, bright, medium, off. This does work in Ubuntu linux-image-4.15.0-1059-oem. It seems the following commits in particular make the difference. UBUNTU: SAUCE: i915: intel_dp_aux_backlight: Fix max backlight calculations https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/eoan/commit/?h=oem&id=ff39163c455f31005e2709a2006a7605b3d8a05f UBUNTU: SAUCE: drm/i915: customize DPCD brightness control for specific panel https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/eoan/commit/?h=oem&id=cf7286b44a6e27967f5ed134c4492dd17bde118a It has been explained to me that these OEM changes are unlikely to be directly ported into -generic images but it seems relevant to document the issue. I ported the above commits to the latest linux mainline kernel and am running that (other than while reporting this issue). This was in part because >= 5.3.12 fixes another issue with this hardware where the screen remains black after a resume (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177). I have filed https://bugzilla.kernel.org/show_bug.cgi?id=205699. https://github.com/altendky/linux/commit/395eb4b85f6a0f85061c0598247727de0d9316f6 https://github.com/altendky/linux/commit/c2dc38e6aadf3d979bea83e382a1b119574df7af Built with: git clean -fdx && cp /boot/config-5.3.0-23-generic .config && yes '' | make oldconfig && make clean && make -j `getconf _NPROCESSORS_ONLN` deb- pkg LOCALVERSION=-altendky-backlight Note that the use of DEVICE_ID_ANY is likely bad and the correct ID for this panel should be identified. I wanted to first confirm it worked before bothering to figure out which ID was needed there and how to get it. I have naively ported these patches. While I have done embedded C for years and some hardware design... I am not familiar with Linux kernel development nor any details of controlling this hardware. 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 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: altendky 1381 F pulseaudio CurrentDesktop: KDE Date: Thu Nov 28 21:24:12 2019 InstallationDate: Installed on 2019-11-26 (2 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/lvm_group-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: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854413 Title: Backlight adjustments shows OSD but does not change anything on Samsung OLED panel Status in linux package in Ubuntu: New Bug description: When running Ubuntu with linux-image-5.3.0-23-generic, mainline 5.3.13, or latest 5.4+ my Lenovo ThinkPad P1 Gen 2 with a Samsung OLED panel is unable to change the backlight brightness. The buttons trigger the on-screen display and move the bar but the actual display brightness does not change. With the kernel option i915.enable_dpcd_backlight=1 it does make the backlight change but erratically. For example moving through the range you get stuff like off, medium bright, dim, bright, medium, off. This does work in Ubuntu lin
[Kernel-packages] [Bug 1854027] Re: bionic/linux: 4.15.0-72.81 -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, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 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/1854027 Title: bionic/linux: 4.15.0-72.81 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854027/+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 1852232] Re: eoan/linux: 5.3.0-24.26 -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, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1854020 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1854006 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 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/1852232 Title: eoan/linux: 5.3.0-24.26 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1854020 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1854006 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+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 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Steve Beattie (sbeattie) => Ubuntu Security Team (ubuntu-security) ** Changed in: kernel-sru-workflow/security-signoff Assignee: Ubuntu Security Team (ubuntu-security) => Canonical Security Team (canonical-security) -- 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/1852232 Title: eoan/linux: 5.3.0-24.26 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1854020 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1854006 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+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 1852230] Re: eoan/linux-oracle: 5.3.0-1007.8 -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: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1852229 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/1852230 Title: eoan/linux-oracle: 5.3.0-1007.8 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852230/+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 1852228] Re: eoan/linux-kvm: 5.3.0-1008.9 -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: 1852232 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 15. November 2019 13:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - 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/1852228 Title: eoan/linux-kvm: 5.3.0-1008.9 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 15. November 2019 13:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852228/+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 1852230] Re: eoan/linux-oracle: 5.3.0-1007.8 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1852230 Title: eoan/linux-oracle: 5.3.0-1007.8 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852230/+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 1852228] Re: eoan/linux-kvm: 5.3.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1852228 Title: eoan/linux-kvm: 5.3.0-1008.9 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 15. November 2019 13:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852228/+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 1852227] Re: eoan/linux-gcp: 5.3.0-1009.10 -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: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1852226 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/1852227 Title: eoan/linux-gcp: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1852226 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852227/+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 1852227] Re: eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1852227 Title: eoan/linux-gcp: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1852226 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852227/+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 1853142] Re: CVE-2019-18660: patches for Ubuntu
The embargo has expired so I'm making this public now. ** Description changed: Hi, Recently you would have been notified about CVE-2019-18660 via email to the linux-distros private mailing list. In short, it is a bug in the Spectre v2 class affecting powerpc. We have developed some backports for supported Ubuntu kernels, and tested them in our lab. I will attach the patches shortly. Most of them should end up being identical to the versions in linux-stable, but the ones for Bionic are slightly different due to it using a 4.15 kernel. Please get in touch with me or Michael Ellerman (powerpc maintainer) if you have any questions or if we can be of any assistance. - If I understand the SRU cycles correctly, we've missed the current one - due for release on 2 December, so the earliest these patches could land - in is the kernel nominally slated to be released ~23 December. Are you - planning to still release a kernel then, or are your cycles going to - change over the end of year period? - - (If it helps, we've got some automation set up so we're able to do the - regression testing of -proposed kernels with these patches quickly.) Kind regards, Daniel ** Information type changed from Private Security to Public Security -- 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/1853142 Title: CVE-2019-18660: patches for Ubuntu Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Triaged Status in linux source package in Eoan: Triaged Status in linux source package in Focal: Triaged Bug description: Hi, Recently you would have been notified about CVE-2019-18660 via email to the linux-distros private mailing list. In short, it is a bug in the Spectre v2 class affecting powerpc. We have developed some backports for supported Ubuntu kernels, and tested them in our lab. I will attach the patches shortly. Most of them should end up being identical to the versions in linux-stable, but the ones for Bionic are slightly different due to it using a 4.15 kernel. Please get in touch with me or Michael Ellerman (powerpc maintainer) if you have any questions or if we can be of any assistance. Kind regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853142/+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 1854401] Re: headphone has noise as not mute on dell machines with alc236/256
** Description changed: - tracking purpose + [Impact] + There is noise in the headphone on some dell machines with the + codec alc256 or alc236 + + [Fix] + Realtek provide a patch to disable PCBEEP_IN to heapdhone. + + [Test Case] + tested the kernel with this patch, the noise disappeared. + + [Regression Risk] + Low, Realtek provided the patch, and it is limited to apply + to alc236 and 256, and just disable the PCBEEP_IN to headphone.. -- 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/1854401 Title: headphone has noise as not mute on dell machines with alc236/256 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] There is noise in the headphone on some dell machines with the codec alc256 or alc236 [Fix] Realtek provide a patch to disable PCBEEP_IN to heapdhone. [Test Case] tested the kernel with this patch, the noise disappeared. [Regression Risk] Low, Realtek provided the patch, and it is limited to apply to alc236 and 256, and just disable the PCBEEP_IN to headphone.. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854401/+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 1854401] 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 1854401 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/1854401 Title: headphone has noise as not mute on dell machines with alc236/256 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: tracking purpose To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854401/+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 1017746] Re: /sys/module/pcie_aspm/parameters/policy not settable
** Changed in: debian Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1017746 Title: /sys/module/pcie_aspm/parameters/policy not settable Status in linux package in Ubuntu: Incomplete Status in Debian: Fix Released Bug description: From: http://ubuntuforums.org/showthread.php?t=2010191 The parameters in /sys/module/pcie_aspm/parameters/policy are not settable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1017746/+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 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1852224 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/1852225 Title: eoan/linux-azure: 5.3.0-1008.9 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852225/+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 1854401] [NEW] headphone has noise as not mute on dell machines with alc236/256
Public bug reported: tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1853952 somerville ** Tags added: originate-from-1853952 somerville -- 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/1854401 Title: headphone has noise as not mute on dell machines with alc236/256 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: tracking purpose To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854401/+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 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1852225 Title: eoan/linux-azure: 5.3.0-1008.9 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852225/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
** Attachment added: "headphones" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308568/+files/headphones -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
The only other Bluetooth headphones I've had access to recently were a pair of Bose QC35 (1st generation). They showed up in the list of visible BT devices, but my laptop couldn't connect to them at all, despite numerous attempts. As a result, I bought the Sonys and got rid of the Bose. If you take a look at bug 1724919, you'll see that other people have the same problem with other models of headphones. Attached is a copy of /var/log/syslog since last boot, with minor cleaning. Note that just after booting I wanted to use the headphones for real, so I manually ran the attached 'headphones' script to disconnect the headphones, reconnect them, and force A2DP mode. Then at 18:09:17, I deliberately recreated the bug by connecting the headphones, and unsuccessfully trying to set A2DP in the sound settings. ** Attachment added: "syslog_cleaned.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308567/+files/syslog_cleaned.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
That's not /really/ helpful anyway. You'd have installed an extra application, for a wholly unrelated issue, and still have to set the profile to A2DP yourself. Alistair, there are messages in your logs that seem to point to a firmware issue: Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) Furthermore, I see some slightly unusual messages that point to an issue with the firmware (usually) as well: Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 It's possible the hardware gets confused by losing the connection that was initially there. I realize this might not be /so/ helpful, but have you also tried with another model of bluetooth headphones, assuming you have something available? Please see if you can attach the full contents of /var/log/syslog after reproducing the issue (with a different model or with the usual Sonys); once you've made sure that it doesn't contain sensitive data. I'd need to know when you started each attempt so we can see exactly how the system reacts to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 co
[Kernel-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
How do I run blueman after installing it? $ blueman Command 'blueman' not found, did you mean: command 'bluemon' from deb bluemon (1.4-7) Try: sudo apt install -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
Sounds similar to https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197 Can you install blueman, connect to the headset, right click on the headset in blueman, go to audio profile, select off, disconnect headset then reconnect and can you set the audio profile to A2DP then -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
Ran fsck from a bootable linux, no issues (this is a LUKS encrypted volume): root@kali:~# fsck /dev/mapper/xubuntu--vg-root fsck from util-linux 2.34 e2fsck 1.45.4 (23-Sep-2019) /dev/mapper/xubuntu--vg-root: clean, 1139039/30162944 files, 77548819/120621056 blocks root@kali:~# echo $? 0 -- 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/1850099 Title: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error message stating "Error: out of memory Press any key to continue..." After pressing a key, nothing changed. I left the room and came back to see that there was a kernel panic. I'll attach picture as I couldn't copy/paste the console output. Description: Ubuntu 19.10 Release: 19.10 linux-image-5.3.0-19-generic I expect the kernel to load without a panic. The kernel panicked. After rebooting and selecting an older kernel, I was able to boot and load the old kernel without issue (5.0.0-32-generic) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lost 1947 F pulseaudio CurrentDesktop: XFCE Date: Mon Oct 28 00:52:26 2019 HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626 InstallationDate: Installed on 2016-06-17 (1227 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0WVDX2 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr: dmi.product.family: Precision dmi.product.name: Precision 5510 dmi.product.sku: 06E5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+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 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
The log only shows the SKIPs. I managed to reproduce one FAIL that I have seen as well: TEST: ipv6: list and flush cached exceptions[FAIL] can't list cached exceptions This one ended up being caused by the script itself and a difference in behavior between different versions of iproute2. Recent iproute2, when introducing json output support for ip route, ended up removing the newline for IPv6, while keeping it for IPv4. The script author assumed the newest behavior, but also accounted for the two lines per entry for IPv4. iproute2, however, has a -oneline option that could just have been used in this case and that would fix the whole problem. Using it fix the FAIL, while we still have the SKIPs, which would require a new version of iproute2, at least on -backports. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: In Progress Status in iproute2 source package in Bionic: New Status in linux-hwe-edge source package in Bionic: In Progress Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftests/net/pmtu.sh [Regression potential] No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] Upgrading iproute2 to 5.2 fixes this. To
[Kernel-packages] [Bug 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
http://patchwork.ozlabs.org/patch/1202263/ Upstream change submitted to fix this. ** Changed in: linux-hwe-edge (Ubuntu) Status: Invalid => In Progress ** Changed in: linux-hwe-edge (Ubuntu Bionic) Status: Invalid => In Progress ** Description changed: + [Impact] + selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. + + [Test case] + Run the script directly and verify there are no failures. + sudo ./tools/testing/selftests/net/pmtu.sh + + [Regression potential] + No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. + + + + 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] - Upgrading iproute2 to 5.2 fixes this. ** Changed in: linux-hwe-edge (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-hwe-edge (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: In Progress Status in iproute2 source package in Bionic: New Status in linux-hwe-edge source package in Bionic: In Progress Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftest
[Kernel-packages] [Bug 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852266 Title: bionic/linux-oem: 4.15.0-1065.75 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+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 1854392] [NEW] Bluetooth headphones won't use A2DP on reconnect
Public bug reported: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: New Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb:
[Kernel-packages] [Bug 1852871] Re: Connect to Android Tablet does not work in 19.10
I am a Linux newbie. How? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852871 Title: Connect to Android Tablet does not work in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: With 19.04 I just plugged my Android Tablet into a USB slot and could move files between my two devices. With 19.10 it usually does not mount my device. When it says it has, then all the directories are claimed to be empty. The code for 19.10 obviously broke something. 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 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2400 F pulseaudio /dev/snd/controlC0: robert 2400 F pulseaudio CurrentDesktop: MATE Date: Sat Nov 16 16:12:16 2019 InstallationDate: Installed on 2018-12-16 (335 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-27 (20 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852871/+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 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
@il_santo: you should probably submit a separate bug report for this issue as it is likely unrelated to the module signing issue that was addressed here. -- 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/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+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 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
When I try to shutdown my PC with kernel 5.3.0-23 i get: [54592.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54620.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54648.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54676.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54704.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54732.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54746.232003] INFO: rcu_sched self-detected stall on CPU This goes on forever and my PC never shuts down. -- 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/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+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 1847454] Re: [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847454 Title: [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2 Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux-oem-osp1 source package in Disco: Confirmed Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: Confirmed Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Confirmed Bug description: Description Cometlake -S 6+2 is using a different CPU Model number: DEC 165, HEX: A5 We need the intel_rapl patch to support CML-S 6+2 Target Kernel: 5.6 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1847454/+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 1849419] Re: kernel panic after upgrading from 19.04 to 19.10
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849419 Title: kernel panic after upgrading from 19.04 to 19.10 Status in linux package in Ubuntu: Invalid Bug description: Upgrading from 19.04 to 19.10 on two of my pc does the same thing. the upgrade is ok , boot ok, but after some time, and never the same, every app is crashing unable to reboot. i manage a reset with the pc button, but after that kernel panic and no boot. every kernel listed is having a panic. only chance after that is clonezilla and turn back to previous image 19.04 that i saved. unable to enter recovery menu. grub works bios secure boot disabled. description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 13GiB *-cpu product: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 3715MHz capacity: 3900MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 09 width: 32 bits clock: 33MHz configuration: driver=ivb_uncore resources: irq:0 *-pci:0 description: PCI bridge product: Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 09 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:f7e0-f7ef ioport:e000(size=268435456) *-display description: VGA compatible controller product: Turks XT [Radeon HD 6670/7670] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:27 memory:e000-efff memory:f7e2-f7e3 ioport:e000(size=256) memory:c-d *-multimedia description: Audio device product: Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:30 memory:f7e4-f7e43fff *-usb:0 description: USB controller product: 7 Series/C210 Series Chipset Family USB xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 04 width: 64 bits clock: 33MHz capabilities: xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:25 memory:f7f0-f7f0 *-communication description: Communication controller product: 7 Series/C216 Chipset Family MEI Controller #1 vendor: Intel Corporation physical id: 16 bus info: pci@:00:16.0 version: 04 width: 64 bits clock: 33MHz capabilities: bus_master cap_list
[Kernel-packages] [Bug 1852575] Re: Kernels 5.022 or higher booting issues
*** This bug is a duplicate of bug 1852581 *** https://bugs.launchpad.net/bugs/1852581 Thanks a lot, Martin. That means you were probably affected by LP: #1852581, which affected the hwe-edge version of the 5.3 kernel and was fixed during an update. That explains how you got an update for that kernel and it fixed your problem. Thanks a lot for helping us finding out what was the case for your issue. I am going to mark this bug as a duplicate of referred bug that had already the fix released. Regards. Cascardo. ** This bug has been marked a duplicate of bug 1852581 hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO -- 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/1852575 Title: Kernels 5.022 or higher booting issues Status in linux package in Ubuntu: Incomplete Bug description: I tried both kernels (5.022 and 5.023) but my new laptop (Asus zenbook 14) cannot boot and had to return to kernel 5.019. The error it gives was something of the following: "boot - ALERT! ...uuid... does not exit! Dropping to shell." I am using Linux Mint as a distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852575/+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 1854006] Re: eoan/linux-raspi2: 5.3.0-1014.16 -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: 1852232 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 26. November 2019 16:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: eoan/linux-raspi2/pi-kernel: bug 1854005 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/1854006 Title: eoan/linux-raspi2: 5.3.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: In Progress 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: 1852232 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 26. November 2019 16:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: eoan/linux-raspi2/pi-kernel: bug 1854005 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854006/+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 1853180] Re: update ENA driver for DIMLIB dynamic interrupt moderation
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1853180
Title:
update ENA driver for DIMLIB dynamic interrupt moderation
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:
Update the Amazon ENA driver to latest mainline version with dynamic
interrupt moderation supplied by DIMLIB, plus a couple of pending
fixes from the netdev mailing list.
Note: For {Xenial,Bionic,Disco}, this needs bug 1852637 ("backport
DIMLIB (lib/dim/) to pre-5.2 kernels") as a prerequisite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853180/+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 1849419] Re: kernel panic after upgrading from 19.04 to 19.10
Solved dirty ram was hardware prob -- 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/1849419 Title: kernel panic after upgrading from 19.04 to 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from 19.04 to 19.10 on two of my pc does the same thing. the upgrade is ok , boot ok, but after some time, and never the same, every app is crashing unable to reboot. i manage a reset with the pc button, but after that kernel panic and no boot. every kernel listed is having a panic. only chance after that is clonezilla and turn back to previous image 19.04 that i saved. unable to enter recovery menu. grub works bios secure boot disabled. description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 13GiB *-cpu product: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 3715MHz capacity: 3900MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 09 width: 32 bits clock: 33MHz configuration: driver=ivb_uncore resources: irq:0 *-pci:0 description: PCI bridge product: Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 09 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:f7e0-f7ef ioport:e000(size=268435456) *-display description: VGA compatible controller product: Turks XT [Radeon HD 6670/7670] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:27 memory:e000-efff memory:f7e2-f7e3 ioport:e000(size=256) memory:c-d *-multimedia description: Audio device product: Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:30 memory:f7e4-f7e43fff *-usb:0 description: USB controller product: 7 Series/C210 Series Chipset Family USB xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 04 width: 64 bits clock: 33MHz capabilities: xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:25 memory:f7f0-f7f0 *-communication description: Communication controller product: 7 Series/C216 Chipset Family MEI Controller #1 vendor: Intel Corporation physical id: 16 bus info: pci@:00:16.0 version: 04 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=me
[Kernel-packages] [Bug 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
already wrote you, i did and it works -- 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/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: System doesn't boot anymore with new kernel update linux- image-5.3.0-22-generic. Here is the screenshot where the boot process stops: https://photos.app.goo.gl/6b7D2SsGBpgKWLd1A I installed old kernel packages out of local deb cache (linux- image-5.3.0-19-generic), initramfs regenerated, same boot options and was able to boot fine. I assume something went wrong with new security patches, ucode for intel CPU seems not to be an issue, because old kernel booted with newly generated initrd image. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrej 3321 F pulseaudio /dev/snd/controlC0: andrej 3321 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 14:37:01 2019 InstallationDate: Installed on 2019-11-04 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q500E2GE ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\initrd.img-5.3.0-19-generic BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET35W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q500E2GE 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:bvrR0ZET35W(1.13):bd10/11/2019:svnLENOVO:pn20Q500E2GE:pvrThinkPadL490:rvnLENOVO:rn20Q500E2GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q500E2GE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+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 1852575] Re: Kernels 5.022 or higher booting issues
Dear Sir / Madam, Many thanks for the prompt reply. The output of the command: dpkg -s linux-image-5.3.0-23-generic | grep Version, in my terminal emulator is: Version: 5.3.0-23.25~18.04.2 Kind regards, Martin On Thu, 28 Nov 2019 at 16:35, Thadeu Lima de Souza Cascardo < 1852...@bugs.launchpad.net> wrote: > So I suspect you are using a hwe-edge version of the kernel that had > another problem related to module signing. > > What is the output of the following command? > > dpkg -s linux-image-5.3.0-23-generic | grep Version > > Thanks. > Cascardo. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1852575 > > Title: > Kernels 5.022 or higher booting issues > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I tried both kernels (5.022 and 5.023) but my new laptop (Asus zenbook > 14) cannot boot and had to return to kernel 5.019. The error it gives > was something of the following: "boot - ALERT! ...uuid... does not > exit! Dropping to shell." > > I am using Linux Mint as a distro. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852575/+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/1852575 Title: Kernels 5.022 or higher booting issues Status in linux package in Ubuntu: Incomplete Bug description: I tried both kernels (5.022 and 5.023) but my new laptop (Asus zenbook 14) cannot boot and had to return to kernel 5.019. The error it gives was something of the following: "boot - ALERT! ...uuid... does not exit! Dropping to shell." I am using Linux Mint as a distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852575/+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 1853791] Re: External microphone can't work on some dell machines with the codec alc256 or alc236
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Critical => Medium -- 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/1853791 Title: External microphone can't work on some dell machines with the codec alc256 or alc236 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: [Impact] The external microphone can't work on some dell machines with the codec alc256 or alc236 [Fix] Need to apply the ALC255_FIXUP_DELL1_MIC_NO_PRESENCE, instead of adding a new pintbl in the quirk table, we use fallback table this time. [Test Case] tested the kernel with these patches, the external mic worked well. [Regression Risk] Low, just make the quirk applying more generic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853791/+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 1852575] Re: Kernels 5.022 or higher booting issues
So I suspect you are using a hwe-edge version of the kernel that had another problem related to module signing. What is the output of the following command? dpkg -s linux-image-5.3.0-23-generic | grep Version Thanks. Cascardo. -- 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/1852575 Title: Kernels 5.022 or higher booting issues Status in linux package in Ubuntu: Incomplete Bug description: I tried both kernels (5.022 and 5.023) but my new laptop (Asus zenbook 14) cannot boot and had to return to kernel 5.019. The error it gives was something of the following: "boot - ALERT! ...uuid... does not exit! Dropping to shell." I am using Linux Mint as a distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852575/+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 1853050] Re: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)
Can you please test this kernel: https://people.canonical.com/~khfeng/rtw88-backport/ -- 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/1853050 Title: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci) Status in linux package in Ubuntu: Confirmed Bug description: Wifi just fails to connect to an access point after upgrading from Ubuntu 19.04 to 19.10. Some outputs: uname -a Linux mothership 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci -nnk | grep 0280 -A3 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950] Kernel driver in use: rtw_pci Kernel modules: rtwpci The typical failure looks like this in journalctl: Nov 18 23:04:13 mothership kernel: wlp3s0: send auth to d4:60:e3:15:4d:71 (try 3/3) Nov 18 23:04:13 mothership kernel: [ cut here ] Nov 18 23:04:13 mothership kernel: purge skb(s) not reported by firmware Nov 18 23:04:13 mothership kernel: WARNING: CPU: 5 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 23:04:13 mothership kernel: Modules linked in: nf_conntrack_netlink xt_owner xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype bpfilter aufs overlay binfmt_misc nvidia_uvm(O Nov 18 23:04:13 mothership kernel: spi_pxa2xx_platform videobuf2_memops asus_wmi videobuf2_v4l2 i915 mxm_wmi wmi_bmof sparse_keymap serio_raw videobuf2_common cfg80211 dw_dmac soundcore dw_dmac_core videodev input_leds drm_kms_helper joydev ipmi_devintf libarc4 mc ipmi_ Nov 18 23:04:13 mothership kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: P W OE 5.3.0-23-generic #25-Ubuntu Nov 18 23:04:13 mothership kernel: Hardware name: ASUSTeK COMPUTER INC. X705UDR/X705UDR, BIOS X705UDR.300 08/29/2017 Nov 18 23:04:13 mothership kernel: RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 23:04:13 mothership kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 cd b3 c0 e8 f6 fa 7b f6 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 3f 1c f7 48 8d 7b e0 49 89 c4 e8 Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b4020ce48 EFLAGS: 00010286 Nov 18 23:04:13 mothership kernel: RAX: RBX: 913317bed848 RCX: 0006 Nov 18 23:04:13 mothership kernel: RDX: 0007 RSI: 0082 RDI: 91331eb57440 Nov 18 23:04:13 mothership kernel: RBP: a25b4020ce60 R08: 1754 R09: 0004 Nov 18 23:04:13 mothership kernel: R10: R11: 0001 R12: 91331eb5b600 Nov 18 23:04:13 mothership kernel: R13: 913317bed848 R14: c0adb7d0 R15: 913317bed848 Nov 18 23:04:13 mothership kernel: FS: () GS:91331eb4() knlGS: Nov 18 23:04:13 mothership kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 18 23:04:13 mothership kernel: CR2: 7fb4eee0b000 CR3: 0003818bc005 CR4: 003606e0 Nov 18 23:04:13 mothership kernel: Call Trace: Nov 18 23:04:13 mothership kernel: Nov 18 23:04:13 mothership kernel: call_timer_fn+0x32/0x130 Nov 18 23:04:13 mothership kernel: __run_timers.part.0+0x177/0x270 Nov 18 23:04:13 mothership kernel: ? enqueue_hrtimer+0x3d/0x90 Nov 18 23:04:13 mothership kernel: ? recalibrate_cpu_khz+0x10/0x10 Nov 18 23:04:13 mothership kernel: ? ktime_get+0x42/0xa0 Nov 18 23:04:13 mothership kernel: run_timer_softirq+0x2a/0x50 Nov 18 23:04:13 mothership kernel: __do_softirq+0xe1/0x2d6 Nov 18 23:04:13 mothership kernel: ? hrtimer_interrupt+0x13b/0x220 Nov 18 23:04:13 mothership kernel: irq_exit+0xae/0xb0 Nov 18 23:04:13 mothership kernel: smp_apic_timer_interrupt+0x7b/0x140 Nov 18 23:04:13 mothership kernel: apic_timer_interrupt+0xf/0x20 Nov 18 23:04:13 mothership kernel: Nov 18 23:04:13 mothership kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x420 Nov 18 23:04:13 mothership kernel: Code: ff e8 5f 73 83 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 ce 89 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18 Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b400f3e38 EFLAGS: 0246 ORIG_RAX: ff13 Nov 18 23:04:13 mothership kernel: RAX: 91331eb6a740 RBX: b895a740 RCX: 001f Nov 18 23:04:13 mothership kernel: RDX: RSI: 4041ceb5 RDI: Nov 18 23:04:13 mothership kernel: RBP: a25b400f3e78 R08: 01076596b017 R09: 1d6b Nov
