From: Diego Calleja <diegocg@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with current linus' git tree
Date: Tue, 17 Jan 2006 14:17:25 +0100 [thread overview]
Message-ID: <20060117141725.d80a1221.diegocg@gmail.com> (raw)
In-Reply-To: <43CC7094.9040404@yahoo.com.au>
El Tue, 17 Jan 2006 15:20:36 +1100,
Nick Piggin <nickpiggin@yahoo.com.au> escribió:
> From your oops it looks as though the radix_tree_lookup in find_get_page
> has returned 0x40. It could be a flipped bit - is your memory OK?
It's ECC memory, I'd doubt it.
> Can you apply the attached patch and try to reproduce the oops?
You're saying that I'll have to spend all the afternoon watching
DVDs? Well, if the linux kernel needs it!
> 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.
next prev parent reply other threads:[~2006-01-17 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 18:15 Diego Calleja
2006-01-17 4:20 ` Nick Piggin
2006-01-17 4:24 ` Nick Piggin
2006-01-17 13:17 ` Diego Calleja [this message]
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
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=20060117141725.d80a1221.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®