On Wed, 30 Aug 2000, Mark Blackman wrote:

> > Hm.  Looks like the error occurred from 
> > confaddr_ok().  confaddr_ok() should be using probeget() to access the
> > address.  The pointer to the trapframe causing that problem should be the
> > second argument to data_access_error, so you can dump it with `mach tf
> > fe037010'.
> > 
> > Anyway, probeget should be able to safely access bad memory
> > locations.  Looks like a bug in probeget().  Let me fix that real quick.
> > 
> > O.K.  I updated: 
> > 
> > 	ftp.netbsd.org:/pub/NetBSD/arch/sparc64/other/netbsd.bootdebug
> > 
> > with another fix.  Give it a try.
> > 
> > Eduardo Horvath				   
> 
> same problem, same address.  'trace' and 'mach tf' follow at
> end of verboseness.
> 
> **********************
[...]

> flashprom at ebus0 addr 0-fffff addr 0-fffff not configured
> SUNW,envctrltwo at ebus0 addr 600000-600003 ipl 40 ipl 37 not configured
> hme1 at pci0 dev 1 function 1
> hme1: device_register: bpname network((null))
> instance_match: pci device, want dev 0x1 fn 0x1 have dev 0x1 fn 0x1
>         -- found ethernet controller hme1
> : address 08:00:20:cf:d2:09
> nsphy0 at hme1 phy 1: DP83840 10/100 media interface, rev. 1
> nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> hme1: using vector 0 for interrupt
> data memory error type 32 sfsr=0x0 sfva=0xfe037010 afsr=0x88000000 afva=0x1fe01000a00 tf=0xf18091
> 00
> panic: trap: memory error
> kdb breakpoint at 0xf126d810
> Stopped in swapper at   cpu_Debugger+0x4:       nop
> db> trace
> data_access_error(32, fe037010, 0, 1fe01000a00, f1410000, f1809100) at data_acce
> ss_error+0x338
> data_error(4008002, 1d, f1802000, 1fe010009ec, 4, 1fe01000a00) at data_error+0x4
> 
> confaddr_ok(f270ff00, a00, f1809470, f270bd30, f142c000, 4) at confaddr_ok+0xa8
> pci_conf_read(f1425dc8, a00, 0, 200, 50a0000, 0) at pci_conf_read+0x98
> pci_probe_bus(f26f3a00, 8, ffff, 2, f26f3d00, f26f3c80) at pci_probe_bus+0x10c

Hm.  Obviously my fix didn't work right.  I'm going to have to spend a bit
more time working on it.  This may take a few days to do since I will need
to artificially reproduce the problem so I can verify the fix.


Eduardo Horvath