Hello Konstantin, Wednesday, December 10, 2003, 10:38:54 AM, you wrote:
KN> Hello oops-users, KN> Tuesday, December 9, 2003, 7:07:03 PM, you wrote: LEK>> We have a problem with oops (both 1.5.23 and the cvs version), it died LEK>> a couple hours after it has been started. LEK>> Here is the output of oops.log: LEK>> [0x19465]run_client(): No mem for header! LEK>> [0x6b1ac]run_client(): No mem for header! LEK>> [0x9a268]fill_mem_obj(): select: timed out. LEK>> [0xbcef3]attach_data(): No mem in attach data. LEK>> [0x5795e]run_client(): No mem for header! KN> What gdb is answer on where in core? How many memory oops use? mb KN> needs set limits or more RAM|swap? LEK>> There's no other messages abnormal, but sometimes with below messages LEK>> from kernel (not always): LEK>> Dec 8 13:54:05 tproxy1 kernel: oops: page allocation failure. order:3, mode:0x20 LEK>> Dec 8 13:54:05 tproxy1 kernel: Call Trace: LEK>> Dec 8 13:54:05 tproxy1 kernel: [<c013ac0d>] __alloc_pages+0x2de/0x31c LEK>> Dec 8 13:54:05 tproxy1 kernel: [<c013ac70>] __get_free_pages+0x25/0x3f LEK>> Dec 8 13:54:05 tproxy1 kernel: [<c013e0cd>] cache_grow+0xed/0x345 LEK>> The swap remain unused at that time. LEK>> Tested on both kernel 2.4.23 and 2.6.0-test9-mm5, LEK>> glibc-2.2.5, gcc-3.3.2 (gcc-2.95.3 also), Debian GNU/Linux-3.0. KN> what threads type are u use? LEK>> The request rate varies from 100 req/s to 550 req/s. KN> what hardware u use? IMHO for this requests rate Linux not a best KN> choise :( MB memory manager really can't allocate memory on this KN> speed... They can, but problem - that memory fragmentation become very fast. I think this is a problem. IMHO best choice to set limit 1/4 of system RAM. LEK>> Any ideas what's wrong? -- Best regards, Denis mailto:[EMAIL PROTECTED] ===================================================================== If you would like to unsubscribe from this list send message to [EMAIL PROTECTED] with "unsubscribe oops" in message body. Archive is accessible on http://lists.paco.net/oops-rus/
