[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
** Tags added: hwe-networking-wifi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Confirmed
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5310 -
[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
Hi Jim, This is a conflict between the (un)signed kernel packages; but it's easy to solve: Please remove the linux-image-5.4.0-47-generic package and try installing again; e.g., $ sudo apt purge linux-image-5.4.0-47-generic # confirm to remove the running kernel if asked. $ sudo dpkg -i *.deb # from alex hung cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Confirmed Bug description: Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663] acpi_ec_space_handler+0xd4/0x280 Sep 20 11:35:33 laxmi kernel: [232492.303666] acpi_ev_address_space_dispatch+0x2f7/0x39f Sep 20
Re: [Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
Hi Maricio, I did as you suggested, but cannot boot, error:/boot/vmlinuz-5.4.0-47-generic has invalid signature loading initial ramdisk error: you need to load the kernel first --Jim On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote: > Hi Jim, > > This is a conflict between the (un)signed kernel packages; but it's easy > to solve: > > Please remove the linux-image-5.4.0-47-generic package and try > installing again; e.g., > > $ sudo apt purge linux-image-5.4.0-47-generic # confirm to remove the running > kernel if asked. > $ sudo dpkg -i *.deb # from alex hung > > cheers, > Mauricio > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657]
Re: [Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
thanks, I fixed that and will start testing On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote: > It looks like you have secure boot enabled. > Unfortunately test kernels are unsigned and thus require it to be disabled in > your BIOS/EFI menu. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] >
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
I would be happy to help with this tool but it is too complicated for me... We have to compile the software. If an executable would exist, it will be more simple and I will try to help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896582] Re: Enable i915 panel self refresh feature
is this for 2020.09.21 or the next cycle after that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1896582 Title: Enable i915 panel self refresh feature Status in linux package in Ubuntu: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] PSR feature has been disabled by default because of below bug, "Dell XPS 13 (7390) Display Flickering - 19.10" https://bugs.launchpad.net/bugs/1849947 But this feature is important to pass the new energy start standard, so re-enable it and set default value to -1 "use per-chip default" [Fix] Revert the below commit to enable it again ecc718f31c90 UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms [Test] Verified on one Dell platform which panel supports PSR [Regression Potential] High, we plan to verify all platforms that shipped with 5.6 OEM kernel to make sure there is no flickering issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896582] Re: Enable i915 panel self refresh feature
and if this is going to be enabled in oem-5.6, needs to happen in groovy kernel as well ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1896582 Title: Enable i915 panel self refresh feature Status in linux package in Ubuntu: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] PSR feature has been disabled by default because of below bug, "Dell XPS 13 (7390) Display Flickering - 19.10" https://bugs.launchpad.net/bugs/1849947 But this feature is important to pass the new energy start standard, so re-enable it and set default value to -1 "use per-chip default" [Fix] Revert the below commit to enable it again ecc718f31c90 UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms [Test] Verified on one Dell platform which panel supports PSR [Regression Potential] High, we plan to verify all platforms that shipped with 5.6 OEM kernel to make sure there is no flickering issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896582/+subscriptions -- Mailing list: https://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 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, thanks for that. I got this error message while installing, dpkg: regarding linux-image-unsigned-5.4.0-47-generic_5.4.0-47.51_amd64.deb contntaining linux-image-unsigned-5.4.0-47-generic: linux-image-unsigned-5.4.0-47-generic conflicts with linux-image-5.4.0-47-genereric linux-image-5.4.0-47-generic (version 5.4.0-47.51) is present and installed. dpkg: error processing archive linux-image-unsigned-5.4.0-47-generic_5.4.0-47.5151_amd64.deb (--install): conflicting packages - not installing linux-image-unsigned-5.4.0-47-generic The others, linux-headers-5.4.0-47_5.4.0-47.51_all.deb linux-headers-5.4.0-47-generic_5.4.0-47.51_amd64.deb linux-modules-5.4.0-47-generic_5.4.0-47.51_amd64.deb linux-modules-extra-5.4.0-47-generic_5.4.0-47.51_amd64.deb seem to have installed properly. Should I go ahead and reboot? regards, Jim On Tue, 22 Sep 2020, Jim Cline wrote: > > > > -- Forwarded message -- > Date: Mon, 21 Sep 2020 21:19:04 - > From: Alex Hung <1896...@bugs.launchpad.net> > To: gxgilt...@gmail.com > Subject: [Bug 1896482] Re: acpi event detection crashes > > The warning messages occurred between "ACPI: EC: interrupt blocked" and > "ACPI: EC: interrupt unblocked". Let's try to apply all (17) mainline > patches to ACPI EC to Ubuntu-5.4.0-47.51. > > If this solves the problems we can then bi-select to identify which > patches are the solution and then backport to 5.4 kernel. > > The test kernel is available @ > https://people.canonical.com/~alexhung/LP1896482/ and the applied > patches are listed in ec_patches.log > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! > i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX:
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: Incomplete
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894605] Re: gtp: unable to associate contextes to interfaces
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894605
Title:
gtp: unable to associate contextes to interfaces
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
When a user dump pdp contextes, it cannot associate them with existing
gtp interfaces. Thus, the dump is unusable.
This problem has been fixed in the upstream commit b274e47d9e3f ("gtp: add
GTPA_LINK info to msg sent to userspace"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b274e47d9e3f
[Test Case]
Create several gtp interfaces and setup PDP contextes on them. Perform
a dump with the genl command GTP_CMD_GETPDP.
[Regression Potential]
The patch affects only the gtp driver and is quite trivial. Thus, the
potential regressions are limited to this area and low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894605/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Details: 4.15 kernel: [0.00] kernel: microcode: microcode updated early to revision 0xdc, date = 2020-04-27 [0.00] kernel: Linux version 4.15.0-112-generic (buildd@lcy01-amd64-027) [0.00] kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=4401fe3d-0506-435d-bc52-d3abc67e2981 ro quiet splash ... [0.837778] kernel: microcode: sig=0x506e3, pf=0x10, revision=0xdc cpu family : 6 model : 94 model name : Intel(R) Core(TM) i7-6770HQ CPU @ 2.60GHz stepping: 3 microcode : 0xdc 5.4 kernel: (needs dis_ucode_ldr) --- [0.00] kernel: Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 (Ubuntu 5.4.0-48.52-generic 5.4.60) [0.00] kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=4401fe3d-0506-435d-bc52-d3abc67e2981 ro dis_ucode_ldr cpu family : 6 model : 94 model name : Intel(R) Core(TM) i7-6770HQ CPU @ 2.60GHz stepping: 3 microcode : 0xba microcode version: --- intel-microcode 3.20200609.0ubuntu0.20.04.2 The blob was introduced two versions back. intel-microcode (3.20200609.0ubuntu0.20.04.0) focal-security; urgency=medium ... sig 0x000506e3, pf_mask 0x36, 2020-04-27, rev 0x00dc, size 104448 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896604] Re: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances
** Changed in: linux-aws (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1896604 Title: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances Status in cloud-images: New Status in linux-aws package in Ubuntu: New Bug description: Hi, When running Groovy daily images on i3.metal instances a broken /dev/console is created. The char device appears to be writable but writing to it causes an Input/output error. This is breaking cloud- init, as it tries to log to /dev/console, and is likely to break other programs. On Focal: root@ip-172-31-24-163:~# ls -l /dev/console crw--- 1 root root 5, 1 Sep 21 16:07 /dev/console root@ip-172-31-24-163:~# echo x > /dev/console root@ip-172-31-24-163:~# On Groovy: root@ip-172-31-20-184:~# ls -l /dev/console crw--w 1 root tty 5, 1 Sep 21 16:03 /dev/console root@ip-172-31-20-184:~# echo x > /dev/console bash: echo: write error: Input/output error The Groovy kernel log has a [ 3.561696] fbcon: Taking over console line in it, which is not present in the Focal kernel log (5.4.0-1024-aws). Perhaps fbcon should be prevented from taking over console? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1896604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896642] Re: Request for CIFS patches to be available in 5.4 kernel
The improvement is generic enough for focal:linux instead of focal :linux-azure. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- 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/1896642 Title: Request for CIFS patches to be available in 5.4 kernel Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: Invalid Bug description: [Impact] Microsoft's CIFS product team requested to ensure below patches are available in 5.4 kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=df58fae72428be113f041fe55c9605a9088bfb14 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=0e6705182d4e1b77248a93470d6d7b3013d59b30 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cf5371ae460eb8e484e4884747af270c86c3c469 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=43f8a6a74ee2442b9410ed297f5d4c77e7cb5ace I notice couple commits are already picked up in 5.4 kernel. Just sharing the CIFS patch commit requests came in. [Test Case] Since those are small improvements a basic smoke test can be used to avoid regressions: 1. Install cifs-utils and dbench: $ sudo apt-get install cifs-utils dbench 2. Mount a CIFS share using: $ sudo mount -t cifs -o username=REMOTEUSER \\remoteip\path\to\shared\folder /mnt 3. Run dbench and check for regressions: $ cd /mnt; dbench 20 -t 120 -D . [Regression potential] The regression potential is restricted to the ability of mounting and accessing CIFS volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896642] Re: Request for CIFS patches to be available in 5.4 kernel
v5.4-rc1~8^2~37 df58fae72428 smb3: Incorrect size for netname negotiate
context
v5.5-rc1~3^2~443f8a6a74ee2 smb3: query attributes on file close
v5.7-rc1~155^2~22 cf5371ae460e smb3: fix performance regression with setting
mtime
v5.8-rc7~15^2 0e6705182d4e Revert "cifs: Fix the target file was deleted
when rename failed."
The first commit was accepted upstream before 5.4 and the last two were
already included to Focal via the upstream stable updates LP:#1873481
and LP:#1889669.
Groovy doesn't need any of the changes because all of them where
included before 5.8.
The only one missing is commit id 43f8a6a74ee2 ("smb3: query attributes
on file close").
--
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/1896642
Title:
Request for CIFS patches to be available in 5.4 kernel
Status in linux package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux-azure source package in Focal:
Invalid
Bug description:
[Impact]
Microsoft's CIFS product team requested to ensure below patches are
available in 5.4 kernel
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=df58fae72428be113f041fe55c9605a9088bfb14
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=0e6705182d4e1b77248a93470d6d7b3013d59b30
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cf5371ae460eb8e484e4884747af270c86c3c469
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=43f8a6a74ee2442b9410ed297f5d4c77e7cb5ace
I notice couple commits are already picked up in 5.4 kernel. Just
sharing the CIFS patch commit requests came in.
[Test Case]
Since those are small improvements a basic smoke test can be used to
avoid regressions:
1. Install cifs-utils and dbench:
$ sudo apt-get install cifs-utils dbench
2. Mount a CIFS share using:
$ sudo mount -t cifs -o username=REMOTEUSER
\\remoteip\path\to\shared\folder /mnt
3. Run dbench and check for regressions:
$ cd /mnt; dbench 20 -t 120 -D .
[Regression potential]
The regression potential is restricted to the ability of mounting and
accessing CIFS volumes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896642/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
This bug was fixed in the package virt-manager - 1:2.2.1-4ubuntu2 --- virt-manager (1:2.2.1-4ubuntu2) groovy; urgency=medium * d/p/lp-1847105-addstorage-Return-to-using-qcow2-sparse-by-default.patch: fix slow disk allocation when using the defaults to to falloc (LP: #1847105) -- Christian Ehrhardt Mon, 21 Sep 2020 16:28:36 +0200 ** Changed in: virt-manager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied:
[Kernel-packages] [Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-azure (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830740 Title: [linux-azure] Delay during boot of some instance sizes Status in cloud-init package in Ubuntu: New Bug description: We are seeing a long delay, about 100s, when booting new E32s_v3 VMs. We don’t see this delay with smaller sized Ubuntu VMs(D2s and NC6 sizes). I attached a screen shot of the boot delay. You can see between 7.022911 and 101.325958 seconds there is no activity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896655] [NEW] Touchpad stopped responding after upgrading to the latest kernel
Public bug reported: No response from the touchpad at all! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cyberdragon 4832 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 00:29:00 2020 InstallationDate: Installed on 2020-07-25 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1770:ff00 MSI EPF USB MSI EPF USB Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GV62 7RD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=c3805fb0-1532-4ac8-b55b-c18827942e04 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.324 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGV627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GV dmi.product.name: GV62 7RD dmi.product.sku: 16J9.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1896655/+attachment/5413298/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896655 Title: Touchpad stopped responding after upgrading to the latest kernel Status in linux package in Ubuntu: New Bug description: No response from the touchpad at all! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cyberdragon 4832 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 00:29:00 2020 InstallationDate: Installed on 2020-07-25 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1770:ff00 MSI EPF USB MSI EPF USB Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GV62 7RD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=c3805fb0-1532-4ac8-b55b-c18827942e04 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.324 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGV627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GV dmi.product.name: GV62 7RD dmi.product.sku: 16J9.3
[Kernel-packages] [Bug 1896642] [NEW] Request for CIFS patches to be available in 5.4 kernel
Public bug reported: [Impact] Microsoft's CIFS product team requested to ensure below patches are available in 5.4 kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=df58fae72428be113f041fe55c9605a9088bfb14 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=0e6705182d4e1b77248a93470d6d7b3013d59b30 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cf5371ae460eb8e484e4884747af270c86c3c469 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=43f8a6a74ee2442b9410ed297f5d4c77e7cb5ace I notice couple commits are already picked up in 5.4 kernel. Just sharing the CIFS patch commit requests came in. [Test Case] Since those are small improvements a basic smoke test can be used to avoid regressions: 1. Install cifs-utils and dbench: $ sudo apt-get install cifs-utils dbench 2. Mount a CIFS share using: $ sudo mount -t cifs -o username=REMOTEUSER \\remoteip\path\to\shared\folder /mnt 3. Run dbench and check for regressions: $ cd /mnt; dbench 20 -t 120 -D . [Regression potential] The regression potential is restricted to the ability of mounting and accessing CIFS volumes. ** Affects: linux-azure (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New -- 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/1896642 Title: Request for CIFS patches to be available in 5.4 kernel Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: New Bug description: [Impact] Microsoft's CIFS product team requested to ensure below patches are available in 5.4 kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=df58fae72428be113f041fe55c9605a9088bfb14 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=0e6705182d4e1b77248a93470d6d7b3013d59b30 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cf5371ae460eb8e484e4884747af270c86c3c469 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=43f8a6a74ee2442b9410ed297f5d4c77e7cb5ace I notice couple commits are already picked up in 5.4 kernel. Just sharing the CIFS patch commit requests came in. [Test Case] Since those are small improvements a basic smoke test can be used to avoid regressions: 1. Install cifs-utils and dbench: $ sudo apt-get install cifs-utils dbench 2. Mount a CIFS share using: $ sudo mount -t cifs -o username=REMOTEUSER \\remoteip\path\to\shared\folder /mnt 3. Run dbench and check for regressions: $ cd /mnt; dbench 20 -t 120 -D . [Regression potential] The regression potential is restricted to the ability of mounting and accessing CIFS volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1896642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896519] Re: kworker consumes 80% of CPU
Hey, Could you please collect the stack traces of the kworker process while the issue happens? 1) Once it starts, get its PID (eg, 86069) and run: $ pid=86069; while sleep 1; do ts="$(date +'%F-%H-%M-%S')"; sudo cat /proc/$pid/stack > /tmp/stack.$pid.$ts; done 2) Once it stops, press ctrl-c to kill the collection, and run: $ tar cf /tmp/lp1896519-stacks.tar /tmp/stack.* And upload the tar file to this LP bug. Thanks, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896519 Title: kworker consumes 80% of CPU Status in linux package in Ubuntu: Confirmed Bug description: Like yesterday I have noticed my CPU on Leonovo Thinkpad T590 laptop has starting to be consumed by kworker for 80% of 2-CPU 4-core processor. I also see fan works like crazy and "ejects" hot air non stop. This has never happened in my 6 months of having this new laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 21 19:29:32 2020 InstallationDate: Installed on 2019-10-23 (334 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20N4S06V00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=5ae35a7d-8195-4867-8bb5-49ab3106da83 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-08-14 (38 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4S06V00 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:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N4S06V00:pvrThinkPadT590:rvnLENOVO:rn20N4S06V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4S06V00 dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896604] Re: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances
Adding some details about this issue. It looks like the real problem is the serial driver, in fact with a 5.4 kernel we can see the following in dmesg: [4.991325] :16:00.0: ttyS0 at MMIO 0xc5a0 (irq = 85, base_baud = 115200) is a 16550A With the 5.8 kernel we don't see any message at all about ttyS0, meaning that the serial isn't properly recognized. A temporary workaround could be to remove console=ttyS0 from the kernel boot parameters, this would probably make cloud-init happy, but this is not obviously the right solution. I'll investigate more to find the exact commit that introduced this regression. Thanks Paride for helping me out to reproduce and test this problem! -- 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/1896604 Title: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances Status in cloud-images: New Status in linux-aws package in Ubuntu: New Bug description: Hi, When running Groovy daily images on i3.metal instances a broken /dev/console is created. The char device appears to be writable but writing to it causes an Input/output error. This is breaking cloud- init, as it tries to log to /dev/console, and is likely to break other programs. On Focal: root@ip-172-31-24-163:~# ls -l /dev/console crw--- 1 root root 5, 1 Sep 21 16:07 /dev/console root@ip-172-31-24-163:~# echo x > /dev/console root@ip-172-31-24-163:~# On Groovy: root@ip-172-31-20-184:~# ls -l /dev/console crw--w 1 root tty 5, 1 Sep 21 16:03 /dev/console root@ip-172-31-20-184:~# echo x > /dev/console bash: echo: write error: Input/output error The Groovy kernel log has a [ 3.561696] fbcon: Taking over console line in it, which is not present in the Focal kernel log (5.4.0-1024-aws). Perhaps fbcon should be prevented from taking over console? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1896604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
It looks like you have secure boot enabled. Unfortunately test kernels are unsigned and thus require it to be disabled in your BIOS/EFI menu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Confirmed Bug description: Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663] acpi_ec_space_handler+0xd4/0x280 Sep 20 11:35:33 laxmi kernel: [232492.303666] acpi_ev_address_space_dispatch+0x2f7/0x39f Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 Sep 20 11:35:33 laxmi kernel: [232492.303670] acpi_ex_access_region+0x454/0x4ed Sep 20 11:35:33 laxmi kernel:
[Kernel-packages] [Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Well, some more information is needed before one can start to look at this more deeply: - What is the Ubuntu release where this happened? - Was the system up-to-date? - Which syslog was used? - What is the version of the syslog package? (apt-cache policy ) - When did the last log rotation happened and did it worked? - Is there any indication in the logs that the service got stopped (by human interaction or by tools/application) or crashed? - Are there entries in /var/crash? - Any indication for problems with systemd? - Was this identified more than once (on this or other systems)? ** Package changed: linux (Ubuntu) => ubuntu ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu Status: New => Incomplete ** Changed in: ubuntu-z-systems 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/1896575 Title: [UBUNTU 20.04] syslog daemon stop running unexpectedly Status in Ubuntu on IBM z Systems: Incomplete Status in Ubuntu: Incomplete Bug description: Example of how was detected that the syslog stop working, it has couple of days without reporting: root@ilzlnx4:~# tail -f /var/log/syslog Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664542] sd 3:0:0:2: [sdt] tag#81 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664543] sd 3:0:0:2: [sdt] tag#81 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664656] sd 4:0:0:2: [sdq] tag#32 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664658] sd 4:0:0:2: [sdq] tag#32 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664773] sd 5:0:0:2: [sdaa] tag#48 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664774] sd 5:0:0:2: [sdaa] tag#48 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664775] sd 5:0:0:2: [sdaa] tag#48 Sense Key : Illegal Request [current] root@ilzlnx4:~# date Thu 17 Sep 2020 08:59:41 PM MST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
The new kernel, 5.4.0-48, indeed solves the problem. Thanks for all the comments! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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/1894378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. It is currently in the md-next tree [1], and I am expecting the commits to be merged during the 5.10 merge window. [1] https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/log/?h =md-next commit 5b2374a6c221f28c74913d208bb5376a7ee3bf70 Author: Xiao Ni Date: Wed Sep 2 20:00:23 2020 +0800 Subject: md/raid10: improve discard request for far layout Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=5b2374a6c221f28c74913d208bb5376a7ee3bf70 commit 8f694215ae4c7abf1e6c985803a1aad0db748d07 Author: Xiao Ni Date: Wed Sep 2 20:00:22 2020 +0800 Subject: md/raid10: improve raid10 discard request Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=8f694215ae4c7abf1e6c985803a1aad0db748d07 commit 6fcfa8732a8cfea7828a9444c855691c481ee557 Author: Xiao Ni Date: Tue Aug 25 13:43:01 2020 +0800 Subject: md/raid10: pull codes that wait for blocked dev into one function Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=6fcfa8732a8cfea7828a9444c855691c481ee557 commit 6f4fed152a5e483af2227156ce7b6263aeeb5c84 Author: Xiao Ni Date: Tue Aug 25 13:43:00 2020 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=6f4fed152a5e483af2227156ce7b6263aeeb5c84 commit 7197f1a616caf85508d81c7f5c9f065ffaebf027 Author: Xiao Ni Date: Tue Aug 25 13:42:59 2020 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=7197f1a616caf85508d81c7f5c9f065ffaebf027 It follows a similar strategy which was implemented in Raid0 in the below commit, which was merged in 4.12-rc2: commit 29efc390b9462582ae95eb9a0b8cd17ab956afc0 Author: Shaohua Li Date: Sun May 7 17:36:24 2017 -0700 Subject: md/md0: optimize raid0 discard handling Link: https://github.com/torvalds/linux/commit/29efc390b9462582ae95eb9a0b8cd17ab956afc0 [Testcase] You will need a machine with at least 4x NVMe drives which support block discard. I use a i3.8xlarge instance on AWS, since it has all of these things. $ lsblk xvda202:008G 0 disk └─xvda1 202:108G 0 part / nvme0n1 259:20 1.7T 0 disk nvme1n1 259:00 1.7T 0 disk nvme2n1 259:10 1.7T 0 disk nvme3n1 259:30 1.7T 0 disk Create a Raid10 array: $ sudo mdadm --create --verbose /dev/md0 --level=10 --raid-devices=4 /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 Format the array with XFS: $ time sudo mkfs.xfs /dev/md0 real 11m14.734s $ sudo mkdir /mnt/disk $ sudo mount /dev/md0
[Kernel-packages] [Bug 1896582] Re: Enable i915 panel self refresh feature
** Description changed: [Impact] + PSR feature has been disabled by default because of below bug, "Dell XPS 13 (7390) Display Flickering - 19.10" + https://bugs.launchpad.net/bugs/1849947 + + But this feature is important to pass the new energy start standard, so + re-enable it and set default value to -1 "use per-chip default" [Fix] + Revert the below commit to enable it again + ecc718f31c90 UBUNTU: SAUCE: drm/i915: Disable PSR by default on all + platforms [Test] + Verified on one Dell platform which panel supports PSR [Regression Potential] + High, we plan to verify all platforms that shipped with 5.6 OEM kernel to make sure there is no flickering issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1896582 Title: Enable i915 panel self refresh feature Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] PSR feature has been disabled by default because of below bug, "Dell XPS 13 (7390) Display Flickering - 19.10" https://bugs.launchpad.net/bugs/1849947 But this feature is important to pass the new energy start standard, so re-enable it and set default value to -1 "use per-chip default" [Fix] Revert the below commit to enable it again ecc718f31c90 UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms [Test] Verified on one Dell platform which panel supports PSR [Regression Potential] High, we plan to verify all platforms that shipped with 5.6 OEM kernel to make sure there is no flickering issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1896582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894591] Re: clock: overriding the clocksource should select the requested clocksource
Performing verification: First, reproducing on older kernel: $ uname -rv 4.4.0-190-generic #220-Ubuntu SMP Fri Aug 28 23:02:15 UTC 2020 $ grep "clocksource" /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc" $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.0-190-generic root=UUID=f6c72a0a-003a-4b81-9550-ba49a547e32d ro clocksource=tsc $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock kvm-clock is the default, even though we explicitly asked for tsc. We can reproduce. Now, I enabled -proposed and installed 4.4.0-191-generic: $ uname -rv 4.4.0-191-generic #221-Ubuntu SMP Fri Sep 18 13:34:04 UTC 2020 $ grep "clocksource" /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc" $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.0-191-generic root=UUID=f6c72a0a-003a-4b81-9550-ba49a547e32d ro clocksource=tsc $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc $ dmesg | grep defer [0.870439] clocksource: Override clocksource tsc is not currently HRT compatible - deferring We have our requested clocksource, tsc, and we did not need to force override the reliability checks from the watchdog. The kernel in -proposed, 4.4.0-191-generic, fixes the problem, and I am happy to mark the bug verified. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894591 Title: clock: overriding the clocksource should select the requested clocksource Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1894591 [Impact] The default clocksource for a KVM VM is kvm-clock, and I happen to need tsc. $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock If I edit /etc/default/grub and append "clocksource=tsc" to GRUB_CMDLINE_LINUX_DEFAULT and reboot, I find the clocksource is still kvm-clock. $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock I can work around this by telling the kernel that the tsc clocksource is reliable, before the watchdog has a chance to see for itself that it is reliable: GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc tsc=reliable" $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc If I override the clocksource, the kernel should respect my wishes and I should receive the requested clocksource. [Fix] The fix landed in Linux 4.9 in the below commit: commit 36374583f9084cdab4b5dcf5521a3ce55bebb9fa Author: Kyle Walker Date: Sat Aug 6 12:07:30 2016 -0400 Subject: clocksource: Defer override invalidation unless clock is unstable Link: https://github.com/torvalds/linux/commit/36374583f9084cdab4b5dcf5521a3ce55bebb9fa The commit ensures the override doesn't get cleared before the watchdog has had an opportunity to check if the clocksource is stable or not. However, if the clocksource is known to be unstable at this point in time, it will clear the override and return to the default. This is a clean cherry-pick to the Xenial 4.4 kernel. [Testcase] Start up a KVM VM, possibly enable invtsc on the QEMU command line. The default clocksource will be kvm-clock: $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock If you set the kernel command line to: GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc" If you reboot, you will see the incorrect option of kvm-clock: $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock There is a test kernel available in the below ppa, with the commit applied: https://launchpad.net/~mruffell/+archive/ubuntu/sf291501-test If you install the test kernel, and leave the kernel command line as: GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc" You will get the requested clocksource: $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc You will also get the following in dmesg: $ dmesg | grep defer [1.002599] clocksource: Override clocksource tsc is not currently HRT compatible - deferring [Regression Potential] This commit changes how the kernel treats clocksource overrides. If any users have an override set, but the kernel is clearing the override and returning to the default, when they install a patched kernel, they will change over to their requested override, which may come as a surprise. If there is a regression, it will only affect systems who have clocksource overrides in place, and in the worst case, will revert the system to its default clocksource if the selected clocksource override is found to be unstable. The commit is well tested, and should not cause any regressions. To manage notifications
[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
** Also affects: oem-priority 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1849947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Fix Released Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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/1894378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893778] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-09-22 04:02 EDT--- I've verified that this now works as expected on focal-proposed kernel 5.4.0-49.53. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893778 Title: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a PCI device (incl. virtio-pci) is hot-plugged during boot-up on s390x, it can be detected as an entry in CLP List PCI functions and via the hot-plug event. * (This is basically equivalent to boot time probing on other architectures.) * In such a case the hot-plug event will be stale, but Linux still tries to add and enable the device which leads to: * a) a duplicate entry in zPCI internal device list * b) an attempt to enable the device with a stale function handle * In case b) the device will be placed in error state which makes it unusable. [Fix] * b76fee1bc56c31a9d2a49592810eba30cc06d61a b76fee1bc56c "s390/pci: ignore stale configuration request event" [Test Case] * Setup an Ubuntu Server 20.04 (focal) Linux operating system on an IBM Z or LinuxONE III LPAR. * It's now easiest to test on KVM using virtio-pci (on s390x). * Start a test virtual machine: sudo virsh start * Attach and hotplug a virtio-pci device: sudo virsh attach-device hotplug_pci_block.xml * Where hotplug_pci_block.xml looks like: [Regression Potential] * The regression risk is moderate, since the modification is very limited and therefore manageable (additional if statement - two lines of code) and easily testable on KVM using virtio-pci. * The changes are in the zPCI event code, so in worst-case it can happen that the event handling get harmed which may break zPCI entirely, affecting all PCI devices incl. virtio-pci (on s390x). * A bug in PCI 'availability' handling also just lead to wrong states of PCI devices which make them unavailable, hence unusable. * Notice that zPCI is the s390x-specific PCI implementation, modifications here do not affect any other architecture. * And zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing atesting can be easily done with virtio-pci on KVM. [Other] * The fix/patch got upstream accepted with kernel v5.9-rc2. * But it landed already in groovy's proposed kernel 5.8 (Ubuntu-5.8.0-18.19), due to 'Groovy update: v5.8.4 upstream stable release' that is handled in LP 1893048. * Hence this fix/patch need to be applied to focal only. __ When a PCI device (including virtio-pci for which this is easiest to test) is hot-plugged while Linux is still booting, it can be detected as an entry in CLP List PCI Functions (basically equivalent to boot time probing on other architectures) and with the hot-plug event. In this case the hot-plug event will be stale but Linux still tried to add and enable the device leading a) to a duplicate entry in zPCI internal device list b) an attempt to enable the device witha stale function handle Part b) would lead to the device being place in the error state and make it unusable. This can most easily be reproduced using KVM and doing # sudo virsh start myguest && sudo virsh attach-device myguest hotplug_pci_block.xml Where hotplug_pci_block.xml looks like the following: The problem is fixed with the 3-line upstream commit b76fee1bc56c31a9d2a49592810eba30cc06d61a s390/pci: ignore stale configuration request event I also confirmed that as of the focal tag Ubuntu-5.4.0-46.50 this cherry-picks cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843742] Re: RM: irda-utils and ircp-tray (was: irda-utils ftbfs in eoan)
** Changed in: irda-utils (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ircp-tray (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to irda-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1843742
Title:
RM: irda-utils and ircp-tray (was: irda-utils ftbfs in eoan)
Status in ircp-tray package in Ubuntu:
Fix Released
Status in irda-utils package in Ubuntu:
Fix Released
Bug description:
https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
.irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c
irdadump.c
irdadump.c: In function ‘print_time’:
irdadump.c:82:13: warning: g_string_append_printf
82 | g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
irdadump.c: In function ‘print_diff_time’:
irdadump.c:108:13: warning: g_string_append_printf
108 | g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
irdadump.c: In function ‘parse_irda_frame’:
irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
irdadump.c: In function ‘irdadump_loop’:
irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this
function); did you mean ‘SIOCGARP’?
286 | if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
irdadump.c:286:16: note: each undeclared identifier is reported only once for
each function it appears in
make[1]: *** [Makefile:48: irdadump.o] Error 1
make[1]: Leaving directory '/<>/irdadump'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ircp-tray/+bug/1843742/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896578] [NEW] raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. It is currently in the md-next tree [1], and I am expecting the commits to be merged during the 5.10 merge window. [1] https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/log/?h =md-next commit 5b2374a6c221f28c74913d208bb5376a7ee3bf70 Author: Xiao Ni Date: Wed Sep 2 20:00:23 2020 +0800 Subject: md/raid10: improve discard request for far layout Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=5b2374a6c221f28c74913d208bb5376a7ee3bf70 commit 8f694215ae4c7abf1e6c985803a1aad0db748d07 Author: Xiao Ni Date: Wed Sep 2 20:00:22 2020 +0800 Subject: md/raid10: improve raid10 discard request Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=8f694215ae4c7abf1e6c985803a1aad0db748d07 commit 6fcfa8732a8cfea7828a9444c855691c481ee557 Author: Xiao Ni Date: Tue Aug 25 13:43:01 2020 +0800 Subject: md/raid10: pull codes that wait for blocked dev into one function Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=6fcfa8732a8cfea7828a9444c855691c481ee557 commit 6f4fed152a5e483af2227156ce7b6263aeeb5c84 Author: Xiao Ni Date: Tue Aug 25 13:43:00 2020 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=6f4fed152a5e483af2227156ce7b6263aeeb5c84 commit 7197f1a616caf85508d81c7f5c9f065ffaebf027 Author: Xiao Ni Date: Tue Aug 25 13:42:59 2020 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next=7197f1a616caf85508d81c7f5c9f065ffaebf027 It follows a similar strategy which was implemented in Raid0 in the below commit, which was merged in 4.12-rc2: commit 29efc390b9462582ae95eb9a0b8cd17ab956afc0 Author: Shaohua Li Date: Sun May 7 17:36:24 2017 -0700 Subject: md/md0: optimize raid0 discard handling Link: https://github.com/torvalds/linux/commit/29efc390b9462582ae95eb9a0b8cd17ab956afc0 [Testcase] You will need a machine with at least 4x NVMe drives which support block discard. I use a i3.8xlarge instance on AWS, since it has all of these things. $ lsblk xvda202:008G 0 disk └─xvda1 202:108G 0 part / nvme0n1 259:20 1.7T 0 disk nvme1n1 259:00 1.7T 0 disk nvme2n1 259:10 1.7T 0 disk nvme3n1 259:30 1.7T 0 disk Create a Raid10 array: $ sudo mdadm --create --verbose /dev/md0 --level=10 --raid-devices=4 /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 Format the array with XFS: $ time sudo mkfs.xfs /dev/md0 real 11m14.734s $ sudo mkdir /mnt/disk $ sudo mount /dev/md0 /mnt/disk Optional, do a fstrim: $ time sudo fstrim /mnt/disk real11m37.643s I built a test kernel based on 5.9-rc6 with the above patches, and we can see that performance dramatically improves: $ sudo mdadm --create --verbose /dev/md0 --level=10 --raid-devices=4
[Kernel-packages] [Bug 1896582] [NEW] Enable i915 panel self refresh feature
Public bug reported: [Impact] [Fix] [Test] [Regression Potential] ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1896582 Title: Enable i915 panel self refresh feature Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] [Fix] [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1896582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893778] Re: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device
Thx Niklas for the verification - updating tags ... ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893778 Title: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a PCI device (incl. virtio-pci) is hot-plugged during boot-up on s390x, it can be detected as an entry in CLP List PCI functions and via the hot-plug event. * (This is basically equivalent to boot time probing on other architectures.) * In such a case the hot-plug event will be stale, but Linux still tries to add and enable the device which leads to: * a) a duplicate entry in zPCI internal device list * b) an attempt to enable the device with a stale function handle * In case b) the device will be placed in error state which makes it unusable. [Fix] * b76fee1bc56c31a9d2a49592810eba30cc06d61a b76fee1bc56c "s390/pci: ignore stale configuration request event" [Test Case] * Setup an Ubuntu Server 20.04 (focal) Linux operating system on an IBM Z or LinuxONE III LPAR. * It's now easiest to test on KVM using virtio-pci (on s390x). * Start a test virtual machine: sudo virsh start * Attach and hotplug a virtio-pci device: sudo virsh attach-device hotplug_pci_block.xml * Where hotplug_pci_block.xml looks like: [Regression Potential] * The regression risk is moderate, since the modification is very limited and therefore manageable (additional if statement - two lines of code) and easily testable on KVM using virtio-pci. * The changes are in the zPCI event code, so in worst-case it can happen that the event handling get harmed which may break zPCI entirely, affecting all PCI devices incl. virtio-pci (on s390x). * A bug in PCI 'availability' handling also just lead to wrong states of PCI devices which make them unavailable, hence unusable. * Notice that zPCI is the s390x-specific PCI implementation, modifications here do not affect any other architecture. * And zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing atesting can be easily done with virtio-pci on KVM. [Other] * The fix/patch got upstream accepted with kernel v5.9-rc2. * But it landed already in groovy's proposed kernel 5.8 (Ubuntu-5.8.0-18.19), due to 'Groovy update: v5.8.4 upstream stable release' that is handled in LP 1893048. * Hence this fix/patch need to be applied to focal only. __ When a PCI device (including virtio-pci for which this is easiest to test) is hot-plugged while Linux is still booting, it can be detected as an entry in CLP List PCI Functions (basically equivalent to boot time probing on other architectures) and with the hot-plug event. In this case the hot-plug event will be stale but Linux still tried to add and enable the device leading a) to a duplicate entry in zPCI internal device list b) an attempt to enable the device witha stale function handle Part b) would lead to the device being place in the error state and make it unusable. This can most easily be reproduced using KVM and doing # sudo virsh start myguest && sudo virsh attach-device myguest hotplug_pci_block.xml Where hotplug_pci_block.xml looks like the following: The problem is fixed with the 3-line upstream commit b76fee1bc56c31a9d2a49592810eba30cc06d61a s390/pci: ignore stale configuration request event I also confirmed that as of the focal tag Ubuntu-5.4.0-46.50 this cherry-picks cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Another Ryzen 7 1800X user here with similar random crashes. [165716.089703] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [165716.095949] rcu:1-...!: (0 ticks this GP) idle=354/0/0x0 softirq=2154363/2154363 fqs=0 [165716.104512] rcu:3-...!: (0 ticks this GP) idle=29c/0/0x0 softirq=883832/883832 fqs=0 [165716.112873] rcu:4-...!: (8 GPs behind) idle=ad8/0/0x0 softirq=2165586/2165586 fqs=0 [165716.121179] rcu:9-...!: (9 GPs behind) idle=acc/0/0x0 softirq=1340600/1340600 fqs=0 [165716.129467] rcu:11-...!: (2 GPs behind) idle=a18/0/0x0 softirq=4538536/4538537 fqs=0 [165716.137828] rcu:12-...!: (0 ticks this GP) idle=870/0/0x0 softirq=2158040/2158040 fqs=0 [165775.697763] rcu: rcu_sched kthread starved for 29898 jiffies! g36134941 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=3 [165775.709013] rcu: RCU grace-period kthread stack dump: [165837.494623] watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [(resolved):52315] [165865.494840] watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [(resolved):52315] [165893.495058] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [(resolved):52315] [165921.495276] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [(resolved):52315] [165949.495494] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [(resolved):52315] Unfortunaltey I didn't have sysrq configured so I can't provide more information other than I also have an X370 motherboard. The system is not not has it ever been overlocked. I've owned all the componentes since new so I'm not going to be able to RMA them like some others have. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel:
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 Bay Trail QWAWKS
I have a workaorund and a fix for this bug. The bug is due to missing UCM2 folders and config files, which are now available on git hub. The missing folders are: - /usr/share/alsa/ucm2/chtmax98090/ : it can be retrieved from https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/chtmax98090 - /usr/share/ucm2/codecs/max98090/ : it can be retrived from https://github.com/alsa-project/alsa-ucm- conf/tree/master/ucm2/codecs/max98090 After adding the above two folders and a reboot, the sound works fine. Tested on Ubuntu 20.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 Bay Trail QWAWKS Status in linux package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893290] Re: The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work after suspend
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1028.28 --- linux-oem-5.6 (5.6.0-1028.28) focal; urgency=medium * focal/linux-oem-5.6: 5.6.0-1028.28 -proposed tracker (LP: #1894630) * Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (LP: #1894778) - SAUCE: PCI: vmd: Add AHCI to fast interrupt list * SRU: Fix system hang when stress S3 on radeon with TTM (LP: #1893609) - mei: bus: don't clean driver pointer * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for the 450 nvidia driver * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM (LP: #1893194) - SAUCE: PCI/ASPM: VMD: add ASPM quirk for 8086:a0bc * The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work after suspend (LP: #1893290) - ALSA: hda/hdmi: always check pin power status in i915 pin fixup * Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288) - ahci: Add Intel Comet Lake PCH-H PCI ID * device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init (LP: #1892827) - efi/tpm: Verify event log header before parsing -- Timo Aaltonen Tue, 08 Sep 2020 11:40:14 +0300 ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12888 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893290 Title: The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work after suspend Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: Since this patch is CCed to stable kernel, I just sent this patch to oem-5.6 kernel, our oem project is waiting for this patch to be landed to oem-5.6 kernel first. [Impact] On the Dell TGL laptop, if connecting a monitor via type-c to DP/HDMI adapter, we will have an audio issue, that is playing the music and suspend the system, after resuming back, the audio can't output from DP/HDMI monitor anymore. [Fix] Cherry-pick a fix from upstream, this patch is verifying the needed converter and pin to be in the D0 state. [Test Case] Connect a monitor with USB-C to DP/HDMI adapter, open the youtu.com and playing sth, suspend the system and resume, check if the sound could play the music, repeat 20 times, all work very well. [Regression Risk] If this patch could introduce regression, it should be the power consumption regression on Intel HDMI audio, since it makes the converter and pin to be D0 state earlier than before. But this impact is very small. one converter and one pin consume very little power. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893609] Re: SRU: Fix system hang when stress S3 on radeon with TTM
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1028.28 --- linux-oem-5.6 (5.6.0-1028.28) focal; urgency=medium * focal/linux-oem-5.6: 5.6.0-1028.28 -proposed tracker (LP: #1894630) * Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (LP: #1894778) - SAUCE: PCI: vmd: Add AHCI to fast interrupt list * SRU: Fix system hang when stress S3 on radeon with TTM (LP: #1893609) - mei: bus: don't clean driver pointer * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for the 450 nvidia driver * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM (LP: #1893194) - SAUCE: PCI/ASPM: VMD: add ASPM quirk for 8086:a0bc * The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work after suspend (LP: #1893290) - ALSA: hda/hdmi: always check pin power status in i915 pin fixup * Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288) - ahci: Add Intel Comet Lake PCH-H PCI ID * device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init (LP: #1892827) - efi/tpm: Verify event log header before parsing -- Timo Aaltonen Tue, 08 Sep 2020 11:40:14 +0300 ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12888 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893609 Title: SRU: Fix system hang when stress S3 on radeon with TTM Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: SRU Justification: [Impact] System hang when stress S3 more than 90 times. [Fix] Upstream kernel is good, after bisecting, bad commit is a Ubuntu sauce patch: "vfio -- release device lock before userspace requests" 5.8 kernel got this fix. 5.4 kernel got this commit by stable update LP:#1888560 [Test Case] Verified for 500 times of S3, system runs good. [Regression Potential] Low uptream fix for specific commit, verified with postive result. == [Summary] System got hang during executing the S3-30-cycle test case. [Steps to reproduce] $ sudo checkbox-support-fwts_test -l /home/u/suspend_30_cycles -f none -s s3 --s3-device-check --s3-device-check-delay=60 --s3-sleep-delay=60 --s3-multiple=30 [Expected result] The test script should be finished smoothly. [Actual result] System got hang at the 7th or 8th S3 resumed back. [Failure rate] 100% [Additional information] CPU: Intel(R) Core(TM) i5-10600 CPU @ 3.30GHz (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:9bc8] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) kernel-version: 5.6.0-1020-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1028.28
---
linux-oem-5.6 (5.6.0-1028.28) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1028.28 -proposed tracker (LP: #1894630)
* Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to
IDENTIFY (I/O error, err_mask=0x4) (LP: #1894778)
- SAUCE: PCI: vmd: Add AHCI to fast interrupt list
* SRU: Fix system hang when stress S3 on radeon with TTM (LP: #1893609)
- mei: bus: don't clean driver pointer
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- update dkms package versions
* Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
- [packaging] add signed modules for the 450 nvidia driver
* CVE-2020-12888
- vfio/type1: Support faulting PFNMAP vmas
- vfio-pci: Fault mmaps to enable vma tracking
- vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
* Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM (LP: #1893194)
- SAUCE: PCI/ASPM: VMD: add ASPM quirk for 8086:a0bc
* The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work
after suspend (LP: #1893290)
- ALSA: hda/hdmi: always check pin power status in i915 pin fixup
* Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288)
- ahci: Add Intel Comet Lake PCH-H PCI ID
* device doesn't boot with kernel older than v5.7.7 on a usb key: hang at
efi_tpm_eventlog_init (LP: #1892827)
- efi/tpm: Verify event log header before parsing
-- Timo Aaltonen Tue, 08 Sep 2020
11:40:14 +0300
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: In Progress => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12888
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1028.28 --- linux-oem-5.6 (5.6.0-1028.28) focal; urgency=medium * focal/linux-oem-5.6: 5.6.0-1028.28 -proposed tracker (LP: #1894630) * Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (LP: #1894778) - SAUCE: PCI: vmd: Add AHCI to fast interrupt list * SRU: Fix system hang when stress S3 on radeon with TTM (LP: #1893609) - mei: bus: don't clean driver pointer * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for the 450 nvidia driver * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM (LP: #1893194) - SAUCE: PCI/ASPM: VMD: add ASPM quirk for 8086:a0bc * The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work after suspend (LP: #1893290) - ALSA: hda/hdmi: always check pin power status in i915 pin fixup * Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288) - ahci: Add Intel Comet Lake PCH-H PCI ID * device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init (LP: #1892827) - efi/tpm: Verify event log header before parsing -- Timo Aaltonen Tue, 08 Sep 2020 11:40:14 +0300 ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12888 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1894778 Title: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Proposed kernel patch https://patchwork.kernel.org/patch/11758345/ [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Regression Potential] Low. For previous NVMe based platforms, this patch brings no effective change for NVMe devices because they will still stay in fast-interrupt list. == Original Bug Description == When booting with root filesystem on sata disks under Intel VMD mode, following errors printed in dmesg and no disk is found, nor booting into it: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 16.659284] ata1.00: qc timeout (cmd 0xec) [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 48.147294] ata1.00: qc timeout (cmd 0xec) [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) $ lspci ... 1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890913] Re: init is using 100% of processor
*** This bug is a duplicate of bug 1891657 *** https://bugs.launchpad.net/bugs/1891657 Will be fixed in next upload, in 246.6-1ubuntu1 https://github.com/systemd/systemd/issues/16669 ** Bug watch added: github.com/systemd/systemd/issues #16669 https://github.com/systemd/systemd/issues/16669 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893194] Re: Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1028.28 --- linux-oem-5.6 (5.6.0-1028.28) focal; urgency=medium * focal/linux-oem-5.6: 5.6.0-1028.28 -proposed tracker (LP: #1894630) * Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (LP: #1894778) - SAUCE: PCI: vmd: Add AHCI to fast interrupt list * SRU: Fix system hang when stress S3 on radeon with TTM (LP: #1893609) - mei: bus: don't clean driver pointer * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for the 450 nvidia driver * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM (LP: #1893194) - SAUCE: PCI/ASPM: VMD: add ASPM quirk for 8086:a0bc * The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work after suspend (LP: #1893290) - ALSA: hda/hdmi: always check pin power status in i915 pin fixup * Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288) - ahci: Add Intel Comet Lake PCH-H PCI ID * device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init (LP: #1892827) - efi/tpm: Verify event log header before parsing -- Timo Aaltonen Tue, 08 Sep 2020 11:40:14 +0300 ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12888 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893194 Title: Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: One VMD equipped platform has another PCI bridge with PCI ID [8086:a0bc] that is not already in Ubuntu sauced PCI_DEV_FLAGS_ENABLE_ASPM list from bug 1889384. Link Capability Register shows ASPM L1 supported, but has ASPM Disabled in Link Control status. 1:e0:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:a0bc] (rev 20) (prog-if 00 [Normal decode]) ... Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #5, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- ... 00: 86 80 bc a0 06 04 10 00 20 00 04 06 00 00 81 00 10: 00 00 00 00 00 00 00 00 00 e1 e1 00 f0 00 00 20 20: 00 72 00 72 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 02 00 40: 10 80 42 01 01 80 00 00 2f 00 10 00 43 48 72 05 ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1023-oem 5.6.0-1023.23 ProcVersionSignature: Ubuntu 5.6.0-1023.23-oem 5.6.19 Uname: Linux 5.6.0-1023-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 04:32:44 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa+X31 InstallationDate: Installed on 2020-08-13 (14 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1767 F pulseaudio CasperMD5CheckResult: skip
[Kernel-packages] [Bug 1892827] Re: device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1028.28
---
linux-oem-5.6 (5.6.0-1028.28) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1028.28 -proposed tracker (LP: #1894630)
* Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to
IDENTIFY (I/O error, err_mask=0x4) (LP: #1894778)
- SAUCE: PCI: vmd: Add AHCI to fast interrupt list
* SRU: Fix system hang when stress S3 on radeon with TTM (LP: #1893609)
- mei: bus: don't clean driver pointer
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- update dkms package versions
* Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
- [packaging] add signed modules for the 450 nvidia driver
* CVE-2020-12888
- vfio/type1: Support faulting PFNMAP vmas
- vfio-pci: Fault mmaps to enable vma tracking
- vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
* Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM (LP: #1893194)
- SAUCE: PCI/ASPM: VMD: add ASPM quirk for 8086:a0bc
* The DP/HDMI audio via USB-C to DP dongle or Dell Zeus adapter can't work
after suspend (LP: #1893290)
- ALSA: hda/hdmi: always check pin power status in i915 pin fixup
* Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288)
- ahci: Add Intel Comet Lake PCH-H PCI ID
* device doesn't boot with kernel older than v5.7.7 on a usb key: hang at
efi_tpm_eventlog_init (LP: #1892827)
- efi/tpm: Verify event log header before parsing
-- Timo Aaltonen Tue, 08 Sep 2020
11:40:14 +0300
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12888
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892827
Title:
device doesn't boot with kernel older than v5.7.7 on a usb key: hang
at efi_tpm_eventlog_init
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Some systems may hang at boot. With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
This affects all mainline kernel since v5.2 to v5.7.6. Fix available in
v5.8-rc3 and has been backported to v5.7.7, v5.4.50.
[Fix]
Commit ea3cdcaa43b0 ("efi/tpm: Verify event log header before parsing")
fixes commit 6b0326190205 ("efi: Attempt to get the TCG2 event log in
the boot stub").
[Test Case]
So far it can be easily reproduced with a green installation of Focal on
USB key on a few Dell platforms.
[Regression Potential]
Low. This checks validity of tmp event log header before parsing them,
so it affects only platforms might generate invalid entries only.
[Other Info]
This affects -generic for eoan and oem-5.6 for focal, but the former has
be EOL-ed.
== Original Bug Description ==
[Summary] device doesn't boot with kernel older than v5.7.7 on USB key
[Steps to reproduce]
1. Try to boot a green installation of Ubuntu Focal on a USB key.
[Expected result]
Boot up normally.
[Actual result]
Stuck at "loading initial ramdisk". With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
[Failure rate]
10/10
[Additional information]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea3cdcaa43b08c9a747639f545b0ed5cca47f87e
("efi/tpm: Verify event log header before parsing") fixes in 6b0326190205
("efi: Attempt to get the TCG2 event log in the boot stub").
The fix is in linux-5.7.y and v5.8-rc3, and focal 5.4 and oem-5.6 are
affected.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-16-generic 5.8.0-16.17
ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
Uname: Linux 5.8.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2',
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p',
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq',
[Kernel-packages] [Bug 1894605] Re: gtp: unable to associate contextes to interfaces
** 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/1894605
Title:
gtp: unable to associate contextes to interfaces
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
When a user dump pdp contextes, it cannot associate them with existing
gtp interfaces. Thus, the dump is unusable.
This problem has been fixed in the upstream commit b274e47d9e3f ("gtp: add
GTPA_LINK info to msg sent to userspace"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b274e47d9e3f
[Test Case]
Create several gtp interfaces and setup PDP contextes on them. Perform
a dump with the genl command GTP_CMD_GETPDP.
[Regression Potential]
The patch affects only the gtp driver and is quite trivial. Thus, the
potential regressions are limited to this area and low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894605/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894977] Re: IBM-iobrick patches for Ubuntu 20.04
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894977
Title:
IBM-iobrick patches for Ubuntu 20.04
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hi,
The request is to backport
09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during
create and destroy
with it the below list (divided to four sets) is required.
most of the patches applied cleanly above focal tree four exceptions.
1. 806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
2. b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
3. 1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying
them
4. b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
the rejected hunks need to be manually applied.
The rejected hunks are due to true<-->1 false<-->0 exchange added support for
wc (b9358bdbc713) and other minor reasons.
set 0: Unrelated code cleanups (needed for applying cleanly the mr cache
set)
https://patchwork.kernel.org/cover/11170991/
909624d8db5b IB/cm: Use container_of() instead of typecast
6f26b2ac699c IB/mlx5: Remove unnecessary else statement
2d67c0798821 IB/mlx5: Remove unnecessary return statement
4b2a67362e78 RDMA/mlx5: Group boolean parameters to take less space
set 1: Rework the locking and datastructures for mlx5 implicit ODP
https://patchwork.kernel.org/cover/11181509/
46870b2391d5 RDMA/odp: Remove broken debugging call to invalidate_range
09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during
create and destroy
d561987f34f2 RDMA/mlx5: Do not store implicit children in the odp_mkeys
xarray
5256edcb98a1 RDMA/mlx5: Rework implicit ODP destroy
b70d785d237c RDMA/mlx5: Avoid double lookups on the pagefault path
3389baa831b6 RDMA/mlx5: Reduce locking in implicit_mr_get_data()
423f52d65005 RDMA/mlx5: Use an xarray for the children of an implicit ODP
54375e738295 RDMA/mlx5: Split implicit handling from pagefault_mr
9162420dde49 RDMA/mlx5: Set the HW IOVA of the child MRs to their place in
the tree
c2edcd69351f RDMA/mlx5: Lift implicit_mr_alloc() into the two routines that
call it
3d5f3c54e7bc RDMA/mlx5: Rework implicit_mr_get_data
74bddb3682f6 RDMA/mlx5: Delete struct mlx5_priv->mkey_table
806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
50211ec9443f RDMA/mlx5: Split sig_err MR data into its own xarray
fb985e278a30 RDMA/mlx5: Use SRCU properly in ODP prefetch
set 2: Consolidate the mmu notifier interval_tree and locking (only first
two patches from this set)
https://patchwork.kernel.org/cover/11240081/
99cb252f5e68 mm/mmu_notifier: add an interval tree notifier
56f434f40f05 mm/mmu_notifier: define the header pre-processor parts even if
disabled
also needed for applying mr cache set cleanly.
03232cc43cff IB/mlx5: Introduce and use mkey context setting helper routine
set 3: MR cache fixes and refactoring
https://www.spinics.net/lists/linux-rdma/msg89706.html
aad719dcf379 RDMA/mlx5: Allow MRs to be created in the cache synchronously
1c78a21a0c6f RDMA/mlx5: Revise how the hysteresis scheme works for cache
filling
b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
ad2d3ef46d2a RDMA/mlx5: Lock access to ent->available_mrs/limit when doing
queue_work
a1d8854aae4e RDMA/mlx5: Fix MR cache size and limit debugfs
1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying
them
b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
7c8691a396bd RDMA/mlx5: Rename the tracking variables for the MR cache
f743ff3b37df RDMA/mlx5: Replace spinlock protected write with atomic var
a3cfdd392811 {IB,net}/mlx5: Move asynchronous mkey creation to mlx5_ib
fc6a9f86f08a {IB,net}/mlx5: Assign mkey variant in mlx5_ib only
54c62e13ad76 {IB,net}/mlx5: Setup mkey variant before mr create command
invocation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1894977/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807682] Re: system does not start
Thanks g.bruno ..it has solved my headache -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807682 Title: system does not start Status in linux package in Ubuntu: Confirmed Bug description: The System does not start. When starting in recovery mode the error "failed to start Create Static Device Nodes in /dev. See 'systemctl status systemd-tmpfiles-setupd-dev.service' for details" is shown. When typing systemctl status systemd-tmpfiles-setupd-dev.service into the console, the answer is: Unit systemd-tmpfiles-setupd-dev.service could not be found. The System does only start in recovery mode and I would expect an normal start. Thanks for help in advance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 2025 F pulseaudio /dev/snd/controlC1: administrator 2025 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 10 10:42:07 2018 HibernationDevice: RESUME=UUID=6ffe8604-b66f-421e-afbd-50bcdeb4ff9e InstallationDate: Installed on 2012-05-11 (2404 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IwConfig: eth0 no wireless extensions. lono wireless extensions. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0c7307f0-bcbe-4a1e-8d04-3004f27151bc ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago) dmi.bios.date: 12/27/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-209 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnbluechipComputerAG:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr: dmi.sys.vendor: bluechip Computer AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896575] [NEW] [UBUNTU 20.04] syslog daemon stop running unexpectedly
You have been subscribed to a public bug: Example of how was detected that the syslog stop working, it has couple of days without reporting: root@ilzlnx4:~# tail -f /var/log/syslog Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664542] sd 3:0:0:2: [sdt] tag#81 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664543] sd 3:0:0:2: [sdt] tag#81 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664656] sd 4:0:0:2: [sdq] tag#32 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664658] sd 4:0:0:2: [sdq] tag#32 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664773] sd 5:0:0:2: [sdaa] tag#48 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664774] sd 5:0:0:2: [sdaa] tag#48 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664775] sd 5:0:0:2: [sdaa] tag#48 Sense Key : Illegal Request [current] root@ilzlnx4:~# date Thu 17 Sep 2020 08:59:41 PM MST ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s3903164 bugnameltc-188206 severity-high targetmilestone-inin--- -- [UBUNTU 20.04] syslog daemon stop running unexpectedly https://bugs.launchpad.net/bugs/1896575 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896575] [NEW] [UBUNTU 20.04] syslog daemon stop running unexpectedly
Public bug reported: Example of how was detected that the syslog stop working, it has couple of days without reporting: root@ilzlnx4:~# tail -f /var/log/syslog Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664542] sd 3:0:0:2: [sdt] tag#81 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664543] sd 3:0:0:2: [sdt] tag#81 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664656] sd 4:0:0:2: [sdq] tag#32 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664658] sd 4:0:0:2: [sdq] tag#32 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664773] sd 5:0:0:2: [sdaa] tag#48 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664774] sd 5:0:0:2: [sdaa] tag#48 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664775] sd 5:0:0:2: [sdaa] tag#48 Sense Key : Illegal Request [current] root@ilzlnx4:~# date Thu 17 Sep 2020 08:59:41 PM MST ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s3903164 bugnameltc-188206 severity-high targetmilestone-inin--- ** Tags added: architecture-s3903164 bugnameltc-188206 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896575 Title: [UBUNTU 20.04] syslog daemon stop running unexpectedly Status in linux package in Ubuntu: New Bug description: Example of how was detected that the syslog stop working, it has couple of days without reporting: root@ilzlnx4:~# tail -f /var/log/syslog Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664542] sd 3:0:0:2: [sdt] tag#81 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664543] sd 3:0:0:2: [sdt] tag#81 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664656] sd 4:0:0:2: [sdq] tag#32 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664658] sd 4:0:0:2: [sdq] tag#32 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664773] sd 5:0:0:2: [sdaa] tag#48 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664774] sd 5:0:0:2: [sdaa] tag#48 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664775] sd 5:0:0:2: [sdaa] tag#48 Sense Key : Illegal Request [current] root@ilzlnx4:~# date Thu 17 Sep 2020 08:59:41 PM MST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
With the 5.4.0-49 from focal-proposed the xsaves flag can now be passed into instances. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Incomplete Bug description: Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]
The corruption also happens in build 5.9.0-050900rc4drmintelnext20200915-generic but the error in dmesg does not, and it's less, it only happens on window management actions (switch window Surprisingly with that, restarting gnome-shell actually fixes the issue (it did not with normal kernel). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896091 Title: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915] Status in linux package in Ubuntu: Confirmed Bug description: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
@rhpot1991, Would you please try oem5.6 again?! the new version is released. #apt install linux-oem-5.6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
@Mike, Are the point 2&3 gone!? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
@Mike, Are the point 2&3 gone!? please also cat /proc/cmdline?! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Incomplete Bug description: Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
No. Same issue still happens. I'm now back to the LTS kernel, which received an update BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic with nvidia driver 450 The same issue still exist, and I think it got even more severe. Chrome will freeze even opening a new tab some time. Also the gnome animations are really really laggy, which could be a bug but I'm unsure if its ubuntu related. Still, I didn't have such issue on Fedora. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
Here is an example:
root@ubuntu1804hwe:~# uname -a
Linux ubuntu1804hwe 5.4.0-47-generic #51~18.04.1-Ubuntu SMP Sat Sep 5 14:35:50
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu1804hwe:~# cat test.c
#include
#include
#ifndef __section
# define __section(NAME) __attribute__((section(NAME), used))
#endif
static int (*bpf_skb_change_head)(void *ctx, int headroom, int flags) =
(void *) BPF_FUNC_skb_change_head;
__section("test")
int _test(struct __sk_buff *skb)
{
bpf_skb_change_head(skb, 14, 0);
return TC_ACT_OK;
}
char _license[] __section("license") = "GPL";
root@ubuntu1804hwe:~# clang -target bpf -I/usr/include/x86_64-linux-gnu/ -O2 -o
test.o -c test.c
root@ubuntu1804hwe:~# ip link add name dummy1 type dummy
root@ubuntu1804hwe:~# ip link set dummy1 up
root@ubuntu1804hwe:~# tc qdisc add dev dummy1 clsact
root@ubuntu1804hwe:~# tc filter add dev dummy1 egress matchall action bpf obj
./test.o sec test
Prog section 'test' rejected: Invalid argument (22)!
- Type: 4
- Instructions: 5 (0 over limit)
- License: GPL
Verifier analysis:
0: (b7) r2 = 14
1: (b7) r3 = 0
2: (85) call bpf_skb_change_head#43
unknown func bpf_skb_change_head#43
processed 3 insns (limit 100) max_states_per_insn 0 total_states 0
peak_states 0 mark_read 0
Error fetching program/map!
bad action parsing
parse_action: bad value (5:bpf)!
Illegal "action"
root@ubuntu1804hwe:~#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
Did you connect with 2.4g or 5g!? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
With a newer kernel, the last command succeeds (not output):
root@ubuntu1804hwe:~# uname -a
Linux ubuntu1804hwe 5.9.0-rc3-ge1b81391421b+6wind-net #1 SMP Mon Sep 21
19:31:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu1804hwe:~# tc filter add dev dummy1 egress matchall action bpf obj
./test.o sec test
root@ubuntu1804hwe:~#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
I forget to explain how to check that the tc command was accepted:
root@ubuntu1804hwe:~# tc filter show dev dummy1 egress
filter protocol all pref 49152 matchall chain 0
filter protocol all pref 49152 matchall chain 0 handle 0x1
not_in_hw
action order 1: bpf test.o:[test] id 9 tag 26af4b090d2d67ee jited
default-action pipe
index 1 ref 1 bind 1
root@ubuntu1804hwe:~#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
Did you connect with 2.4g or 5g!? Only play html5 on chrome can trigger the issue!? Did you ever try Firefox!? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
1. Did you connect with 2.4g or 5g!? 2. Only play html5 on chrome can trigger the issue!? Did you ever try Firefox!? 3. please prime-select intel & reboot, try -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890913] Re: init is using 100% of processor
*** This bug is a duplicate of bug 1891657 *** https://bugs.launchpad.net/bugs/1891657 ** This bug has been marked a duplicate of bug 1891657 systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] Re: Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably fails from any given boot
*** This bug is a duplicate of bug 1878279 *** https://bugs.launchpad.net/bugs/1878279 I have the same problem on a fresh install of manjaro. However, when I first live booted it from the usb, the touchpad worked, and it worked also after I have installed the system. It only stopped working when I switched the screen to the tablet mode. After that it was not recognized anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably fails from any given boot Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
This bug was fixed in the package thermald - 2.3-3 --- thermald (2.3-3) unstable; urgency=medium * Add Cometlake and Rocketlake CPU models (LP: #1896419) [Srinivas Pandruvada] - 7f2003ee911d Added Cometlake and Rocketlake CPU models -- Colin King Mon, 21 Sep 2020 16:04:11 +0100 ** Changed in: thermald (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Released Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896582] 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 1896582 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/1896582 Title: Enable i915 panel self refresh feature Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] PSR feature has been disabled by default because of below bug, "Dell XPS 13 (7390) Display Flickering - 19.10" https://bugs.launchpad.net/bugs/1849947 But this feature is important to pass the new energy start standard, so re-enable it and set default value to -1 "use per-chip default" [Fix] Revert the below commit to enable it again ecc718f31c90 UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms [Test] Verified on one Dell platform which panel supports PSR [Regression Potential] High, we plan to verify all platforms that shipped with 5.6 OEM kernel to make sure there is no flickering issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Linux Mint 19.3 user and I can also confirm this bug. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/virt-manager/+git/virt-manager/+merge/391055 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied:
[Kernel-packages] [Bug 1840784] [NEW] suspend.target: Job suspend.target/start failed with result 'dependency'.
You have been subscribed to a public bug: System fails to suspend, screen goes dark then turns back on. The lid won't suspend the system either. Things I've tried: turning off baloo, disconnecting from network. >From the logs: suspend.target: Job suspend.target/start failed with result 'dependency'. I've observed this behavior a often enough during the past month that suspend is unpredictable. Luckily my computer has a suspend state indicator - some laptops don't. A google search shows this to be a very old bug, earliest mentions are from 2014. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.3 ProcVersionSignature: Ubuntu 5.0.0-26.27-generic 5.0.21 Uname: Linux 5.0.0-26-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 20 17:34:30 2019 InstallationDate: Installed on 2018-11-15 (278 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-26-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to disco on 2019-04-27 (114 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- suspend.target: Job suspend.target/start failed with result 'dependency'. https://bugs.launchpad.net/bugs/1840784 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891454] Comment bridged from LTC Bugzilla
--- Comment From tmri...@de.ibm.com 2020-09-22 08:14 EDT---
I just installed bionic (Ubuntu 18.04) and installed the latest kernel from the
bionic-proposed repository. I can confirm that this bug is fixed.
The counter name DFLT_CCFINISH is available:
oot@t35lp46:~# uname -a
Linux t35lp46 4.15.0-119-generic #120-Ubuntu SMP Fri Sep 18 11:07:39 UTC 2020
s390x s390x s390x GNU/Linux
root@t35lp46:~# ls -l /sys/devices/cpum_cf/events/DFLT*
-r--r--r-- 1 root root 4096 Sep 22 14:10 /sys/devices/cpum_cf/events/DFLT_ACCESS
-r--r--r-- 1 root root 4096 Sep 22 14:10 /sys/devices/cpum_cf/events/DFLT_CC
-r--r--r-- 1 root root 4096 Sep 22 14:10
/sys/devices/cpum_cf/events/DFLT_CCFINISH
-r--r--r-- 1 root root 4096 Sep 22 14:10 /sys/devices/cpum_cf/events/DFLT_CYCLES
root@t35lp46:~# lsb_release -cs
bionic
root@t35lp46:~#
Verified ok.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications
[Kernel-packages] [Bug 1896598] Re: Enable LTR for endpoints behind VMD
** Tags added: oem-priority originate-from-1890125 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1896598 Title: Enable LTR for endpoints behind VMD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] PCIe links behind VMD may not be able to reach ASPM L1.2, because PCIe Link Tolenrence Reporting doesn't get programmed with a sensible value. [Fix] Temporarily hardcode LTR value, which is used by Windows, for NVMe devices behind VMD. [Test] With the patch applied, PCIe links can reach ASPM L1.2, hence the entire Intel SoC can reach deeper power saving state. [Regression Potential] This patch targets specifically Intel Tigerlake VMD bridges, so there won't be any regression since they are not on the market yet. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: changeDFLT_CCERROR counter name
Thx Thomas for the verification on bionic - adjusting tags ...
** 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/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840784] Re: suspend.target: Job suspend.target/start failed with result 'dependency'.
Your ethernet driver or hw is preventing suspend: [231201.406221] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x50 [e1000e] returns -2 [231201.406226] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [231201.406230] PM: Device :00:19.0 failed to suspend async: error -2 [231201.406291] PM: Some devices failed to suspend, or early wake event detected This looks like maybe this kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=198519 Which maybe is bug 1865570. In any case, this is not a systemd bug, it's a kernel bug, so I'm changing the affected pacakge to the kernel. ** Bug watch added: Linux Kernel Bug Tracker #198519 https://bugzilla.kernel.org/show_bug.cgi?id=198519 ** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840784 Title: suspend.target: Job suspend.target/start failed with result 'dependency'. Status in linux package in Ubuntu: New Bug description: System fails to suspend, screen goes dark then turns back on. The lid won't suspend the system either. Things I've tried: turning off baloo, disconnecting from network. From the logs: suspend.target: Job suspend.target/start failed with result 'dependency'. I've observed this behavior a often enough during the past month that suspend is unpredictable. Luckily my computer has a suspend state indicator - some laptops don't. A google search shows this to be a very old bug, earliest mentions are from 2014. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.3 ProcVersionSignature: Ubuntu 5.0.0-26.27-generic 5.0.21 Uname: Linux 5.0.0-26-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 20 17:34:30 2019 InstallationDate: Installed on 2018-11-15 (278 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-26-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to disco on 2019-04-27 (114 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896598] [NEW] Enable LTR for endpoints behind VMD
Public bug reported: [Impact] PCIe links behind VMD may not be able to reach ASPM L1.2, because PCIe Link Tolenrence Reporting doesn't get programmed with a sensible value. [Fix] Temporarily hardcode LTR value, which is used by Windows, for NVMe devices behind VMD. [Test] With the patch applied, PCIe links can reach ASPM L1.2, hence the entire Intel SoC can reach deeper power saving state. [Regression Potential] This patch targets specifically Intel Tigerlake VMD bridges, so there won't be any regression since they are not on the market yet. ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: Won't Fix => Invalid ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) 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/1896598 Title: Enable LTR for endpoints behind VMD Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] PCIe links behind VMD may not be able to reach ASPM L1.2, because PCIe Link Tolenrence Reporting doesn't get programmed with a sensible value. [Fix] Temporarily hardcode LTR value, which is used by Windows, for NVMe devices behind VMD. [Test] With the patch applied, PCIe links can reach ASPM L1.2, hence the entire Intel SoC can reach deeper power saving state. [Regression Potential] This patch targets specifically Intel Tigerlake VMD bridges, so there won't be any regression since they are not on the market yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896604] [NEW] Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances
Public bug reported: Hi, When running Groovy daily images on i3.metal instances a broken /dev/console is created. The char device appears to be writable but writing to it causes an Input/output error. This is breaking cloud-init, as it tries to log to /dev/console, and is likely to break other programs. On Focal: root@ip-172-31-24-163:~# ls -l /dev/console crw--- 1 root root 5, 1 Sep 21 16:07 /dev/console root@ip-172-31-24-163:~# echo x > /dev/console root@ip-172-31-24-163:~# On Groovy: root@ip-172-31-20-184:~# ls -l /dev/console crw--w 1 root tty 5, 1 Sep 21 16:03 /dev/console root@ip-172-31-20-184:~# echo x > /dev/console bash: echo: write error: Input/output error The Groovy kernel log has a [ 3.561696] fbcon: Taking over console line in it, which is not present in the Focal kernel log (5.4.0-1024-aws). Perhaps fbcon should be prevented from taking over console? ** Affects: cloud-images Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-images Importance: Undecided Status: New ** Summary changed: - Groovy kernel (5.8.0-1004-aws) created broken /dev/console on i3.metal instances + Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances -- 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/1896604 Title: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances Status in cloud-images: New Status in linux-aws package in Ubuntu: New Bug description: Hi, When running Groovy daily images on i3.metal instances a broken /dev/console is created. The char device appears to be writable but writing to it causes an Input/output error. This is breaking cloud- init, as it tries to log to /dev/console, and is likely to break other programs. On Focal: root@ip-172-31-24-163:~# ls -l /dev/console crw--- 1 root root 5, 1 Sep 21 16:07 /dev/console root@ip-172-31-24-163:~# echo x > /dev/console root@ip-172-31-24-163:~# On Groovy: root@ip-172-31-20-184:~# ls -l /dev/console crw--w 1 root tty 5, 1 Sep 21 16:03 /dev/console root@ip-172-31-20-184:~# echo x > /dev/console bash: echo: write error: Input/output error The Groovy kernel log has a [ 3.561696] fbcon: Taking over console line in it, which is not present in the Focal kernel log (5.4.0-1024-aws). Perhaps fbcon should be prevented from taking over console? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1896604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896616] 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 1896616 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/1896616 Title: set correct device size of loopback devices Status in linux package in Ubuntu: Incomplete Status in linux source package in Groovy: Incomplete Bug description: [Impact] SRU test ubuntu_ltp_syscalls is reporting the following message: 11:52:03 DEBUG| [stdout] ioctl_loop07.c:62: FAIL: /sys/block/loop4/size != 1024 got 2048 11:52:03 DEBUG| [stdout] ioctl_loop07.c:63: PASS: /sys/block/loop4/loop/sizelimit = 524288 11:52:03 DEBUG| [stdout] ioctl_loop07.c:66: PASS: LOOP_GET_STATUS64 gets correct lo_sizelimit(524288) 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79e5dc59e297 [Test case] $ sudo autotest/client/autotest-local -v autotest/client/tests/ubuntu_ltp_syscalls/control [Fix] Apply upstream commit 79e5dc59e297. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893752] Re: Get the extended DPCD according to the related field in the DPCD registers.
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893752 Title: Get the extended DPCD according to the related field in the DPCD registers. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] low, Just get one more DPCD from the extended register, compare them and get the faster one. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896616] [NEW] set correct device size of loopback devices
Public bug reported: [Impact] SRU test ubuntu_ltp_syscalls is reporting the following message: 11:52:03 DEBUG| [stdout] ioctl_loop07.c:62: FAIL: /sys/block/loop4/size != 1024 got 2048 11:52:03 DEBUG| [stdout] ioctl_loop07.c:63: PASS: /sys/block/loop4/loop/sizelimit = 524288 11:52:03 DEBUG| [stdout] ioctl_loop07.c:66: PASS: LOOP_GET_STATUS64 gets correct lo_sizelimit(524288) 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79e5dc59e297 [Test case] $ sudo autotest/client/autotest-local -v autotest/client/tests/ubuntu_ltp_syscalls/control [Fix] Apply upstream commit 79e5dc59e297. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Groovy) 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/1896616 Title: set correct device size of loopback devices Status in linux package in Ubuntu: Incomplete Status in linux source package in Groovy: Incomplete Bug description: [Impact] SRU test ubuntu_ltp_syscalls is reporting the following message: 11:52:03 DEBUG| [stdout] ioctl_loop07.c:62: FAIL: /sys/block/loop4/size != 1024 got 2048 11:52:03 DEBUG| [stdout] ioctl_loop07.c:63: PASS: /sys/block/loop4/loop/sizelimit = 524288 11:52:03 DEBUG| [stdout] ioctl_loop07.c:66: PASS: LOOP_GET_STATUS64 gets correct lo_sizelimit(524288) 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79e5dc59e297 [Test case] $ sudo autotest/client/autotest-local -v autotest/client/tests/ubuntu_ltp_syscalls/control [Fix] Apply upstream commit 79e5dc59e297. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895606] Re: Thunderbolt3 daisy chain sometimes doesn't work
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1895606 Title: Thunderbolt3 daisy chain sometimes doesn't work Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Focal: Triaged Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] Plug-in thunderbolt external monitor, and then plug-in thunderbolt external Hard drive on the external monitor, it sometimes can't detect the TBT storage. [Fix] Retry tb_drom_read_n() when failed fixes this issue. [Test] Verified on Dell platform with ASUS PA27AC Thunderbolt 3, and HP P800 TBT storage. [Regression Potential] Low, it only add 100ms delay and retry once. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1895718 Title: Fix non-working NVMe after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Won't Fix Bug description: [Impact] KIOXIA NVMe has a 10% chance to stop working after S3. [Fix] Enable ACS quirk on Intel CML root port. [Test] With the patch applied, KIOXIA NVMe always works after S3. [Regression Potential] ACS works at hardware level, so I can't really assess the risk of regression. Since Intel confirmed CML also needs ACS quirk, we can only trust them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896598] Re: Enable LTR for endpoints behind VMD
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1896598 Title: Enable LTR for endpoints behind VMD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] PCIe links behind VMD may not be able to reach ASPM L1.2, because PCIe Link Tolenrence Reporting doesn't get programmed with a sensible value. [Fix] Temporarily hardcode LTR value, which is used by Windows, for NVMe devices behind VMD. [Test] With the patch applied, PCIe links can reach ASPM L1.2, hence the entire Intel SoC can reach deeper power saving state. [Regression Potential] This patch targets specifically Intel Tigerlake VMD bridges, so there won't be any regression since they are not on the market yet. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Hi Petar, Thanks for providing the files. The original issue, boot failure, seems to be a conflict between the 5.4 kernel and the intel-microcode blob, since the same blob works fine in the 4.15 kernel. (For the printout alignment issue, let's track that on another bug report.) Let's try to bisect when this microcode/kernel conflict started. Could you please test with: 1) the 5.4.0-26 kernel from focal-release? $ sudo apt install linux-image-5.4.0-26-generic (you might also need linux-modules-extra-5.4.0-26-generic and/or linux- headers-5.4.0-26-generic depending on your hardware; please check if those are installed with 'dpkg -l | grep linux-modules-extra' and similarly for headers) 2) the 5.3.0-67 kernel from bionic? (current HWE kernel) $ echo 'deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted' | sudo tee /etc/apt/sources.list.d/bionic.list $ sudo apt update $ sudo apt install linux-image-5.3.0-67-generic # same observation for modules-extra and headers. $ sudo rm /etc/apt/sources.list.d/bionic.list Please confirm whether or not these kernels can boot without dis_ucode_ldr. Thanks, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896646] Re: bluetooth no longer installed
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1896646 Title: bluetooth no longer installed Status in bluez package in Ubuntu: New Bug description: 22 september 2020 update removed bluetooth capability. No Bluetooth hardware detected by system, cannot turn on or add devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 22 12:53:31 2020 InstallationDate: Installed on 2019-12-07 (290 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: ASUSTeK COMPUTER INC. X556UAM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UAM.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UAM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UAM.305:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX556UAM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UAM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1896646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
Hello Kai-Chuan, or anyone else affected, Accepted thermald into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/1.9.1-1ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Released Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896655] 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/1896655 Title: Touchpad stopped responding after upgrading to the latest kernel Status in linux package in Ubuntu: Confirmed Bug description: No response from the touchpad at all! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cyberdragon 4832 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 00:29:00 2020 InstallationDate: Installed on 2020-07-25 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1770:ff00 MSI EPF USB MSI EPF USB Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GV62 7RD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=c3805fb0-1532-4ac8-b55b-c18827942e04 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.324 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGV627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GV dmi.product.name: GV62 7RD dmi.product.sku: 16J9.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896646] [NEW] bluetooth no longer installed
You have been subscribed to a public bug: 22 september 2020 update removed bluetooth capability. No Bluetooth hardware detected by system, cannot turn on or add devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 22 12:53:31 2020 InstallationDate: Installed on 2019-12-07 (290 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: ASUSTeK COMPUTER INC. X556UAM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UAM.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UAM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UAM.305:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX556UAM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UAM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- bluetooth no longer installed https://bugs.launchpad.net/bugs/1896646 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895615] Re: Backlight adjustment doesn't work on Google Pixel Slate
It is a good idea to send your patch to below kernel's mailing lists so this can be reviewed by broader audiences to confirm it will work in all scenario. INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative chipsets) M: Jani Nikula M: Joonas Lahtinen M: Rodrigo Vivi L: intel-...@lists.freedesktop.org Note: you can also run kernel script "./scripts/get_maintainer.pl dpcd59.patch" for all parties who will be interested in this patch. You can also include "Cc: sta...@vger.kernel.org" in your patch so it will be included to previous stable kernels (see https://www.kernel.org/doc/Documentation/process/stable-kernel- rules.rst) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895615 Title: Backlight adjustment doesn't work on Google Pixel Slate Status in linux package in Ubuntu: Confirmed Bug description: The Pixel Slate/nocturne backlight does not work due to DPCD logic not identifying the DPCD backlight connection since there is no PWM on the nocturne or eve devices. ChromeOS documentation of disconnected PWM: https://chromium- review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1171922 Discussion of issue & solution: https://github.com/EmbeddedAndroid /linux-eve/issues/2#issuecomment-561382927 This can be fixed with a simple patch which I have applied successfully to mainline 5.9-rc5: https://gist.github.com/satmandu/d6c2192f66cd14525049fd34d356d71d Luckily the Ubuntu kernel patches set i915.enable_psr=0 which keeps Panel Self Refresh from dimming the backlight at boot, but that isn't even needed for this device once the backlight is hooked up correctly. (As a bonus the keyboard backlight also starts working properly at boot.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-lowlatency 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4 Uname: Linux 5.8.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Sep 14 23:52:45 2020 InstallationDate: Installed on 2020-08-24 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 18d1:5030 Google Inc. Hammer Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nocturne ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-lowlatency root=UUID=90e26b2a-aaad-4576-8e90-1962b97d4e96 ro fsck.repair=yes fsck.mode=force PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-18-lowlatency N/A linux-backports-modules-5.8.0-18-lowlatency N/A linux-firmware 1.190 SourcePackage: linux StagingDrivers: ipu3_imgu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: Google_Nocturne.10984.90.0 dmi.board.name: Nocturne dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrGoogle_Nocturne.10984.90.0:bd06/04/2019:br4.0:efr0.0:svnGoogle:pnNocturne:pvr1.0:rvnGoogle:rnNocturne:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nocturne dmi.product.name: Nocturne dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895947] Re: backport tls-rx to ubuntu 5.8
** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895947 Title: backport tls-rx to ubuntu 5.8 Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Hi, [Impact] The request here is to backport support for ktls-rx from upstream 5.9 to Ubuntu 20.10/20.04-HWE 5.8 kernel. [Other Info] list of required patches: (1 patch) from https://patchwork.ozlabs.org/project/netdev/patch/20200626055943.99943-3-sae...@mellanox.com/ 2d1b69ed65ee net/mlx5: kTLS, Improve TLS params layout structures (needed to apply ‘net/mlx5e: kTLS, Improve TLS feature modularity’ below cleanly) (15 patches ) https://patchwork.ozlabs.org/project/netdev/list/?series=186181=* a29074367b34 net/mlx5e: kTLS, Improve rx handler function call ed9a7c53b878 net/mlx5e: kTLS, Cleanup redundant capability check c5607360ec4e net/mlx5e: Increase Async ICO SQ size 76c1e1ac2aae net/mlx5e: kTLS, Add kTLS RX stats 0419d8c9d8f8 net/mlx5e: kTLS, Add kTLS RX resync support ed9b7646b06a net/tls: Add asynchronous resync acb5a07aaf27 Revert "net/tls: Add force_resync for driver resync" 1182f3659357 net/mlx5e: kTLS, Add kTLS RX HW offload support df8d866770f9 net/mlx5e: kTLS, Use kernel API to extract private offload context 7d0d0d86ec6c net/mlx5e: kTLS, Improve TLS feature modularity 5229a96e59ec net/mlx5e: Accel, Expose flow steering API for rules add/del c062d52ac24c net/mlx5e: Receive flow steering framework for accelerated TCP flows b8922a73ec3e net/mlx5e: API to manipulate TTC rules destinations c293ac927fbb net/mlx5e: Refactor build channel params 8d94b590f1e4 net/mlx5e: Turn XSK ICOSQ into a general asynchronous one (3 bug fixes patches submitted to upstream and should be accepted soon - attached) net/mlx5e: kTLS, Fix napi sync and possible use-after-free net/mlx5e: Use synchronize_rcu to sync with NAPI net/mlx5e: Use RCU to protect rq->xdp_prog all patches are applied cleanly beside 1182f3659357 net/mlx5e: kTLS, Add kTLS RX HW offload support that has one hunk rejected in file: drivers/net/ethernet/mellanox/mlx5/core/en_main.c function: mlx5e_init_nic_rx the rejection is caused by and extra #ifdef statement inserted by commit f4aebbfb56ed0c186adbeb2799df836da50f78e3 here we just need to add manually the needed lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
Hey Jim, That's very good news! I believe Alex should send you more test kernels, with different sets of patches included/removed, so to bisect/identify which specific patch(es) resolve the problem. If you could help with testing that as well, that would be great, so a smaller patch(set) can be put into the Ubuntu stable release(s). cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Confirmed Bug description: Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663] acpi_ec_space_handler+0xd4/0x280 Sep 20 11:35:33 laxmi kernel: [232492.303666]
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Thanks a lot for catching up with this @mfo. And Richard for all the tests. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
problem seems gone since 5.4.0-48-generic #52 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861295] Re: Bluetooth not working
@kaihengfeng yes both BT and Wifi stop working intermittently. I found a fix that will bring both the BT and Wifi back if they go down, however. By removing the BT-related modules from the kernel, issuing a USB reset, and then loading the BT modules back into the kernel. BT will work after that. For the Wifi, I reset the PCI device via Linux and rescan the PCI bus, and then I set the wireless mode to "managed" and it works again. I set systemd to remove the Wifi module from the kernel before suspending, and then have systemd re-insert the Wifi module into the kernel upon waking up from sleep. I can include the scripts I use to do this, if anyone is interested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861295 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 19.10 on this Macbook Pro a couple of weeks ago. Bluetooth was working during the first days, but now it won't work anymore. Here is the output of dmesg | grep -i blue, showing some errors that might be interesting: > dmesg | grep -i blue [1.562871] usb 1-3: Product: Bluetooth USB Host Controller [2.104835] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0003/input/input10 [2.164582] hid-generic 0003:05AC:8290.0003: input,hidraw2: USB HID v1.11 Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input0 [2.164685] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0004/input/input11 [2.164761] hid-generic 0003:05AC:8290.0004: input,hidraw3: USB HID v1.11 Mouse [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input1 [3.605086] Bluetooth: Core ver 2.22 [3.605103] Bluetooth: HCI device and connection manager initialized [3.605107] Bluetooth: HCI socket layer initialized [3.605109] Bluetooth: L2CAP socket layer initialized [3.605112] Bluetooth: SCO socket layer initialized [5.720427] Bluetooth: hci0: command 0x0c03 tx timeout [6.637120] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.637122] Bluetooth: BNEP filters: protocol multicast [6.637126] Bluetooth: BNEP socket layer initialized [ 13.876494] Bluetooth: hci0: BCM: Reset failed (-110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: maurizio 1377 F pulseaudio /dev/snd/controlC0: maurizio 1377 F pulseaudio /dev/snd/controlC1: maurizio 1377 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 14:16:01 2020 InstallationDate: Installed on 2020-01-23 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Apple Inc. MacBookPro12,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=adc45397-ab6d-4a20-8795-b9e7f3d733b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 188.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr188.0.0.0.0:bd10/30/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
Looks like it is working! At any rate the old kernel started having the problem much sooner while this one is still fine. Thanks very much for your help with this! > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ?
[Kernel-packages] [Bug 1840784] 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/1840784 Title: suspend.target: Job suspend.target/start failed with result 'dependency'. Status in linux package in Ubuntu: Confirmed Bug description: System fails to suspend, screen goes dark then turns back on. The lid won't suspend the system either. Things I've tried: turning off baloo, disconnecting from network. From the logs: suspend.target: Job suspend.target/start failed with result 'dependency'. I've observed this behavior a often enough during the past month that suspend is unpredictable. Luckily my computer has a suspend state indicator - some laptops don't. A google search shows this to be a very old bug, earliest mentions are from 2014. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.3 ProcVersionSignature: Ubuntu 5.0.0-26.27-generic 5.0.21 Uname: Linux 5.0.0-26-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 20 17:34:30 2019 InstallationDate: Installed on 2018-11-15 (278 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-26-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to disco on 2019-04-27 (114 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
Installed, give me some time to do some tests and see if the issue is fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Update Released
The verification of the Stable Release Update for gdm3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Fix Committed Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in gdm3 source package in Focal: Fix Released Status in gnome-session source package in Focal: Invalid Status in grub2 source package in Focal: Invalid Status in nvidia-graphics-drivers-390 source package in Focal: Invalid Status in nvidia-graphics-drivers-430 source package in Focal: Invalid Status in nvidia-graphics-drivers-435 source package in Focal: Invalid Status in nvidia-graphics-drivers-440 source package in Focal: Invalid Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Thanks Richard and Marco! Looking forward for further testing/results. :) Fingers crossed it will all go well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Tags removed: sts-sponsor-mfo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Released Status in makedumpfile source package in Bionic: Fix Released Status in makedumpfile source package in Eoan: Fix Released Status in makedumpfile source package in Focal: Fix Released Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Oh sorry, I'm not familiar with OCFS2, but maybe you need to have both servers/whole cluster on same kernel version to verify this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Dear Mauricio, now it seems working, but probably we need to test it more in details. Best, Marco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Hi Mauricio I have updated the kernel using apt (and ran all the other available updates at the same time) on the SECOND server in this cluster. The update to 5.4.0-48-generic seems to have WORKED OK. However, as these are live servers and the end users were desperate to use their data, I rsync'd their data in the first site out to USB disk, so I haven't tested the first server. I will have to do this over the weekend so that user disruption is minimised. I will verify by Monday (28th) at the latest, maybe before. But to see the second server working, allowing writes to the ocfs filesystem makes me think it's gonna work when the two are syncing again. Thanks for your work! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This bug was fixed in the package gdm3 - 3.36.3-0ubuntu0.20.04.1
---
gdm3 (3.36.3-0ubuntu0.20.04.1) focal; urgency=medium
[ Iain Lane ]
* New upstream release (LP: #1894874).
- Always use separate session bus for greeter sessions
This runs dbus-run-session, so the binary needs to be available
- Chrome remote desktop fix
- Don't hardcode path to plymouth
- Fixes for when GDM isn't started on its configured initial VT (LP:
#1845801)
- keyutils has a .pc file so use it
- User switching fix
* debian/{control,gbp.conf}: Update for ubuntu/focal & upstream/3.36.x
[ Simon McVittie ]
* Add Depends on dbus, for dbus-run-session
* Update symbols file.
This ignores a change to private symbols: gdm_find_display_session_for_uid
isn't declared in a public header, and nothing in Debian/Ubuntu seems to
call it.
-- Iain Lane Tue, 08 Sep 2020 18:01:39 +0100
** Changed in: gdm3 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing gnome-session-binary fixes it, or just not using automatic
login.
Status in OEM Priority Project:
Fix Committed
Status in gdm3 package in Ubuntu:
Fix Released
Status in gnome-session package in Ubuntu:
Invalid
Status in grub2 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Invalid
Status in gdm3 source package in Focal:
Fix Released
Status in gnome-session source package in Focal:
Invalid
Status in grub2 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-390 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-430 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-435 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
Invalid
Bug description:
[ Impact ]
In some platforms with specific Nvidia cards (with nvidia-driver-440), enable
auto-login (either during installation or after installation) will fail (either
stuck in gdm login screen and not able to login even typing correct password).
[ Test Case ]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1) Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically" during installation.
2) Install groovy daily build with default options, after installation
completed:
2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive.
2.2) Enable "Login automatically" from system settings.
Then reboot.
[Expected result]
System will boot into desktop environment without the login page.
[Actual result]
System boots to login page, and can't login to desktop environment with the
correct password.
[ Regression potential ]
Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0)
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3]
and it works good. It passed the 30 times reboot stress test by using
stress/reboot_30 from checkbox.
[1] sha256sum:
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
[2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4
https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01
[3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801
---
I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
login screen (which I shouldn't; I have auto login enabled), and
logging in just takes me back to the same user selection screen even
though the password is correct.
If I switch to a TTY and run `sudo pkill gnome-session-binary`,
logging in through GDM starts working again.
I should add that the do-release-upgrade was rocky; I did it in a
terminal from within gnome, went away for a while, and when I
returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
dpkg --configure -a` and complete the upgrade, but I don't know if
something's still messed up due to that.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX
