[OpenAFS-devel] panic on sun4u_57 on machine running 64bit OS+HW
Neulinger, Nathan
nneul@umr.edu
Tue, 9 Apr 2002 12:28:39 -0500
DAMN!. I just found out this appears to be something I've done in the
prototypes branch. When I tested to see if the main branch also had the
problem, I forgot to update the lib's in /kernel, so I really didn't
test it.=20
Now I just need to figure out how I broke it.=20
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: nneul@umr.edu
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services Fax: (573) 341-4216
> -----Original Message-----
> From: Neulinger, Nathan=20
> Sent: Tuesday, April 09, 2002 12:01 PM
> To: 'Frank.Batschulat@Sun.COM'
> Subject: RE: RE: [OpenAFS-devel] panic on sun4u_57 on machine=20
> running 64bit OS+HW
>=20
>=20
> Not sure if this will help any, but it looks to me like it's=20
> failing on the first afs syscall.
>=20
> Anything specific you'd like me to try to dig into?
>=20
> # ./afs start
> Entry for afs already exists in /etc/name_to_sysnum
> Loading NFS server kernel extensions
> Loading AFS kernel extensions
> Starting afsd
> afsd: My home cell is 'umr.edu'
> SScall(73, 28, 17)=3D0 afsd: Forking rx listener daemon.
> afsd: Forking rx callback listener.
> afsd: Forking rxevent daemon.
> afsd: Forking AFS daemon.
> afsd: Forking Check Server Daemon.
> afsd: Forking 5 background daemons.
> AD TRAP: cpu=3D0 type=3D0x31 rp=3D0x2a1001e6fc0 addr=3D0x7c6000 =
mmu_fsr=3D0x0
> afsd: trap type =3D 0x31
> addr=3D0x7c6000
> pid=3D121, pc=3D0x1000cad4, sp=3D0x2a1001e6861,=20
> tstate=3D0x4480001604, context=3D0x33
> g1-g7: 78034000, c0001, c0001, 2fc000, 2c000, 0, 300001b47a0
> Begin traceback... sp =3D 2a1001e6861
> Called from 102c4d64, fp=3D2a1001e6951, args=3D61=20
> ffffffffffffffff 2a700 0 7c6000 0
> Called from 102ec3ac, fp=3D2a1001e6a31, args=3D1b59=20
> ffffffffffffffff 1c 30000631800 30000631000 0
> Called from 102ec5cc, fp=3D2a1001e6af1, args=3Db22 0 300000b57fc 73 0 =
ff00
> Called from 102edf74, fp=3D2a1001e6fa1, args=3D30 b22 0 0 ff231f98 0
> Called from 10067108, fp=3D2a1001e70b1, args=3D30000051e68=20
> 3000043c0c0 2a1001e7968 1c 8 0
> Called from 10067260, fp=3D2a1001e7171, args=3D10449880=20
> 2a1001e7b80 3000043c008 0 0 300000b4f90
> Called from 10067330, fp=3D2a1001e7221, args=3D1c 30 b22 0 0 ff231f98
> Called from 10031f58, fp=3D2a1001e72d1, args=3D49 10449880 30 b22 0 0
> Called from 21a08, fp=3Dffbec7a8, args=3D49 1c 30 b22 0 0
> End traceback...
> panic[cpu0]/thread=3D300001b47a0: trap
> syncing file systems... done
> dumping to /dev/dsk/c0t0d0s1, offset 125927424
>=20
> -- Nathan
>=20
> ------------------------------------------------------------
> Nathan Neulinger EMail: nneul@umr.edu
> University of Missouri - Rolla Phone: (573) 341-4841
> Computing Services Fax: (573) 341-4216
>=20
>=20
> > -----Original Message-----
> > From: Neulinger, Nathan=20
> > Sent: Monday, April 08, 2002 1:09 PM
> > To: 'Frank.Batschulat@Sun.COM'
> > Subject: RE: RE: [OpenAFS-devel] panic on sun4u_57 on machine=20
> > running 64bit OS+HW
> >=20
> >=20
> > # adb -k unix.0 vmcore.0
> > physmem 3b76
> > C
> > bad modifier
> > $C
> > complete_panic(1040d400,2a10030cc70,0,3,0,0) + 20
> > [savfp=3D0x2a10030c1c1,savpc=3D0x1000ff44]
> > do_panic(10408000,2a10030cc70,0,0,3000044abc0,1) + 158
> > [savfp=3D0x2a10030c271,savpc=3D0x1006fed0]
> > vcmn_err(2a10030cc70,3,10416020,3,300007f1c20,4) + 198
> > [savfp=3D0x2a10030c331,savpc=3D0x1006fd28]
> > cmn_err(3,10416020,5bf48,14a,14a,1040d800) + 1c
> > [savfp=3D0x2a10030c3e1,savpc=3D0x100290a8]
> > die(31,2a10030cfc0,10416020,0,806000,2a10030cfc0) + b0
> > [savfp=3D0x2a10030c4b1,savpc=3D0x10029b08]
> > trap(806000,1,0,300007b0a78,2a10030cfc0,5) + 85c
> > [savfp=3D0x2a10030c601,savpc=3D0x1001da6c]
> > $q
> >=20
> >=20
> > Doesn't look too useful to me unfortunately, but maybe it=20
> > means something to you. Looks to me like the BAD TRAP is what=20
> > did it, but what caused that type of trap is the question.=20
> >=20
> > -- Nathan
> >=20
> > ------------------------------------------------------------
> > Nathan Neulinger EMail: nneul@umr.edu
> > University of Missouri - Rolla Phone: (573) 341-4841
> > Computing Services Fax: (573) 341-4216
> >=20
> >=20
> > > -----Original Message-----
> > > From: Frank.Batschulat@Sun.COM [mailto:Frank.Batschulat@Sun.COM]=20
> > > Sent: Monday, April 08, 2002 12:56 PM
> > > To: Neulinger, Nathan
> > > Subject: Re: RE: [OpenAFS-devel] panic on sun4u_57 on machine=20
> > > running 64bit OS+HW
> > >=20
> > >=20
> > > >Hmm... Panic message I can get you. You'll have to tell me how to
> > > >generate the stacktrace.=20
> > >=20
> > > if you have solaris 8
> > >=20
> > > use mdb (see man mdb) like this:
> > >=20
> > > mdb corefile number <enter>
> > > $C <enter>
> > > $q <enter
> > >=20
> > > end send me the output...
> > >=20
> > > on former versions of solaris use
> > > adb (see man adb) like this:
> > >=20
> > > adb -k ./namelist (akak unix.N) ./crashfile (akak vmcore.N).
> > > $C <enter>
> > > $q <enter>
> > >=20
> > > and send me the stacktrace....
> > >=20
> > > I can then try to see if that rings a bell...
> > >=20
> > > frankB
> > >=20
> > > >Loading AFS kernel extensions
> > > >Starting afsd
> > > >BAD TRAP: cpu=3D0 type=3D0x31 rp=3D0x2a1001f2fc0 addr=3D0x88a000=20
> > mmu_fsr=3D0x0
> > > >afsd: trap type =3D 0x31
> > > >addr=3D0x88a000
> > > >pid=3D148, pc=3D0x1000cad4, sp=3D0x2a1001f2861, =
tstate=3D0x4480001600,
> > > >context=3D0x102b
> > > >g1-g7: 78034000, c0002, c0002, 576000, 2c000, 0, 300001ce2a0
> > > >Begin traceback... sp =3D 2a1001f2861
> > > >Called from 102c5d7c, fp=3D2a1001f2951, args=3D61=20
> > > ffffffffffffffff 2a700 0
> > > >88a000 0
> > > >Called from 102ed5d4, fp=3D2a1001f2a31, args=3D1b59=20
> ffffffffffffffff 1c
> > > >300008d3800 300008d3000 0
> > > >Called from 102ed7f4, fp=3D2a1001f2af1, args=3Db22 0 300000c57fc=20
> > > 73 0 ff00
> > > >Called from 102ef1c4, fp=3D2a1001f2fa1, args=3D30 b22 0 0 =
ff231f98 0
> > > >Called from 10067108, fp=3D2a1001f30b1, args=3D300000e1e68=20
> 300008f1c08
> > > >2a1001f3968 1c 8 0
> > > >Called from 10067260, fp=3D2a1001f3171, args=3D10449880 =
2a1001f3b80
> > > >300008f1b50 0 0 300000c4f90
> > > >Called from 10067330, fp=3D2a1001f3221, args=3D1c 30 b22 0 0 =
ff231f98
> > > >Called from 10031f58, fp=3D2a1001f32d1, args=3D49 10449880 30 b22 =
0 0
> > > >Called from 21ae8, fp=3Dffbec7b8, args=3D49 1c 30 b22 0 0
> > > >End traceback...
> > > >panic[cpu0]/thread=3D300001ce2a0: trap
> > > >syncing file systems... 2 done
> > > >dumping to /dev/dsk/c0t0d0s1, offset 125927424
> > > >
> > > >
> > > >
> > > >-- Nathan
> > > >
> > > >------------------------------------------------------------
> > > >Nathan Neulinger EMail: nneul@umr.edu
> > > >University of Missouri - Rolla Phone: (573) 341-4841
> > > >Computing Services Fax: (573) 341-4216
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Frank Batschulat - Solaris Sustaining Engineering=20
> > > >> [mailto:Frank.Batschulat@Sun.COM]=20
> > > >> Sent: Monday, April 08, 2002 3:30 PM
> > > >> To: Neulinger, Nathan
> > > >> Subject: RE: [OpenAFS-devel] panic on sun4u_57 on machine=20
> > > >> running 64bit OS+HW
> > > >>=20
> > > >>=20
> > > >> Do you have the panic message from the console
> > > >> and a stacktrace from the core file handy ?
> > > >>=20
> > > >> frankB
> > > >>=20
> > > >>=20
> > > >
> > >=20
> >=20
>=20