Date: Wed, 7 Jun 2006 19:22:05 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Pete French" <petefrench@ticketswitch.com> Cc: freebsd-stable@freebsd.org Subject: Re: Dual Opteron system will not run SMP Message-ID: <2a41acea0606071922n48add8fbw3f6d73ab79c6a3d6@mail.gmail.com> In-Reply-To: <E1Fo1rg-000Boq-2s@dilbert.firstcallgroup.co.uk> References: <E1FnZsk-0007i7-DE@dilbert.firstcallgroup.co.uk> <E1Fo1rg-000Boq-2s@dilbert.firstcallgroup.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/7/06, Pete French <petefrench@ticketswitch.com> wrote: > > If just non-ACPI isnt sufficient, the other thing SAFE does is turn > > off disk DMA. I have an as-yet unreleased system that has this > > same type of issue, and the problem is that two PCI device ID's > > are not recognized, so maybe that will be your problem. > > So, I got around to booting the system without ACPI and there are quite > a number of 'unknown' reports at boot, viz: > > unknown: <PNP0c01> can't assign resources (memory) > unknown: <PNP0303> can't assign resources (port) > unknown: <PNP0f13> can't assign resources (irq) > unknown: <PNP0501> can't assign resources (port) > unknown: <PNP0501> can't assign resources (port) > unknown: <PNP0700> can't assign resources (port) > unknown: <PNP0400> can't assign resources (port) > > pciconf -l gives me 5 devices without drivers attached, these being: > > none0@pci0:7:2: class=0x0c0500 card=0x13101462 chip=0x746a1022 rev=0x02 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'AMD-8111 SMBus 2.0 Controller' > class = serial bus > subclass = SMBus > none1@pci0:7:3: class=0x068000 card=0x13101462 chip=0x746b1022 rev=0x05 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'AMD-8111 ACPI System Management Controller' > class = bridge > none2@pci0:10:1: class=0x080010 card=0x13101462 chip=0x74511022 rev=0x01 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'AMD-8131 PCI-X IOAPIC' > class = base peripheral > subclass = interrupt controller > none3@pci0:11:1: class=0x080010 card=0x13101462 chip=0x74511022 rev=0x01 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'AMD-8131 PCI-X IOAPIC' > class = base peripheral > subclass = interrupt controller > none4@pci3:6:0: class=0x030000 card=0x13101462 chip=0x47521002 rev=0x27 hdr=0x00 > vendor = 'ATI Technologies Inc' > device = 'Rage XL PCI' > class = display > subclass = VGA > > I am assuming that it's only the two interrup controller ones which are > likely to be causing the problems - but other people are using 8111/8131 based > systems fine. Also I note that other SMP systems I have uuse 'none' as the > driver for these chips. > > Does this help shed any more light at all ? You are right about what the suspect devices are, having IOAPICs unrecognized seems like it could be a problem. When you say others are using such systems, do you mean they are using them with FreeBSD RELEASE? If you want info on the missing ID's try pciids.sourceforge.net, however figuring out what to do may require some work. In the easy cases you find a driver that is good enough but just doesnt have these new ID's in it, and a simple entry or two in a array will get you going. Course there is also going to be the case where its not that easy... Fraid I can't be too much help beyond that, hope it gets you headed in a direction you need anyway. Good luck, Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0606071922n48add8fbw3f6d73ab79c6a3d6>