Thursday, September 08, 2005

Panic while checking devices during a reboot

Problems and their solutions

* Panic while checking devices during a reboot

Occasional when booting the server, a message similar to the
following may appear:

Configuring /dev and /devices

panic[cpu1]/thread=30001218fe0: bad kernel MMU miss at TL 2

%tl %tpc %tnpc %tstate %tt
1 0000000001035cc4 0000000001035cc8 4480001605 068
%ccr: 44 %asi: 80 %cwp: 5 %pstate: 16<PEF,PRIV,IE>
2 00000000010071f0 00000000010071f4 9180001506 068
%ccr: 91 %asi: 80 %cwp: 6 %pstate: 15<PEF,PRIV,AG>
%g0-3: 0000000000000000 0000000000000002 0000000077196900 0000000077196900
%g4-7: 0000000000000000 0000000000000002 000000000140a4c0 0000000000000068
Register window 6, caller kmem_cache_alloc+64
%o0-3: 000003000000bb88 000002a1002c6000 0000000000000031 0000000000000000
%o4-7: 00000000000002a1 000000007804f960 000002a1002c7501 00000000010ac520
%l0-3: 0000000001035cc4 0000000001035cc8 0000004480001605 000000000102bf54
%l4-7: 000003000000bd30 000003000000bd58 0000000000000000 000002a1002c7db0
%i0-3: 000003000000b408 0000030001218fe0 0000000000000000 0000000000000000

This appears to be caused by one of the server CPUs becoming
slightly unseated. The CPUs are secured to the motherboard by screws
which are tightened using the torque screwdriver provided with each
server. The CPU retaining screws in every server we have put into
service so far have been far looser than they should be leading to
this problem occurring. The screws have now been tightened but should
this problem occur, the first thing to try is re-tightening the
screws. The screwdriver can be found to the front of the server when
the cover is removed (it's bright green and is hard to miss) and
instructions for tightening the screws are attached to the top of the


Post a Comment

<< Home