From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with current linus' git tree
Date: Wed, 18 Jan 2006 14:25:30 +1100 [thread overview]
Message-ID: <43CDB52A.9030103@yahoo.com.au> (raw)
In-Reply-To: <20060117141725.d80a1221.diegocg@gmail.com>
Diego Calleja wrote:
> El Tue, 17 Jan 2006 15:20:36 +1100,
> Nick Piggin <nickpiggin@yahoo.com.au> escribió:
>
>>What happens if you run several infinite loops to increase the load?
>>Does everything still stay on CPU0?
>
>
> Yes, I run several "cat /dev/zero > /dev/null &" and they all kept in
> CPU #0.
>
> I did a bitsection search and I couldn't found the culprit, apparently
> it is caused by a config option; now it works fine after switching off
> CONFIG_HOTPLUG_CPU and some ACPI options. Also, when it didn't work
> the CPU that would get all the processes could be CPU #0 or #1 - it
> changed randomly depending on the boot.
>
If you can report those configuration options and the symptoms in a
new thread to lkml that would be helpful. Also if you can work out
when it started happening, that helps too.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-01-18 3:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 18:15 Oops with current linus' git tree Diego Calleja
2006-01-17 4:20 ` Nick Piggin
2006-01-17 4:24 ` Nick Piggin
2006-01-17 13:17 ` Diego Calleja
2006-01-18 0:20 ` Diego Calleja
2006-01-18 3:23 ` Nick Piggin
2006-01-19 19:31 ` Diego Calleja
2006-01-18 3:25 ` Nick Piggin [this message]
2006-01-18 14:02 ` Diego Calleja
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=43CDB52A.9030103@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=diegocg@gmail.com \
--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.