LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "dAniel hAhler" <dhahler@googlemail.com>
To: vatsa@linux.vnet.ibm.com
Cc: "Dhaval Giani" <dhaval@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: Regression with idle cpu cycle handling in 2.6.24 (compared to 2.6.22)
Date: Tue, 22 Jan 2008 02:59:26 +0100	[thread overview]
Message-ID: <bcadbdf50801211759j5e55ba88n26c24b2f12afaf26@mail.gmail.com> (raw)
In-Reply-To: <20080121171834.GA31049@linux.vnet.ibm.com>

On Jan 21, 2008 6:18 PM, Srivatsa Vaddagiri wrote:
> On Sun, Jan 20, 2008 at 09:03:38AM +0530, Dhaval Giani wrote:
> > > btw: writing 1 into "cpu_share" totally locks up the computer!
> > >
> >
> > Can you please provide some more details. Can you go into another
> > console (try ctrl-alt-f1) and try to reproduce the issue there. Could
> > you take a photo of the oops/panic and upload it somewhere so that we
> > can see it?
>
> I couldn't recreate this problem either on 2.6.24-rc8.
>
> Daniel,
>         Could you pass the config file you used pls?

Sure, I've uploaded the config to
http://codeprobe.de/tmp/config-2.6.24-4-generic

It only happens when changing the cpu_share for another user and this
user needs to have a cpu hogging process running (like boinc, a
while-1 loop or similar).
It does not dump anything to the console, but the VirtualBox process
on the host takes all CPU - there seems to be no crash, but an endless
loop only.

I have reported it at http://bugzilla.kernel.org/show_bug.cgi?id=9779
already, with a testcase (outlined above).

Thank you for your help.

-- 
http://daniel.hahler.de/

      reply	other threads:[~2008-01-22  1:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 14:05 dAniel hAhler
2008-01-19 14:52 ` dAniel hAhler
2008-01-20  3:33   ` Dhaval Giani
2008-01-20  4:03     ` Dhaval Giani
2008-01-21 17:18     ` Srivatsa Vaddagiri
2008-01-22  1:59       ` dAniel hAhler [this message]

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=bcadbdf50801211759j5e55ba88n26c24b2f12afaf26@mail.gmail.com \
    --to=dhahler@googlemail.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vatsa@linux.vnet.ibm.com \
    --subject='Re: Regression with idle cpu cycle handling in 2.6.24 (compared to 2.6.22)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).