public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>, Mike Galbraith <efault@gmx.de>,
	Frederik Deweerdt <deweerdt@free.fr>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	suresh.b.siddha@intel.com, Ingo Molnar <mingo@elte.hu>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000002
Date: Tue, 29 Jul 2008 16:53:48 +0200	[thread overview]
Message-ID: <20080729145348.GN30344@one.firstfloor.org> (raw)
In-Reply-To: <20080729065635.27630e33@infradead.org>

On Tue, Jul 29, 2008 at 06:56:35AM -0700, Arjan van de Ven wrote:
> On Tue, 29 Jul 2008 14:09:11 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
> 
> > On Tue, Jul 29, 2008 at 06:22:15AM +0200, Mike Galbraith wrote:
> > > On Tue, 2008-07-29 at 00:26 +0200, Frederik Deweerdt wrote:
> > > > Hello  Aneesh,
> > > > 
> > > > On Fri, Jul 25, 2008 at 03:23:17PM +0530, Aneesh Kumar K.V wrote:
> > > > > [  163.378265] BUG: unable to handle kernel NULL pointer
> > > > > dereference at 00000002 [  163.378276] IP: [<c0124933>]
> > > > > sched_power_savings_store+0x13/0x70
> > > > 
> > > > Does the attached patch solve the problem?
> > > 
> > > Patch seems to have missed the boat for rc1 too.
> > 
> > Hmm.  I'll resend. 
> > 
> > BTW i think it's clearly a  bug that distributions are even accessing
> > that file. It doesn't make any sense in the context they are using
> > it (like at every boot). 
> 
> it's a power saving feature that they very likely turn on by default...

A power saving feature that has a significant trade off between power
and performance. 

This means performance will go down. Perhaps it would be ok on  battery,
but it's a feature that only makes sense on servers which don't have batteries.
So enabling it by default in a standard installation seems quite wrong 
to me.

BTW opensuse seems to even set it to 2 which doesn't even exist. This means
there was a BOF at OLS discussing adding more modes, but right now there is 
only 0 or 1.

-Andi

  reply	other threads:[~2008-07-29 14:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  9:53 BUG: unable to handle kernel NULL pointer dereference at 00000002 Aneesh Kumar K.V
2008-07-28 22:26 ` Frederik Deweerdt
2008-07-29  4:22   ` Mike Galbraith
2008-07-29 12:09     ` Andi Kleen
2008-07-29 13:56       ` Arjan van de Ven
2008-07-29 14:53         ` Andi Kleen [this message]
2008-07-29 15:30           ` Arjan van de Ven
2008-07-29 16:31             ` Andi Kleen
2008-07-29 17:22               ` Arjan van de Ven
2008-07-29 17:50                 ` Andi Kleen
2008-07-30  9:05     ` Ingo Molnar
2008-07-30  9:26       ` Andrew Morton
2008-07-30 16:31         ` Greg KH

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=20080729145348.GN30344@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=arjan@infradead.org \
    --cc=deweerdt@free.fr \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox