On Fri, Jan 07, 2000 at 08:21:36AM -0800, Eduardo E. Horvath wrote:
> > sc->sc_reg == 0xfe02a040
> >     This is a pointer to an sbus_reg structure containing
> >     the values as mentioned in be previous mail (slot==2,
> >     offset==0x40, size==0x100)
> 
> What? [...] which means that sc->sc_reg should point to the
> register's VA [...]

Oops, of course you are right. The value for sc_reg was correct,
but the text was for sa_reg.

> cd SUNW,DBRIs3@2,40
> .properties

Unfortunately, I have version 2.X, so there is no .properties.
See below.

> One thing to try is once the machine has panic'ed, grab the address it
> panic'ed on and:
> 
> <addr>	map?

Virtual  : fe02.a040
Context  : @ 0.0023.0000 0002.3101 #0
Region   : @ 0.0023.13f8 0002.3221
Segment  : @ 0.0023.2200 0002.6a41
Page     : @ 0.0026.a4a8 0500.003e Referenced Access : rwx---
Physical : 0.5000.0040

The physical address is correct (according to the 3GX technical
manual).
 

Additionally, I have done the following (after reset):

ok " /sbus" select-dev
ok 40 2 100 map-in .s
ffecf040
ok 2 dump
......headerline......
ffecf040  Data Access Error

The same happens with a dump of length 1 or length 4.

If I poke into the register, a Level 15 interrupt is
generated. The 0x100-byte range has "holes", but the
interrupt seems to be of which (valid) register I use.

    Ingolf
-- 

Ingolf Koch                      Beste Kneipe in Jena-Ost
PGP: 0x7B3B5661  213C 828E 0C92 16B5  05D0 4D5B A324 EC04