similar to: [Bug 75620] New: [NVAA] nouveau: tearing regression

https://bugs.freedesktop.org/show_bug.cgi?id=90423 Bug ID: 90423 Summary: [NVAA]: Shutdown (poweroff) get stuck when runtime PM is enabled Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

When reading EDID from firmware file, the nouveau driver can not setup it's native_mode like when reading EDID from hardware. Add this callback to allow driver to update their native_mode. Signed-off-by: Alexander Stein <alexanders83 at web.de> --- This might be a fast forward hack. I'm wondering if there is a better way to achieve the same. The actual problem is that

(This is a v3 of patch "drm/nouveau/fb/nv50: Add PFB writes") This fix a GPU lockup on 9400M (NVAC) when using acceleration, see https://bugs.freedesktop.org/show_bug.cgi?id=27501 v2: - Move code to subdev/fb/nv50.c as suggested by Roy Spliet; - Remove arbitrary writes to 100c18/100c24 - Replace write to 100c1c of arbitrary value by the address of a scratch page as proposed by Ilia

Dear All, After recently taking a little dive into the NVAC clock tree, I was wondering what that net would look like on cards I expect to be similar. In this case I'm looking for MMIOtraces of NVAA and NVAF, which is marketed as the 8x00 mGPU, 9x00 mGPU, 320M, ION and/or some nForce IGP. If there is anyone who could provide me with an MMIO trace for any of these cards that would be

https://bugs.freedesktop.org/show_bug.cgi?id=111503 Bug ID: 111503 Summary: [NVAA] Impossible to adjust brightness Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority: not set Component: Driver/nouveau Assignee:

https://bugs.freedesktop.org/show_bug.cgi?id=72399 Priority: medium Bug ID: 72399 Assignee: nouveau at lists.freedesktop.org Summary: [NVAA][NV50][Regression] Oops : nouveau: 3.13-rc1+ probe of 0000:02:00.0 failed with error -22 QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified

https://bugs.freedesktop.org/show_bug.cgi?id=71484 Priority: medium Bug ID: 71484 Assignee: nouveau at lists.freedesktop.org Summary: [NVAA] random graphical corruption with vlc on 3.12 (and earlier) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux

https://bugs.freedesktop.org/show_bug.cgi?id=68344 Priority: medium Bug ID: 68344 Assignee: nouveau at lists.freedesktop.org Summary: [piglit] shaders/glsl-fs-texture2d-dependent-4 randomly passes or fails on NVAA/NV50 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

On Wed, Dec 10, 2014 at 5:53 PM, Pierre Moreau <pierre.morrow at free.fr> wrote: > (This is a v3 of patch "drm/nouveau/fb/nv50: Add PFB writes") > > This fix a GPU lockup on 9400M (NVAC) when using acceleration, see > https://bugs.freedesktop.org/show_bug.cgi?id=27501 > > v2: > - Move code to subdev/fb/nv50.c as suggested by Roy Spliet; > - Remove arbitrary

Jim Hall wrote: > On Sun, May 2, 2010 at 6:08 PM, doumakes <wineforum-user at winehq.org> wrote: > Don't know if it's a total solution, but, go to in-game settings ---> Video. > I seem to remember one of the settings mentions this kind of thing. That would be Vertical Sync, which as I've said does not fix the problem.

I've recently set up a system built on an ASUS P5E-VM HDMI motherboard running Ubuntu 7.10 and I'm experiencing some very noticeable tearing during video playback with mplayer. I have read some discussion about video tearing with other Intel chipsets in the mailing list a while back but hadn't heard much about it lately. I've experimented with both xv and gl video output as well

Bump. FWIW, I note that sound disappears a random interval after I start playing WoW, which suggests some kind of creeping memory corruption to me. Perhaps it's related to the video problems, perhaps not.

As a follow-up, I have traced the PRI connection and discovered that calls hung up by a local BCM voice station (analog, digital, whatever) send a disconnect with a clear cause of 1 (Number not assigned) instead of a normal clear cause of 16. Calls forwarded through the BCM disconnect with the normal clear cause. I have kludged up a fix to change all clear causes below 2 to 16 (I placed

When a drm_crtc structure is destroyed with drm_crtc_cleanup(), the DRM core does not turn off the crtc first and neither do the drivers. With nouveau, radeon and amdgpu, this causes a runtime pm ref to be leaked on driver unload if at least one crtc was enabled. (See usage of have_disp_power_ref in nouveau_crtc_set_config(), radeon_crtc_set_config() and amdgpu_crtc_set_config()). Fixes:

http://bugs.freedesktop.org/show_bug.cgi?id=13944 Summary: nouveau video blitter gives tearing with two outputs Product: xorg Version: 7.3 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi Daniel, On Tue, May 24, 2016 at 11:30:42PM +0200, Daniel Vetter wrote: > On Tue, May 24, 2016 at 06:03:27PM +0200, Lukas Wunner wrote: > > When a drm_crtc structure is destroyed with drm_crtc_cleanup(), the DRM > > core does not turn off the crtc first and neither do the drivers. With > > nouveau, radeon and amdgpu, this causes a runtime pm ref to be leaked on > >

I have a samba 2.2.8a PDC, no windows servers at all. The local network works. Conan, the PDC also acts as a WINS server. Postie, the DHCP server sets: option netbios-name-servers 192.168.1.241 ; option netbios-node-type 2 ; All clients have lmhosts file with: 192.168.1.241 conan #pre #dom:sjsa 192.168.1.242 postie #pre Last week I needed to reinstall a computer, named pixel On server

http://bugs.freedesktop.org/show_bug.cgi?id=16490 Summary: Xv overlay tearing Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: pq at

I've been having the screen tearing issue as well, for about a week. It's not clear whether the symptoms followed the WoW 3.3.3 update, or an update to wine or the ATI drivers. At times the whole Wow window is broken into rapidly moving colored polygons, at other times there's just some flashing bright lines like tracer fire. Only seems to affect the background window if there is a

On Wed, May 25, 2016 at 03:43:42PM +0200, Daniel Vetter wrote: > On Wed, May 25, 2016 at 12:51 PM, Lukas Wunner <lukas at wunner.de> wrote: > > On Tue, May 24, 2016 at 11:30:42PM +0200, Daniel Vetter wrote: > >> On Tue, May 24, 2016 at 06:03:27PM +0200, Lukas Wunner wrote: > >> > When a drm_crtc structure is destroyed with drm_crtc_cleanup(), the DRM >