I found some other info in dmesg which I overlooked first, but nevertheless displaying info and then crashing seems a bit harsh:
Found system call table at 0xc048f780 (pattern scan) Starting AFS cache scan...<4>allocation failed: out of vmalloc space - use vmall oc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. afs_osi_Alloc: Can't vmalloc 16384 bytes. afsd: memCache allocation failure at 58576 KB. afsd: memory cache too large for available memory. afsd: AFS files cannot be accessed. found 0 non-empty cache files (0%). Unable to handle kernel NULL pointer dereference at virtual address 00000147 printing eip: f9b58c77 *pde = 00000000 etc. _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
