Date: Wed, 9 Jun 1999 20:01:04 -0400 (EDT) From: Luoqi Chen <luoqi@watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, tich@ma.ikos.com Subject: Re: 4-way SMP broken ? Message-ID: <199906100001.UAA07014@lor.watermarkgroup.com>
next in thread | raw e-mail | index | archive | help
> Hi,
>
> I've been trying to install 19990604-CURRENT on a couple of SC450NX
> boxes. It works fine with 2 cpu's, but an SMP kernel with 4 cpu's
> falls over very quickly (I think while it's setting up the APIC
> stuff, or very shortly after - the messages about APIC bus ids appear
> on the screen very briefly, then the machine reboots itself).
>
Do you mean messages like these?
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000
cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000
io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000
By the time you see these messages, all cpus should have been booted up
successfully, any crash immediately follows is not likely to be SMP related.
It's helpful to pinpoint the crash if you could include the last few lines
from a verbose boot.
> Does anyone know a) when was the last time it worked on 4 cpu's
> b) what's changed recently which might relate to this.
>
> Also in trying to figure this out I looked at the DRAM probing
> code in /usr/src/sys/i386/i386/machdep.c:getmemsize(), and it looks
> as though it's not safe for >2GB (e.g. comparisons of byte addresses
> against signed "int end"). It would also be good if this probing
> code was carefule not to ventrue past 4GB-64MB (PCI device space) -
> then a generic kernel could work on a 4GB machine without any tweaking,
> which would simplify installation - I get nervous shuffling DIMMs
> in and out of the machine ...
>
> Thanks
> Richard Cownie (tich@ma.ikos.com)
>
-lq
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906100001.UAA07014>