On 03/13/2013 11:15 AM, richard -rw- weinberger wrote: > On Tue, Mar 12, 2013 at 9:59 PM, Toralf Förster <toralf.foers...@gmx.de> > wrote: >> While trying trinity under a UML I often run into this situation : >> >> >> 2013-03-12T21:54:41.934+01:00 trinity kernel: ------------[ cut here >> ]------------ >> 2013-03-12T21:54:41.934+01:00 trinity kernel: WARNING: at >> mm/page_alloc.c:2386 __alloc_pages_nodemask+0x153/0x750() >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fcfc: [<083426b8>] >> dump_stack+0x22/0x24 >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fd14: [<0807d11a>] >> warn_slowpath_common+0x5a/0x80 >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fd3c: [<0807d1e3>] >> warn_slowpath_null+0x23/0x30 >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fd4c: [<080d2bb3>] >> __alloc_pages_nodemask+0x153/0x750 >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fdd8: [<080d31d8>] >> __get_free_pages+0x28/0x50 >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fdf0: [<080fbe1f>] >> __kmalloc_track_caller+0x3f/0x180 >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fe18: [<080de616>] >> memdup_user+0x26/0x70 >> 2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fe34: [<080de81e>] >> strndup_user+0x3e/0x60 >> 2013-03-12T21:54:41.935+01:00 trinity kernel: 3837fe50: [<0823c493>] >> sys_request_key+0x53/0x170 >> 2013-03-12T21:54:41.935+01:00 trinity kernel: 3837feac: [<08062a92>] >> handle_syscall+0x82/0xb0 >> 2013-03-12T21:54:41.935+01:00 trinity kernel: 3837fef4: [<08074e7d>] >> userspace+0x46d/0x590 >> 2013-03-12T21:54:41.935+01:00 trinity kernel: 3837ffec: [<0805f7cc>] >> fork_handler+0x6c/0x70 >> 2013-03-12T21:54:41.935+01:00 trinity kernel: 3837fffc: [<00000000>] 0x0 >> 2013-03-12T21:54:41.935+01:00 trinity kernel: >> 2013-03-12T21:54:41.935+01:00 trinity kernel: ---[ end trace >> 2e631e8b4588be93 ]--- >> 2013-03-12T21:54:41.935+01:00 trinity kernel: VFS: Warning: trinity-child0 >> using old stat() call. Recompile your binary. >> 2013-03-12T21:54:41.935+01:00 trinity kernel: VFS: Warning: trinity-child0 >> using old stat() call. Recompile your binary. > > Do you see this with both slub and slab? >
With SLUB (linux-v3.9-rc2-178-g4febd95) I see that behaviour. A recent UML kernel with SLAB (linux-v3.9-rc2-188-g6c23cbb) holds just here in trinity output : [1050] [2174] getrlimit(resource=3, rlim=1) = -1 (Bad address) [1050] [2175] ustat(dev=4096, ubuf=4) = -1 (Invalid argument) [1050] [2176] mremap(addr=0, old_len=0x80000001, new_len=0xffa2, flags=1, new_addr=0) [watchdog] 2177 iterations. [F:1790 S:386] [watchdog] kernel became tainted! Last seed was 2735014321 after that the system hangs. I can still ssh into it from other console and run "ps -ef" , but even a "ps -ef | grep <bla bla>" then hangs too and can't be stopped via Ctrl.C. Furthermore "gdb -p <pid>" could not be run, b/c in the meanwhile the pids are vanished too (at least from /proc). And the syslog and anything else is empty. Host kernel is always 3.7.10. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
