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: Tue, 17 Jan 2006 15:20:36 +1100 [thread overview]
Message-ID: <43CC7094.9040404@yahoo.com.au> (raw)
In-Reply-To: <20060116191556.bd3f551c.diegocg@gmail.com>
Diego Calleja wrote:
> I'm having two noticeable problems with the current linus' tree
>
> 1) Oops while watching a DVD with kaffeine (kde based video player),
> oops pasted below.
>
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?
Can you apply the attached patch and try to reproduce the oops?
> 2) This is a dual p3 machine, but only one CPU is being used to
> run processes on it. CPU #1 is detected etc, but processes will
> be scheduled only in CPU #0. /proc/interrupts shows that CPU #1 is
> still used to service interrupts. I'm able to force processes to run
> on that CPU with taskset but it won't happen automatically like it
> usually does. dmesg here: http://terra.es/personal/diegocg/dmesg
>
What happens if you run several infinite loops to increase the load?
Does everything still stay on CPU0?
>
> Jan 16 18:04:07 estel kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000040
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-17 4:21 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 [this message]
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
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=43CC7094.9040404@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox