[Touch-packages] [Bug 911206] Re: /etc/init.d/ondemand unconditionally overrules /etc/init.d/cpufrequtils

2016-05-13 Thread Greg Mason
This also led to the problem in bug 1579278

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/911206

Title:
  /etc/init.d/ondemand unconditionally overrules
  /etc/init.d/cpufrequtils

Status in cpufrequtils package in Ubuntu:
  Confirmed
Status in sysvinit package in Ubuntu:
  Triaged

Bug description:
  /etc/init.d/ondemand *always* sets the cpu scaling governor to
  ondemand, and is executed after /etc/init.d/cpufrequtils.

  This causes two problems:
  1. Confusion, because it seems as if /etc/init.d/cpufrequtils is being run, 
but has no effect
  2. Possible problems down the road, because /etc/init.d/ondemand has no 
/etc/default/ondemand, so either editing or deleting
/etc/init.d/ondemand. I just discovered that updating initscripts will fail 
if /etc/init.d/ondemand has been deleted (dpkg complains about this file 
missing and aborts)

  Suggested fixes:

  a) Remove /etc/init.d/ondemand, make the ondemand governor the default
  for /etc/init.d/cpufrequtils, install package cpufrequtils by default.

  b) If this is not desired, make absolutely sure that
  /etc/init.d/ondemand is executed *before* /etc/init.d/cpufrequtils,
  maybe by making /etc/init.d/cpufrequtils depend on
  /etc/init.d/ondemand.

  I'm looking forward to your responses,
  Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: initscripts 2.88dsf-13.10ubuntu4.1
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Jan  3 13:13:59 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to oneiric on 2011-12-10 (23 days ago)
  modified.conffile..etc.init.d.ondemand: [modified]
  mtime.conffile..etc.init.d.ondemand: 2012-01-03T13:13:33.783902

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/911206/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1480320] Re: ondemand init script sets governor "powersave" when only "powersave" and "performance" available

2016-05-13 Thread Greg Mason
This is also the problem behind bug 1579278 which recently affected an
IS machine. Forcing "powersave" on all newer x86 CPUs is a bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1480320

Title:
  ondemand init script sets governor "powersave" when only "powersave"
  and "performance" available

Status in sysvinit package in Ubuntu:
  Triaged

Bug description:
  My system seems to have governors "powersave" and "performance"
  available. No others.

  So by ondemand, I end up with "powersave", which makes my workstation
  excruciatingly slow.

  I think that in this case, "performance" should be preferred.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: initscripts 2.88dsf-59.2ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 31 17:08:08 2015
  InstallationDate: Installed on 2010-10-12 (1752 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to wily on 2014-11-11 (262 days ago)
  mtime.conffile..etc.init.d.ondemand: 2015-07-31T16:51:58.391407

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1480320/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server)

2016-05-13 Thread Greg Mason
It looks like /etc/init.d/ondemand doesn't have any support for the
performance governor at all. On systems that only have "performance" and
"powersave" the only thing /etc/init.d/ondemand will do is set the
governor to powersave.

I'll file the appropriate bug against the initscripts package.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1579278

Title:
  Consider changing default CPU frequency scaling governor back to
  "performance" (Ubuntu Server)

Status in linux package in Ubuntu:
  Invalid
Status in sysvinit package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in sysvinit source package in Xenial:
  New

Bug description:
  Hi,

  With the new Ubuntu archive servers, we saw constantly high load and
  after some tinkering, we found that it was mostly CPUs being woken up
  to see if they should enter idle states. Changing the CPU frequency
  scaling governor to "performance" saw a considerable drop.

  Perf report using the following commands:

  | perf record -g -a sleep 10
  | perf report

  | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906
  |   Children  Self  Command  Shared Object Symbol
  | +   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  | +   53.51% 0.00%  swapper  [kernel.kallsyms] [k] 
start_secondary
  | +   53.02% 0.08%  swapper  [kernel.kallsyms] [k] 
call_cpuidle
  | +   52.94% 0.02%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter
  | +   31.81% 0.67%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter_state
  | +   29.59% 0.12%  swapper  [kernel.kallsyms] [k] 
acpi_idle_enter
  | +   29.45% 0.05%  swapper  [kernel.kallsyms] [k] 
acpi_idle_do_entry
  | +   29.43%29.43%  swapper  [kernel.kallsyms] [k] 
acpi_processor_ffh_cstate_enter
  | +   20.51% 0.04%  swapper  [kernel.kallsyms] [k] 
ret_from_intr
  | +   20.47% 0.12%  swapper  [kernel.kallsyms] [k] do_IRQ
  | +   19.30% 0.07%  swapper  [kernel.kallsyms] [k] 
irq_exit
  | +   19.18% 0.07%  apache2  [kernel.kallsyms] [k] 
entry_SYSCALL_64_fastpath
  | +   18.80% 0.17%  swapper  [kernel.kallsyms] [k] 
__do_softirq
  | +   16.45% 0.11%  swapper  [kernel.kallsyms] [k] 
net_rx_action
  | +   16.25% 0.43%  swapper  [kernel.kallsyms] [k] be_poll
  | +   14.74% 0.21%  swapper  [kernel.kallsyms] [k] 
be_process_rx
  | +   13.61% 0.07%  swapper  [kernel.kallsyms] [k] 
napi_gro_frags
  | +   12.58% 0.04%  swapper  [kernel.kallsyms] [k] 
netif_receive_skb_internal
  | +   12.48% 0.03%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb
  | +   12.42% 0.24%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb_core
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f27983b5028
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f2798369028
  | +   11.49% 0.16%  swapper  [kernel.kallsyms] [k] ip_rcv
  | +   11.29% 0.09%  swapper  [kernel.kallsyms] [k] 
