On Sat, Feb 05, 2000 at 04:16:41PM -0500, Curt Sampson wrote:
>=20
> At the debugger prompt, you could type `trace' or just `t' to find out
> what was going on when things blew up.

here is the trace:

data fault: pc=3D0xf00b6a84 addr=3D0x0 sfsr=3D1a6<PERR=3D0,LVL=3D1,AT=3D5,F=
T=3D1,FAV,OW>
panic: kernel fault
Stopped in  at  _Debugger+0x4:  jmpl            [%o7 + 0x8], %g0
db> t
_mem_access_fault4m(0x0, 0x1a6, 0x0, 0xf0109cd0, 0xf0353468, 0xf0002000) at=
 _me
m_access_fault4m+0x308
memfault_sun4m(0x0, 0x0, 0xf02d49cc, 0x3b5b, 0xf02d4800, 0xffffffff) at mem=
faul
t_sun4m+0xe4
_uvm_map(0xf041b000, 0x4dc000, 0x0, 0x0, 0x0, 0x0) at _uvm_map+0x478
_uvm_km_alloc1(0xf02b3e38, 0x4dc000, 0x1, 0x0, 0x0, 0xf00f1980) at _uvm_km_=
allo
c1+0xf4
_kmeminit(0xf04dc000, 0xfe000000, 0xf02cef54, 0x1, 0xf04dbe7c, 0xf02cef00) =
at _
kmeminit+0x10
_uvm_init(0xf010c400, 0x1, 0xf0002000, 0xf0109f20, 0xf0109f18, 0x120) at _u=
vm_i
nit+0x68
_main(0x0, 0xf02cddc8, 0xf00021b8, 0xf010a0a3, 0x312828, 0x18) at _main+0x34
startmap_done(0x0, 0x50, 0x0, 0xf05f7c07, 0x2f78fa, 0x309720) at startmap_d=
one+
0x1cc
db>=20


I solved the problem using the bootdisk from sparc/snapshot/19991223/. Now=
=20
the installation runs very well.

> I just booted boot-141.fs on my Sparc Classic (actually a converted
> SPARCclassic X) and it came up fine. I'm using four 64 MB SIMMs in the
> box, though, and this was on the graphics display.

You mean you are using 4*64=3D256MB RAM in a Classic??? I thought 2*32+4*16=
 ist=20
the maximal configuration supported by the Classic an the LX.=20

Reinhard
--=20
Reinhard F=F6rster, Dresden University of Technology, Dept. of CS
email: rf11@inf.tu-dresden.de  URL: http://www.inf.tu-dresden.de/~rf11/
phone: +49-351-8900023  addr: Nixenweg 21, 01108 Dresden, Germany