[Bug 1878780] [NEW] [PATCH] hddtemp reports drive name incorrectly
Public bug reported: hddtemp reports drive name incorrectly for some drives: $ sudo hddtemp /dev/sda /dev/sda: KINGSTON RBU-SC100S37128DG �: 37°C Note extra spaces and garbage characters before colon. This is not only minor cosmetic issue, but breaks some gnome-shell plugins for HDD temperature reporting. I've found a patch included into Fedora which fixes the issue: https://bugzilla.redhat.com/show_bug.cgi?id=1061649 hddtemp output is correct with the patch applied: $ sudo hddtemp /dev/sda /dev/sda: KINGSTON RBU-SC100S37128GD: 37°C Patched package is available in my ppa: https://launchpad.net/~yura-p/+archive/ubuntu/tests ** Affects: hddtemp (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "hddtemp-fix-drive-name.diff" https://bugs.launchpad.net/bugs/1878780/+attachment/5371903/+files/hddtemp-fix-drive-name.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878780 Title: [PATCH] hddtemp reports drive name incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hddtemp/+bug/1878780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691025] Re: Installing xpra on HWE-enabled LTS breaks system
** Also affects: hwe-next Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691025 Title: Installing xpra on HWE-enabled LTS breaks system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1691025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1793997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1793997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1793997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1793997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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:
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1793997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1793997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"
still happens in 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709699 Title: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Is it possible to backport fix which recently landed for bionic to xenial? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
** Also affects: gdm Importance: Undecided Status: New ** Also affects: gnome-shell Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1286910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573959] Re: On-screen text disappears after suspend
I'm having same problem with: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1573959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
I believe this is not duplicate bug. And it is definitely not in case if GNOME shell in use, not compiz. ** This bug is no longer a duplicate of bug 1605012 compiz lockscreen crashed with SIGABRT in AcceleratorController :: OnActionActivated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1286910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
Exactly the same issue with GNOME in Ubuntu 16.04 ** Also affects: ubuntu-gnome Importance: Undecided Status: New ** Project changed: ubuntu-gnome => gnome-screensaver ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1286910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056869] Re: Make libpq multi-arch capable
** Also affects: postgresql-9.3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056869 Title: Make libpq multi-arch capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.3/+bug/1056869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056869] Re: Make libpq multi-arch capable
Hello, Is it possible to backport this fix to trusty (postgresql-9.3)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056869 Title: Make libpq multi-arch capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.4/+bug/1056869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
** Changed in: linux (Ubuntu) Status: Triaged = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
apport information ** Tags added: apport-collected ** Description changed: 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 COMMAND + /dev/snd/controlC0: yura 2759 F pulseaudio + Card0.Amixer.info: + Card hw:0 'Intel'/'HDA Intel at 0xf480 irq 45' +Mixer name : 'Intel Cantiga HDMI' +
[Bug 1177507] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672351/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672352/+files/AplayDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672353/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672354/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672355/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672356/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Card0.Codecs.codec.1.txt
apport information ** Attachment added: Card0.Codecs.codec.1.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672357/+files/Card0.Codecs.codec.1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Card0.Codecs.codec.3.txt
apport information ** Attachment added: Card0.Codecs.codec.3.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672358/+files/Card0.Codecs.codec.3.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672359/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672360/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672361/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672362/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672363/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672364/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672365/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672366/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672367/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672368/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672369/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672370/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672371/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1177507/+attachment/3672372/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] [NEW] per route mtu settings are broken in linux kernel 3.2
Public bug reported: 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 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1177507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
** Description changed: 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 + 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. + 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 + 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. + 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 To manage
[Bug 569273] Re: memory leak in gnome-power-manager
Why won`t fix for lucid? Please backport to lucid also -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569273 Title: memory leak in gnome-power-manager To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/569273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
