Summary: | Nouveau does DMA to/from unexpected address | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Stijn Tintel <stijn+bugs> | ||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||
Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | major | ||||||
Priority: | medium | CC: | cristian.ciupitu | ||||
Version: | unspecified | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Stijn Tintel
2013-07-08 13:12:01 UTC
Looking at that redhat bug report, someone added comments about similar issues on NV43 a while after it was closed. Since you have a NV4B, I expect that the issue is the same. Has this always been happening, or is this a new issue? (Guessing the former...) If it's a new issue, doing a kernel bisect would narrow down the commit that broke things. If it has always been like that, does this issue occur with the nvidia binary driver? If not, doing an mmiotrace would be helpful (guide at https://wiki.ubuntu.com/X/MMIOTracing). The register written to by 4eb3033c only exists on NV50+ according to envytools. Are all the errors the same (i.e. trying to read from address 0) or does it vary? (In reply to comment #1) > Has this always been happening, or is this a new issue? (Guessing the > former...) I can't tell, as I have been using nvidia.ko until now. > If it has always been like that, does this issue occur with the nvidia > binary driver? If not, doing an mmiotrace would be helpful (guide at > https://wiki.ubuntu.com/X/MMIOTracing). The register written to by 4eb3033c > only exists on NV50+ according to envytools. It does not occur with nvidia.ko. MMIOTrace output @ http://stewie.be.tintel.eu/mmiotrace.log > Are all the errors the same (i.e. trying to read from address 0) or does it > vary? Grep on /var/log messages shows only address 0. Forgot to actually start X, updated the log @ http://stewie.be.tintel.eu/mmiotrace.log :-) Created attachment 82309 [details] [review] Attempt at adding some writes that the blob does Please give this patch a shot. Just saw a few things that stood out in your mmiotrace, I have no idea what they actually do :) Perhaps totally unrelated. If it causes new problems, try the new writes individually. After correcting the typos (mv_wr32 -> nv_wr32), I was able to build the kernel. Unfortunately I still see the same DMAR errors. Still something actually happening with newer kernels (3.17/3.18)? (In reply to Tobias Klausmann from comment #7) > Still something actually happening with newer kernels (3.17/3.18)? Unfortunately the card died so I am unable to test anything. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/46. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.