Re: BUG at kmem_cache_alloc

[Dave Jones]

On Tue, Mar 26, 2013 at 05:32:27AM -0400, CAI Qian wrote:

 > Still running and will update ASAP. One thing I noticed was that trinity
 > threw out this error before the kernel crash.
 > 
 > BUG!:       
 > CHILD (pid:28825) GOT REPARENTED! parent pid:19380. Watchdog pid:19379 
 >       
 > BUG!:       
 > Last syscalls: 
 > [0]  pid:28515 call:settimeofday callno:10356 
 > [1]  pid:28822 call:setgid callno:322 
 > [2]  pid:28581 call:init_module callno:3622 
 > [3]  pid:28825 call:readlinkat callno:403 
 > child 28581 exiting 
 > child 28515 exiting 
 >  ...killed. 

When this happens, it usually means that the parent segfaulted.
I've been trying to reproduce a few reports of this for a while
without success.  If you get time, running trinity inside gdb should
be enough to get a useful backtrace.

(Or run with -D, and collect coredumps [there will a lot], and match the
 core to the pid of the process we're interested in)

	Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/