EDIT: This BUG is caused by VDPAU in conjunction with enabled intel IOMMU.
Can be triggered by either closing mplayer when it plays a video using vdpau, or if you have
libva and libva-vdpau-driver installed, simply by calling vainfo. Easiest workarouds so far
are to either disable CONFIG_IOMMU in the kernel’s .config or adding “intel_iommu=off” to the
kernel commandline.
EDIT2: fixed in 340.24!
Closing firefox usually yields the following kernel BUG() and an almost completely unresponsive system (nvidia-bugreport doesn’t finish, even in --safe-mode).
FWIW, I noticed something related with 331.38, also on 3.12.10:
NVRM: Xid (0000:01:00): 8, Channel 00000003
dmar: DRHD: handling fault status reg 3
dmar: DMAR:[DMA Write] Request device [01:00.0] fault addr fdf65000
DMAR:[fault reason 05] PTE Write access is not set
dmar: DRHD: handling fault status reg 3
[ tons more of the same ]
Have you tried unticking the “use hardware acceleration when available” option on the advanced tab in options? Firefox has caused me serious problems on Windows due to its attempts to utilise the hardware, god knows why it’s so appalling.
I’ve now gotten this BUG() when I change display settings, i.e. use KDE’s kscreen to add and remove a HDMI connected screen, and once when a full-screen mplayer shut down.
I have a Dell laptop with a different card (Quadro 2000M) and haven’t seen this, although I turned off Optimus and I’m not running KDE. Is Prime/Optimus set up on the system?
My PCs have no Optimus feature because they are all desktop.
I have 5 desktop PCs with NVIDIA’s GPU, and no problem if the CPU has no Intel’s VT-d (aka IOMMU) feature.
So, I think this is a regression of 331.38 related to VT-d or DMA handling.
hi guys, We are not able to repro this issue in house ? We’ve tried with various Fermi cards on a few different systems now with and without IOMMU enabled, and I’m still not reproducing.
Same issue here on Dell E6530 laptop (NVIDIA Corporation GF108GLM [NVS 5200M]) triggered by fullscreen mplayer playback with vdpau output. Unfortunately taking nvidia-bug-report after bug is triggered causes script to hang. I can only provide with report taken before that moment. nvidia-bug-report.log.gz (109 KB)
I confirm the bug. Tried with 334.x driver and 3.13 and 3.14 kernel. 100% reproducible with vainfo tool: it shows VDPAU info and gets killed on exit. Kernel oops appears in log. First run of MPV player is fine usually. I suppose that bug is triggered on some VDPAU closing. 331.x driver is OK. Turning intel_iommu=off fixes (or hides) the bug.
It’s still reproducable with 337.12. Identical backtrace, same way to reproduce: just close mplayer using vdpau, on plain X, no WMs or desktop environment.