[OpenAFS] openafs 1.6.0pre4 and OSX 10.6.7 and 64bit kernel (NOT really) FIXED ;(

[Derrick Brashear]

On Tue, Mar 29, 2011 at 3:08 PM, Chris Jones
<christopher.rob.jones@cern.ch> wrote:
>
> On 29 Mar 2011, at 8:00pm, Derrick Brashear wrote:
>
>> On Tue, Mar 29, 2011 at 2:46 PM, Chris Jones
>> <christopher.rob.jones@cern.ch> wrote:
>>> Hi,
>>>
>>> Actually. I have to take it back I'm afraid. It doesn't seem to work th=
at well for me.
>>>
>>> Initially, with some basic checks it seemed OK. But then quite quickly =
after I started more extensive usage I started to get again the same old ha=
ngs and unresponsive behaviour. I tried reinstalling, restarting etc., with=
 no success.
>>
>> that's quite odd; i'm running 1.6.0pre4 in 64 bit without issue. when
>> it hangs, can you gather output from cmdebug localhost (cmdebug is in
>> /Library/OpenAFS/Tools/bin if it's not on your path)
>
> Sure, this is what I get
>
> Chris-Jones-Macbook-Pro /Library/OpenAFS/Tools/bin > ./cmdebug localhost
> Lock afs_discon_lock status: (none_waiting, 1 read_locks(pid:1133))
> ** Cache entry @ 0xd35161a0 for 0.1.16777996.1 [dynroot]
> =A0 =A0locks: (none_waiting, write_locked(pid:1133 at:599))
> =A0 =A0 =A0 =A0 =A0 =A0 =A018 bytes =A0DV =A0 =A0 =A0 =A0 =A0 =A01 =A0ref=
cnt =A0 =A0 0
> =A0 =A0callback 00000000 =A0 expires 0
> =A0 =A00 opens =A0 =A0 0 writers
> =A0 =A0mount point
> =A0 =A0states (0x5), stat'd, read-only

given where the panic was, that makes some sense.

it's unrelated to the 64 bit issue.