All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [bisected] sys_paccept: disable paccept() causes my macbook	pro to  have an annoying whining sound
Date: Thu, 07 Jan 2010 11:22:44 -0800	[thread overview]
Message-ID: <4B463484.7060703@gmail.com> (raw)
In-Reply-To: <20100107160246.GB16076@basil.fritz.box>

On 01/07/10 08:02, Andi Kleen wrote:

o.k. so using the boot param
with the latest kernel takes care
of the noise.

Now as a test I did
git reset --hard origin 2d4c8266
to where the bisect was pointing too.
then once booting the noise was there.
Then reverting that commit, caused the system
to be noiseless..

My guess since this might be power related
it could be anything(sys_paccept hit it just right)
i.g. whatever sys_paccept does(when turned on)
generates enough wakeups(if this is correct term),
to keep the system from generating this noise at the certain
C level or however/whatever it's doing.

At this point I'm not sure what to really do.
if using the boot param(max_cstate) is a safe option
then I'll just use that and/or look at paccept/accept4 to see
what really generates enough wakeups or keeps the processor
at a level to keep the noise from generating.


Justin P. Mattock

  parent reply	other threads:[~2010-01-07 19:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07  6:16 [bisected] sys_paccept: disable paccept() causes my macbook pro to have an annoying whining sound Justin Mattock
2010-01-07  6:16 ` Justin Mattock
2010-01-07  9:51 ` Andi Kleen
2010-01-07 15:43   ` Justin P. Mattock
2010-01-07 16:02     ` Andi Kleen
2010-01-07 16:34       ` Justin P. Mattock
2010-01-07 19:22       ` Justin P. Mattock [this message]
2010-01-07 12:54 ` John W. Linville
2010-01-07 15:45   ` Justin P. Mattock
2010-01-07 20:37     ` John W. Linville
2010-01-07 20:43       ` Justin P. Mattock

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=4B463484.7060703@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.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.