There's a general protection fault within kmem_cache_alloc_trace when
dcn10_create_resource_pool calls kzalloc (which looks innocuous). There's
another general protection fault in kmem_cache_alloc_trace later, called from
cgroup code. Looks like there might be a general memory management related
issue.