[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
BTW, just applying this patch[1] to bluez package from 18.04 fixes the a2dp problem for me with Sony WH-CH700N headphones. Patch applies cleanly to 5.48. 1. https://git.kernel.org/pub/scm/bluetooth/bluez.git/patch/?id=477ecca127c529611adbc53f08039cefaf86305d -- 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/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
May we have this backported to 18.04? -- 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/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
lspci no longer shows "Intel Corporation Wireless 7260" entry on my system. So I guess it is a hardware problem. Funny thing that bluetooth which is located on the same chip still works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: Confirmed Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 libahci ipmi_devintf mii ipmi_msghandler video wmi Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swa
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
Joseph do you need any more information? Any ideas to try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: Confirmed Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 libahci ipmi_devintf mii ipmi_msghandler video wmi Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5 Tainted: P OE4.15.0-34-generic #37-Ubuntu Sep 24 11:42:10 bonobo kernel: [109525.538983] Hardware name:
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
In my case crash can happen on freshly booted system as well. And it is more likely to happen when I'm using Wi-Fi actively, although it sometimes happens even if I barely use Wi-Fi (eg. I'm connected via ethernet cable and Wi-Fi at the same time and routing is configured to use the cable). @berend have you tried replacing the card? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: Confirmed Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rts
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
I've grepped through dmesg and journalctl there is zero messages about temperature from iwlwifi in my case. I've some from CPU, but they are probably not related. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: Confirmed Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 libahci ipmi_devintf mii ipmi_msghandler video wmi Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5 Tainted: P
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
I've tested with mainline kernel and it is crashes as well. Also I've tried booting previous Ubuntu releases (4.15.0-20-generic, 4.15.0-29-generic, 4.15.0-32-generic, 4.15.0-33-generic) and bug happens with all of them. This is strange because I've used these kernels without any problems for months. Wi-Fi worked extremely stable until problem recently appeared. So looks like bug was present for long time, however it have not manifested itself. But some non-kernel update uncovered it. Bug is pretty severe on my system, it happens in few minutes of active Wi-Fi usage (eg. open speedtest.net and run it for few times). If I do not use Wi-Fi at maximum speed it (eg. just listening online radio) it may work for hours. Log from mainline kernel: [ 119.671276] [ cut here ] [ 119.671280] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) [ 119.671333] WARNING: CPU: 7 PID: 0 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2009 iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi] [ 119.671335] Modules linked in: rfcomm ccm ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 ipt_MASQUERADE xt_CHECKSUM iptable_nat nf_nat_ipv4 nf_nat iptable_mangle bridge stp llc ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_mac xt_tcpudp xt_conntrack nf_conntrack vmw_vsock_vmci_transport vsock nf_defrag_ipv6 nf_defrag_ipv4 vmw_vmci iptable_filter bpfilter cmac bnep binfmt_misc nls_iso8859_1 arc4 cmdlinepart intel_spi_platform intel_spi spi_nor asus_nb_wmi mtd asus_wmi mxm_wmi sparse_keymap gpio_ich snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic uvcvideo snd_hda_intel videobuf2_vmalloc videobuf2_memops intel_rapl videobuf2_v4l2 x86_pkg_temp_thermal videobuf2_common intel_powerclamp snd_hda_codec videodev btusb coretemp snd_hda_core btrtl btbcm snd_hwdep media [ 119.671388] btintel kvm_intel bluetooth snd_pcm snd_seq_dummy iwlmvm snd_seq_oss mac80211 snd_seq_midi intel_cstate ecdh_generic iwlwifi snd_seq_midi_event snd_rawmidi intel_rapl_perf joydev rtsx_pci_ms memstick cfg80211 snd_seq input_leds serio_raw snd_seq_device snd_timer snd mei_me mei soundcore mac_hid ie31200_edac lpc_ich wmi sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c algif_skcipher af_alg dm_crypt hid_generic usbhid hid i915 kvmgt vfio_mdev mdev vfio_iommu_type1 crct10dif_pclmul vfio crc32_pclmul ghash_clmulni_intel pcbc kvm rtsx_pci_sdmmc irqbypass i2c_algo_bit aesni_intel drm_kms_helper syscopyarea aes_x86_64 sysfillrect crypto_simd cryptd sysimgblt fb_sys_fops glue_helper drm [ 119.671457] psmouse ahci rtsx_pci r8169 libahci video [ 119.671467] CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.19.0-041900rc5-generic #201809231830 [ 119.671468] Hardware name: ASUSTeK COMPUTER INC. N751JK/N751JK, BIOS N751JK.205 03/11/2015 [ 119.671480] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi] [ 119.671482] Code: 05 ee 49 8d 56 08 bf 00 20 00 00 e8 92 1a 87 ec e9 31 ff ff ff 89 c6 48 c7 c7 60 f3 c5 c0 c6 05 5c 7a 02 00 01 e8 fa 3f 85 ec <0f> 0b e9 ec fe ff ff 48 8b 7b 30 48 c7 c1 c8 f3 c5 c0 31 d2 31 f6 [ 119.671484] RSP: 0018:9f091edc3dc8 EFLAGS: 00010082 [ 119.671487] RAX: RBX: 9f0914830018 RCX: 0006 [ 119.671488] RDX: 0007 RSI: 0092 RDI: 9f091edd6420 [ 119.671490] RBP: 9f091edc3de8 R08: 0001 R09: 0472 [ 119.671491] R10: 0004 R11: R12: 9f091483a298 [ 119.671493] R13: 9f091edc3df8 R14: R15: 9f0914830018 [ 119.671495] FS: () GS:9f091edc() knlGS: [ 119.671497] CS: 0010 DS: ES: CR0: 80050033 [ 119.671499] CR2: 7fe754035d80 CR3: 7640a002 CR4: 001606e0 [ 119.671500] Call Trace: [ 119.671502] [ 119.671514] iwl_read_prph+0x38/0x90 [iwlwifi] [ 119.671526] iwl_trans_pcie_log_scd_error+0x13b/0x210 [iwlwifi] [ 119.671531] ? trigger_load_balance+0x3b/0x190 [ 119.671542] iwl_pcie_txq_stuck_timer+0x4b/0x70 [iwlwifi] [ 119.671553] ? iwl_pcie_clear_cmd_in_flight+0xb0/0xb0 [iwlwifi] [ 119.671558] call_timer_fn+0x30/0x130 [ 119.671561] run_timer_softirq+0x3ea/0x420 [ 119.671564] ? ktime_get+0x3c/0xa0 [ 119.671569] ? lapic_next_deadline+0x26/0x30 [ 119.671572] ? clockevents_program_event+0x93/0xf0 [ 119.671578] __do_softirq+0xdc/0x2b5 [ 119.671582] irq_exit+0xb7/0xc0 [ 119.671586] smp_apic_timer_interrupt+0x79/0x130 [ 119.671589] apic_timer_interrupt+0xf/0x20 [ 119.671590] [ 119.671596] RIP: 0010:cpuidle_enter_state+0xb9/0x310 [ 119.671598] Code: ff e8 db c7 87 ff 80 7d cb 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 35 02 00 00 31 ff e8 2e e5 8d ff fb 66 0f 1f 44 00 00 <48> b8 ff ff ff ff f3 01 00 00 4c 2b 7d d0 ba ff ff ff 7f 49 39 c7 [ 119.671599] RSP: 0018:af6d0196be50 EFLAGS:
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
I've meant with 33 and 34. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: Incomplete Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 libahci ipmi_devintf mii ipmi_msghandler video wmi Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5 Tainted: P OE4.15.0-34-generic #37-Ubuntu Sep 24 11:42:10 bonobo kernel: [109525.538983] Hardware name: System76, Inc.
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
Started happen to me few days ago as well. Happens with 4.15.0-34-generic and 4.15.0-34-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: Incomplete Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 libahci ipmi_devintf mii ipmi_msghandler video wmi Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5 Tainted: P OE4.15.0-34-generic #37-Ubuntu Sep 24 11:42:10 bonobo
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Hi Richard, I do not use Precise anymore, so I do not know whether this bug still present. But this problem was present only in 3.2 kernel. MTU always worked fine with 3.5 kernel, Pricese and Trusty. Your logs indicate that it was probably fixed in 3.2 kernel as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in linux package in Ubuntu: Incomplete Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise), results are same to 3.5. Is there any chance to get fixes from 3.5/3.8 backported to the default precise kernel 3.2? 1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.2 Archi
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
I meant: MTU always worked fine with 3.5 kernel, Trusty and 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/1177507
Title:
per route mtu settings are broken in linux kernel 3.2
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello,
Looks like setting per route mtu (as described in [1]) is broken in linux
kernel 3.2 (default kernel from ubuntu 12.04).
I made script to illustrate this:
root@germany7:~# cat route-mtu
#!/bin/bash
uname -a
ip tuntap add dev test mode tun
ifconfig test 10.1.1.1/16 mtu 1500
echo =
echo No per route mtu entry
ping -c1 -Mdo -s2000 10.1.1.2
echo =
echo Per route MTU is set to 800
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
echo =
echo Per route MTU is set to 600
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
echo =
echo No per route mtu entry
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip tuntap del dev test mode tun
With kernel 3.2 I get following output:
Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC
2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
After once set to 800, MTU is always 800, even if you add different
route and clean routing cache.
It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything
works like expected:
root@germany7:~# ./route-mtu
Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05
UTC 2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise),
results are same to 3.5.
Is there any chance to get fixes from 3.5/3.8 backported to the
default precise kernel 3.2?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Oh, really? I think appreciate tag would be developer-emulating-work. Anyone can check that problem with ubuntu kernel 3.2 on every system, independently of hw configuration and bios version. More over, problem is fixed upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise), results are same to 3.5. Is there any chance to get fixes from 3.5/3.8 backported to the default precise kernel 3.2? 1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 ArecordDevices:
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Also Joseph Salisbury (jsalisbury) already marked this change as
Triaged. I reverted this to Verified by accident before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1177507
Title:
per route mtu settings are broken in linux kernel 3.2
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Hello,
Looks like setting per route mtu (as described in [1]) is broken in linux
kernel 3.2 (default kernel from ubuntu 12.04).
I made script to illustrate this:
root@germany7:~# cat route-mtu
#!/bin/bash
uname -a
ip tuntap add dev test mode tun
ifconfig test 10.1.1.1/16 mtu 1500
echo =
echo No per route mtu entry
ping -c1 -Mdo -s2000 10.1.1.2
echo =
echo Per route MTU is set to 800
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
echo =
echo Per route MTU is set to 600
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
echo =
echo No per route mtu entry
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip tuntap del dev test mode tun
With kernel 3.2 I get following output:
Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC
2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
After once set to 800, MTU is always 800, even if you add different
route and clean routing cache.
It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything
works like expected:
root@germany7:~# ./route-mtu
Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05
UTC 2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise),
results are same to 3.5.
Is there any chance to get fixes from 3.5/3.8 backported to the
default precise kernel 3.2?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
I'm pretty sure this problem is not depends on hardware. I tried not only on mine laptop, but on several servers with different hardware configurations. You can run attached script and will see that it happens on your system too (if you are running ubuntu kernel 3.2). ** 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/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise), results are same to 3.5. Is there any chance to get fixes from 3.5/3.8 backported to the default precise kernel 3.2? 1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html --- AlsaVersion: Advanced Linux Sound Architec
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
I meant: this bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1177507
Title:
per route mtu settings are broken in linux kernel 3.2
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Hello,
Looks like setting per route mtu (as described in [1]) is broken in linux
kernel 3.2 (default kernel from ubuntu 12.04).
I made script to illustrate this:
root@germany7:~# cat route-mtu
#!/bin/bash
uname -a
ip tuntap add dev test mode tun
ifconfig test 10.1.1.1/16 mtu 1500
echo =
echo No per route mtu entry
ping -c1 -Mdo -s2000 10.1.1.2
echo =
echo Per route MTU is set to 800
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
echo =
echo Per route MTU is set to 600
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
echo =
echo No per route mtu entry
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip tuntap del dev test mode tun
With kernel 3.2 I get following output:
Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC
2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
After once set to 800, MTU is always 800, even if you add different
route and clean routing cache.
It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything
works like expected:
root@germany7:~# ./route-mtu
Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05
UTC 2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise),
results are same to 3.5.
Is there any chance to get fixes from 3.5/3.8 backported to the
default precise kernel 3.2?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COM
