From: Chuck Ebbert <76306.1226@compuserve.com>
To: Chris Largret <largret@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic when compiling with SMP support
Date: Tue, 21 Feb 2006 02:03:38 -0500 [thread overview]
Message-ID: <200602210207_MC3-1-B8DE-2105@compuserve.com> (raw)
In-Reply-To: <1140437271.7849.21.camel@shogun.daga.dyndns.org>
On Mon, 20 Feb 2006 at 04:07:51 -0800, Chris Largret wrote:
> In short, I only get these kernel panics when I enable SMP.
> ...
> invalid opcode: 0000 [1] SMP
> RIP: 0010:[<ffffffff8100efa8>] <ffffffff8100efa8>{timer_interrupt+0}
> ...
> Code: 83 3d 7d d6 38 00 01 55 48 89 d7 48 89 e5 7f 13 e8 50 fc ff
> --------------------------------------------------------------------
> Unable to handle kernel NULL pointer dereference at 0000000000000001
> RIP:
> <ffffffff8100cfa8>{timer_interrupt+0}
> ...
> Code: 83 3d 7d d6 38 00 01 55 48 89 d7 48 89 e5 7f 13 e8 50 fc ff
Maybe your CPU is overheating or it's not getting enough current.
Both oopses happen at the same exact address and they are complete
nonsense. For #1, the instruction is valid (it's
cmpl $1,0x38d67d(%rip)) and for #2 it's the same instruction, which
can't be referencing address 1.
You can try slowing down your CPUs by doing:
# echo -n "powersave" >/sys/devices/system/cpu/cpuN/cpufreq/scaling_governor
for each cpu (assuming you have a driver loaded, and you should.)
And please post your complete .config
--
Chuck
"Equations are the Devil's sentences." --Stephen Colbert
next reply other threads:[~2006-02-21 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 7:03 Chuck Ebbert [this message]
2006-02-22 5:56 ` Chris Largret
-- strict thread matches above, loose matches on Subject: below --
2006-02-25 6:41 Chuck Ebbert
2006-02-23 6:30 Chuck Ebbert
2006-02-23 22:15 ` Chris Largret
2006-02-20 12:07 Chris Largret
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=200602210207_MC3-1-B8DE-2105@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=largret@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
all inboxes | Powered by JetHome®