Date: Tue, 15 Feb 2005 16:15:47 -0700 From: Tom Ponsford <tponsford@theriver.com> To: freebsd-alpha@FreeBSD.ORG Subject: Re: kernel panic on AS100A Message-ID: <421282A3.3040308@theriver.com> In-Reply-To: <20050215120805.GE7576@cicely12.cicely.de> References: <420E3483.8090609@theriver.com> <20050215120805.GE7576@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter wrote: > On Sat, Feb 12, 2005 at 09:53:23AM -0700, Tom Ponsford wrote: > >>Hi All, >> >>I picked up a AS 1000A a few weeks ago. It has an EV5 300mhz cpu, 64MB mem, >>and 3 disks attached to a KZPSC raid controller ( a DAC960), , which is >>supported by freebsd. >>I upgraded to v2.70 on the raid controller and the dmesg readout did not show >>any error messages, BUT the machine get a kernel panic after mounting the mfsroot >>complaining about a memory management fault. > > Strange this is the fdc0 process. > Maybe you are getting out of physical RAM and the fdc driver fails to > handle this properly - 64M is not very much for such a machine. > Yeah, I'll dig up some more ram. but I wanted to see if the install worked first. It actually ran NT with that much ram. >Since the fault address is 0x0 it's a NULL pointer dereference of some >sort. A stack trace would be very useful if you can get one Tom. As a workaround, >you can try unsetting the hints related to fd0 (i.e. variables in the loader >that start with 'hint.fd.0') and see if that fixes the issue for now. If it does, >then get the machine installed, build a kernel with debug symbols and KDB and DDB and we >can look at fixing the actual panic. OK I'll try that tonite or tommorrow and see where it goes. Thanks Tom -- --- Please do not read this sig. If you have read this far, please unread back to the beginning.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?421282A3.3040308>