Date: Wed, 21 Jun 2006 09:12:11 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Jim Bryant <enderw@chattingaway.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: Problem: fpa(4) on sparc64 6.1-RELEASE Message-ID: <20060621001211.GB13097@cdnetworks.co.kr> In-Reply-To: <449834CA.2030005@chattingaway.com> References: <449834CA.2030005@chattingaway.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 20, 2006 at 12:47:54PM -0500, Jim Bryant wrote: > I am getting a panic with a GENERIC with all non-available hardware > drivers stripped out with "device fddi" and "device fpa" in the config. > The only things I added to GENERIC after stripping out the unneeded > things was the fddi, the sound, and the openfirmware. The system boots > fine with the fddi stuff commented out of the config. > > Any suggestions? Is anyone working on this? > [Removed unnecessary CC except freebsd-sparc64 ML] > Console log follows: ... [snip] ... > sym1: No NVRAM, ID 7, Fast-20, SE, parity checking > sym1: [GIANT-LOCKED] > fpa0: <Digital DEFPA PCI FDDI Controller> port 0xc00-0xc7f mem ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > 0x5000-0x507f,0x10000-0x1ffff at device 2.0 on pci2 > panic: trap: fast data access mmu miss > Uptime: 1s > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > Resetting ... > Quick reading the fpa(4) source code shows that the driver is not bus_dma(9) aware driver. So I guess it would not work for sparc64. -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060621001211.GB13097>