From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 19:13:15 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8EA016A420; Tue, 15 Nov 2005 19:13:15 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD1A543D45; Tue, 15 Nov 2005 19:13:14 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 72E6CF24E0; Tue, 15 Nov 2005 11:13:14 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (triton.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00821-01; Tue, 15 Nov 2005 11:13:12 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id AB6CAF24B4; Tue, 15 Nov 2005 11:13:12 -0800 (PST) From: Sean McNeil To: John Baldwin In-Reply-To: <200511151308.25729.jhb@freebsd.org> References: <1131641262.99700.3.camel@triton.mcneil.com> <200511101420.04967.jhb@freebsd.org> <200511151308.25729.jhb@freebsd.org> Content-Type: text/plain Date: Tue, 15 Nov 2005 11:13:12 -0800 Message-Id: <1132081992.1334.7.camel@triton.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Cc: Roman Neuhauser , freebsd-amd64@freebsd.org Subject: Re: problems booting recompiled 5.4-kernel (Was: amd64 does not see all 4 GB RAM on tyan GT24) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 19:13:15 -0000 On Tue, 2005-11-15 at 13:08 -0500, John Baldwin wrote: > On Thursday 10 November 2005 02:20 pm, John Baldwin wrote: > > On Thursday 10 November 2005 11:47 am, Sean McNeil wrote: > > > On Thu, 2005-11-10 at 11:11 -0500, John Baldwin wrote: > > > > On Wednesday 09 November 2005 04:12 pm, Sean McNeil wrote: > > > > > On Wed, 2005-11-09 at 16:04 -0500, John Baldwin wrote: > > > > > > On Wednesday 09 November 2005 02:47 pm, Roman Neuhauser wrote: > > > > > > > # jhb@freebsd.org / 2005-11-09 10:22:07 -0500: > > > > > > > > On Wednesday 09 November 2005 04:22 am, Claus Guttesen wrote: > > > > > > > > > I tried FreeBSD 6.0 a few days ago and I seem to recall that > > > > > > > > > the above mentioned line is not needed in FreeBSD 6.0, but my > > > > > > > > > (own) memory is probably corrupt :-) > > > > > > > > > > > > > > > > That's correct. > > > > > > > > > > > > > > EAMBIGUOUS. > > > > > > > > > > > > > > Which part is correct? "mentioned line is not needed in > > > > > > > FreeBSD 6.0" or "my (own) memory is probably corrupt"? > > > > > > > > > > > > You don't need atpic on 6.0. > > > > > > > > > > Not true. My Athlon 2x Gigabyte K8 Triton (GA-K8NSC-939) requires > > > > > atpic or it will not boot. This is an nVidia nForce3-Pro250 board. > > > > > > > > You need to post a problem report about it then since we are probably > > > > going to remove atpic in 7.0. When atpic was taken out of GENERIC in > > > > HEAD recently no one said it broke for them. What problems do you see > > > > with atpic taken out on 6.0? > > > > > > Again, not true. When it was asked in email subject > > > > > > Re: [PATCH] remove 'device atpic' > > > > > > I responded at that time with: > > > > > > On Thu, 2005-10-20 at 10:40 -0400, John Baldwin wrote: > > > > On Wednesday 19 October 2005 05:28 pm, Sean McNeil wrote: > > > > > Just recently fried my MSI MB and got a new one with an Athlon 64x2. > > > > > The following setup still requires the 'device atpic' or it will > > > > > > fault > > > > > > > > with an unknown/reserved trap of 30: > > > > > > > > > > GigaByte K8 Triton Series GA-K8NSC-939 BIOS rev. F5 > > > > > AMD Athlon 64 X2 Dual-Core Processor 3800+ > > > > > > > > > > It works perfectly fine as a single core without the atpic device > > > > > > and as > > > > > > > > a dual-cpu with the atpic device. This board has the nForce3 250Gb > > > > > chipset. > > > > > > > > What version(s) of FreeBSD does it fail on? > > > > > > This was/is 6-current RC1. > > > > Ok, can you get a stack trace? The only time I've seen these recently was > > when the 8259A wasn't truly shut down correctly during boot and it fired an > > interrupt before it was shut up. Hmm, I thought Peter had added some hack > > code to just shut the 8259As up during boot, but now I can't find it. Ah, > > it's earlier in that function. It might be that his hack is incomplete as > > it assumes the 8259As are in a certain state, and if they aren't then his > > hack won't work. I'll try to flesh it out some more. > > Here's a patch you can test. Tried the patch and it looks like things fail earlier. I haven't been able to make the time yet to build a kernel with debug and get you a backtrace. I will try to do so as soon as possible. For me, I think it has to do with the second CPU settings as it works when SMP is not enabled. This is what I see when things work: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: on acpi0 pci_link1: irq 5 on acpi0 pci_link2: on acpi0 pci_link3: irq 10 on acpi0 pci_link4: irq 7 on acpi0 pci_link5: irq 11 on acpi0 pci_link6: irq 11 on acpi0 pci_link7: on acpi0 pci_link8: on acpi0 pci_link9: irq 9 on acpi0 pci_link10: on acpi0 pci_link11: irq 10 on acpi0 pci_link12: irq 11 on acpi0 pci_link13: on acpi0 pci_link14: on acpi0 pci_link15: on acpi0 pci_link16: on acpi0 pci_link17: irq 11 on acpi0 pci_link18: irq 0 on acpi0 pci_link19: irq 0 on acpi0 pci_link20: irq 0 on acpi0 pci_link21: irq 0 on acpi0 pci_link22: irq 16 on acpi0 pci_link23: irq 0 on acpi0 pci_link24: irq 0 on acpi0 pci_link25: irq 0 on acpi0 pci_link26: irq 0 on acpi0 pci_link27: irq 0 on acpi0 pci_link28: irq 0 on acpi0 pci_link29: irq 23 on acpi0 pci_link30: irq 0 on acpi0 pci_link31: irq 0 on acpi0 pci_link32: irq 0 on acpi0 pci_link33: irq 0 on acpi0 pci_link34: irq 0 on acpi0 pci_link35: irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci_link29: BIOS IRQ 10 for -2145892088.1.INTA is invalid pci_link23: BIOS IRQ 11 for -2145892088.2.INTA is invalid pci_link24: BIOS IRQ 11 for -2145892088.2.INTB is invalid pci_link30: BIOS IRQ 11 for -2145892088.2.INTC is invalid pci_link27: BIOS IRQ 9 for -2145892088.6.INTA is invalid pci_link35: BIOS IRQ 11 for -2145892088.10.INTA is invalid pci0: on pcib0 Sean