>Number:         25554
>Category:       port-sparc64
>Synopsis:       panic() during update 1.6.1->1.6.2 procedure (./build.sh distribution/install)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    port-sparc64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 13 09:01:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     eau@phear.org
>Release:        NetBSD 1.6.2_STABLE
>Organization:
	individual
>Environment:
System: NetBSD flufme 1.6.2_STABLE NetBSD 1.6.2_STABLE (GENERIC) #1: Mon May 10 10:21:43 CEST 2004 root@flufme:/usr/src/sys/arch/sparc64/compile/GENERIC sparc64
Architecture: sparc64
Machine: sparc64 (Ultra-1)

>Description:

During updates from 1.6.1 to 1.6.2 by  doing ./build.sh distribution i got a panic() 
then i recompiled my kernel with DIAGNOSTIC enabled (as advised).

./build.sh distribution was going fine and i reached a new panic() at ./build.sh install=/

and redoing it, i got the panic at the same place.

db> trace
Letext(953dd10, 6, 0, 93eb230, 947e260, 1) at Letext+0x1e4
uvm_fault(947e260, 947e32c, 0, 1, 21, 0) at uvm_fault+0x2e8
data_access_fault(953ded0, 30, 40204e24, 40211217, 40210090, 0) at data_access_f
ault+0xf4
Ldatafault_internal(0, 330, 0, 0, 0, 0) at Ldatafault_internal+0xc8

db> show registers
tstate      0x9982000605
pc           0x1240080  amap_copy+0x258
npc          0x1240084  amap_copy+0x25c
ipl                  0
y                    0
g0                   0
g1          0x4482008200
g2              0x4000
g3           0x1899000  uvm_vmspace_pool+0xa0
g4                   0
g5                   0
g6                   0
g7                   0
o0           0x1e1d2c0  end+0x57f110
o1          0x7b216d6370752a3a
o2           0x1e1d2c0  end+0x57f110
o3                   0
o4           0x1e1d040  end+0x57ee90
o5                   0  
o6           0x953d181  end+0x7c9efd1
o7           0x123ffc4  amap_copy+0x19c
l0                   0
...
<all zeros until..> 
gsr                  0
amap_copy+0x258:        ld              [%o1 + %g0], %o0

db> machin stack
Window 0 frame64 0x953d980 locals, ins:
1898400 1898800 20 59aa 0 0 0 0
9416210 93eb230 9416e10 8 20 5 953d241=sp 12433cc=pc:Letext+0x1e4
Window 1 frame64 0x953da40 locals, ins:
947e260 947e32c 953dd38 59aa 947e268 1 0 0 
953dd10 6 0 93eb230 947e260 1 953d301=sp 1243a7c=pc:uvm_fault+0x2e8
Window 2 frame64 0x953db00 locals, ins:
1da1b08 0 0 59aa 0 0 0 1
947e260 947e32c 0 1 21 0 953d561=sp 12c64e4=pc:data_access_fault+0xf4
Window 3 frame64 0x953dd60 locals, ins:
94a71c0 0 947e260 40210000 0 1898b88 0 5
953ded0 30 40204e24 40211217 40210090 0 953d621=sp 1008730=pc:Ldatafault_internal+0xc8
Window 4 frame64 0x953de20 locals, ins:
0 0 0 0 0 0 0 0
0 330 0 0 0 0 ffffffffffffc071=sp 0=pc:         0
Window 5 frame64 0xffffffffffffc870 locals, ins:
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0=sp 0=pc:         0

If you need more debugging informations let me know.

>How-To-Repeat:
take an Ultra-1 on 1.6.1 and update to 1.6.2
using the ./build.sh procedure (not sure but may be it's hardware related).

>Fix:
no fix yet.
>Release-Note:
>Audit-Trail:
>Unformatted: