All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Janne M O Heikkinen <jmoheikk@cc.helsinki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64: 2.6.14 with NUMA panics at boot
Date: 28 Oct 2005 23:06:33 +0200	[thread overview]
Message-ID: <p73vezhtkpy.fsf@verdi.suse.de> (raw)
In-Reply-To: <Pine.OSF.4.61.0510282218310.411472@rock.it.helsinki.fi>

Janne M O Heikkinen <jmoheikk@cc.helsinki.fi> writes:

> With CONFIG_K8_NUMA I get the following right after boot:
> 
> PANIC: early exception rip ffffffff8023429f error 0 cr2 0
> PANIC: early exception rip ffffffff8011893a error 0 cr2 ffffffffff5fd023
> 
> Looking at the System.map 8023429f seems to be find_first_bit
> and 80118993a safe_smp_processor_id. When I compile kernel without
> K8 NUMA it boots fine but eg. ATI Radeon driver doesn work.
> 
> Board I'm using is Tyan S2885 with two Opteron 246's and 4GB ram.

Did earlier kernels work? Please post full log with earlyprintk=vga
or earlyprintk=serial,ttySx,baud

-Andi

  reply	other threads:[~2005-10-28 21:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 19:26 x86_64: 2.6.14 with NUMA panics at boot Janne M O Heikkinen
2005-10-28 21:06 ` Andi Kleen [this message]
2005-10-28 22:06   ` Janne M O Heikkinen
2005-10-28 22:21     ` Janne M O Heikkinen
2005-10-29 10:01     ` Andi Kleen
2005-10-29 11:08       ` Janne M O Heikkinen
2005-10-29 14:54         ` Janne M O Heikkinen
2005-10-29 16:41           ` Andi Kleen
2005-10-29 17:30             ` Dave Hansen
2005-10-31  0:17               ` Bob Picco
2005-10-31  2:12                 ` Andi Kleen
2005-10-31  1:40                   ` Bob Picco
2005-10-31  3:28                     ` Andi Kleen
2005-10-31  2:46                       ` Bob Picco
2005-11-02  5:07                   ` Martin J. Bligh
2005-11-02 18:08                     ` Andy Whitcroft
2005-11-03 14:43                       ` Bob Picco
2005-11-03 17:06                         ` Andy Whitcroft

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=p73vezhtkpy.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=jmoheikk@cc.helsinki.fi \
    --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.