On Wed, Mar 22, 2017 at 01:58:58AM +0000, Cai, Jason wrote: > Dear Kernel Hackers, > > I'm Jason Cai, a kernel developer from Dell EMC. I hit the same issue as the > one Lennart Sorensen sent at Dec 19, 2016. > > I narrow down the issue now. It seems that an unexpected DNA > (Device not Available) may be triggered in the `execve` code path. > Specifically, it exists between `setup_new_exec()` and `start_thread()` in > file `load_elf_binary()`. > > I've added a BUG_ON() just before `start_thread` in `load_elf_binary ` to > assert the fpu status of the current process descriptor should be clean > when performing an exec. It gets triggered and the stack is as the following: As you have a closed kernel module loaded, it's impossible for us to actually tell what you are doing, or support you at all, sorry. Please work with the group that gave you that code, as they are the only ones that can do so. Also, does this happen with 4.10? 3.2 is _really_ old you know. thansk, greg k-h