search for: pinnable

...7424 Jun 8 00:58 core.13483 -rw------- 1 root root 4624773120 Jun 8 03:21 core.8792 On 06/08/2012 04:34 PM, Anand Avati wrote: Is it possible the system was running low on memory? I see you have 48GB, but memory registration failure typically would be because the system limit on the number of pinnable pages in RAM was hit. Can you tell us the size of your core dump files after the crash? Avati On Fri, Jun 8, 2012 at 4:22 PM, Ling Ho < ling at slac.stanford.edu > wrote: Hello, I have a brick that crashed twice today, and another different brick that crashed just a while a go. T...

Hello, I am running SAMBA 2.0.7.0 on AIX 4.3.3.0 I have a 1 Tera Byte filesystem on AIX made available to NT and MAC. There is heavy IO activity on this filesystem and all of a sudden the NT's and MAC's can't read or write any file on this shared filesystem. Also AIX is running out of memory whenever this happens and files cannot be copied onto the said filesystem even at unix

With pretty trivial user mode programs being able to crash the kernel due to the ref counter widths in Xen being more narrow than in Linux, I started an attempt to put together a kernel side fix. While addressing the plain hypercalls is pretty strait forward, dealing with multicalls (both when using them for lazy mmu mode batching and when explicitly using them in e.g. netback - the backends are