To clarify, since a while the lockup moved to ttm_bo_wait_cpu (as seen
in the last Xorg.wedge.log. I hacked a bit around with function tracing
and got the following trace (which is limited atm to the two functions):

# tracer: function
#
#           TASK-PID    CPU#    TIMESTAMP  FUNCTION
#              | |       |          |         |
       plymouthd-316   [000]    16.812883: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
       plymouthd-316   [000]    16.812938: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860119: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860316: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860319: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860320: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860322: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860324: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860326: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860333: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860335: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860337: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860338: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860340: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860342: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.860384: nouveau_gem_ioctl_cpu_fini 
<-drm_ioctl
           <...>-1069  [000]    17.880233: ttm_bo_wait_cpu <-validate_init

-- 
nouveau hard lockup in nouveau_gem_ioctl_cpu_fini
https://bugs.launchpad.net/bugs/539655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to