Martin - the value written to /sys/kernel/debug/tracing/buffer_size_kb is the amount of _contiguous_ RAM allocated for each CPU. The initial value of 128000 was somewhat arbitrary, so I decided to proceed likewise and arbitrarily divide the value by the number of CPUs. I've tried it on an Emerald class server (64 CPU) without any complaints in dmesg. It appears to have solved the issue on low RAM systems as indicated above.
-- Kernel trace buffer should be set to less unrealistic value https://bugs.launchpad.net/bugs/491943 You received this bug notification because you are a member of Registry Administrators, which is the registrant for NULL Project. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
