[OpenAFS-port-darwin] OpenAFS and MacosX 10.1.2/Darwin 5.2 - new and old crash

Ragnar Sundblad ragge@nada.kth.se
Mon, 14 Jan 2002 22:05:15 +0100


Got another crash, while shutting down:
...
continuing
WARM shutting down of: CB... afs... BkG... CTrunc... AFSDB... RxEvent... 
RxListener... panic(cpu 0): sbdrop
Latest stack bracktrace for cpu 0:
  Backtrace:
   [see below]
  Kernel loadable modules in backtrace:
   org.openafs.fileystems.afs(1.2.2)@0xaf16000
Proceeding back via exception chain:
  ....
Backtrace from remote gdb:
#0  0x00081964 in Debugger ()
#1  0x00028080 in panic ()
#2  0x000417ec in zalloc_canblock ()
#3  0x0002d02c in kalloc_canblock ()
#4  0x001842cc in _MALLOC ()
#5  0x001a35c0 in dup_sockaddr ()
#6  0x001a02fc in soreceive ()
#7  0x0af6b5e0 in ?? ()
#8  0x0af6c998 in ?? ()
#9  0x0af6cd0c in ?? ()
#10 0x0af7fef4 in ?? ()
#11 0x0af81810 in ?? ()
#12 0x00092b88 in unix_syscall ()
#13 0x0008ed40 in .L_call_server_syscall_exception ()
#14 0x616d6470 in ?? ()
Cannot access memory at address 0xbfffc870


And the other one:

--On den 13 januari 2002 01:06 +0100 Ragnar Sundblad <ragge@nada.kth.se> 
wrote:
...
> I have also had a few crashes. I haven't had the symbols for
> the afs kext, and certainly not for the kernel since the source
> isn't out yet, but it has been in sorecieve every time.
> (sorry, thought I hade a backtrace at least, but I have lost it.)
...

Found it:
#0  0x00081964 in Debugger ()
#1  0x00028080 in panic ()
#2  0x000417ec in zalloc_canblock ()
#3  0x0002d02c in kalloc_canblock ()
#4  0x001842cc in _MALLOC ()
#5  0x001a35c0 in dup_sockaddr ()
#6  0x001a02fc in soreceive ()
#7  0x0af6b5e0 in ?? ()
#8  0x0af6c998 in ?? ()
#9  0x0af6cd0c in ?? ()
#10 0x0af7fef4 in ?? ()
#11 0x0af81810 in ?? ()
#12 0x00092b88 in unix_syscall ()
#13 0x0008ed40 in .L_call_server_syscall_exception ()
#14 0x616d6470 in ?? ()
Cannot access memory at address 0xbfffc870


(Does anybody listen? Does anybody use this info? :-)

/ragge