linux-kernel - Re: [bisected] sys_paccept: disable paccept() causes my macbook pro to have an annoying whining sound

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B463484.7060703@gmail.com>
Date:	Thu, 07 Jan 2010 11:22:44 -0800
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [bisected] sys_paccept: disable paccept() causes my macbook	pro
 to  have an annoying whining sound

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/