ip_rcv_finish
  | +   10.77% 0.05%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver
  | +   10.70% 0.06%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver_finish
  | +   10.55% 0.22%  swapper  [kernel.kallsyms] [k] 
tcp_v4_rcv
  | +   10.10% 0.00%  apache2  [unknown] [k] 

  | +   10.01% 0.04%  swapper  [kernel.kallsyms] [k] 
tcp_v4_do_rcv

  Expanding in a few of those, you'll see:

  | -   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  |- 55.04% cpu_startup_entry
  |   - 52.98% call_cpuidle
  |  + 52.93% cpuidle_enter
  |  + 0.00% ret_from_intr
  |0.00% cpuidle_enter_state
  |0.00% irq_entries_start
  |   + 1.14% cpuidle_select
  |   + 0.47% schedule_preempt_disabled
  | 0.10% rcu_idle_enter
  | 0.09% rcu_idle_exit
  |   + 0.05% ret_from_intr
  |   + 0.05% tick_nohz_idle_enter
  |   + 0.04% arch_cpu_idle_enter
  | 0.02% cpuidle_enter
  | 0.02% tick_check_broadcast_expired
  |   + 0.01% cpuidle_reflect
  | 0.01% menu_reflect
  | 0.01% atomic_notifier_call_chain
  | 0.01% local_touch_nmi
  | 0.01% cpuidle_not_available
  | 0.01% menu_select
  | 0.01% cpuidle_get_cpu_driver
  |   + 0.01% tick_nohz_idle_exit
  |   + 0.01% sched_ttwu_pending
  | 0.00% set_cpu_sd_state_idle

[Touch-packages] [Bug 1564426] Re: Import problem - Spanish (es) - glib20 in Ubuntu Xenial package "glib2.0"

2016-04-05 Thread Greg Mason
** Changed in: glib2.0 (Ubuntu)
Milestone: wily-updates => xenial-updates

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1564426

Title:
  Import problem - Spanish (es) - glib20 in Ubuntu Xenial package
  "glib2.0"

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Looks like there was an accidental word-wrap problem in po/es.po.

  Line 13 is really the end of line 12. I've included a patch to send
  upstream.

  Here's a copy of the email that IS has been getting for a while now:

  Hello Launchpad Translations Administrators,

  On 2016-03-18 13:50z (12 days 14 hours 16 minutes ago), you uploaded a
  file with Spanish (es) translations for glib20 in Ubuntu Xenial package
  "glib2.0" to Launchpad.

  We were unable to import the file because of errors in its format:

  Line 13: Invalid content: u', 2013, 2014, 2015, 2016.'

  If you use gettext, you can check your file for correct formatting with
  the 'msgfmt -c' command. Please fix any errors raised by msgfmt and
  upload the file again. If you check the file and you don't find any
  error in it, please look for an answer or file a question at
  https://answers.launchpad.net/rosetta/

  For your convenience, you can get the file you uploaded at:
  http://launchpadlibrarian.net/250464407/es.po

  Thank you,

  The Launchpad team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1564426/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1564426] [NEW] Import problem - Spanish (es) - glib20 in Ubuntu Xenial package "glib2.0"

2016-03-31 Thread Greg Mason
Public bug reported:

Looks like there was an accidental word-wrap problem in po/es.po.

Line 13 is really the end of line 12. I've included a patch to send
upstream.

Here's a copy of the email that IS has been getting for a while now:

Hello Launchpad Translations Administrators,

On 2016-03-18 13:50z (12 days 14 hours 16 minutes ago), you uploaded a
file with Spanish (es) translations for glib20 in Ubuntu Xenial package
"glib2.0" to Launchpad.

We were unable to import the file because of errors in its format:

Line 13: Invalid content: u', 2013, 2014, 2015, 2016.'

If you use gettext, you can check your file for correct formatting with
the 'msgfmt -c' command. Please fix any errors raised by msgfmt and
upload the file again. If you check the file and you don't find any
error in it, please look for an answer or file a question at
https://answers.launchpad.net/rosetta/

For your convenience, you can get the file you uploaded at:
http://launchpadlibrarian.net/250464407/es.po

Thank you,

The Launchpad team

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "fix invalid comment line."
   
https://bugs.launchpad.net/bugs/1564426/+attachment/4618276/+files/fix_es.po_invalid_line.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1564426

Title:
  Import problem - Spanish (es) - glib20 in Ubuntu Xenial package
  "glib2.0"

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Looks like there was an accidental word-wrap problem in po/es.po.

  Line 13 is really the end of line 12. I've included a patch to send
  upstream.

  Here's a copy of the email that IS has been getting for a while now:

  Hello Launchpad Translations Administrators,

  On 2016-03-18 13:50z (12 days 14 hours 16 minutes ago), you uploaded a
  file with Spanish (es) translations for glib20 in Ubuntu Xenial package
  "glib2.0" to Launchpad.

  We were unable to import the file because of errors in its format:

  Line 13: Invalid content: u', 2013, 2014, 2015, 2016.'

  If you use gettext, you can check your file for correct formatting with
  the 'msgfmt -c' command. Please fix any errors raised by msgfmt and
  upload the file again. If you check the file and you don't find any
  error in it, please look for an answer or file a question at
  https://answers.launchpad.net/rosetta/

  For your convenience, you can get the file you uploaded at:
  http://launchpadlibrarian.net/250464407/es.po

  Thank you,

  The Launchpad team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1564426/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp