On Thu, 10 Jun 1999, Luoqi Chen wrote:
> Could you narrow down the crash further inside mp_start()? I'd like to
> know whether the crash occurred inside start_all_aps(). One or two lines of
> debug messages would be really helpful, you don't have to write down the exact
> words. Do you have options
> I have added more debugging messages, and the crash appears to be inside
> mp_start(). I don't have a log because this is too early in the boot
> to get the messages saved anywhere, and they go by too quickly to
> write it down. The evidence that this is an SMP problem is simple -
> with 2 cpu
On Wed, 09 Jun 1999, Luoqi Chen wrote:
> > 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 a
In reply:
> > interesting. then why the delay in bringing up the AP? Note in the
> > dmesg output below, that the AP only comes up during th SCSI delay. I
> > have also added other comments to the following output.
>
> The APs need the giant kernel lock when initializing the
> local APIC and p
In article
you write:
>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").
I just made this into a vm_offset_t, so it
> interesting. then why the delay in bringing up the AP? Note in the
> dmesg output below, that the AP only comes up during th SCSI delay. I
> have also added other comments to the following output.
The APs need the giant kernel lock when initializing the
local APIC and printing the "launched
> > 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 0xfec0
> > By
In reply:
> > 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 id
> 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 scre
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 briefl
10 matches
Mail list logo
