[Kernel-packages] [Bug 1872856] Re: whole system freezes frequently
Hi, I just found this bug by just googling for "kernel 5.3.0-46
problem", funny...
I got a very similar behaviour this week when I updated to kernel
5.3.0-46-generic and IntelliJ IDEA Ultimate:
Just by scrolling the editor by the scrollbar handle a bit up and down,
my PC freezes up for a few seconds (I'm only able to move the mouse
pointer).
I could pinpoint the problem to Xorg producing higher and higher IOWait
when I'm scrolling, up to the point when it freezes. Then I tried
several window managers (KDE, XFCE, MATE, GNOME) with and without
compositing, all made no difference. The only thing that helped was
switching to Wayland in KDE and GNOME (which is not stable nor usable
for me).
Can you confirm any of this with kernels >=5.3.0-46?
At the moment I have to switch back to kernel 5.3.0-45-generic, no
problem there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872856
Title:
whole system freezes frequently
Status in linux-meta package in Ubuntu:
New
Bug description:
version_signature -> Ubuntu 5.3.0-48.41-generic 5.3.18
uname-a -> Linux work 5.3.0-48-generic #41-Ubuntu SMP Fri Apr 10 06:59:18 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
dmesg and lspci logs attached.
$> lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
The problem is with the kernel versions 5.3.0-48-generic, 5.3.0-46-generic,
and 5.3.0-45-generic.
Kernel version 5.3.0-42-generic is working fine.
Steps to reproduce:
Download some Java project (say, https://github.com/yegor256/cactoos/)
Open this Java project in IntellijIdea community version
(https://www.jetbrains.com/idea/)
Type Ctrl+Shift+f (to search for all the files in a project)
This freezes the system for 7-8 seconds.
Similar behavior was seen when browsing firefox and or switching
windows (Alt+Tab). But not that easy to reproduce.
The problem does not occur when running heavy memory task (i.e.
stress-ng --vm-bytes $(awk '/MemAvailable/{printf "%d\n", $2 * 0.9;}'
< /proc/meminfo)k --vm-keep -m 1)
The problem does not occur when running heavy cpu task (i.e. sudo
stress-ng --cpu 8 --timeout 60 --metrics-brief)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1872856/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872856] Re: whole system freezes frequently
Me too (problem also with kernel 5.3.0-51-generic). Has anyone tried a 5.4
kernel?
If not, I'll install IntelliJ on my second notebook (which has kernel 5.4).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872856
Title:
whole system freezes frequently
Status in linux-meta package in Ubuntu:
Confirmed
Bug description:
version_signature -> Ubuntu 5.3.0-48.41-generic 5.3.18
uname-a -> Linux work 5.3.0-48-generic #41-Ubuntu SMP Fri Apr 10 06:59:18 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
dmesg and lspci logs attached.
$> lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
The problem is with the kernel versions 5.3.0-48-generic, 5.3.0-46-generic,
and 5.3.0-45-generic.
Kernel version 5.3.0-42-generic is working fine.
Steps to reproduce:
Download some Java project (say, https://github.com/yegor256/cactoos/)
Open this Java project in IntellijIdea community version
(https://www.jetbrains.com/idea/)
Type Ctrl+Shift+f (to search for all the files in a project)
This freezes the system for 7-8 seconds.
Similar behavior was seen when browsing firefox and or switching
windows (Alt+Tab). But not that easy to reproduce.
The problem does not occur when running heavy memory task (i.e.
stress-ng --vm-bytes $(awk '/MemAvailable/{printf "%d\n", $2 * 0.9;}'
< /proc/meminfo)k --vm-keep -m 1)
The problem does not occur when running heavy cpu task (i.e. sudo
stress-ng --cpu 8 --timeout 60 --metrics-brief)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1872856/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885266] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387499/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313
[Kernel-packages] [Bug 1885266] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387503/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 23
[Kernel-packages] [Bug 1885266] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387497/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313
[Kernel-packages] [Bug 1885266] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387498/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313142] i
[Kernel-packages] [Bug 1885266] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387502/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.31314
[Kernel-packages] [Bug 1885266] Re: iwlwifi causes random UI freezes
apport information ** Tags added: apport-collected ** Description changed: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313142] irq_thread_fn+0x28/0x60 [ 2313.313144] irq_thread+0xda/0x170 [ 2313.313147] ? irq_forced_thread_fn+0x80/0x80 [ 2313.313149] kthread+0x104/0x140 [ 2313.313151] ? irq_thread_check_affinity+0xf0/0xf0 [ 2313.313153] ? kthread_park+0x90/0x90 [ 2313.313156] ret_from_fork+0x35/0x40 [ 2313.313158] ---[ end trace
[Kernel-packages] [Bug 1885266] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387496/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [
[Kernel-packages] [Bug 1885266] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387495/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313142] irq
[Kernel-packages] [Bug 1885266] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387504/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0x
[Kernel-packages] [Bug 1885266] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387501/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.31314
[Kernel-packages] [Bug 1885266] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387500/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313142] i
[Kernel-packages] [Bug 1885266] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387505/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0
[Kernel-packages] [Bug 1885266] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387507/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313142]
[Kernel-packages] [Bug 1885266] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387508/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313142]
[Kernel-packages] [Bug 1885266] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387509/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwi
[Kernel-packages] [Bug 1885266] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1885266/+attachment/5387506/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Confirmed Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 23
[Kernel-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
And it's an issue with 20.04 daily builds. Hardware is Lenovo P73 with NVIDIA RTX-5000 Q-Max. So how can the driver be made to register the backlight device? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-settings package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872856] Re: whole system freezes frequently
I think it was fixed with 5.3.0-55, at least I could not reproduce it
(5.3.0-55.49).
Same for newest version of kernel 5.4.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872856
Title:
whole system freezes frequently
Status in linux-meta package in Ubuntu:
Confirmed
Bug description:
version_signature -> Ubuntu 5.3.0-48.41-generic 5.3.18
uname-a -> Linux work 5.3.0-48-generic #41-Ubuntu SMP Fri Apr 10 06:59:18 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
dmesg and lspci logs attached.
$> lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
The problem is with the kernel versions 5.3.0-48-generic, 5.3.0-46-generic,
and 5.3.0-45-generic.
Kernel version 5.3.0-42-generic is working fine.
Steps to reproduce:
Download some Java project (say, https://github.com/yegor256/cactoos/)
Open this Java project in IntellijIdea community version
(https://www.jetbrains.com/idea/)
Type Ctrl+Shift+f (to search for all the files in a project)
This freezes the system for 7-8 seconds.
Similar behavior was seen when browsing firefox and or switching
windows (Alt+Tab). But not that easy to reproduce.
The problem does not occur when running heavy memory task (i.e.
stress-ng --vm-bytes $(awk '/MemAvailable/{printf "%d\n", $2 * 0.9;}'
< /proc/meminfo)k --vm-keep -m 1)
The problem does not occur when running heavy cpu task (i.e. sudo
stress-ng --cpu 8 --timeout 60 --metrics-brief)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1872856/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885266] Re: Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi causes random UI freezes
I didn't receive confirmation about the mainline kernel to use. In the meantime I created a file called /etc/modprobe.d/iwl.conf and filled it with the following: options iwlwifi 11n_disable=1 swcrypto=0 bt_coex_active=0 power_save=0 options iwlmvm power_scheme=1 options iwlwifi d0i3_disable=1 options iwlwifi uapsd_disable=1 options iwlwifi lar_disable=1 After rebooting, the freezes stopped. It is clearly an issue with some of the options of the driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi causes random UI freezes Status in linux package in Ubuntu: Incomplete Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106]
[Kernel-packages] [Bug 1885266] Re: Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi causes random UI freezes
I wish I could place a date on when the issues started. My guess is that it was either late May or early June. The issue happens quite frequently in the last updates and now I get sometimes a black screen on the laptop while the external monitor remains working. A restart of the system brings things back to work but the freezes quite happening maybe even more frequently now. I will try the mainline kernel and report results. The list of kernels I had in the system as per your command is below. I would say that version 5.4.0-29 was definitely working fine and that it was one of the 5.4.0-3x release that started the problem. Aug 03 22:01:02 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Aug 01 06:52:50 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 29 09:48:41 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 26 10:15:00 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 24 13:44:02 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 23 08:11:18 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 21 08:15:04 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 15 17:41:07 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 14 08:33:03 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 11 13:24:59 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 10 07:46:22 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 08 08:04:09 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 05 12:58:30 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 03 08:41:41 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jul 02 16:08:33 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jun 26 10:49:52 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau Jun 26 09:57:03 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro Jun 25 21:53:56 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro Jun 20 18:15:04 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro Jun 18 11:35:43 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro Jun 16 18:26:37 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro Jun 15 16:43:07 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_x13bv2@autozsys_1kiv8w/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_x13bv2@autozsys_1kiv8w ro Jun 15 06:45:14 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_x13bv2@/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_x13bv2 ro Jun 12 14:25:05 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@autozsys_x65hvt/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_w5d0b7@autozsys_x65hvt ro Jun 11 13:14:30 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-37-generic root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro Jun 08 21:27:44 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-33-generic root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro Jun 01 20:50:11 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-33-generic root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro May 31 13:00:17 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-33-generic root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro May 28 10:52:58 kernel: Command line: BOOT_IMAGE=/BOOT/ubuntu_v46mn6@/vmlinuz-5.4.0-33-generic root=ZFS=rpool/ROOT/ub
[Kernel-packages] [Bug 1885266] Re: Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi causes random UI freezes
The link you sent says: >Note: If you are testing to isolate a bug or regression, please do not use the >daily folder. >Instead, use the latest mainline kernel at the top from the link above. Could you clarify if you want me to test the latest mainline kernel (5.8) or the latest in the 5.4? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi causes random UI freezes Status in linux package in Ubuntu: Incomplete Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35
[Kernel-packages] [Bug 1329291] Re: Terrible crackling/choppy sound with the Intel Z97 chipset
*** This bug is a duplicate of bug 1321421 *** https://bugs.launchpad.net/bugs/1321421 What command you should do int terminal to fix it? Sorry but I dont' t understand the procedure on the linked page. Is it fixed on Ubuntu 14.10? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1329291 Title: Terrible crackling/choppy sound with the Intel Z97 chipset Status in linux package in Ubuntu: Triaged Bug description: I found this patch: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=77f07800cb456bed6e5c345e6e4e83e8eda62437 After patching my kernel (3.13.0-29) with this, the sound is working great! Please include this patch in the next Ubuntu kernel. :-) Kind regards from Norway. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jorn 2324 F pulseaudio /dev/snd/pcmC1D0p: jorn 2324 F...m pulseaudio /dev/snd/controlC0: jorn 2324 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 12 13:22:15 2014 HibernationDevice: RESUME=UUID=d7cd8865-08ce-46b5-9807-68163de5a0e9 InstallationDate: Installed on 2014-06-03 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. Z97N-WIFI ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=01a0b9f1-6500-4af6-9e91-49a01464c396 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd04/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97N-WIFI dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628694] Re: Ubuntu 16.10 bluetooth doesn't work
I have the same problem, but i'm on a Dell XPS13-9350 with BCM4350 (installed it myself before the dev edition came out). I have a headset Jabra Evo, that used to work fine in 15.10, stutters on 16.04.1 and does not detect on 16.10. I also have trouble with an other headset, a plantronics voyager legend. It worked fine on 15.10, reconnecting/detection issues in 16.04 and i haven't tried 16.10 yet. Let me know what I can do to give more information. In the meantime, i'm considering placing back the original intel card to see if that makes a difference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628694 Title: Ubuntu 16.10 bluetooth doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I'm trying unsuccessfully to connect headphone via bluetooth. Configuration: Ubuntu-gnome 16:10, Dell XPS-15. lspci shows: 06:00.0 Network controller: Broadcom Limited BCM4352 802.11ac Wireless Network Adapter (rev 03) lsusb shows: Bus 003 Device 004: ID 0a5c:216f Broadcom Corp. BCM20702A0 Bluetooth Below is what I see in my syslog: Sep 27 18:19:22 alex-XPS-15-9530 /usr/lib/gdm3/gdm-x-session[4781]: (II) modeset(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher gufw (missing desktop file) Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher landscape-client-settings (missing desktop file) Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher ubuntuone-installer (missing desktop file) Sep 27 18:19:22 alex-XPS-15-9530 dbus-daemon[4819]: Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' Sep 27 18:19:22 alex-XPS-15-9530 dbus-daemon[4819]: Activation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found. Sep 27 18:20:29 alex-XPS-15-9530 systemd[1]: Starting Cleanup of Temporary Directories... Sep 27 18:20:29 alex-XPS-15-9530 systemd-tmpfiles[6783]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Sep 27 18:20:29 alex-XPS-15-9530 systemd[1]: Started Cleanup of Temporary Directories. Sep 27 18:20:41 alex-XPS-15-9530 bluetoothd[6689]: a2dp-sink profile connect failed for 00:18:16:07:03:FD: Protocol not available --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 2188 F pulseaudio /dev/snd/controlC0: alex 2188 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=9c7af056-2269-4b01-9b5c-eeb6e7b3b43a InstallationDate: Installed on 2016-06-01 (119 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160426) MachineType: Dell Inc. XPS 15 9530 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip disk lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460768] Re: Unable to build kernel 3.19.0-18
Confirmed in 4.2. My fix: Go to the directory ubuntu/vbox/ Inside each directory (vboxsf vboxguest, ...) do ln -s ../include/ then it will compile fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460768 Title: Unable to build kernel 3.19.0-18 Status in One Hundred Papercuts: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: There is a bug during compiling kernel version 3.19.0-18. First I executed patch file from archive linux_3.19.0-18.18.diff.gz and source https://launchpad.net/ubuntu/+source/linux/3.19.0-18.18 Then I executed make-kpkg --initrd buildpackage with attached config file. But I got a compiling error: CC [M] ubuntu/vbox/vboxguest/VBoxGuest-linux.o In file included from :0:0: ././include/linux/kconfig.h:46:1: fatal error: ./ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or directory #endif /* __LINUX_KCONFIG_H */ ^ compilation terminated. make[6]: *** [ubuntu/vbox/vboxguest/VBoxGuest-linux.o] Error 1 make[5]: *** [ubuntu/vbox/vboxguest] Error 2 make[4]: *** [ubuntu/vbox] Error 2 make[3]: *** [ubuntu] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1460768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Observed with VS Code and VS Codium as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518457]
Reproduced on latest centos kernel 3.10.0-1160.53 It's so strange that this keeps on happening I tried disabling swap and everything but it doesn't care. There's 100 GB free ram and yet it happens -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
I have the same problem. In my case, it is caused by upgrading the NVIDIA driver metapackage to 510 from 470. I am very grateful to @lockszmith for sharing his steps on https://askubuntu.com/questions/1388997/zsys-commit-service-fails-with- couldnt-promote-dataset-not-a-cloned-filesy It really makes me very wary of upgrading my systems. Those are LTS releases and things like this are very concerning. -- 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/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947568] Re: cannot promote clone: "not a cloned filesystem"
I have the same problem. In my case, it is caused by upgrading the NVIDIA driver metapackage to 510 from 470. -- 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/1947568 Title: cannot promote clone: "not a cloned filesystem" Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a zvol containing a Windows image for a virtual machine. After restarting the system a node under /dev/zvol/... was not created for the virtual disk and no amount of prompting by `udevadm trigger` helped. Instead I created a snapshot from the most recent hourly backup: # zfs clone rpool/vm/windows/windows10/hda@hourly07 rpool/vm/windows/windows10/hda-new # zfs promote rpool/vm/windows/windows10/hda-new cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem (didn't work here but carried on assuming something can be sorted later) # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda Entries in /dev appeared and I could start the virtual machine. Trying to promote the clone gives 'not a cloned filesystem' message. I later renamed the old zvol and tried to cleanup: # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted # zfs destroy rpool/to-be-deleted@hourly07 cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones use '-R' to destroy the following datasets: rpool/vm/windows/windows10/hda@hourly09 rpool/vm/windows/windows10/hda@hourly10 rpool/vm/windows/windows10/hda # zfs promote rpool/vm/windows/windows10/hda cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem # zfs get origin rpool/vm/windows/windows10/hda NAMEPROPERTY VALUE SOURCE rpool/vm/windows/windows10/hda originrpool/to-be-deleted@hourly07 - # zfs get clones rpool/to-be-deleted@hourly07 NAME PROPERTY VALUE SOURCE rpool/to-be-deleted@hourly07 clonesrpool/vm/windows/windows10/hda - The dependency between seems to be as expected. This small test fails in the same way: # zfs create -V1G rpool/vm/test # zfs snapshot rpool/vm/test@test2 # zfs clone rpool/vm/test@test2 rpool/vm/test3 # zfs promote rpool/vm/test3 cannot promote 'rpool/vm/test3': not a cloned filesystem # zfs get origin rpool/vm/test3 NAMEPROPERTY VALUESOURCE rpool/vm/test3 originrpool/vm/test@test2 - # zfs get clones rpool/vm/test@test2 NAME PROPERTY VALUE SOURCE rpool/vm/test@test2 clonesrpool/vm/test3 - All the zpool members are ONLINE and no errors are reported. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal # uname -r 5.11.0-37-generic # modinfo zfs | grep -i version version:2.0.2-1ubuntu5.1 srcversion: F267DF7B3FFB43AFE76257D vermagic: 5.11.0-37-generic SMP mod_unload modversions # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.13 Version table: 0.8.3-1ubuntu12.13 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 0.8.3-1ubuntu12.12 100 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Touchpad is not working nor is it listed in xinput with latest BIOS (DJCN17WW) on following kernels with or without kernel parameters suggested in comment #39: 5.6.0-1011-oem 5.4.0-37-generic -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
This issue is fixed with kernel version 5.4.49 (current longterm kernel). I was having the exact same issue for almost 3 months. My Wifi speed used to get throttled whenever I download something or just consume more bandwidth continuously. More importantly whenever the throttling happens, the laptop also freezes for a few seconds. During these 3 months I tried several iwlwifi configurations, changed its driver versions... etc. Nothing worked. But then updating the kernel from version 5.3.0 to 5.4.49 manually fixed the issue. Now the wifi works perfectly without any issues. I haven't faced any other issue with this kernel yet(I am on Ubuntu 18.04). Also, now I couldn't see any iwlwifi error messages getting reported in dmesg logs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid Oct 20 01:
[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
$ modinfo iwlwifi | grep 9260 firmware: iwlwifi-9260-th-b0-jf-b0-46.ucode $ dmesg | grep firmware [ 14.894863] iwlwifi :3b:00.0: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [ 15.050919] iwlwifi :3b:00.0: Allocated 0x0040 bytes for firmware monitor. [13966.871684] iwlwifi :3b:00.0: Loaded firmware version: 46.6bf1df06.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | l2p_addr_match Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Touchpad is still not working in latest kernels on Focal: 5.6.0-1017-oem 5.4.0-39-generic Perhaps it should have it status changed from Fix released back to Confirmed? I'm willing to provide any information required to fix this issue in a promptly manner. -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850728] Re: CPU mis identified, need to force workaround
My guess is that .../drivers/media/pci/cx23885/cx23885-core.c is important and maybe my IOMMU, but I don't feel competent to patch the code myself. Nor am I certain that "15d1" is the magic number for Raven Ridge APUs. psd@myth:~$ lspci -s 0:00.2 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 15d1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850728 Title: CPU mis identified, need to force workaround Status in linux package in Ubuntu: Confirmed Bug description: This is probably an upstream bug, but this looks like the first pont of contact. I have a TV tuner card that works with old CPUs but fails with new CPUs that are "too fast". This is a known problem and there is a workaround for it. The workaround is automatically applied when a "fast" CPU is detected, but not mine. The workaround can be forced by adding this file to /etc/modprobe.d # /etc/modprobe.d/Hauppauge-WinTV-QuadHD.conf # 0 means force workaround off # 1 means auto detect troublsome CPUs # 2 means force workaround on options cx23885 dma_reset_workaround=2 My CPU is only a Ryzen 3 2200G. I will attach the output of cpuid, minus the serial number. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psd1263 F pulseaudio /dev/snd/controlC1: psd1263 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 31 10:34:56 2019 InstallationDate: Installed on 2019-10-21 (9 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp12s0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a506aa84-ff7a-48c6-8121-fae57b937f9c ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
Workarounds include; use an older version of Ubuntu, use a faster monitor, use a video card (nVidia GT 710), use a mainline kernel 5.4.0-050400rc6-generic which also reports the VGA port as a VGA port. But using a mainline kernel and a video card xrandr reports a 77 Hz refresh rate and a lower resolution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xs
[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
@Morten I think that all Ryzen motherboards are going to have UEFI firmware rather than the old BIOS firmware - even though everyone keeps using the old name. If it is your computer and you know what you are doing you could turn off secure boot. If you don't know, then don't do it. I grabbed all of these files; CHECKSUMS CHECKSUMS.gpg linux-headers-5.4.0-050400rc7_5.4.0-050400rc7.201911102031_all.deb linux-headers-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb linux-image-unsigned-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb linux-modules-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb @Kai-Heng Rc7 is better than rc6, but not a lot. I might have imagined the part about the VGA port being reported as a VGA port. Sorry. That was probably when I had the graphics card plugged in. The VGA port is being reported as a second Display Port again. With a fresh install of Eoan Ermine Xubuntu, updates, and rc7; Standard boot gives a badly pixelated display for menus, moving windows, changing text; xrandr reports reasonable things, then after 10 or 20 minutes the machine locks up. Booting with safe graphics from the grub menu gives a stable display, but xrandr seems confused and only reports one mode with a 77 Hz vertical refresh rate, and no mention of any ports. Do you want log files, or anything in particular? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chas
[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
Correction: Rc7 sometimes boots in the standard way. Sometimes it goes to a black screen. Rc7 boots reliably from the *recovery* mode in the grub 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/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config sec
[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
I'm not so sure that it is a kernel problem. Bionic with the edge kernel 5.3.0-24 seems OK, although it has locked up once or twice. Eoan with kernel 5.3.0-23 misbehaves. Could the XFCE desktop be important? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri
[Kernel-packages] [Bug 1850728] [NEW] CPU mis identified, need to force workaround
Public bug reported: This is probably an upstream bug, but this looks like the first pont of contact. I have a TV tuner card that works with old CPUs but fails with new CPUs that are "too fast". This is a known problem and there is a workaround for it. The workaround is automatically applied when a "fast" CPU is detected, but not mine. The workaround can be forced by adding this file to /etc/modprobe.d # /etc/modprobe.d/Hauppauge-WinTV-QuadHD.conf # 0 means force workaround off # 1 means auto detect troublsome CPUs # 2 means force workaround on options cx23885 dma_reset_workaround=2 My CPU is only a Ryzen 3 2200G. I will attach the output of cpuid, minus the serial number. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psd1263 F pulseaudio /dev/snd/controlC1: psd1263 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 31 10:34:56 2019 InstallationDate: Installed on 2019-10-21 (9 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp12s0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a506aa84-ff7a-48c6-8121-fae57b937f9c ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan ** Attachment added: "output of cpuid" https://bugs.launchpad.net/bugs/1850728/+attachment/5301554/+files/cpuid.out.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850728 Title: CPU mis identified, need to force workaround Status in linux package in Ubuntu: Confirmed Bug description: This is probably an upstream bug, but this looks like the first pont of contact. I have a TV tuner card that works with old CPUs but fails with new CPUs that are "too fast". This is a known problem and there is a workaround for it. The workaround is automatically applied when a "fast" CPU is detected, but not mine. The workaround can be forced by adding this file to /etc/modprobe.d # /etc/modprobe.d/Hauppauge-WinTV-QuadHD.conf # 0 means force workaround off # 1 means auto detect troublsome CPUs # 2 means force workaround on options cx23885 dma_reset_workaround=2 My CPU is only a Ryzen 3 2200G. I will attach the output of cpuid, minus the serial number. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psd1263 F pulseaudio /dev/snd/controlC1: psd1263 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 31 10:34:56 2019 InstallationDate: Installed on 2019-10-21 (9 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp12s0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a506aa84-ff7a-48c6-8121-fae57b937f9c ro quiet splash RelatedPackageVersions:
[Kernel-packages] [Bug 1550270] Re: Touchpad stops working randomly
Same issue here, running Ubuntu 17.10 on a Lenovo Thinkpad T440. Touchpad + trackpoint move between these three states: 1) everything works fine: touch to click, touch pad, two finger scroll/right-click and trackpoint 2) everything except for two-finger actions work 3) nothing works: touchpad + trackpoint unresponsive All of this seems to happen at random. Putting the machine into suspend and waking it up again will put it in a random state of working/not working. This behavior was not observed when running 17.04 or 16.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550270 Title: Touchpad stops working randomly Status in linux package in Ubuntu: Expired Bug description: Touchpad stops working randomly, sometimes only scroll function stops working but mostly entire mouse freezes. Unable to move around the desktop. Cant find anything in dmesg-, xorg- or syslog- logs that seems to cause it. A reboot solves the problem temporarily but occures soon again so something is borked. Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Feb 26 11:31:46 2016 DistUpgraded: 2016-02-23 12:13:20,341 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] InstallationDate: Installed on 2016-02-19 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20344 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic root=UUID=56fd75d9-c132-48f8-8cd4-e69995ecae91 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-02-23 (2 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Fri Feb 26 10:42:31 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 805 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8237 vendor AUO xserver.version: 2:1.17.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
I also experience this bug on Dell Inspiron 7370 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812679] Re: Upgraded kernel to linux-image-4.18.0-14.15-generic 4.18.20, and discovered I can no longer log into a local console
*** This bug is a duplicate of bug 1813873 *** https://bugs.launchpad.net/bugs/1813873 ** This bug has been marked a duplicate of bug 1813873 Userspace break as a result of missing patch backport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812679 Title: Upgraded kernel to linux-image-4.18.0-14.15-generic 4.18.20, and discovered I can no longer log into a local console Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to log into a local (Getty) console, having entered my username, the password prompt appears but then the cursor moves to the next line as I'm typing the password, and the log in times out with a 'Login incorrect' message, then the console prompt loops, displaying '[machine-name] login', followed by 'Login incorrect', until systemd restarts the service for that console. With the previous kernel, i.e. 4.18.0-13.14-generic the login process works fine. This wouldn't normally bother me, as I don't tend to use the local consoles for much, I just noticed it when I wanted to use one to check that something else was working correctly. I've currently set my GRUB config to boot the old 4.18.0-13.14-generic kernel, as a work-around. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: qyv3428 F pulseaudio /dev/snd/controlC0: qyv3428 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 21 14:37:03 2019 HibernationDevice: RESUME=/swapfile InstallationDate: Installed on 2018-04-10 (286 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-14-generic N/A linux-backports-modules-4.18.0-14-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-19 (93 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3566 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr068F1320471620100:rvnHewlett-Packard:rn3566:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: B6G97EA#ABU dmi.product.version: 068F1320471620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814993] Re: linux kernel 4.15.0-44 and 4.15.0-45 break tty login
*** This bug is a duplicate of bug 1813873 *** https://bugs.launchpad.net/bugs/1813873 ** This bug has been marked a duplicate of bug 1813873 Userspace break as a result of missing patch backport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814993 Title: linux kernel 4.15.0-44 and 4.15.0-45 break tty login Status in linux package in Ubuntu: Incomplete Bug description: On systems with either version of the kernel installed (4.15.0-44 or 4.15.0-45), login to the console (tty) is not possible. When the prior version, 4.15.0-43, is running this issue does not occur. 1) The release of Ubuntu via 'lsb_release -rd': Description:Ubuntu 18.04.1 LTS Release:18.04 2) The version of the package, via 'apt-cache policy pkgname' linux-generic: Installed: (none) Candidate: 4.15.0.45.47 Version table: 4.15.0.45.47 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 4.15.0.20.23 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) What I expected to happen: Normal login via tty 4) What happened instead login program would not allow login process to proceed, password prompts were interrupted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815122] Re: Unable to login via tty
*** This bug is a duplicate of bug 1813873 *** https://bugs.launchpad.net/bugs/1813873 ** This bug has been marked a duplicate of bug 1813873 Userspace break as a result of missing patch backport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815122 Title: Unable to login via tty Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 16.04. After upgrading the kernel from 4.4.0-141.167-generic to 4.4.0-142.168-generic I am experiencing problem logging in via the tty. I am able to provide my username, but the terminal automatically submit password before I am able to type it. If I start the computer with the previous kernel (4.4.0-141.167) it works as expected. I have done strace on the tty in both scenarios while performing the login with the following command: "sudo strace -p 1572 -s 1024 -vff -o tty-login-issue/login" 4.4.0-141.167-generic (works): https://gist.github.com/ivarconr/b022d2b4cadfc654031e8a930bf4408b 4.4.0-142.168-generic (fails): https://gist.github.com/ivarconr/603409ad1f0a3343a7f44a854283befc Let me know if you need me to provide any additional details. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ivaosthu 3706 F pulseaudio /dev/snd/controlC1: ivaosthu 3706 F pulseaudio CurrentDesktop: i3 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314 InstallationDate: Installed on 2016-08-12 (909 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EQS2HW00 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS2HW00 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:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS2HW00:pvrThinkPadP50:rvnLENOVO:rn20EQS2HW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20EQS2HW00 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ivaosthu 3706 F pulseaudio /dev/snd/controlC1: ivaosthu 3706 F pulseaudio CurrentDesktop: i3 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314 InstallationDate: Installed on 2016-08-12 (909 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EQS2HW00 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS2HW00 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:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS2HW00:pvrThinkPadP50:rvnLENOVO:rn20EQS2HW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20EQS2HW00 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815
[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
I have this issue, but with kernel 45, I had to revert back to 44. With Dell Vostro 15 7580 and Nvidia GTX 1060. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: I am using a docking station for my laptop. After install the 4.15.0-44 update my external monitors goes undetected after logging in or having the laptop closed. I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2) Graphics. Going back to the 4.15.0-43 version makes it all work fine again. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonas 2407 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4 InstallationDate: Installed on 2018-10-17 (103 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004MMX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004MMX 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:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004MMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Can we get an update on this issue, preferably from https://launchpad.net/~vicamo to whom this issue is assigned? Is anything being done to resolve it? It is marked as resolved for some time now while actually it is not. I'm asking this because I'll return this laptop if I cannot use Ubuntu on it since I've bought it to become my work laptop. -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903388] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432154/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 ---
[Kernel-packages] [Bug 1903388] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432151/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+
[Kernel-packages] [Bug 1903388] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432155/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 ---
[Kernel-packages] [Bug 1903388] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432142/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816
[Kernel-packages] [Bug 1903388] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432147/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 ---
[Kernel-packages] [Bug 1903388] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432146/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 ---
[Kernel-packages] [Bug 1903388] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432143/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 ---
[Kernel-packages] [Bug 1903388] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432148/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/18
[Kernel-packages] [Bug 1903388] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432153/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/180581
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
** Attachment added: "Recovery console errors (at startup, otherwise doesn't crash)" https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1903388/+attachment/5432141/+files/symptom__recovery-mode-boot-console-errors.jpg ** Description changed: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: - During regular use, system starts failing after 10m - 1hr after start. - Icons start disappearing, writing to disk fails. - In-memory operations still work for a while (switching windows, streaming video calls, typing). - After some time the entire system crashes, with a Black Screen Of Death constantly looping: - --- - EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 - [... same repeats for 8 times on average] - systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only files system - [... repeats for 10 times on average] - --- + During regular use, system starts failing after 10m - 1hr after start. + Icons start disappearing, writing to disk fails. + In-memory operations still work for a while (switching windows, streaming video calls, typing). + After some time the entire system crashes, with a Black Screen Of Death constantly looping: + --- + EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 + [... same repeats for 8 times on average] + systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system + [... repeats for 10 times on average] + --- Probable causes: - Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. - Don't know how to determine which kernel and bios I was running before the update. - Looks like APST issue, based on info from web and previous bug reports. + Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. + Don't know how to determine which kernel and bios I was running before the update. + Looks like APST issue, based on info from web and previous bug reports. Verification: - Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. - Ran script using: -- different nvme_core.default_ps_max_latency_us settings - in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" -- regular boot mode -- logged in to account -- on battery power - With default_ps_max_latency_us NOT SET: - writing FAILS between 57 and 70 seconds timeout between writes - With default_ps_max_latency_us=5500: - no write failure during 1hrs run - With default_ps_max_latency_us=200: - no write failure during 30m run - With latency 0: - no write failure during 10m run + Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. + Ran script using: + - different nvme_core.default_ps_max_latency_us settings + in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" + - regular boot mode + - logged in to account + - on battery power + With default_ps_max_latency_us NOT SET: + writing FAILS between 57 and 70 seconds timeout between writes + With default_ps_max_latency_us=5500: + no write failure during 1hrs run + With default_ps_max_latency_us=200: + no write failure during 30m run + With latency 0: + no write failure during 10m run This suggests an APST issue. Machine: - Lenovo Thinkpad T570 - Disk: - SAMSUNG MZVLB512HAJQ-000L7 - 512 GB (512110190592 bytes) - Firmware: 3L2QEXA7 - Serial#: S3TNNE0K119126 + Lenovo Thinkpad T570 + Disk: + SAMSUNG MZVLB512HAJQ-000L7 + 512 GB (512110190592 bytes) + Firmware: 3L2QEXA7 + Serial#: S3TNNE0K119126 System: - OS 1: Ubuntu 18.04.5 LTS - Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 - OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). - + OS 1: Ubuntu 18.04.5 LTS + Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 + OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: - Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. - Starting in "recovery mode" yields an error (among other suspicious behavior): - - sd 0:0:0:0: Attached scsi generic sg0 type 0 - sd 0:0:0:0: [sda] Attached SCSI removable Disk - input: TPPS/2 IBM TrackPoint
[Kernel-packages] [Bug 1903388] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432152/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/18
[Kernel-packages] [Bug 1903388] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432145/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816
[Kernel-packages] [Bug 1903388] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432144/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
[Kernel-packages] [Bug 1903388] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432149/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source
[Kernel-packages] [Bug 1903388] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432150/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/18
[Kernel-packages] [Bug 1903388] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1903388/+attachment/5432156/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: New Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
I will use "core.default_ps_max_latency_us=5500" for my daily use and see how it behaves. Or would you suggest any other setting? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: Confirmed Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 --
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
After setting core.default_ps_max_latency_us=0 and running for more than an hour, the system crahsed again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: Confirmed Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 --- ProblemType: Bug
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
After setting core.default_ps_max_latency_us=200 and running for a few hours, the system slows down significantly with intermittent long pauses. As all of this is rendering my computer unusable for work, can somebody advise how to restore an use a previous kernel (and which one)? Thanks and much appreciated! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: Confirmed Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'su
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
Another update regarding the the system slowdown. It seems it was caused by starting "Ubuntu on Wayland" from the main screen. (had to do so previously to be able to login). So it seems unrelated to the APST issue. Should I repeat the tests with different latency again? How dangerous is it for me to manually change from Kernel 4.15.18 to the suggested v5.10-rc3? As this is my workstation, I am reluctant on breaking my system entirely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: Incomplete Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.def
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Hi, I am running Ubuntu 17.10 GNOME with Wayland using a Thinkpad T440 as well. Installing `intel-microcode` fixed the issue immediately. I'm assuming this is proprietary code :\ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Hello again, I spoke too soon. Problem went away immediately after installing `intel-microcode` but returned after suspend and resume. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
I JUST started getting this bug with a firmware update pushed to me by Ubuntu 17.10. Never had this problem until now. So annoying. I'm on the Dell 9360 too. ** Attachment added: "dmesg.output.gz" https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+attachment/5008366/+files/dmesg.output.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Also, why would ubuntu push out a firmware update for a notebook that breaks it? They just added it without testing it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
..and just when I was about to downgrade the bios, it seems to be working. I cleaned some crud out from the sides of the trackpad. Could have been it. Maybe driver config can be changed to ignore the edges of the trackpad to avoid this? If anything changes I will update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Spoke too soon. Happened again, downgraded BIOS to 2.2.1 , works fine now. I can tell this is the correct fix because on initial ubuntu login the mouse would hang for a few seconds before even becoming usable. Now it doesn't do that at all and no other glitches seem to be happening. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Still experiencing some glitches. I'll shutup for awhile until i actually figure something out. It does seem better since ive been messing with it. I may just try a downgrade to ubuntu 16 and see what happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Tried to downgrade the firmware, still issues but they seem different. I still don't know what broke it... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
I downgraded the BIOS and it seems to have helped but still get glitches. Drives me mad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
I'm sending it back to dell then... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
I'm not convinced it's hardware related, booted with 16.04.3 , going to use it until tonight. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Solid hour so far , zero problems. Usually the problem would have already happened on 17.10. I believe there is a bug, that's not to say some people don't have a hardware issue, it doesn't seem to apply in my case. I'm rolling my install on this notebook back to 16.04 lts and I will report back if it happens again, if nobody hears from me in days or weeks, it means moving back to 16 resolved my problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Haha, ok ok. Recreated it in 16.04 by applying pressure to the trackpad with my palm. It seems better now on both versions but I do suspect a hw issue. Dell is coming out to replace it under warranty. Hoping it's not a design flaw that impacts all touchpads ,, or maybe they have a newer revision of trackpad because of this issue. that'd be nice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
It destroyed my BIOS on Lenovo Y50-70. Unable to change BIOS settings nor boot through USB devices. I installed windows through bootable partition on another SSD luckily. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi
Hi everyone, I had the same wifi/bluetooth interference problem. My setup is as follows: - Ubuntu 14.04 with custom-built vanilla kernel 4.3.0 - Lenovo B50 laptop having QCA9565 / AR9565 Wireless Network Adapter (ath9k) onboard - Linksys WRT-54GL router running DD-WRT v24-sp2 (10/10/09) mini - Marshall Acton bluetooth speaker Initially when I was streaming audio to the speaker, wifi degraded dramatically. After doing some research, I have successfully resolved the issue. What I have done is: * On my laptop: - added ``` Enable=Source Disable=Socket AutoConnect=True ``` to /etc/bluetooth/audio.conf - Added ``` options iwlwifi 11n_disable=1 bt_coex_active=1 ``` to /etc/modprobe.d/iwlwifi.conf However, since I'm not using iwlwifi, I'm not sure whether this had had any effect whatsoever. * On my router: - Under Wireless / Advanced Settings, I set "Bluetooth Coexistence Mode" to "Preemption" Then I've rebooted everything just in case. FYI, I encourage you to read through https://wireless.wiki.kernel.org/en/users/documentation/bluetooth- coexistence to find out what bluetooth coexistence is, and I wonder why everybody keeps switching it off (by setting bt_coex_active=0). On the contrary, this technique is designed to defeat interference problem. Also, you may find nice to add "load-module module-switch-on-connect" to /etc/pulse/default.pa so that audio starts streaming to bluetooth speaker automatically when it connects (and then back to laptop speakers when it disconnects.) Cheers, PD. -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550839] Re: wakealarm is cleared on boot unless hpet disabled
First, I am surprised and pleased that ASRock is still issuing firmware updates for such an old motherboard. There was an update issued weeks before I opened this bug report. Firmware updated from 2.50 to 2.60. The stated fix in the firmware update has nothing to do with this bug - but the stated improvements are often wildly incomplete. $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for psd: P2.60 02/01/2016 *A* bug still exists, but it is not what I thought it was. The wakealarm is not being cleared when 16.04 starts. It is being cleared when 14.04 (and others) stop. "shutdown" preserves wakealarm (hence my MthyTV setup is working well) but "reboot", and I suspect "poweroff" clear the wakealarm, causing the apparent problem in 16.04 when I rebooted to test the new release. I suspect that "hpet" was just a co-incidence. This bug report needs to be renamed, I'm just not sure what to. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550839 Title: wakealarm is cleared on boot unless hpet disabled Status in linux package in Ubuntu: Confirmed Bug description: Wiley Werewolf 15.10 and Xenial Xerus 16.04 (alpha) clear /sys/class/rtc/rtc0/wakealarm during the bootup process, unless "hpet=disable" is given as a boot parameter. (Tested on Xenia, not tested on Wiley.) Trusty Tahr 14.04 is well behaved, without the hpet parameter. Background; the main installation runs MythTV which sets and uses the wake alarm. A test boot into a newer OS clears the alarm and MythTV on Trusty does not wake up to record the next scheduled TV program. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.2.1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psd1154 F pulseaudio /dev/snd/controlC0: psd1154 F pulseaudio CurrentDesktop: XFCE Date: Sun Feb 28 12:28:59 2016 HibernationDevice: RESUME=UUID=2f3325b3-f04c-4c61-98b8-d4a23624b37a InstallationDate: Installed on 2016-02-03 (24 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160202) IwConfig: enp5s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: \vmlinuz ro root=LABEL=XX quiet splash bootdegraded=true video=vesa:off hpet=disable initrd=\initrd.img RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: 970 Pro3 R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd01/08/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550839] [NEW] wakealarm is cleared on boot unless hpet disabled
Public bug reported: Wiley Werewolf 15.10 and Xenial Xerus 16.04 (alpha) clear /sys/class/rtc/rtc0/wakealarm during the bootup process, unless "hpet=disable" is given as a boot parameter. (Tested on Xenia, not tested on Wiley.) Trusty Tahr 14.04 is well behaved, without the hpet parameter. Background; the main installation runs MythTV which sets and uses the wake alarm. A test boot into a newer OS clears the alarm and MythTV on Trusty does not wake up to record the next scheduled TV program. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.2.1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psd1154 F pulseaudio /dev/snd/controlC0: psd1154 F pulseaudio CurrentDesktop: XFCE Date: Sun Feb 28 12:28:59 2016 HibernationDevice: RESUME=UUID=2f3325b3-f04c-4c61-98b8-d4a23624b37a InstallationDate: Installed on 2016-02-03 (24 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160202) IwConfig: enp5s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: \vmlinuz ro root=LABEL=XX quiet splash bootdegraded=true video=vesa:off hpet=disable initrd=\initrd.img RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: 970 Pro3 R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd01/08/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages 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/1550839 Title: wakealarm is cleared on boot unless hpet disabled Status in linux package in Ubuntu: New Bug description: Wiley Werewolf 15.10 and Xenial Xerus 16.04 (alpha) clear /sys/class/rtc/rtc0/wakealarm during the bootup process, unless "hpet=disable" is given as a boot parameter. (Tested on Xenia, not tested on Wiley.) Trusty Tahr 14.04 is well behaved, without the hpet parameter. Background; the main installation runs MythTV which sets and uses the wake alarm. A test boot into a newer OS clears the alarm and MythTV on Trusty does not wake up to record the next scheduled TV program. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.2.1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psd1154 F pulseaudio /dev/snd/controlC0: psd1154 F pulseaudio CurrentDesktop: XFCE Date: Sun Feb 28 12:28:59 2016 HibernationDevice: RESUME=UUID=2f3325b3-f04c-4c61-98b8-d4a23624b37a InstallationDate: Installed on 2016-02-03 (24 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160202) IwConfig: enp5s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: \vmlinuz ro root=LABEL=XX quiet splash bootdegraded=true video=vesa:off hpet=disable initrd=\initrd.img RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: 970 Pro3 R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd01/08/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledBy
[Kernel-packages] [Bug 1527740] [NEW] Touchpad intermittently stops working
Public bug reported: Touchpad intermittently stops working on lenovo carbon x1 (gen1) If I close the lid, or sometimes disable and then re-enable touchpad in BIOS, it may sometimes come back. Sometimes running the software updater seems to fix or break it, but this may be incidental also perhaps incidental, im using virtualbox alot, and thats really the only thing new in my workflow. when it doesn't work, xinput list sometimes does not show the device. Once it shows, i can see properties in system settings -> mouse and touchpad', but that doesn't necessarily mean the touchpad is going to come alive. If it does start to work, it often works across several reboots. i've attached some additional files in a tarball: -- beforeaAndAfterLidClose -- this was a run of cat /proc/bus/input/devices before and after closing lid ... note that after closing and reopening, the TouchPad shows up. -- dmesg -- devices: a full '/cat/proc/bus/devices', obtained after the touchpad reappeared, which will show the vendor information -- Xorg.0.log define@x1:~/Desktop/touchPad$ lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-74-generic 3.13.0-74.118 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: define 2741 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 18 14:32:53 2015 HibernationDevice: RESUME=UUID=298e288a-808a-477a-b4b6-3905d0819c47 InstallationDate: Installed on 2014-10-12 (432 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 34606V9 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 34606V9 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG6ET96WW(2.56):bd04/29/2013:svnLENOVO:pn34606V9:pvrThinkPadX1Carbon:rvnLENOVO:rn34606V9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34606V9 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "this is a tarball of the files mentioned in the description" https://bugs.launchpad.net/bugs/1527740/+attachment/4537017/+files/touchPad.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1527740 Title: Touchpad intermittently stops working Status in linux package in Ubuntu: New Bug description: Touchpad intermittently stops working on lenovo carbon x1 (gen1) If I close the lid, or sometimes disable and then re-enable touchpad in BIOS, it may sometimes come back. Sometimes running the software updater seems to fix or break it, but this may be incidental also perhaps incidental, im using virtualbox alot, and thats really the only thing new in my workflow. when it doesn't work, xinput list sometimes does not show the device. Once it shows, i can see properties in system settings -> mouse and touchpad', but that doesn't necessarily mean the touchpad is going to come alive. If it does start to work, it often works across several reboots. i've attached some additional files in a tarball: -- beforeaAndAfterLidClose -- this was a run of cat /proc/bus/input/devices before and after closing lid ... note that after closing and reopening, the TouchPad shows up. -- dmesg -- devices: a full '/cat/proc/bus/devices', obtained after the touchpad reappeared, which will show the vendor information -- Xorg.0.log define@x1:~/Desktop/touchPad$ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-74-generic 3.13.0-74.118 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: define 2741 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 18 14:32:53 2015 HibernationDevice: RESU
[Kernel-packages] [Bug 1527740] Re: Touchpad intermittently stops working
I should also note that this Lenovo carbonx1 generation 1 has a touchscreen (have seen that if there's on same bus there can be.problems) ... It has no bios option to disable touchscreen nor is there any kind of function key to disable touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1527740 Title: Touchpad intermittently stops working Status in linux package in Ubuntu: Confirmed Bug description: Touchpad intermittently stops working on lenovo carbon x1 (gen1) If I close the lid, or sometimes disable and then re-enable touchpad in BIOS, it may sometimes come back. Sometimes running the software updater seems to fix or break it, but this may be incidental also perhaps incidental, im using virtualbox alot, and thats really the only thing new in my workflow. when it doesn't work, xinput list sometimes does not show the device. Once it shows, i can see properties in system settings -> mouse and touchpad', but that doesn't necessarily mean the touchpad is going to come alive. If it does start to work, it often works across several reboots. i've attached some additional files in a tarball: -- beforeaAndAfterLidClose -- this was a run of cat /proc/bus/input/devices before and after closing lid ... note that after closing and reopening, the TouchPad shows up. -- dmesg -- devices: a full '/cat/proc/bus/devices', obtained after the touchpad reappeared, which will show the vendor information -- Xorg.0.log define@x1:~/Desktop/touchPad$ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-74-generic 3.13.0-74.118 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: define 2741 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 18 14:32:53 2015 HibernationDevice: RESUME=UUID=298e288a-808a-477a-b4b6-3905d0819c47 InstallationDate: Installed on 2014-10-12 (432 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 34606V9 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 34606V9 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG6ET96WW(2.56):bd04/29/2013:svnLENOVO:pn34606V9:pvrThinkPadX1Carbon:rvnLENOVO:rn34606V9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34606V9 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527740/+subscriptions -- Mailing list: https://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 1527740] Re: Touchpad intermittently stops working
Hi Joseph, My battery ran down. When i plugged booted up everything was working, so it's really intermittent, and the steps to resolve seem to always involve always a reboot (after sometimes several times trying to disable the trackpoint in BIOS, boot in and then enable trackpoint in BIOS and boot in ... but this does not always work), or a suspend. Several kernel versions have had this problem, and so I was sort of starting to wonder if there was some kind of a patch war going on behind the scenes, breaking it then fixing it. It might just be my hardware too, unless we see this from other users. I did initially need to get this trackpad replaced a year ago, and so it might be degrading? As i mentioned, it has also a touchscreen. Idk if this can cause bus conficts. One interesting thing is that when i disable the trackpoint in bios, i can often get the pad itself to show up again and wok, but the buttons won't work. So we've got the touchpad, the trackpad and a trackpoint possibly conflicting? i'd be hesitent to check the upstream kernel for sec reasons, since i work on this laptop, but i can certainly tell you if i see the problem once it gets pushed out. I'll just note that uname -a is currently: Linux x1 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux and if i see a problem on a later version let you know? thanks for your reply! _d On Fri, Dec 18, 2015 at 3:40 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.4 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc5-wily > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1527740 > > Title: > Touchpad intermittently stops working > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Touchpad intermittently stops working on lenovo carbon x1 (gen1) > > If I close the lid, or sometimes disable and then re-enable touchpad > in BIOS, it may sometimes come back. Sometimes running the software > updater seems to fix or break it, but this may be incidental > > also perhaps incidental, im using virtualbox alot, and thats really > the only thing new in my workflow. > > when it doesn't work, xinput list sometimes does not show the device. > Once it shows, i can see properties in system settings -> mouse and > touchpad', but that doesn't necessarily mean the touchpad is going to > come alive. > > If it does start to work, it often works across several reboots. > > i've attached some additional files in a tarball: > -- beforeaAndAfterLidClose -- this was a run of cat > /proc/bus/input/devices before and after closing lid ... note that after > closing and reopening, the TouchPad shows up. > -- dmesg > -- devices: a full '/cat/proc/bus/devices', obtained after the > touchpad reappeared, which will show the vendor information > -- Xorg.0.log > > define@x1:~/Desktop/touchPad$ lsb_release -rd > Description: Ubuntu 14.04.3 LTS > Release: 14.04 > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: linux-image-3.13.0-74-generic 3.13.0-74.118 > ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 > Uname: Linux 3.13.0-74-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.19 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: define 2741 F pulseaudio > CurrentDesktop: Unity > Date: Fri Dec 18 14:32:53 2015 > HibernationDevice: RESUME=UUID=298e288a-808a-477a-b4b6-3905d0819c47 > InstallationDate: Installed on 2014-10-12 (432 days ago) > InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.2) > MachineType: LENOVO 34606V9 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-3.13.0-74-generic N/A >linux-backports-modules-3.13.0-74-generic N/A >linux-firmware 1.127.19 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/29/2013 > dmi.bios.vendor: LENOVO > dmi.bios.version
[Kernel-packages] [Bug 1527740] Re: Touchpad intermittently stops working
Hi Updated BIOS per Christopher's request: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date G6ETB2WW (2.72 ) 10/08/2015 Issue is still reproducible. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1527740 Title: Touchpad intermittently stops working Status in linux package in Ubuntu: Confirmed Bug description: Touchpad intermittently stops working on lenovo carbon x1 (gen1) If I close the lid, or sometimes disable and then re-enable touchpad in BIOS, it may sometimes come back. Sometimes running the software updater seems to fix or break it, but this may be incidental also perhaps incidental, im using virtualbox alot, and thats really the only thing new in my workflow. when it doesn't work, xinput list sometimes does not show the device. Once it shows, i can see properties in system settings -> mouse and touchpad', but that doesn't necessarily mean the touchpad is going to come alive. If it does start to work, it often works across several reboots. i've attached some additional files in a tarball: -- beforeaAndAfterLidClose -- this was a run of cat /proc/bus/input/devices before and after closing lid ... note that after closing and reopening, the TouchPad shows up. -- dmesg -- devices: a full '/cat/proc/bus/devices', obtained after the touchpad reappeared, which will show the vendor information -- Xorg.0.log define@x1:~/Desktop/touchPad$ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-74-generic 3.13.0-74.118 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: define 2741 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 18 14:32:53 2015 HibernationDevice: RESUME=UUID=298e288a-808a-477a-b4b6-3905d0819c47 InstallationDate: Installed on 2014-10-12 (432 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 34606V9 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 34606V9 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG6ET96WW(2.56):bd04/29/2013:svnLENOVO:pn34606V9:pvrThinkPadX1Carbon:rvnLENOVO:rn34606V9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34606V9 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1527740] Re: Touchpad intermittently stops working
im going to change the status to incomplete pending one more replication I had restarted the machine during the BIOS flash as per the utils request, and then ubuntu 14.04 came back up there was no mouse. I did my little dance of closing the lid and waiting for a while, which was not working for about 3 hrs straight yesterday, and it immediately started to work after first try I want to see this issue happen at lest once again on a completely fresh boot before marking it confirmed again in order to not waste anyone's time. Thanks for everyone's help so far! Cheers _d ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1527740 Title: Touchpad intermittently stops working Status in linux package in Ubuntu: Incomplete Bug description: Touchpad intermittently stops working on lenovo carbon x1 (gen1) If I close the lid, or sometimes disable and then re-enable touchpad in BIOS, it may sometimes come back. Sometimes running the software updater seems to fix or break it, but this may be incidental also perhaps incidental, im using virtualbox alot, and thats really the only thing new in my workflow. when it doesn't work, xinput list sometimes does not show the device. Once it shows, i can see properties in system settings -> mouse and touchpad', but that doesn't necessarily mean the touchpad is going to come alive. If it does start to work, it often works across several reboots. i've attached some additional files in a tarball: -- beforeaAndAfterLidClose -- this was a run of cat /proc/bus/input/devices before and after closing lid ... note that after closing and reopening, the TouchPad shows up. -- dmesg -- devices: a full '/cat/proc/bus/devices', obtained after the touchpad reappeared, which will show the vendor information -- Xorg.0.log define@x1:~/Desktop/touchPad$ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-74-generic 3.13.0-74.118 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: define 2741 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 18 14:32:53 2015 HibernationDevice: RESUME=UUID=298e288a-808a-477a-b4b6-3905d0819c47 InstallationDate: Installed on 2014-10-12 (432 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 34606V9 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 34606V9 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG6ET96WW(2.56):bd04/29/2013:svnLENOVO:pn34606V9:pvrThinkPadX1Carbon:rvnLENOVO:rn34606V9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34606V9 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1527740] Re: Touchpad intermittently stops working
OK moving back to confirmed Have had the new BIOS running for a week and have seen the issue recur several times. Current workaround is to boot up, and then open [ System Properties --> Mouse and Touchpad ] mouse properties, where i will only see General (and not Touchpad). I then close the lid and walk away for several minutes. It seems that lately this works after 1-5 tries, but I suspect its really luck of the draw. In every case, after one suspend or laptop-lid-close, the Touchpad category will show up, but will not necessarily mean that the touchpad works. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1527740 Title: Touchpad intermittently stops working Status in linux package in Ubuntu: Confirmed Bug description: Touchpad intermittently stops working on lenovo carbon x1 (gen1) If I close the lid, or sometimes disable and then re-enable touchpad in BIOS, it may sometimes come back. Sometimes running the software updater seems to fix or break it, but this may be incidental also perhaps incidental, im using virtualbox alot, and thats really the only thing new in my workflow. when it doesn't work, xinput list sometimes does not show the device. Once it shows, i can see properties in system settings -> mouse and touchpad', but that doesn't necessarily mean the touchpad is going to come alive. If it does start to work, it often works across several reboots. i've attached some additional files in a tarball: -- beforeaAndAfterLidClose -- this was a run of cat /proc/bus/input/devices before and after closing lid ... note that after closing and reopening, the TouchPad shows up. -- dmesg -- devices: a full '/cat/proc/bus/devices', obtained after the touchpad reappeared, which will show the vendor information -- Xorg.0.log define@x1:~/Desktop/touchPad$ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-74-generic 3.13.0-74.118 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: define 2741 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 18 14:32:53 2015 HibernationDevice: RESUME=UUID=298e288a-808a-477a-b4b6-3905d0819c47 InstallationDate: Installed on 2014-10-12 (432 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 34606V9 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 34606V9 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG6ET96WW(2.56):bd04/29/2013:svnLENOVO:pn34606V9:pvrThinkPadX1Carbon:rvnLENOVO:rn34606V9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34606V9 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328182] [NEW] package linux-image-3.5.0-51-generic 3.5.0-51.76 failed to install/upgrade: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko',
Public bug reported: I am on Ubuntu 12.10 and I was simply doing a software update that includes the linux-image-3.5.0-51-generic And it fails with this error info: Unpacking replacement linux-image-3.5.0-51-generic ... dpkg: error processing /var/cache/apt/archives/linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.5.0-51-generic /boot/vmlinuz-3.5.0-51-generic run-parts: executing /etc/kernel/postrm.d/zz-extlinux 3.5.0-51-generic /boot/vmlinuz-3.5.0-51-generic P: Checking for EXTLINUX directory... found. P: Writing config for /boot/vmlinuz-3.5.0-51-generic... P: Writing config for /boot/vmlinuz-3.5.0-49-generic... P: Installing debian theme... done. run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.5.0-51-generic /boot/vmlinuz-3.5.0-51-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-51-generic 3.5.0-51.76 ProcVersionSignature: Ubuntu 3.5.0-51.76-generic 3.5.7.33 Uname: Linux 3.5.0-51-generic x86_64 ApportVersion: 2.6.1-0ubuntu13 AptOrdering: linux-image-3.5.0-51-generic: Install linux-image-3.5.0-51-generic: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 1743 F pulseaudio /dev/snd/controlC0: james 1743 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jun 9 12:03:42 2014 DpkgTerminalLog: Preparing to replace linux-image-3.5.0-51-generic 3.5.0-51.76 (using .../linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb) ... Done. Unpacking replacement linux-image-3.5.0-51-generic ... dpkg: error processing /var/cache/apt/archives/linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 DuplicateSignature: package:linux-image-3.5.0-51-generic:3.5.0-51.76:trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 ErrorMessage: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 HibernationDevice: RESUME=UUID=e7d3af07-5d1b-48d2-b3ed-7be2be62ea12 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 570 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-51-generic root=UUID=79a2945a-1d97-4e2e-80b8-06587c2fd812 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-7ubuntu11 RfKill: SourcePackage: linux Title: package linux-image-3.5.0-51-generic 3.5.0-51.76 failed to install/upgrade: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 UpgradeStatus: Upgraded to quantal on 2013-07-16 (328 days ago) dmi.bios.date: 01/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 04GJJT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd01/25/2010:svnDellInc.:pnInspiron570:pvr00:rvnDellInc.:rn04GJJT:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Inspiron 570 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict quantal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328182 Title: package linux-image-3.5.0-51-generic 3.5.0-51.76 failed to install/upgrade: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 Status in “linux” package in Ubuntu: New Bug description: I am on Ubuntu 12.10 and I was simply doing a software update that includes the linux-image-3.5.0-51-generic And it fails with this error info: Unpacking replacement linux-image-3.
[Kernel-packages] [Bug 1328182] Re: package linux-image-3.5.0-51-generic 3.5.0-51.76 failed to install/upgrade: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', w
This did not actually fix the problem . The only way I was able to fix this was to run the install via dpkg and use --force-overwrite. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328182 Title: package linux-image-3.5.0-51-generic 3.5.0-51.76 failed to install/upgrade: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 Status in “linux” package in Ubuntu: Confirmed Bug description: I am on Ubuntu 12.10 and I was simply doing a software update that includes the linux-image-3.5.0-51-generic And it fails with this error info: Unpacking replacement linux-image-3.5.0-51-generic ... dpkg: error processing /var/cache/apt/archives/linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.5.0-51-generic /boot/vmlinuz-3.5.0-51-generic run-parts: executing /etc/kernel/postrm.d/zz-extlinux 3.5.0-51-generic /boot/vmlinuz-3.5.0-51-generic P: Checking for EXTLINUX directory... found. P: Writing config for /boot/vmlinuz-3.5.0-51-generic... P: Writing config for /boot/vmlinuz-3.5.0-49-generic... P: Installing debian theme... done. run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.5.0-51-generic /boot/vmlinuz-3.5.0-51-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-51-generic 3.5.0-51.76 ProcVersionSignature: Ubuntu 3.5.0-51.76-generic 3.5.7.33 Uname: Linux 3.5.0-51-generic x86_64 ApportVersion: 2.6.1-0ubuntu13 AptOrdering: linux-image-3.5.0-51-generic: Install linux-image-3.5.0-51-generic: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 1743 F pulseaudio /dev/snd/controlC0: james 1743 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jun 9 12:03:42 2014 DpkgTerminalLog: Preparing to replace linux-image-3.5.0-51-generic 3.5.0-51.76 (using .../linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb) ... Done. Unpacking replacement linux-image-3.5.0-51-generic ... dpkg: error processing /var/cache/apt/archives/linux-image-3.5.0-51-generic_3.5.0-51.77~precise1_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 DuplicateSignature: package:linux-image-3.5.0-51-generic:3.5.0-51.76:trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 ErrorMessage: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 HibernationDevice: RESUME=UUID=e7d3af07-5d1b-48d2-b3ed-7be2be62ea12 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 570 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-51-generic root=UUID=79a2945a-1d97-4e2e-80b8-06587c2fd812 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-7ubuntu11 RfKill: SourcePackage: linux Title: package linux-image-3.5.0-51-generic 3.5.0-51.76 failed to install/upgrade: trying to overwrite '/lib/modules/3.5.0-51-generic/kernel/net/bluetooth/bnep/bnep.ko', which is also in package linux-image-extra-3.5.0-51-generic 3.5.0-51.76 UpgradeStatus: Upgraded to quantal on 2013-07-16 (328 days ago) dmi.bios.date: 01/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 04GJJT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd01/25/2010:svnDellInc.:pnInspiron570:pvr00:rvnDellInc.:rn04GJJT:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Inspiron 570 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage no
[Kernel-packages] [Bug 282220]
I wanted to add that I faced the exact same issue with Dell Latitude E7440 (4th generation intel laptop) which is known to have very good compatibility with Linux, I have updated my bios(currently at A07) and the kernel but the problem persisted. I am using opensuse 13.1 and the kernel from Kernel:stable which is currently 3.13.7-1-desktop and suspend to disk used to work only occassionally, after adding the kernel parameter and restarting it seems to work 100% of the time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/282220 Title: Hibernate fails on Thinkpad T41 Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Won't Fix Bug description: I've installed Ubuntu 8.10 (Intrepid) on my Thinkpad T41 (which previously had 8.04 installed) and got all updates available. I can hibernate, and the hard-disk light indicates that memory state is saved to the disk. When I start the machine again, the kernel boots, the Ubuntu splash screen appears (all as in 8.04), and the disk light indicates that memory is initialized again. However, after that, the machine locks up, nothing more happens, except the Caps-lock LED flashing Ctrl-alt-F1-9 did not do anything, i.e. there was no way I could find out what's wrong. I also did not find anything relevant in /var/log/dmesg* or /var/log/syslog* (at least from my view; I'm no kernel hacker). When hibernating, the T41 switches the screen to text/console mode with just a blinking _ cursor. On 8.10, I now get a message about "PCI" and "unable to thaw device" or something like it, which may be relevant to this behavior. (yes, the "thaw..." message appears not on resuming, but on hibernating) kernel is 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:24 UTC 2008 i686 (from uname -a) I'm unsure if this bug is related to bug #134680. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/282220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300424] [NEW] Bug reports keep popping up on login, not entirely sure why
Public bug reported: Bug reports pop up on login. There are three or four of them, they occur on all logins, even if I just log out and log in again. I did rebuild unity from a modified source to suport touch controls through touchegg, so if these are caused by unity, you should ignore them. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2004 F pulseaudio /dev/snd/pcmC1D0p: john 2004 F...m pulseaudio /dev/snd/controlC0: john 2004 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 31 14:12:39 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=92cd549d-6672-4f29-bf76-c1e39e93812f InstallationDate: Installed on 2014-03-30 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20A7CTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=322273b3-4567-4897-a1a7-3c789fe96d24 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago) dmi.bios.date: 03/05/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET34WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET34WW(1.11):bd03/05/2014:svnLENOVO:pn20A7CTO1WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CTO1WW:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CTO1WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300424 Title: Bug reports keep popping up on login, not entirely sure why Status in “linux” package in Ubuntu: New Bug description: Bug reports pop up on login. There are three or four of them, they occur on all logins, even if I just log out and log in again. I did rebuild unity from a modified source to suport touch controls through touchegg, so if these are caused by unity, you should ignore them. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2004 F pulseaudio /dev/snd/pcmC1D0p: john 2004 F...m pulseaudio /dev/snd/controlC0: john 2004 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 31 14:12:39 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=92cd549d-6672-4f29-bf76-c1e39e93812f InstallationDate: Installed on 2014-03-30 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20A7CTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=322273b3-4567-4897-a1a7-3c789fe96d24 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago) dmi.bios.date: 03/05/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET34WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET34WW(1.11):bd03/05/2014:svnLENOVO:pn20A7CTO1WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CTO1WW:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CTO1WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 282232] Re: [Hardy] Philips Audio Set MCM595 PC Link USB doesn't work.
Hi, I come up with a solution using libusb. The connection protocol lacks (at least) two packets that switch on the sound on the HiFi. I made a C script that works with MCM530, but it should also work with MCM5xx https://github.com/nheir/usb_pc_link The readme describes the missing packets. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/282232 Title: [Hardy] Philips Audio Set MCM595 PC Link USB doesn't work. Status in The Linux Kernel: In Progress Status in “linux” package in Ubuntu: Invalid Bug description: This is a "Boombox" Philips Micro HiFi System model MCM595 with the "PC Link" feature. It's detected bye ALSA and even the mixer shows up. But testing sound with it does not work. I've tested sound redirecting it with System -> Preferences -> Sound ... and even with MPlayer assigning the hw0.1 in the alsa mplayer module. This is the system configuration: http://www.alsa-project.org/db/?f=e9c1c1671b9d9ba26489d45fb4f8298124515a77 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/282232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339199] [NEW] mpi getmem.64 user job crashes ubuntu 14.04 ppc64le LE
Public bug reported: mpi getmem.64 user job crashes ubuntu 14.04 ppc64le LE SUMMARY: mpi user job launch getmem.64 user job crashes ubuntu 14.04 We still have the node c656f2n05 in debug with console opened and can give access when needed. ^^ CONFIGURATION: ^^ Job launched across cluster of 4 p8 22L systems ( hostnames on the ibm 9.* net ) c656f2n03 is c656f2n03.pok.stglabs.ibm.com is 9.114.39.143 c656f2n04 is c656f2n04.pok.stglabs.ibm.com is 9.114.39.144 c656f2n05 is c656f2n05.pok.stglabs.ibm.com is 9.114.39.145 <--- node crashed c656f2n06 is c656f2n06.pok.stglabs.ibm.com is 9.114.39.146 ^^ BUILD: ^^ Ubuntu 14.04 LTS c656f2n05 hvc0 Linux c656f2n05 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:46:02 UTC 2014 ppc 64le ppc64le ppc64le GNU/Linux ^ SCENARIO: ^ Hi, all: P8 server c656f2n05 crashed again. I have launched openshmem regression with the efix of D198270 before the server crashed. Here below are the steps that I have used to launched the test: - 1. ssh c656f2n03 with root/davega. 2. su - qixiaol 3. cd /u/qixiaol/fvt/openshmem/get 4. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> env | grep MP MP_ADAPTER_USE=shared MP_EUIDEVICE=sn_all MP_EUILIB=us MP_EUILIBPATH=/u/qixiaol/fvt/efix/RVIN_LE/ MP_HOSTFILE=/u/qixiaol/fvt/openshmem/host.list MP_PROCS=8 MP_RESD=poe 5. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> ./run.all And the test log is at /u/qixiaol/fvt/openshmem/get/RESULTS: --- [c656f2n03][/u/qixiaol/fvt/openshmem/get/RESULTS]> /afs/apd/u/shapiro/gpfs/PRO140708.12 (12:52:10) c199sq03:/u/shapiro/le # cat /afs/apd/u/shapiro/gpfs/PRO140708.11 mpi getmem.64 user job crashes ubuntu 14.04 ppc64le LE SUMMARY: mpi user job launch getmem.64 user job crashes ubuntu 14.04 We still have the node c656f2n05 in debug with console opened and can give access when needed. ^^ CONFIGURATION: ^^ Job launched across cluster of 4 p8 22L systems ( hostnames on the ibm 9.* net ) c656f2n03 is c656f2n03.pok.stglabs.ibm.com is 9.114.39.143 c656f2n04 is c656f2n04.pok.stglabs.ibm.com is 9.114.39.144 c656f2n05 is c656f2n05.pok.stglabs.ibm.com is 9.114.39.145 <--- node crashed c656f2n06 is c656f2n06.pok.stglabs.ibm.com is 9.114.39.146 ^^ BUILD: ^^ Ubuntu 14.04 LTS c656f2n05 hvc0 Linux c656f2n05 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:46:02 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ^ SCENARIO: ^ Hi, all: P8 server c656f2n05 crashed again. I have launched openshmem regression with the efix of D198270 before the server crashed. Here below are the steps that I have used to launched the test: - 1. ssh c656f2n03 with root/davega. 2. su - qixiaol 3. cd /u/qixiaol/fvt/openshmem/get 4. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> env | grep MP MP_ADAPTER_USE=shared MP_EUIDEVICE=sn_all MP_EUILIB=us MP_EUILIBPATH=/u/qixiaol/fvt/efix/RVIN_LE/ MP_HOSTFILE=/u/qixiaol/fvt/openshmem/host.list MP_PROCS=8 MP_RESD=poe 5. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> ./run.all And the test log is at /u/qixiaol/fvt/openshmem/get/RESULTS: --- [c656f2n03][/u/qixiaol/fvt/openshmem/get/RESULTS]> The binary file of getmem.64 is at c656f2n03:/u/qixiaol/fvt/openshmem/get/bin/ppc64le/getmem.64 And its source code is at c656f2n03:/u/qixiaol/fvt/openshmem/get/src/getmem.c Best Wishes Xiao Lu Qi(???) SYMPTOM: Ubuntu 14.04 LTS c656f2n05 hvc0 c656f2n05 login: [418442.082487] rport-1:0-3: blocked FC remote port time out: removing rport [418442.082492] rport-5:0-6: blocked FC remote port time out: removing rport [418442.082494] rport-2:0-3: blocked FC remote port time out: removing rport [466884.681785] kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! cpu 0x19: Vector: 700 (Program Check) at [c01f39a13310] pc: c022fa34: .kfree+0x124/0x220[466884.683019] kernel BUG at /b uild/buildd/linux-3.13.0/mm/slub.c:3365! lr: c07fb6a8: .skb_free_head+0x78/0xb0 sp: c01f39a13590 msr: 90029033 current = 0xc01f58828bf0 paca= 0xcfe45780 softe: 0irq_happened: 0x01 pid = 98622, comm = getmem.64 [466884.685546] kekernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! [466884.687415] kernel BUG at /build/buildd/linux-3.13.0/mm/slub .c:3365! cpu 0x11: Vector: 700 (Program Check) at [c01f39a6b310] pc: c022fa34: .kfree+0x124/0x220 lr: c07fb6a8: .skb_free_head+0x78/0xb0 sp: c01f39a6b590 msr: 90029033 current = 0xc01f5886f840 paca= 0xcfe43b80 softe: 0irq_happened: 0x01 pid = 98621, comm = getmem.64 kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! enter ? for help 19:mon> t print backtrace 19:mon> t [c01f39a13620] c07fb6a8 .skb_free_head+0x78/0xb0 [c
[Kernel-packages] [Bug 1296066] Re: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure
Oh, and apport detect the problem on next boot so I sent the reports (but I don't know where it goes). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1296066 Title: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: system does not wake up after sudo pm-suspend. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1502 F pulseaudio plejaden 2151 F pulseaudio /dev/snd/controlC0: lightdm1502 F pulseaudio plejaden 2151 F pulseaudio Date: Fri Mar 21 23:26:37 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-20 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140318) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 20A7005JGE ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=59ec0854-9dc0-41fd-a7b9-da9df8969a7f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [LENOVO 20A7005JGE] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET30WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7005JGE 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:bvrGRET30WW(1.07):bd01/13/2014:svnLENOVO:pn20A7005JGE:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7005JGE:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7005JGE dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1296066] Re: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure
I also have this bug. Same laptop (Lenovo thinkpad X1 carbon gen2). Ubuntu 14.04, fresh install (today). This blog post talk about the same bug : http://www.adventuresinoss.com/?p=3698 . It identifies the origin as "xhci_hcd". One solution is to deactivate the USB3 in the BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1296066 Title: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: system does not wake up after sudo pm-suspend. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1502 F pulseaudio plejaden 2151 F pulseaudio /dev/snd/controlC0: lightdm1502 F pulseaudio plejaden 2151 F pulseaudio Date: Fri Mar 21 23:26:37 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-20 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140318) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 20A7005JGE ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=59ec0854-9dc0-41fd-a7b9-da9df8969a7f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [LENOVO 20A7005JGE] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET30WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7005JGE 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:bvrGRET30WW(1.07):bd01/13/2014:svnLENOVO:pn20A7005JGE:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7005JGE:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7005JGE dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1296066] Re: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure
** Changed in: linux (Ubuntu) Status: Expired => 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/1296066 Title: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: system does not wake up after sudo pm-suspend. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1502 F pulseaudio plejaden 2151 F pulseaudio /dev/snd/controlC0: lightdm1502 F pulseaudio plejaden 2151 F pulseaudio Date: Fri Mar 21 23:26:37 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-20 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140318) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 20A7005JGE ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=59ec0854-9dc0-41fd-a7b9-da9df8969a7f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [LENOVO 20A7005JGE] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET30WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7005JGE 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:bvrGRET30WW(1.07):bd01/13/2014:svnLENOVO:pn20A7005JGE:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7005JGE:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7005JGE dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308674] Re: [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked
look here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377120 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308674 Title: [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Fedora: Unknown Bug description: This happens on my X220, running trusty, linux 3.13.0-24-generic. It's the exact same problem discussed on https://bugzilla.redhat.com/show_bug.cgi?id=1067071. Discussed also on kernel mailing list: https://lkml.org/lkml/2014/2/19/720. It worked on 3.12, and upstream acknowledges the regression. To reproduce, remove the X220 from the dock. The brightness is set to minimum (the screen is nearly unreadable) and the brightness control is broken, you can't adjust it by hardware keys. My hardware: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21da Kernel driver in use: i915 Docked on a ThinkPad mini dock series 3. I have nothing much relevant in /var/log/syslog. Below there are excerpts of it when brightness is working: Apr 16 14:55:37 galactica kernel: [79261.217384] [drm:asle_set_backlight], bclp = 0x80ff Apr 16 14:55:37 galactica kernel: [79261.217390] [drm:asle_set_backlight], updating opregion backlight 255/255 Apr 16 14:55:37 galactica kernel: [79261.217394] [drm:intel_panel_get_max_backlight], max backlight PWM = 4648 Apr 16 14:55:37 galactica kernel: [79261.217396] [drm:intel_panel_actually_set_backlight], set backlight PWM = 4590 Apr 16 14:55:37 galactica kernel: [79261.217537] [drm:asle_set_pwm_freq], PWM freq is not supported And brightness not working: Apr 16 15:23:46 galactica kernel: [80948.263160] [drm:asle_set_backlight], bclp = 0x8058 Apr 16 15:23:46 galactica kernel: [80948.263168] [drm:asle_set_pwm_freq], PWM freq is not supported Apr 16 15:23:46 galactica kernel: [80948.280637] [drm:asle_set_backlight], bclp = 0x8041 Apr 16 15:23:46 galactica kernel: [80948.280642] [drm:asle_set_pwm_freq], PWM freq is not supported A workaround is to echo values directly to /sys/class/backlight/intel_backlight/brightness. Maximum brightness is 4648 (/sys/class/backlight/intel_backlight/max_brightness). e.g.: # echo 500 > /sys/class/backlight/intel_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ursula 3881 F pulseaudio /dev/snd/controlC0: ursula 3881 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 15:09:23 2014 HibernationDevice: RESUME=UUID=68890e28-0eee-4184-9456-cc267c4a5f31 InstallationDate: Installed on 2013-05-27 (323 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: LENOVO 4286CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4db5451d-c250-47bc-9c4e-235fb1967ee5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-04 (162 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1308674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
