All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63011] New: radeon: horizontal stripes when updating screen
Date: Mon, 14 Oct 2013 10:53:30 +0000	[thread overview]
Message-ID: <bug-63011-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=63011

            Bug ID: 63011
           Summary: radeon: horizontal stripes when updating screen
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.11.5
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: mikko.rapeli@iki.fi
        Regression: No

After updating kernel from 3.10.9 to 3.11.2 and now .5, content in non-active
windows in X are showing horizontal stripes, I guess one pixel high and width
of the non-active window in X, when for example scrolling down a browser page
using the mouse wheel. Also the mouse pointer in X is sometimes flickering much
more than before with 3.10 and older kernels.

Base system: Ubuntu 12.04 LTS, Xorg 1.11.3.

PC: HP EliteBook 8560p, Core i7 with Radeon graphics

Radeon graphics details, lcpci -v -v:

01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Seymour 
[Radeon HD 6400M Series] (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company Device 161a
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Step
ping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at d4400000 (64-bit, non-prefetchable) [size=128K]
        Region 4: I/O ports at 4000 [size=256]
        Expansion ROM at d4440000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1
unlimited
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
TransPend-
                LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency
L0 <64ns, L1 <1us
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
                LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-,
Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -3.5dB
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1
Len=010 <?>
        Capabilities: [150 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap+ ChkEn-
        Kernel modules: radeon

Tried to bisect this but the results were pointing to drm/i915 commits between
3.10 and 3.11rc2 so I guess I did something wrong. Will try again later.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2013-10-14 10:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 10:53 bugzilla-daemon [this message]
2013-10-14 16:15 ` [Bug 63011] radeon: horizontal stripes when updating screen bugzilla-daemon
2013-10-14 16:23 ` bugzilla-daemon
2013-10-14 16:31 ` bugzilla-daemon
2013-10-15 15:47 ` bugzilla-daemon
2013-10-15 16:13 ` bugzilla-daemon
2013-10-15 18:10 ` bugzilla-daemon
2013-10-16  6:45 ` bugzilla-daemon
2013-10-16 15:18 ` bugzilla-daemon
2013-10-16 15:20 ` bugzilla-daemon
2013-10-16 15:29 ` bugzilla-daemon
2013-10-16 15:37 ` bugzilla-daemon
2013-10-16 15:38 ` bugzilla-daemon
2013-10-16 16:31 ` bugzilla-daemon
2017-08-28  6:49 ` bugzilla-daemon

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-63011-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.