From: Ted Kaczmarek <tedkaz@optonline.net>
To: habanero@us.ibm.com
Cc: xen-devel@lists.xensource.com
Subject: Re: x86_64 dom0 smp broken?
Date: Mon, 24 Oct 2005 12:55:51 -0400 [thread overview]
Message-ID: <1130172951.955.3.camel@pluto.linsolutions.com> (raw)
In-Reply-To: <200510241049.09810.habanero@us.ibm.com>
I am in same boat with SMP Athlon, ever since 2.6.12.5 first started
showing up, and through 7483:98c6c36ac444.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=359
I can actually boot, but nic cards don't work and likely other fun as
well.
Regards,
Ted
On Mon, 2005-10-24 at 10:49 -0500, Andrew Theurer wrote:
> On changeset 7483, actually I haven't been able to boot an SMP dom0 in a
> while, anyway, here's the boot log:
>
> Initializing CPU#6
> Brought up 8 CPUs
> Initializing CPU#7
> ERROR: domain->span does not contain CPU0
> ERROR: groups don't span domain->span
> ERROR: domain->span does not contain CPU1
> ERROR: domain->groups does not contain CPU1
> ERROR: empty group
> 00
> ERROR: group is NULL
>
> CPU2 attaching sched-domain:
> Unable to handle kernel NULL pointer dereference at 0000000000000008 RIP:
> <7><ffffffff80130d50>{find_busiest_group+96} domain 0: span 00
> ERROR: domain->span does not contain CPU2
> ERROR: domain->groups does not contain CPU2
> groups:
> ERROR: empty group
> 00
> ERROR: group is NULL
>
> domain 1: span ff
> groups: ff
>
> PGD 0
> Oops: 0000 [1] SMP
> CPU 1
> Modules linked in:
> Pid: 4, comm: migration/1 Not tainted 2.6.12-xen0-smp
> RIP: e030:[<ffffffff80130d50>] <ffffffff80130d50>{find_busiest_group+96}
> RSP: e02b:ffff880000697d28 EFLAGS: 00010213
> RAX: 0000000000000000 RBX: 0000000000000080 RCX: 0000000000000080
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: ffff880000697d98 R08: 0000000000000008 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
> R13: ffffffff805d1738 R14: 0000000000000008 R15: 0000000000000008
> FS: 0000000000000000(0000) GS:ffffffff80625980(0000) knlGS:0000000000000000
> CS: e033 DS: 0000 ES:
> 0000 )Process migration/1
> (pid: 4, threadinfo ffff880000696000, task ffff880000690750
> Stack: ffffffff80686d80 ffffffff80686d80 000000020000d9a7 ffff880000697e70
> ffff88000100cc80 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> ffff880000690750 }Call
> Trace:<ffffffff8045714c>{schedule+684} <ffffffff8012e9d3>{__wake_up_common}
> <ffffffff8013120b>{migration_thread+491} <ffffffff80131020>{migration_th
> <ffffffff8014c4a9>{kthread+217} <ffffffff80132020>{schedule_tail+64}
> <ffffffff8011353f>{child_rip+8} <ffffffff8014c3d0>{kthread+0}
>
> -Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2005-10-24 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 15:49 x86_64 dom0 smp broken? Andrew Theurer
2005-10-24 16:55 ` Ted Kaczmarek [this message]
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=1130172951.955.3.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=habanero@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.