From owner-freebsd-ia64 Sat Oct 6 1:44: 0 2001 Delivered-To: freebsd-ia64@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id D6C0937B406 for ; Sat, 6 Oct 2001 01:43:54 -0700 (PDT) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 15pn3p-000DdR-0A; Sat, 6 Oct 2001 08:43:53 +0000 Received: from salmon.nlsystems.com (salmon [10.0.0.3]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f968gb749538; Sat, 6 Oct 2001 09:42:37 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 6 Oct 2001 09:41:16 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: Subject: Re: Woohoo! In-Reply-To: <20011006025113.BF4BB380A@overcee.netplex.com.au> Message-ID: <20011006093916.P530-100000@salmon.nlsystems.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ia64@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 5 Oct 2001, Peter Wemm wrote: > Peter Wemm wrote: > > Doug Rabson wrote: > > > Single-user mode on real hardware. The root filesystem is mounted over > > > NFS. I think I'll go and buy a bottle of wine now :-) > > > > Holy shit!! Wow! :-) If this is over NFS then that means interrupts are > > working, right? That means we should be able to do the EFI disk partitioning > > in order to boot off disk.. > > I've run into trouble (as usual): > undefined function: wbinvd() called from hwsleep.o > ia64/sapic.c was not in files.ia64 > > Something is still messed up in the interrupt routing.. I added some > printf()s: > > ... > ==== pci_add_resources = rerouting intline - was 10! > ==== pci_add_resources -> new intline 255 > found-> vendor=0x8086, dev=0x1229, revid=0x08 > bus=0, slot=2, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > intpin=a, irq=255 > powerspec 2 supports D0 D1 D2 D3 current D0 > ... > fxp0: port 0x1140-0x117f mem 0xf7e00000-0xf7efffff,0xf7cc9000-0xf7cc9fff irq 255 at device 2.0 on pci0 > fxp0: using memory space register mapping > === pci_alloc_resource: alloc IRQ, intline 255, intpin 1 > === pci_alloc_resource: alloc IRQ got intline 255 > fxp0: could not map interrupt > device_probe_and_attach: fxp0 attach returned 6 I just rebooted with a fresh copy of acpica (after stubbing out the wbinvd) and I'm working fine. What is the parent of pci0? It should be acpi_pcib - I'm going to nuke the legacy pcib code in nexus_pcib.c today. We can't possibly work without acpi on these machines. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message