[OpenAFS] System still panicing.. no help found yet..

[Mitchell Baker]

Here is the stack trace...

adb -k unix.76 vmcore.76
physmem 3e118
$c
panicsys(10423630,2a100844f28,10139e18,78002000,2000,0) + 44
vpanic(10139e18,2a100844f28,14,2a100844e88,100cf634,30004fc58e6) + cc
panic(10139e18,3000e6c6728,10437dc0,3000e682100,a,3000e6c6728) + 1c
kmem_error(1042ec00,30000029000,3000e6c6738,6,30000029000,3000e6c6728) + 448
afs_osi_Free(3000e6c6728,1,0,7efefeff,81010100,ff0000) + 8c
afs_FlushVCache(3000794b3e8,2a1008451c8,4000,0,780fdb60,3000794b3e8) + 2ec
afs_NewVCache(2a100845470,0,5,3000794b458,3000794b630,3000794b3e8) + 2b8
afs_GetVCache(2a100845470,2a100845500,2a10084544c,0,2,0) + 218
afs_lookup(300079a5030,2a100845750,2a100845748,30007e7e9b0,0,0) + cf8
gafs_lookup(300079a5030,2a100845750,2a100845748,2a100845a10,0,300051d7da8) + 40
lookuppnvp(2a100845a10,0,1045ea78,1045a908,0,2) + 2cc
lookuppn(300051d7da8,0,0,300051d7da8,2a100845ae8,2a100845a10) + 128
lookupname(0,0,1,0,2a100845ae8,fb298) + e8
stat32(fb298,fa810,67000000,7efefeff,81010100,ff00) + 14

Thanks.....


See-ya
Mitch

At 12:01 PM 3/14/2002 -0500, you wrote:
>To: openafs-info@openafs.org
>Subject: Re: [OpenAFS] System still panicing.. no help found yet..
>Date: Wed, 13 Mar 2002 13:08:08 -0500
>From: Nickolai Zeldovich <kolya@MIT.EDU>
>
> > I still have a system which is panicing 2-3 time a day...  SUN says it is
> > in the same place each time
> > from the coredump...
>
>This seems very similar to the panics we see on one of our web
>servers, though with much less frequency than you describe (maybe
>once every few weeks).  Could you also show the stack trace from
>the crash dumps?  (E.g., adb -k unix.N vmcore.N, and $c).
>
> > kernel memory allocator: buffer freed to wrong cache
> > buffer was allocated from kmem_alloc_16,
> > caller attempting free to kmem_alloc_8.
> > buffer=300092fd6c0 bufctl=3000bf703c0 cache: kmem_alloc_8
>
>Actually, could you also run something like "300092fd6c0/s"
>and "300092fd6c0/4X", to see what's in the link data field?
>
>Given the allocator stack trace you've shown, it seems very
>likely to be an AFS problem, though.  Infact, I was suspecting
>AFS link data allocation as well, when debugging our webserver,
>but didn't have any reliable stack traces to go on further.
>
>-- kolya

/####################################################################/
/# Mitchell "Buzz" Baker                "To Infinity And Beyond..." #/
/# Sr. Systems/Security Admin   Rose-Hulman Institute of Technology #/
/# Mitchell.D.Baker@rose-hulman.edu             www.rose-hulman.edu #/
/#         For PGP Public key, check out www.keyserver.net         #/
/####################################################################/