[OpenAFS-port-darwin] Re: Many crashes on OS X 10.3 - MP problem?

[Steve Lidie]

On Feb 13, 2004, at 5:06 PM, Ragnar Sundblad wrote:

>
> --On den 13 februari 2004 10:54 -0500 "Tim C." <tim@umbc.edu> wrote:
>
>>   I've been watching this thread with some interest.  My two coworkers
>> have been using their powerbooks, running 10.3 and openafs 1.2.10+ 
>> since
>> 10.3 came out.  They've had minor complaints, but no panics.  I have
>> been using a mac with 10.3 and openafs 1.2.11a for the past week or 
>> two,
>> and haven't had any problem what so ever with it.
> ...
>
> This is very interresting, and I am glad to hear that!
>
> Coming to think of it, I have only tested openafs (and had
> panics) on MP machines. Powerbooks typically aren't MPs.
>
> Could it be an MP problem? What do everyone else on this list
> say, what machines have you typically used?

Dual G5.  My kernel panics are of two types,

1) [lusol@Dragonfly:/Library/Logs] grep vnreclaim panic.log
panic(cpu 0): vnreclaim: v_usecount
panic(cpu 0): vnreclaim: v_usecount
panic(cpu 0): vnreclaim: v_usecount
panic(cpu 1): vnreclaim: v_usecount
panic(cpu 1): vnreclaim: v_usecount
panic(cpu 1): vnreclaim: v_usecount
panic(cpu 1): vnreclaim: v_usecount
panic(cpu 0): vnreclaim: v_usecount
panic(cpu 1): vnreclaim: v_usecount
panic(cpu 1): vnreclaim: v_usecount

2) [lusol@Dragonfly:/Library/Logs] grep afs panic.log
panic(cpu 0): Increase -stat parameter of afsd(VLRU cycle?)
          org.openafs.filesystems.afs(1.2.10)@0x29f57000
panic(cpu 0): Increase -stat parameter of afsd(VLRU cycle?)
          org.openafs.filesystems.afs(1.2.10)@0x28ecb000


>
> Other questions to those who have used openafs on osx longer
> than me:
>
> Are these problem entirely new with 10.3, or have they
> just intensified, or what is the history here?

I have no data here - dual G5 and 10.3.x is current setup, previous 
setup was a Cube and 10.2.x.

>
> On one machine here beside me I have had a bunch of
> "vnreclaim: v_usecount" panics and a
> "vinactive: vnode still on list" panic, which to me, who knows
> far to little about this but anyway, sounds like it could be
> problem with how something, and I have only added openafs,
> handles it vnode interaction with the vfs layer.
> This doesn't really say where the problem is of course, but
> could be an indication.
> If it is new to 10.3 we maybe could get an even better hint
> of where to start looking from the apple file system people
> who should know what has changed (like Edward, whom we also
> want to tha
>
> /ragge
>

Steve