[Bug 510243] [NEW] linux-ec2 x86_64 memory calculation incorrect

2010-01-20 Thread Major Hayden
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

[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)

2015-02-06 Thread Major Hayden
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

[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)

2015-02-05 Thread Major Hayden
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

[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)

2015-02-05 Thread Major Hayden
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

[Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

2015-02-07 Thread Major Hayden
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.

[Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)

2015-02-02 Thread Major Hayden
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

[Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

2015-02-12 Thread Major Hayden
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

[Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

2015-02-18 Thread Major Hayden
@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

[Bug 1638695] Re: Python 2.7.12 performance regression

2017-02-13 Thread Major Hayden
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

[Bug 1657837] [NEW] systemd-networkd can't add a VLAN interface to bridge

2017-01-19 Thread Major Hayden
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

[Bug 1638695] Re: Python 2.7.12 performance regression

2016-11-10 Thread Major Hayden
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

[Bug 1638695] [NEW] Python 2.7.12 performance regression

2016-11-02 Thread Major Hayden
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

[Bug 1638695] Re: Python 2.7.12 performance regression

2016-11-03 Thread Major Hayden
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

[Bug 1638695] Re: Python 2.7.12 performance regression

2016-11-03 Thread Major Hayden
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.

[Bug 1638695] Re: Python 2.7.12 performance regression

2017-08-17 Thread Major Hayden
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.

[Bug 1702910] Re: System freeze after in6_dev_finish_destroy errors

2017-09-19 Thread Major Hayden
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