Date: Wed, 14 Jul 2004 21:57:08 +0200 From: "Willem Jan Withagen" <wjw@withagen.nl> To: "John Baldwin" <jhb@FreeBSD.org> Cc: freebsd-amd64@FreeBSD.org Subject: Re: Help my SMP is broken??? Message-ID: <069c01c469dc$c0dac1a0$471b3dd4@digiware.nl> References: <06b401c46591$49a2b600$471b3dd4@digiware.nl> <02e301c4691c$630f14b0$471b3dd4@digiware.nl> <030701c46920$fef38a60$471b3dd4@digiware.nl> <200407141459.32024.jhb@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
> > > Well, booting Windows/64 XP seems to be a good "heilmeister" for the > > trouble: > > > > real memory = 2146304000 (2046 MB) > > Physical memory chunk(s): > > 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) > > 0x000000000074c000 - 0x000000007c2b7fff, 2075574272 bytes (506732 pages) > > avail memory = 2062815232 (1967 MB) > > ACPI APIC Table: <VIAK8 AWRDACPI> > > SMP: bootAP CPU #1 Trying to launch! > > APIC ID: physical 0, logical 0:0 > > APIC ID: physical 1, logical 0:1 > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > APIC: CPU 0 has ACPI ID 0 > > APIC: CPU 1 has ACPI ID 1 > > MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 > > > > And now the box just boots fine??? > > > > Any suggestions what XP might have fixed???? Can't be that a firmware > > setting is sticky and windows unglued it?! > > I have no idea. > > -- > John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ Well, for the time I'm just calling it alpha-particles, since I've seen this system fly just about every direction possible. Lets just hope -current is in a sort of flux state for my box. I've got an old 17-june kernel, which does just fine. Probably we'll converge back again into less panics. --WjWhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?069c01c469dc$c0dac1a0$471b3dd4>