[Bug 510243] [NEW] linux-ec2 x86_64 memory calculation incorrect
Public bug reported: Brief summary: The linux-ec2 kernel erroneously adds in the freed initrd memory to the total memory allocated to the vm which makes the output of 'free' misleading. For example, if you create a domU with 256MB of RAM and the initrd is 9MB in size, your instance will show 265MB of RAM when you run 'free'. Steps to reproduce: 1) Create a Xen domU of any distribution on an x86_64 hypervisor running Xen 3.0.3 through 3.4.2 2) Use the linux-ec2 kernel from karmic or lucid to boot the domU paravirtualized 3) Run free If I create a 256MB instance, I see the following in the dmesg output: [1.491064] Freeing initrd memory: 9652k freed [1.600141] Freeing unused kernel memory: 188k freed Once it boots, and I run free, it shows 265MB of total memory: # free -m total used free sharedbuffers cached Mem: 265262 3 0 5 90 -/+ buffers/cache:166 99 Swap: 511 0511 The odd part is that it increases the used memory by 9MB as well to make up for it. In summary, this is a somewhat cosmetic issue, but the instance operates normally otherwise. ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Description changed: Brief summary: The linux-ec2 kernel erroneously adds in the freed initrd memory to the total memory allocated to the vm which makes the output of 'free' misleading. For example, if you create a domU with 256MB of RAM and the initrd is 9MB in size, your instance will show 265MB of RAM when you run 'free'. Steps to reproduce: - 1) Create a Xen domU of any distribution + 1) Create a Xen domU of any distribution on an x86_64 hypervisor running Xen 3.0.3 through 3.4.2 2) Use the linux-ec2 kernel from karmic or lucid to boot the domU paravirtualized 3) Run free If I create a 256MB instance, I see the following in the dmesg output: [1.491064] Freeing initrd memory: 9652k freed [1.600141] Freeing unused kernel memory: 188k freed Once it boots, and I run free, it shows 265MB of total memory: # free -m - total used free sharedbuffers cached + total used free sharedbuffers cached Mem: 265262 3 0 5 90 -/+ buffers/cache:166 99 Swap: 511 0511 The odd part is that it increases the used memory by 9MB as well to make up for it. In summary, this is a somewhat cosmetic issue, but the instance operates normally otherwise. -- linux-ec2 x86_64 memory calculation incorrect https://bugs.launchpad.net/bugs/510243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
Thanks for the deep dive, Elvis! :) Is it possible to adjust some of these settings in the Ubuntu packages, or is just the way it will be going forward? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702910] Re: System freeze after in6_dev_finish_destroy errors
There's a discussion here possibly about the same problem: https://patchwork.ozlabs.org/patch/801533/ And they referred to this patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/?id=242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00 The changes look like they line up with the call trace order, but I could be wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702910 Title: System freeze after in6_dev_finish_destroy errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
My testing was done on Xen virtual machines, KVM virtual machines, and bare metal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
Thanks for confirming that, Matthias. Testing with GCC 4.8 seemed to yield (mostly) better results. I put the data into a Google Sheet: https://goo.gl/9gW82j Out of the 10 pyperformance tests: * 3 tests were actually faster with python compiled w/gcc-4.8 * 4 tests were slightly slower (but within 5%) * 3 tests were ~ 20-25% slower Overall, these numbers look quite a bit better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657837] [NEW] systemd-networkd can't add a VLAN interface to bridge
Public bug reported: This is apparently fixed in systemd 231: https://lists.freedesktop.org/archives/systemd- devel/2016-August/037385.html When systemd tries to put a VLAN interface into a bridge on Xenial, it fails: # journalctl --boot -u systemd-networkd Jan 15 09:16:46 hydrogen systemd[1]: Started Network Service. Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: netdev exists, using existing without changing its parameters Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Could not append VLANs: Operation not permitted Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Failed to assign VLANs to bridge port: Operation not permitted Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Could not set bridge vlan: Operation not permitted Jan 15 09:16:59 hydrogen systemd-networkd[1903]: enp3s0: Configured Jan 15 09:16:59 hydrogen systemd-networkd[1903]: enp2s0: Configured Here are the systemd-networkd configs I used: root@hydrogen:/etc/systemd/network# cat enp3s0.network [Match] Name=enp3s0 [Network] VLAN=vlan10 root@hydrogen:/etc/systemd/network# cat vlan10.netdev [NetDev] Name=vlan10 Kind=vlan [VLAN] Id=10 root@hydrogen:/etc/systemd/network# cat vlan10.network [Match] Name=vlan10 [Network] Bridge=br-mgmt root@hydrogen:/etc/systemd/network# cat br-mgmt.netdev [NetDev] Name=br-mgmt Kind=bridge root@hydrogen:/etc/systemd/network# cat br-mgmt.network [Match] Name=br-mgmt [Network] Address=172.29.236.21/22 ** Affects: systemd (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/1657837 Title: systemd-networkd can't add a VLAN interface to bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1657837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] [NEW] Python 2.7.12 performance regression
Public bug reported: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
Hello Matthias, I'm sorry for the confusion there. What I meant is that I compiled 2.7.12 on 14.04 and found that it had the same performance as 2.7.6 (from the default Ubuntu python package) on 14.04. I also loaded Xenial's kernel on the 14.04 installation and found no performance difference either. The problem seems to be unique to 2.7.12 on 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
I can try that. Just to be clear, you're suggesting to do the following: 1) Install gcc-4.8 on 16.04 2) Compile 2.7.12 with gcc-4.8 on 16.04 3) Re-run tests Did I get that right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04
@Andon-2 -- I wish I had better news. :/ Long story short, I was able to build a 3.19-ish kernel with some additional ASoC patches earlier this week and the card showed up on the I2S bus with full input/output capabilities. However, whenever I played sounds, I never heard anything. PulseAudio showed data going into the card (signal levels were moving), but nothing was heard via speakers or headphones. I dug into amixer to figure out if something needed to be unmuted or an amplifier switched on and found nothing. I tried with a newer kernel last night but there are some serious hard lockup bugs in the pre-3.20 patches. I'm now kicking myself for not saving the kernel branch that I had the other night. :/ The contact at Realtek feels that there's either a BIOS update required or one small option on the card isn't enabled. I'd like to test again but the kernel is a bit of a mess as of when I tested it last night. Hacking DSDT's won't fix the issue according to someone who has much more knowledge about ACPI tables than I do. TL;DR: - Waiting on 3.20-rc1 - Card shows up, can't hear anything - Realtek gave me some stuff to test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413446 Title: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)
FWIW, this issue happens for me on the same hardware on Fedora. Already tried kernels 3.17.4, 3.18.3, and 3.18.5. Blacklisting i2c_hid doesn't have an effect on the touchpad freeze-ups that Jared noted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416601 Title: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)
I'll be firing up a kernel bisect this weekend to see if I can find the issue. From multiple reports (incuding some in the RHBZ[1]), 3.16 works and 3.17 has issues. 3.18 and 3.19-rc7 have no improvements. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1188439 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416601 Title: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)
Mario -- So 3.18 didn't have any touchpad freeze or tapping issues? I've tested 3.18.3 and 3.18.5 on Fedora and they have the freezes. I'm wondering if something broke between 3.18.0 and 3.18.3. Do you have any additional details on that 3.18 kernel you tested? Perhaps the git hash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416601 Title: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)
Done with the git bisect. It's somewhere in the late days of 3.17 and early days of 3.18. Here's the RHBZ with the patch: https://bugzilla.redhat.com/show_bug.cgi?id=1188439#c25 I'm hoping someone with more knowledge than me around this part of the kernel can make sense of it. If I pull the patch, the touchpad works extremely well (see RHBZ entry for more). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416601 Title: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04
I tested David's rt288.patch above on 3.19-rc7 and it had no effect on the audio problem. I tried it with and without reverting the i2c IRQ patch that fixed the touchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413446 Title: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04
I'm building with those new SoC patches now. My first couple of builds didn't work out and I discovered that my .config didn't have modules enabled for some of those SoC audio codecs. I'll hopefully know something more soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413446 Title: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
