Re: UDS Developments
On Tue, 2012-05-08 at 22:02 +0200, Kaj Ailomaa wrote: # CONFIG_NO_HZ is not set I and many others used NO_HZ yes for a long time without any issues. For testing purpose I switched to not set too. Don't forget to enable hrtimer/hpet modules and not to set all kinds of trace/debug options. Default CPU frequency scaling should be performance, but ondemand should be possible to. If threadirqs wouldn't be compiled as a string to the kernel, it would be possible to boot without threadirqs. Dunno, but this might be an advantage for a recovery boot or if performance of the GUI sometimes is more important than threading for audio work. This might enable t simply use different boot options instead of using different kernels. - Ralf -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On Tue, 2012-05-08 at 14:09 -0700, Scott Lavender wrote: -- Please don't post under the signature lines ;). my understanding is that the patch is what actually changes the config file. perhaps I am mistaken, however. It's likely that you're right, since spinymouse@precise:~$ grep PREEMPT /media/oz/boot/config-3.0.0-17-generic # CONFIG_PREEMPT_RCU is not set CONFIG_PREEMPT_NOTIFIERS=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set So to set CONFIG_PREEMPT will unset PREEMPT_VOLUNTARY and might do additional changes, e.g. it perhaps automatically will set PREEMPT_RCU. spinymouse@precise:~$ grep FORCE /media/oz/boot/config-3.0.0-17-generic CONFIG_IRQ_FORCED_THREADING=y Hm, already is set. spinymouse@precise:~$ grep HZ /media/oz/boot/config-3.0.0-17-generic CONFIG_RCU_FAST_NO_HZ=y CONFIG_NO_HZ=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_MACHZ_WDT=m So the second line for a two line config patch might be to set HZ_1000. For the same kernel source there might be a patch available that does set two options only for the config, than running oldconfig couldn't harm and it's ready to build the kernel. When I build 3.0.30 I used the config of 3.2.0-23-lowlatency and only echoed this by my build script: # Clean LOCALVERSION grep CONFIG_LOCALVERSION .config echo CONFIG_LOCALVERSION=\\ .config # Optimize config echo CONFIG_MK8=y .config echo CONFIG_DEBUG_KERNEL=n .config echo CONFIG_NO_HZ=n .config make oldconfig IIRC there was no need to clean LOCALVERSION, MK8 for optimizing to my machine, IIRC DEBUG_KERNEL already is not set, so the echo also isn't needed, but NO_HZ was the only option that is set. I'll check this now: spinymouse@precise:~$ grep NO_HZ /boot/config-3.2.0-23-lowlatency # CONFIG_NO_HZ is not set I'm mistaken. So when building a new kernel, there's only the need to use the config of another lowlatency and to run oldconfig. No patch is needed, it's only needed for the config when using the config of a generic. - Ralf -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On Wed, May 9, 2012 1:39 am, Ralf Mardorf wrote: On Tue, 2012-05-08 at 22:02 +0200, Kaj Ailomaa wrote: # CONFIG_NO_HZ is not set I and many others used NO_HZ yes for a long time without any issues. For testing purpose I switched to not set too. There are still some tweaks we need to look at. I noticed that one as well. We tend to be blind to some things. This one affects midi more than audio as I understand... probably why we missed it. Don't forget to enable hrtimer/hpet modules and not to set all kinds of trace/debug options. Default CPU frequency scaling should be performance, but ondemand should be possible to. Yup. If threadirqs wouldn't be compiled as a string to the kernel, it would be possible to boot without threadirqs. Dunno, but this might be an advantage for a recovery boot or if performance of the GUI sometimes is more important than threading for audio work. This might enable t simply use different boot options instead of using different kernels. As we are also a graphics distro (or trying to be) it may be worth while configuring grub to have three options per kernel. Graphics, Audio and Recovery. Our main idea with making threadirqs a boot option was that it would be easier to auto build because it is then the same as the normal ubuntu kernel (no patches required) just a different config. But, you have pointed out another reason. Len -- Len Ovens www.OvenWerks.net -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On 05/09/2012 05:50 PM, Len Ovens wrote: On Wed, May 9, 2012 1:39 am, Ralf Mardorf wrote: On Tue, 2012-05-08 at 22:02 +0200, Kaj Ailomaa wrote: # CONFIG_NO_HZ is not set I and many others used NO_HZ yes for a long time without any issues. For testing purpose I switched to not set too. There are still some tweaks we need to look at. I noticed that one as well. We tend to be blind to some things. This one affects midi more than audio as I understand... probably why we missed it. Don't forget to enable hrtimer/hpet modules and not to set all kinds of trace/debug options. Default CPU frequency scaling should be performance, but ondemand should be possible to. Yup. If threadirqs wouldn't be compiled as a string to the kernel, it would be possible to boot without threadirqs. Dunno, but this might be an advantage for a recovery boot or if performance of the GUI sometimes is more important than threading for audio work. This might enable t simply use different boot options instead of using different kernels. As we are also a graphics distro (or trying to be) it may be worth while configuring grub to have three options per kernel. Graphics, Audio and Recovery. Our main idea with making threadirqs a boot option was that it would be easier to auto build because it is then the same as the normal ubuntu kernel (no patches required) just a different config. But, you have pointed out another reason. Len I've also recenlty discovered that threadirqs and the rtirq script are actually making one of my machines misbehave, something that I've never heard of before, so it might be a good idea to think about having that as a tweakable option between boots, since it might be causing problems for some machines, that normally don't need it enabled. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On 05/09/2012 11:02 AM, Ralf Mardorf wrote:
On Tue, 2012-05-08 at 14:09 -0700, Scott Lavender wrote:
--
Please don't post under the signature lines ;).
my understanding is that the patch is what actually changes the config
file. perhaps I am mistaken, however.
It's likely that you're right, since
spinymouse@precise:~$ grep
PREEMPT /media/oz/boot/config-3.0.0-17-generic
# CONFIG_PREEMPT_RCU is not set
CONFIG_PREEMPT_NOTIFIERS=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
This is the patch that enables threadirqs by default:
0001-UBUNTU-SAUCE-Made-kernel-irq-threaded-by-default.patch
From 2ff937d93960829c33189b189ae0f19a1d5f6aab Mon Sep 17 00:00:00 2001
From: Alessio Igor Bogani abog...@ubuntu.com
Date: Wed, 28 Mar 2012 11:05:53 +0200
Subject: [PATCH] UBUNTU: SAUCE: Made kernel irq-threaded by default
Signed-off-by: Alessio Igor Bogani abog...@ubuntu.com
---
kernel/irq/manage.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index ae95cd2..c48e1d8 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -18,14 +18,20 @@
#include internals.h
#ifdef CONFIG_IRQ_FORCED_THREADING
-__read_mostly bool force_irqthreads;
+__read_mostly bool force_irqthreads = true;
static int __init setup_forced_irqthreads(char *arg)
{
force_irqthreads = true;
return 0;
}
+static int __init setup_no_irqthreads(char *arg)
+{
+ force_irqthreads = false;
+ return 0;
+}
early_param(threadirqs, setup_forced_irqthreads);
+early_param(nothreadirqs, setup_no_irqthreads);
#endif
/**
-- 1.7.0.4
--
Ubuntu-Studio-devel mailing list
Ubuntu-Studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On 05/09/2012 11:02 AM, Ralf Mardorf wrote: On Tue, 2012-05-08 at 14:09 -0700, Scott Lavender wrote: -- Please don't post under the signature lines ;). my understanding is that the patch is what actually changes the config file. perhaps I am mistaken, however. It's likely that you're right, since spinymouse@precise:~$ grep PREEMPT /media/oz/boot/config-3.0.0-17-generic # CONFIG_PREEMPT_RCU is not set CONFIG_PREEMPT_NOTIFIERS=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set So to set CONFIG_PREEMPT will unset PREEMPT_VOLUNTARY and might do additional changes, e.g. it perhaps automatically will set PREEMPT_RCU. spinymouse@precise:~$ grep FORCE /media/oz/boot/config-3.0.0-17-generic CONFIG_IRQ_FORCED_THREADING=y Hm, already is set. spinymouse@precise:~$ grep HZ /media/oz/boot/config-3.0.0-17-generic CONFIG_RCU_FAST_NO_HZ=y CONFIG_NO_HZ=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_MACHZ_WDT=m So the second line for a two line config patch might be to set HZ_1000. For the same kernel source there might be a patch available that does set two options only for the config, than running oldconfig couldn't harm and it's ready to build the kernel. When I build 3.0.30 I used the config of 3.2.0-23-lowlatency and only echoed this by my build script: # Clean LOCALVERSION grep CONFIG_LOCALVERSION .config echo CONFIG_LOCALVERSION=\\ .config # Optimize config echo CONFIG_MK8=y .config echo CONFIG_DEBUG_KERNEL=n .config echo CONFIG_NO_HZ=n .config make oldconfig IIRC there was no need to clean LOCALVERSION, MK8 for optimizing to my machine, IIRC DEBUG_KERNEL already is not set, so the echo also isn't needed, but NO_HZ was the only option that is set. I'll check this now: spinymouse@precise:~$ grep NO_HZ /boot/config-3.2.0-23-lowlatency # CONFIG_NO_HZ is not set I'm mistaken. So when building a new kernel, there's only the need to use the config of another lowlatency and to run oldconfig. No patch is needed, it's only needed for the config when using the config of a generic. - Ralf Here's the address to the current git source git://kernel.ubuntu.com/themuso/ubuntu-precise-lowlatency -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On 05/09/2012 07:00 PM, Kaj Ailomaa wrote: Here's the address to the current git source git://kernel.ubuntu.com/themuso/ubuntu-precise-lowlatency Since I'm not a kernel maintainer myself, I don't know the full story behind how the source is generated or built. But, you will find the most interesting stuff related to the lowlatency flavor under debian.lowlatency. I believe some configs are auto-generated, but there's one config that is the basis for all the -lowlatency builds, which include the few necessary options that diff with the standard ubuntu config. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On Wed, 2012-05-09 at 18:54 +0200, Kaj Ailomaa wrote: threadirqs and the rtirq script are actually making one of my machines misbehave What exactly happens? - Ralf -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On 05/09/2012 07:19 PM, Ralf Mardorf wrote: On Wed, 2012-05-09 at 18:54 +0200, Kaj Ailomaa wrote: threadirqs and the rtirq script are actually making one of my machines misbehave What exactly happens? - Ralf I don't know. Haven't had the time to find out yet. I get massive amounts of xruns at quite high latencies. Without the threadirqs option enabled, all is fine at the usual low latencies I am able to get with this machine. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UDS Developments
On Wed, 2012-05-09 at 19:16 +0200, Kaj Ailomaa wrote: On 05/09/2012 07:00 PM, Kaj Ailomaa wrote: Here's the address to the current git source git://kernel.ubuntu.com/themuso/ubuntu-precise-lowlatency [snip] there's one config that is the basis for all the -lowlatency builds, which include the few necessary options that diff with the standard ubuntu config. Flagged this mail. I won't take a look at this now. - Ralf -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Minutes from the Developer Membership Board meeting - 2012-05-09
== Developer Membership Board meeting, 2012-05-09 == Chair: laney Present: barry stgraber tumbleweed micahg bdrung === MOTU application Ante Karamatić === Application: https://wiki.ubuntu.com/AnteKaramatic/DeveloperApplicationMOTU Voting: +1 barry tumbleweed micahg stgraber laney bdrung The application is accepted. Action: micahg to add permissions. === Per-Package uploader Ike Panhc === Application: https://wiki.ubuntu.com/IkePanhc/DeveloperApplication-PPU Voting for linux-armadaxp, linux-meta-armadaxp, linux-highbank and linux-meta-highbank (the latter two for discussion and approval on the mailing list after the enter the archive) Voting: +1 barry laney tumbleweed stgraber +0 micahg bdrung The application is accepted. ACTION: stgraber to add permissions === Per-Package uploader James Hunt === Application: https://wiki.ubuntu.com/JamesHunt/PPUApplication Voting for friendly-recovery, libnih, mountall, upstart Voting: +1 barry laney tumbleweed stgraber micahg bdrung The application is accepted. ACTION: stgraber to add permissions === AOB === Chair for next meeting: micahg -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] PhD student [ i...@cs.nott.ac.uk ] signature.asc Description: Digital signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
questions about current ways of work in Ubuntu release process
Hi All, Some of you might remember me, some of you won't. I used to be part of the Ubuntu community and loved every minute of it. I've been drawn to some other open source projects since then, but the apparent quality boost I'm experiencing with 12.04 has left me eager and curious about things, not to mention Mark's helped to engage this curiosity[0]. So, I'm terribly curious about: 1) we’ll ratchet up the continuous integration - What sort of continues integration system Ubuntu is using now? I guess its based on Jenkins ? I'd love to read the gory details somewhere. 2) smoke testing - is it done by hand by Ubuntu members, or also taken care of by the CI system? 3) automated benchmarking of the release - How's that done? Again, happy to read the gory details somewhere ;) 4) ..both qualitative and quantitative, with user research and testing continuing to shape our design decisions.. - How is user research being conducted? for testing, I suppose there's the community QA team the has the test cases executed by hand? How is it shaping the design decision? Are there new Launchpad modules that assist in that? 5) Is 'Fauna' another software / cloud component? (I've never seen such a blog post with so many cryptic words for the non native English speaker ;) 6) Where can I read more about 'Quantum' , the virtualized network madness in the cloud ;) ? Kudos to the great team of Ubuntu - reading all of this and asking all those question makes me wanna rejoin the party again, doing some catching up. I might also try to pitch up some of the practices to the other open source projects I'm part of ;) (I've always admired the way we do things in Ubuntu!) -- -Sivan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: questions about current ways of work in Ubuntu release process
On Wed, May 9, 2012 at 11:30 AM, Sivan Greenberg si...@omniqueue.comwrote: Hi All, Some of you might remember me, some of you won't. I used to be part of the Ubuntu community and loved every minute of it. I've been drawn to some other open source projects since then, but the apparent quality boost I'm experiencing with 12.04 has left me eager and curious about things, not to mention Mark's helped to engage this curiosity[0]. So, I'm terribly curious about: 5) Is 'Fauna' another software / cloud component? (I've never seen such a blog post with so many cryptic words for the non native English speaker ;) English borrows that from Latin: flora fauna === plants animals He was simply referring to the animal code names that Ubuntu uses. Also, I believe you missed your footnote link: [0] http://www.markshuttleworth.com/archives/1121 Sorry I can't help with any of the other more interesting questions. Evan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: questions about current ways of work in Ubuntu release process
On Wed, May 9, 2012 at 6:40 PM, Evan Huus eapa...@gmail.com wrote: English borrows that from Latin: flora fauna === plants animals Yes, flora I know - I was not familiar with fauna. Phew, I was going to email this to ubuntu-devel but then the bounce back told me only ubuntu-developers are allowed to post to it. He was simply referring to the animal code names that Ubuntu uses. Also, I believe you missed your footnote link: [0] http://www.markshuttleworth.com/archives/1121 Indeed I have, thanks for re-mentioning it. -Sivan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Problems with setuid app in Ubuntu 12.04
Hi all. I've recently installed Ubuntu 12.04 64bit. I'm using a proprietary VPN utility from Juniper Networks on my Linux system. In previous versions of Ubuntu, it worked just fine. In the current version of Ubuntu, I'm getting failures. For some reason it's not letting me invoke a setuid application. The way it is deployed is it unpacks into a hidden directory under $HOME, then the main VPN program needs to be made setuid root so that it can be invoked by me but do root-y things. Then, you can either run the tool directly from the command line or you can run a little Java control window which manages the VPN. If I run the program directly from the command line, the setuid works and the VPN comes up and works fine. But, I can't control it or see how long it's been up. Whenever I try to use the Java control panel the GUI comes up and tries to run the setuid program, but it fails and then the whole thing crashes. I get this error: Failed to setuid to root. Error 1: Operation not permitted But I have clearly set the right bits and it works when invoked directly. I've tried many different variations of Java including downloaded ones directly from Sun/Oracle. One note, the application is 32bit and so I need to run 32bit Java as well. Not sure if that matters. Has the 12.04 release installed some new security measures that might be keeping my setuid program from working properly? I've tried putting Java under /opt/jvm and also run service apparmor teardown to try to be sure apparmor is not involved, but I don't know enough to know if I succeeded. I'm really stuck and could use any pointers or tips anyone has. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
