All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Barrett <bob at bob131.so>
To: powertop@lists.01.org
Subject: Re: [Powertop] Fwd: Suggested tunables addition: sysctl kernel.core_pattern
Date: Tue, 05 Jan 2016 11:49:23 +1100	[thread overview]
Message-ID: <1451954963.2932.0@mail.bob131.so> (raw)
In-Reply-To: 20160105004749.GA18569@noemi.bahnhof.se

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

I primarily use my laptop for hacking on my own little projects, so 
this occurs fairly frequently

On Tue, Jan 5, 2016 at 11:47 AM, Magnus Fromreide 
<magfr(a)lysator.liu.se> wrote:
> On Sat, Jan 02, 2016 at 09:00:57PM +1100, George Barrett wrote:
>>  Hi, first off thanks for the great tool!
>> 
>>  I currently rely on a systemd unit file present in the Fedora 
>> package for
>>  powertop to do most of my laptop's power saving config on boot, and 
>> it works
>>  great. However, I've noticed a missing tunable which might be 
>> helpful for
>>  some folks: setting the kernel.core_pattern sysctl parameter to 
>> |/dev/null
>>  or similar. On my x220, this parameter set to it's default causes
>>  systemd-coredump to peg a single core, sometimes for quite an 
>> extended
>>  period of time. On many devices this would cause substantially 
>> greater heat
>>  output, and most importantly substantially higher power consumption.
> 
> I have to ask, why do you get enough core dumps for this to be a 
> problem?
> Wouldn't a better solution be to fix the application that dumps core?
> 
> /MF


             reply	other threads:[~2016-01-05  0:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  0:49 George Barrett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-05  1:11 [Powertop] Fwd: Suggested tunables addition: sysctl kernel.core_pattern Arjan van de Ven
2016-01-05  0:47 Magnus Fromreide
2016-01-02 10:00 George Barrett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1451954963.2932.0@mail.bob131.so \
    --to=powertop@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.