Date: Sat, 06 Oct 2001 01:59:15 -0700 From: Peter Wemm <peter@wemm.org> To: Doug Rabson <dfr@nlsystems.com> Cc: ia64@FreeBSD.ORG Subject: Re: Woohoo! Message-ID: <20011006085915.40E50380A@overcee.netplex.com.au> In-Reply-To: <20011006093916.P530-100000@salmon.nlsystems.com>
index | next in thread | previous in thread | raw e-mail
Doug Rabson wrote:
> 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 partitio
ning
> > > 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: <Intel Pro 10/100B/100+ Ethernet> port 0x1140-0x117f mem 0xf7e00000-0
xf7efffff,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.
See the thread "Not all devices get attached" in freebsd-ia64.
I dont think you were on the explicit to:/cc: list in case you're
procmail rules are checking for that. The problem has been solved, we're
running from disk.
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ia64" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011006085915.40E50380A>