From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 75620] New: [NVAA] nouveau: tearing regression
Date: Fri, 28 Feb 2014 19:56:21 +0000 [thread overview]
Message-ID: <bug-75620-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2630 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75620
Priority: medium
Bug ID: 75620
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [NVAA] nouveau: tearing regression
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexanders83-S0/GAf8tV78@public.gmane.org
Hardware: Other
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 94915
--> https://bugs.freedesktop.org/attachment.cgi?id=94915&action=edit
git bisect log
I noticed mplayer showing some tearing starting from kernel version v3.10.7
which wasn't there in v3.8.
I could bisect it down to commit 1d7c71a3e2f77336df536855b0efd2dc5bdeb41b
(drm/nouveau/disp: port vblank handling to event interface).
Unfortunately c7d73f6a8ad71f9d9f58c86981322c6e48093a4f introduced a
NULL-pointer dereference regression. Luckily I found
526810adb93554e17bdb83023a01cfa8758960b2 which fixes that. Doing the bisect I
had to cherry-pick that each time until I tried commit 1d7c71a. At this commit
I additionally need to cherry-pick c8f28f8.
After adding those 2 commits I could run mplayer again and could clearly see
the tearing effect.
My hardware:
02:00.0 VGA compatible controller: NVIDIA Corporation C77 [GeForce 8300] (rev
a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 82f2
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at f0000000 (64-bit, prefetchable) [size=128M]
Region 3: Memory at fa000000 (64-bit, prefetchable) [size=32M]
Region 5: I/O ports at ec00 [size=128]
Expansion ROM at feae0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Kernel driver in use: nouveau
Kernel modules: nouveau
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4048 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-02-28 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 19:56 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-75620-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-26 22:05 ` [Bug 75620] [NVAA] nouveau: tearing regression bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-75620-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.