Hello,
3.4 breaks rendering on my Radeon evergreen card. Immediately after
logging in into the desktop, I get the following errors in the kernel
log:
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
575)
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
surf: (192 192) (0 4 1 0 0 0 0)
radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
575)
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
surf: (192 192) (0 4 1 0 0 0 0)
radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
small (layer size 798720, offset 0, max layer 1, bo size 794624, slice
3119)
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
surf: (384 520) (0 4 1 0 0 0 0)
radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
small (layer size 458752, offset 0, max layer 1, bo size 446464, slice
1791)
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
surf: (512 224) (0 4 1 0 0 0 0)
radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 7170
[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
small (layer size 798720, offset 0, max layer 1, bo size 790528, slice
3119)
radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
surf: (384 520) (0 4 1 0 0 0 0)
radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
Meanwhile, windows on the desktop are rendered incorrectly (with
certain regions covered by strange patterns or smudged) or not at all.
This makes the desktop unusable.
I can always reproduce this problem on 3.4
Kernels prior to 3.4 work fine.
I will try and find the time to bisect this issue but meanwhile here
are some further details:
Output of lspci -v
--------------------------
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
Kernel modules: intel-agp
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16
Root Port (rev 18) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fbe00000-fbefffff
Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0, IRQ 48
Memory at fbf09000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel driver in use: mei
Kernel modules: mei
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI])
Subsystem: Dell Device 0447
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at fbf08000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at fbf00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=11, subordinate=11, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: d1800000-d19fffff
Prefetchable memory behind bridge: 00000000d1a00000-00000000d1bfffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=12, subordinate=12, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: fbd00000-fbdfffff
Prefetchable memory behind bridge: 00000000d1600000-00000000d17fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 3 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=13, subordinate=13, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fb300000-fbcfffff
Prefetchable memory behind bridge: 00000000d0c00000-00000000d15fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=15, subordinate=15, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fa900000-fb2fffff
Prefetchable memory behind bridge: 00000000d0100000-00000000d0afffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI])
Subsystem: Dell Device 0447
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at fbf07000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
(prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=20, subordinate=20, sec-latency=32
Capabilities: <access denied>
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
Subsystem: Dell Device 0447
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
Kernel modules: iTCO_wdt
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series
Chipset 6 port SATA AHCI Controller (rev 06) (prog-if 01 [AHCI 1.0])
Subsystem: Dell Device 0447
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 46
I/O ports at f070 [size=8]
I/O ports at f060 [size=4]
I/O ports at f050 [size=8]
I/O ports at f040 [size=4]
I/O ports at f020 [size=32]
Memory at fbf06000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
Subsystem: Dell Device 0447
Flags: medium devsel, IRQ 3
Memory at fbf05000 (64-bit, non-prefetchable) [size=256]
I/O ports at f000 [size=32]
Kernel modules: i2c-i801
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400
Series Chipset Thermal Subsystem (rev 06)
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at fbf04000 (64-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: intel ips
Kernel modules: intel_ips
01:00.0 VGA compatible controller: ATI Technologies Inc Redwood
[Radeon HD 5600 Series] (prog-if 00 [VGA controller])
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at fbe20000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at fbe00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
01:00.1 Audio device: ATI Technologies Inc Redwood HDMI Audio [Radeon
HD 5600 Series]
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0, IRQ 51
Memory at fbe40000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel
12:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
Flags: bus master, fast devsel, latency 0, IRQ 49
Memory at fbd00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
13:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0, IRQ 45
I/O ports at d000 [size=256]
Memory at d0c10000 (64-bit, prefetchable) [size=4K]
Memory at d0c00000 (64-bit, prefetchable) [size=64K]
Expansion ROM at fb300000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-core Registers (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
First stable kernel version exhibiting the problem
----------------------------------------------------------------------------
3.4.0 (From kernel.org)
Distribution
--------------------
Ubuntu 11.04
Xorg Packages/ Drivers
-------------------------------------
ii xorg 1:7.6+4ubuntu3.2
X.Org X Window System
ii xorg-docs-core 1:1.5.99.901-1ubuntu1
Core documentation for the X.org X
Window System
ii xorg-sgml-doctools 1:1.6-1
Common tools for building X.Org SGML
documentation
ii xserver-xorg 1:7.6+4ubuntu3.2
the X.Org X server
ii xserver-xorg-core 2:1.10.1-1ubuntu1.3
Xorg X server - core server
ii xserver-xorg-core-dbg 2:1.10.1-1ubuntu1.3
Xorg - the X.Org X server (debugging
symbols)
ii xserver-xorg-input-all 1:7.6+4ubuntu3.2
the X.Org X server -- input driver
metapackage
ii xserver-xorg-input-evdev 1:2.6.0-1ubuntu12
X.Org X server -- evdev input driver
ii xserver-xorg-input-mouse 1:1.6.0-1ubuntu3
X.Org X server -- mouse input driver
ii xserver-xorg-input-synaptics
1.3.99+git20110116.0e27ce3a-0ubuntu12.1 Synaptics
TouchPad driver for X.Org server
ii xserver-xorg-input-vmmouse 1:12.6.99.901-1ubuntu2
X.Org X server -- VMMouse input
driver to use with VMWare
ii xserver-xorg-input-wacom 1:0.10.11-0ubuntu4
X.Org X server -- Wacom input driver
ii xserver-xorg-video-all 1:7.6+4ubuntu3.2
the X.Org X server -- output driver
metapackage
ii xserver-xorg-video-apm 1:1.2.3-0ubuntu5
X.Org X server -- APM display driver
ii xserver-xorg-video-ark 1:0.7.3-1ubuntu3
X.Org X server -- ark display driver
ii xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1
X.Org X server -- AMD/ATI display
driver wrapper
ii xserver-xorg-video-chips 1:1.2.3-2ubuntu5
X.Org X server -- Chips display
driver
ii xserver-xorg-video-cirrus 1:1.3.2-2ubuntu7
X.Org X server -- Cirrus display
driver
ii xserver-xorg-video-fbdev 1:0.4.2-3ubuntu6
X.Org X server -- fbdev display
driver
ii xserver-xorg-video-i128 1:1.3.4-1ubuntu3
X.Org X server -- i128 display driver
ii xserver-xorg-video-intel 2:2.14.0-4ubuntu7.3
X.Org X server -- Intel i8xx, i9xx
display driver
ii xserver-xorg-video-mach64
6.8.2+git20101202.d60087f0-4ubuntu3 X.Org X
server -- ATI Mach64 display driver
ii xserver-xorg-video-mga 1:1.4.13.dfsg-3build1
X.Org X server -- MGA display driver
ii xserver-xorg-video-neomagic 1:1.2.5-1ubuntu3
X.Org X server -- Neomagic display
driver
ii xserver-xorg-video-nouveau
1:0.0.16+git20110107+b795ca6e-0ubuntu7 X.Org X
server -- Nouveau display driver (experimental)
ii xserver-xorg-video-openchrome 1:0.2.904+svn916-1build1
X.Org X server -- VIA display driver
ii xserver-xorg-video-qxl 0.0.12-1ubuntu4
X.Org X server -- QXL display driver
ii xserver-xorg-video-r128 6.8.1-4ubuntu3
X.Org X server -- ATI r128 display
driver
ii xserver-xorg-video-radeon 1:6.14.0-0ubuntu4.1
X.Org X server -- AMD/ATI Radeon
display driver
ii xserver-xorg-video-radeon-dbg 1:6.14.0-0ubuntu4.1
X.Org X server -- AMD/ATI Radeon
display driver (debugging symbols)
Full dmesg output
-----------------------------
Please see attached.
'Please let me know if I should provide further details.
Thanks!
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Sun, Jun 3, 2012 at 8:26 PM, Brian Gitonga Marete <[email protected]> wrote:
> Hello,
>
> 3.4 breaks rendering on my Radeon evergreen card. Immediately after
> logging in into the desktop, I get the following errors in the kernel
> log:
I should add that I have nothing in my xorg.conf. In fact, it doesn't
exist on my system.
Thanks!
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Sun, Jun 3, 2012 at 8:26 PM, Brian Gitonga Marete <[email protected]> wrote:
> Hello,
>
> 3.4 breaks rendering on my Radeon evergreen card. Immediately after
> logging in into the desktop, I get the following errors in the kernel
> log:
>
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
> small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
> 575)
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
> surf: (192 192) (0 4 1 0 0 0 0)
> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
> small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
> 575)
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
> surf: (192 192) (0 4 1 0 0 0 0)
> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
> small (layer size 798720, offset 0, max layer 1, bo size 794624, slice
> 3119)
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
> surf: (384 520) (0 4 1 0 0 0 0)
> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
> small (layer size 458752, offset 0, max layer 1, bo size 446464, slice
> 1791)
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
> surf: (512 224) (0 4 1 0 0 0 0)
> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 7170
> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
> small (layer size 798720, offset 0, max layer 1, bo size 790528, slice
> 3119)
> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
> surf: (384 520) (0 4 1 0 0 0 0)
> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>
> Meanwhile, windows on the desktop are rendered incorrectly (with
> certain regions covered by strange patterns or smudged) or not at all.
> This makes the desktop unusable.
>
> I can always reproduce this problem on 3.4
>
> Kernels prior to 3.4 work fine.
>
> I will try and find the time to bisect this issue but meanwhile here
> are some further details:
>
I have git-bisected this to find that the first bad commit is:
285484e2d55 - drm/radeon: add support for evergreen/ni tiling
informations v11.
So I have also added Jerome to the CC list. Please see the attached
bisect.log for the git-bisect log.
Once again, my card is:
01:00.0 VGA compatible controller: ATI Technologies Inc Redwood
[Radeon HD 5600 Series] (prog-if 00 [VGA controller])
Subsystem: Dell Device 0447
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at fbe20000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at fbe00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
To reproduce, simply:
1. Install Ubuntu 11.04 on a system with the above Radeon card (In
order to get the version of Xorg and DRM libs that I have)
2. Boot and login.
The problem manifests upon login, presumably on that start of Compiz
but I am not sure.
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Thu, Jun 7, 2012 at 1:59 AM, Brian Gitonga Marete <[email protected]> wrote:
> On Sun, Jun 3, 2012 at 8:26 PM, Brian Gitonga Marete <[email protected]> wrote:
>> Hello,
>>
>> 3.4 breaks rendering on my Radeon evergreen card. Immediately after
>> logging in into the desktop, I get the following errors in the kernel
>> log:
>>
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>> small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
>> 575)
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>> surf: (192 192) (0 4 1 0 0 0 0)
>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>> small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
>> 575)
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>> surf: (192 192) (0 4 1 0 0 0 0)
>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>> small (layer size 798720, offset 0, max layer 1, bo size 794624, slice
>> 3119)
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>> surf: (384 520) (0 4 1 0 0 0 0)
>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>> small (layer size 458752, offset 0, max layer 1, bo size 446464, slice
>> 1791)
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>> surf: (512 224) (0 4 1 0 0 0 0)
>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 7170
>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>> small (layer size 798720, offset 0, max layer 1, bo size 790528, slice
>> 3119)
>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>> surf: (384 520) (0 4 1 0 0 0 0)
>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>>
>> Meanwhile, windows on the desktop are rendered incorrectly (with
>> certain regions covered by strange patterns or smudged) or not at all.
>> This makes the desktop unusable.
>>
>> I can always reproduce this problem on 3.4
>>
>> Kernels prior to 3.4 work fine.
>>
>> I will try and find the time to bisect this issue but meanwhile here
>> are some further details:
>>
>
> I have git-bisected this to find that the first bad commit is:
> 285484e2d55 - drm/radeon: add support for evergreen/ni tiling
> informations v11.
>
> So I have also added Jerome to the CC list. Please see the attached
> bisect.log for the git-bisect log.
Sorry, forgot to attach. Now attached.
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Wed, Jun 6, 2012 at 7:01 PM, Brian Gitonga Marete <[email protected]> wrote:
> On Thu, Jun 7, 2012 at 1:59 AM, Brian Gitonga Marete <[email protected]> wrote:
>> On Sun, Jun 3, 2012 at 8:26 PM, Brian Gitonga Marete <[email protected]> wrote:
>>> Hello,
>>>
>>> 3.4 breaks rendering on my Radeon evergreen card. Immediately after
>>> logging in into the desktop, I get the following errors in the kernel
>>> log:
>>>
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>>> small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
>>> 575)
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>>> surf: (192 192) (0 4 1 0 0 0 0)
>>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>>> small (layer size 147456, offset 0, max layer 1, bo size 143360, slice
>>> 575)
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>>> surf: (192 192) (0 4 1 0 0 0 0)
>>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>>> small (layer size 798720, offset 0, max layer 1, bo size 794624, slice
>>> 3119)
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>>> surf: (384 520) (0 4 1 0 0 0 0)
>>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>>> small (layer size 458752, offset 0, max layer 1, bo size 446464, slice
>>> 1791)
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>>> surf: (512 224) (0 4 1 0 0 0 0)
>>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 7170
>>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:439 cb[0] bo too
>>> small (layer size 798720, offset 0, max layer 1, bo size 790528, slice
>>> 3119)
>>> radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 problematic
>>> surf: (384 520) (0 4 1 0 0 0 0)
>>> radeon 0000:01:00.0: evergreen_packet3_check:2055 invalid cmd stream 461
>>> [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>>>
>>> Meanwhile, windows on the desktop are rendered incorrectly (with
>>> certain regions covered by strange patterns or smudged) or not at all.
>>> This makes the desktop unusable.
>>>
>>> I can always reproduce this problem on 3.4
>>>
>>> Kernels prior to 3.4 work fine.
>>>
>>> I will try and find the time to bisect this issue but meanwhile here
>>> are some further details:
>>>
>>
>> I have git-bisected this to find that the first bad commit is:
>> 285484e2d55 - drm/radeon: add support for evergreen/ni tiling
>> informations v11.
>>
>> So I have also added Jerome to the CC list. Please see the attached
>> bisect.log for the git-bisect log.
>
> Sorry, forgot to attach. Now attached.
>
> --
> Brian Gitonga Marete
> Toshnix Systems - http://toshnix.com
Update your libdrm to libdrm from git should fix your issue.
Cheers,
Jerome
On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
> Update your libdrm to libdrm from git should fix your issue.
Thanks Jerome. Will try that and report back promptly.
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
> Update your libdrm to libdrm from git should fix your issue.
That's unfortunate -- it means a kernel change breaks working userspace?
On Thu, Jun 7, 2012 at 11:35 AM, Roland Dreier <[email protected]> wrote:
>> Update your libdrm to libdrm from git should fix your issue.
>
> That's unfortunate -- it means a kernel change breaks working userspace?
Yes and no, welcome to GPU world. So this patch is suppose to report
some GPU informations to userspace, sadly on some GPU we report wrong
informations (that's a bug). So solution is to fix kernel to report
right information, i think the following patch does that.
http://www.mail-archive.com/[email protected]/msg09247.html
The no side, is to have it broken you also need to have upgraded your
libdrm, ie old libdrm/radeon with this kernel will work as previously.
This issue have been fix recently in libdrm :
http://cgit.freedesktop.org/mesa/drm/commit/?id=c2b77a02d4e188cfa6d1b73a721946fd9b1d3577
Of course here i am assuming that the bug Brian is experiencing is
related to wrong tile infos reporting.
Cheers,
Jerome
On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>
> Update your libdrm to libdrm from git should fix your issue.
Hello Jerome,
Thanks for looking into this.
I am afraid that even with the very latest libdrm (git 93a5117d), the
rendering is still broken.
What else should I try? I would revert the patch that git-bisect
fingered (your patch, git 285484e2d, Linux mainline) but there are
merge problems when I try to do that, which I have not yet looked
into. Perhaps you can see if you can help me revert that patch so that
we can see if the problem then goes away?
Thanks!
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>
>> Update your libdrm to libdrm from git should fix your issue.
>
> Hello Jerome,
>
> Thanks for looking into this.
>
> I am afraid that even with the very latest libdrm (git 93a5117d), the
> rendering is still broken.
>
> What else should I try? I would revert the patch that git-bisect
> fingered (your patch, git 285484e2d, Linux mainline) but there are
> merge problems when I try to do that, which I have not yet looked
> into. Perhaps you can see if you can help me revert that patch so that
> we can see if the problem then goes away?
>
> Thanks!
>
> --
> Brian Gitonga Marete
> Toshnix Systems - http://toshnix.com
What happen if you upgrade to xf86-video-ati from git ?
Cheers,
Jerome
On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
> What happen if you upgrade to xf86-video-ati from git ?
>
Had actually just though of that and cloned it :) Will try and report.
Thanks!
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Thu, Jun 7, 2012 at 4:22 PM, Brian Gitonga Marete <[email protected]> wrote:
> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>> What happen if you upgrade to xf86-video-ati from git ?
>>
>
> Had actually just though of that and cloned it :) Will try and report.
>
> Thanks!
>
> --
> Brian Gitonga Marete
> Toshnix Systems - http://toshnix.com
If it works please also give me mesa version, and am i right assuming
you are using unity ? Is this a stock ubuntu 12 installation (ie not
custome package) ?
Cheers,
Jerome
On Thu, Jun 7, 2012 at 11:23 PM, Jerome Glisse <[email protected]> wrote:
> On Thu, Jun 7, 2012 at 4:22 PM, Brian Gitonga Marete <[email protected]> wrote:
>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>> What happen if you upgrade to xf86-video-ati from git ?
>>>
>>
>> Had actually just though of that and cloned it :) Will try and report.
>>
>> Thanks!
>>
>> --
>> Brian Gitonga Marete
>> Toshnix Systems - http://toshnix.com
>
> If it works please also give me mesa version, and am i right assuming
> you are using unity ? Is this a stock ubuntu 12 installation (ie not
> custome package) ?
>
These are stock Ubuntu 11.04 Xorg/drm/mesa packages. I am using Ubuntu
in the _classic_ mode, not in the usual Unity mode.
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Thu, Jun 7, 2012 at 11:26 PM, Brian Gitonga Marete
<[email protected]> wrote:
> On Thu, Jun 7, 2012 at 11:23 PM, Jerome Glisse <[email protected]> wrote:
>> On Thu, Jun 7, 2012 at 4:22 PM, Brian Gitonga Marete <[email protected]> wrote:
>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>>
>>>
>>> Had actually just though of that and cloned it :) Will try and report.
>>>
>>> Thanks!
>>>
>>> --
>>> Brian Gitonga Marete
>>> Toshnix Systems - http://toshnix.com
>>
>> If it works please also give me mesa version, and am i right assuming
>> you are using unity ? Is this a stock ubuntu 12 installation (ie not
>> custome package) ?
>>
>
> These are stock Ubuntu 11.04 Xorg/drm/mesa packages. I am using Ubuntu
> in the _classic_ mode, not in the usual Unity mode.
>
By stock, I mean they are the official _and_ fully updated Ubuntu
11.04 packages.
Will compile the git radeon drivers and test. Thanks!
BGM.
On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>
>>> Update your libdrm to libdrm from git should fix your issue.
>>
>> Hello Jerome,
>>
>> Thanks for looking into this.
>>
>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>> rendering is still broken.
>>
>> What else should I try? I would revert the patch that git-bisect
>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>> merge problems when I try to do that, which I have not yet looked
>> into. Perhaps you can see if you can help me revert that patch so that
>> we can see if the problem then goes away?
>>
> What happen if you upgrade to xf86-video-ati from git ?
Hello Jerome,
Once again, thanks a lot for your help.
Some progress but also a setback: Upgrading to the latest
xf86-video-ati git gets rid of the stream command failures - No more
error messages in dmesg(8). But then, now, rendering is completely
messed up. Previously, it was mostly the window boundaries that were
blurred/messed but now also entire windows and text so that you can't
read anything from the desktop. (For example, the previous render
problems would still allow me to use gnome-terminal even though its
frames were completely blurred. Now the text withing gnome-terminal is
also blurred/smudged)
Do you recommend that I also try to upgrade Mesa? (I have to solve a
gl-proto library dependency before I can do that.) Or perhaps rebuild
Compiz itself against the new libdrm and xf86-video-ati? What do you
recommend?
On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
<[email protected]> wrote:
> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>
>>>> Update your libdrm to libdrm from git should fix your issue.
>>>
>>> Hello Jerome,
>>>
>>> Thanks for looking into this.
>>>
>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>> rendering is still broken.
>>>
>>> What else should I try? I would revert the patch that git-bisect
>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>> merge problems when I try to do that, which I have not yet looked
>>> into. Perhaps you can see if you can help me revert that patch so that
>>> we can see if the problem then goes away?
>>>
>> What happen if you upgrade to xf86-video-ati from git ?
>
> Hello Jerome,
>
> Once again, thanks a lot for your help.
>
> Some progress but also a setback: Upgrading to the latest
> xf86-video-ati git gets rid of the stream command failures - No more
> error messages in dmesg(8). But then, now, rendering is completely
> messed up. Previously, it was mostly the window boundaries that were
> blurred/messed but now also entire windows and text so that you can't
> read anything from the desktop. (For example, the previous render
> problems would still allow me to use gnome-terminal even though its
> frames were completely blurred. Now the text withing gnome-terminal is
> also blurred/smudged)
>
I should add that in this case rendering is completely messed up in
_both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
upon upgrading to the latext xf86-video-ati git HEAD.
Thanks.
On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
<[email protected]> wrote:
> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
> <[email protected]> wrote:
>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>
>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>
>>>> Hello Jerome,
>>>>
>>>> Thanks for looking into this.
>>>>
>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>> rendering is still broken.
>>>>
>>>> What else should I try? I would revert the patch that git-bisect
>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>> merge problems when I try to do that, which I have not yet looked
>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>> we can see if the problem then goes away?
>>>>
>>> What happen if you upgrade to xf86-video-ati from git ?
>>
>> Hello Jerome,
>>
>> Once again, thanks a lot for your help.
>>
>> Some progress but also a setback: Upgrading to the latest
>> xf86-video-ati git gets rid of the stream command failures - No more
>> error messages in dmesg(8). But then, now, rendering is completely
>> messed up. Previously, it was mostly the window boundaries that were
>> blurred/messed but now also entire windows and text so that you can't
>> read anything from the desktop. (For example, the previous render
>> problems would still allow me to use gnome-terminal even though its
>> frames were completely blurred. Now the text withing gnome-terminal is
>> also blurred/smudged)
>>
>
> I should add that in this case rendering is completely messed up in
> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
> upon upgrading to the latext xf86-video-ati git HEAD.
Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
latest git. Jerome, many thanks for your help on this!
So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
distributions released around the same time) is fixed by:
a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
c) Upgrade mesa to latest GIT as of this writing (529476b)
Now kernel 3.4 works on my laptop.
Thanks!
BGM.
On Fri, Jun 8, 2012 at 6:13 AM, Brian Gitonga Marete <[email protected]> wrote:
> On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
> <[email protected]> wrote:
>> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
>> <[email protected]> wrote:
>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>
>>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>>
>>>>> Hello Jerome,
>>>>>
>>>>> Thanks for looking into this.
>>>>>
>>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>>> rendering is still broken.
>>>>>
>>>>> What else should I try? I would revert the patch that git-bisect
>>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>>> merge problems when I try to do that, which I have not yet looked
>>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>>> we can see if the problem then goes away?
>>>>>
>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>
>>> Hello Jerome,
>>>
>>> Once again, thanks a lot for your help.
>>>
>>> Some progress but also a setback: Upgrading to the latest
>>> xf86-video-ati git gets rid of the stream command failures - No more
>>> error messages in dmesg(8). But then, now, rendering is completely
>>> messed up. Previously, it was mostly the window boundaries that were
>>> blurred/messed but now also entire windows and text so that you can't
>>> read anything from the desktop. (For example, the previous render
>>> problems would still allow me to use gnome-terminal even though its
>>> frames were completely blurred. Now the text withing gnome-terminal is
>>> also blurred/smudged)
>>>
>>
>> I should add that in this case rendering is completely messed up in
>> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
>> upon upgrading to the latext xf86-video-ati git HEAD.
>
> Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
> latest git. Jerome, many thanks for your help on this!
>
> So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
> distributions released around the same time) is fixed by:
>
> a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
> b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
> c) Upgrade mesa to latest GIT as of this writing (529476b)
>
> Now kernel 3.4 works on my laptop.
>
> Thanks!
>
> BGM.
Well i still need to find out what's wrong with 6.14.0, what your
screen resolution ?
Cheers,
Jerome
On Fri, Jun 8, 2012 at 6:13 AM, Brian Gitonga Marete <[email protected]> wrote:
> On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
> <[email protected]> wrote:
>> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
>> <[email protected]> wrote:
>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>
>>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>>
>>>>> Hello Jerome,
>>>>>
>>>>> Thanks for looking into this.
>>>>>
>>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>>> rendering is still broken.
>>>>>
>>>>> What else should I try? I would revert the patch that git-bisect
>>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>>> merge problems when I try to do that, which I have not yet looked
>>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>>> we can see if the problem then goes away?
>>>>>
>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>
>>> Hello Jerome,
>>>
>>> Once again, thanks a lot for your help.
>>>
>>> Some progress but also a setback: Upgrading to the latest
>>> xf86-video-ati git gets rid of the stream command failures - No more
>>> error messages in dmesg(8). But then, now, rendering is completely
>>> messed up. Previously, it was mostly the window boundaries that were
>>> blurred/messed but now also entire windows and text so that you can't
>>> read anything from the desktop. (For example, the previous render
>>> problems would still allow me to use gnome-terminal even though its
>>> frames were completely blurred. Now the text withing gnome-terminal is
>>> also blurred/smudged)
>>>
>>
>> I should add that in this case rendering is completely messed up in
>> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
>> upon upgrading to the latext xf86-video-ati git HEAD.
>
> Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
> latest git. Jerome, many thanks for your help on this!
>
> So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
> distributions released around the same time) is fixed by:
>
> a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
> b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
> c) Upgrade mesa to latest GIT as of this writing (529476b)
>
> Now kernel 3.4 works on my laptop.
>
> Thanks!
>
> BGM.
Brian can you please test patch below on 6.14.0 ddx and old mesa (ie
revert to ubuntu mesa & ddx) and report if it fix your issue. Thanks
http://people.freedesktop.org/~glisse/0001-drm-radeon-fix-tiling-and-command-stream-checking-on.patch
Cheers,
Jerome
On Fri, Jun 8, 2012 at 3:56 PM, Jerome Glisse <[email protected]> wrote:
> On Fri, Jun 8, 2012 at 6:13 AM, Brian Gitonga Marete <[email protected]> wrote:
>> On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
>> <[email protected]> wrote:
>>> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
>>> <[email protected]> wrote:
>>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>>
>>>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>>>
>>>>>> Hello Jerome,
>>>>>>
>>>>>> Thanks for looking into this.
>>>>>>
>>>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>>>> rendering is still broken.
>>>>>>
>>>>>> What else should I try? I would revert the patch that git-bisect
>>>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>>>> merge problems when I try to do that, which I have not yet looked
>>>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>>>> we can see if the problem then goes away?
>>>>>>
>>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>>
>>>> Hello Jerome,
>>>>
>>>> Once again, thanks a lot for your help.
>>>>
>>>> Some progress but also a setback: Upgrading to the latest
>>>> xf86-video-ati git gets rid of the stream command failures - No more
>>>> error messages in dmesg(8). But then, now, rendering is completely
>>>> messed up. Previously, it was mostly the window boundaries that were
>>>> blurred/messed but now also entire windows and text so that you can't
>>>> read anything from the desktop. (For example, the previous render
>>>> problems would still allow me to use gnome-terminal even though its
>>>> frames were completely blurred. Now the text withing gnome-terminal is
>>>> also blurred/smudged)
>>>>
>>>
>>> I should add that in this case rendering is completely messed up in
>>> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
>>> upon upgrading to the latext xf86-video-ati git HEAD.
>>
>> Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
>> latest git. Jerome, many thanks for your help on this!
>>
>> So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
>> distributions released around the same time) is fixed by:
>>
>> a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
>> b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
>> c) Upgrade mesa to latest GIT as of this writing (529476b)
>>
>> Now kernel 3.4 works on my laptop.
>>
>> Thanks!
>>
>> BGM.
>
> Brian can you please test patch below on 6.14.0 ddx and old mesa (ie
> revert to ubuntu mesa & ddx) and report if it fix your issue. Thanks
>
> http://people.freedesktop.org/~glisse/0001-drm-radeon-fix-tiling-and-command-stream-checking-on.patch
>
> Cheers,
> Jerome
Patch is against 3.5 but should apply on 3.4 too.
Cheers,
Jerome
On Fri, Jun 8, 2012 at 5:51 PM, Jerome Glisse <[email protected]> wrote:
> On Fri, Jun 8, 2012 at 6:13 AM, Brian Gitonga Marete <[email protected]> wrote:
>> On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
>> <[email protected]> wrote:
>>> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
>>> <[email protected]> wrote:
>>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>>
>>>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>>>
>>>>>> Hello Jerome,
>>>>>>
>>>>>> Thanks for looking into this.
>>>>>>
>>>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>>>> rendering is still broken.
>>>>>>
>>>>>> What else should I try? I would revert the patch that git-bisect
>>>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>>>> merge problems when I try to do that, which I have not yet looked
>>>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>>>> we can see if the problem then goes away?
>>>>>>
>>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>>
>>>> Hello Jerome,
>>>>
>>>> Once again, thanks a lot for your help.
>>>>
>>>> Some progress but also a setback: Upgrading to the latest
>>>> xf86-video-ati git gets rid of the stream command failures - No more
>>>> error messages in dmesg(8). But then, now, rendering is completely
>>>> messed up. Previously, it was mostly the window boundaries that were
>>>> blurred/messed but now also entire windows and text so that you can't
>>>> read anything from the desktop. (For example, the previous render
>>>> problems would still allow me to use gnome-terminal even though its
>>>> frames were completely blurred. Now the text withing gnome-terminal is
>>>> also blurred/smudged)
>>>>
>>>
>>> I should add that in this case rendering is completely messed up in
>>> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
>>> upon upgrading to the latext xf86-video-ati git HEAD.
>>
>> Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
>> latest git. Jerome, many thanks for your help on this!
>>
>> So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
>> distributions released around the same time) is fixed by:
>>
>> a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
>> b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
>> c) Upgrade mesa to latest GIT as of this writing (529476b)
>>
>> Now kernel 3.4 works on my laptop.
>>
>> Thanks!
>>
>> BGM.
>
> Well i still need to find out what's wrong with 6.14.0, what your
> screen resolution ?
1366 x 768. I am happy to run whatever tests you would like to debug.
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Fri, Jun 8, 2012 at 10:56 PM, Jerome Glisse <[email protected]> wrote:
> On Fri, Jun 8, 2012 at 6:13 AM, Brian Gitonga Marete <[email protected]> wrote:
>> On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
>> <[email protected]> wrote:
>>> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
>>> <[email protected]> wrote:
>>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>>
>>>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>>>
>>>>>> Hello Jerome,
>>>>>>
>>>>>> Thanks for looking into this.
>>>>>>
>>>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>>>> rendering is still broken.
>>>>>>
>>>>>> What else should I try? I would revert the patch that git-bisect
>>>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>>>> merge problems when I try to do that, which I have not yet looked
>>>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>>>> we can see if the problem then goes away?
>>>>>>
>>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>>
>>>> Hello Jerome,
>>>>
>>>> Once again, thanks a lot for your help.
>>>>
>>>> Some progress but also a setback: Upgrading to the latest
>>>> xf86-video-ati git gets rid of the stream command failures - No more
>>>> error messages in dmesg(8). But then, now, rendering is completely
>>>> messed up. Previously, it was mostly the window boundaries that were
>>>> blurred/messed but now also entire windows and text so that you can't
>>>> read anything from the desktop. (For example, the previous render
>>>> problems would still allow me to use gnome-terminal even though its
>>>> frames were completely blurred. Now the text withing gnome-terminal is
>>>> also blurred/smudged)
>>>>
>>>
>>> I should add that in this case rendering is completely messed up in
>>> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
>>> upon upgrading to the latext xf86-video-ati git HEAD.
>>
>> Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
>> latest git. Jerome, many thanks for your help on this!
>>
>> So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
>> distributions released around the same time) is fixed by:
>>
>> a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
>> b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
>> c) Upgrade mesa to latest GIT as of this writing (529476b)
>>
>> Now kernel 3.4 works on my laptop.
>>
>> Thanks!
>>
>> BGM.
>
> Brian can you please test patch below on 6.14.0 ddx and old mesa (ie
> revert to ubuntu mesa & ddx) and report if it fix your issue. Thanks
>
> http://people.freedesktop.org/~glisse/0001-drm-radeon-fix-tiling-and-command-stream-checking-on.patch
>
OK. Will test and report back. Thanks!
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Fri, Jun 8, 2012 at 4:28 PM, Brian Gitonga Marete <[email protected]> wrote:
> On Fri, Jun 8, 2012 at 10:56 PM, Jerome Glisse <[email protected]> wrote:
>> On Fri, Jun 8, 2012 at 6:13 AM, Brian Gitonga Marete <[email protected]> wrote:
>>> On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
>>> <[email protected]> wrote:
>>>> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
>>>> <[email protected]> wrote:
>>>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>>>
>>>>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>>>>
>>>>>>> Hello Jerome,
>>>>>>>
>>>>>>> Thanks for looking into this.
>>>>>>>
>>>>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>>>>> rendering is still broken.
>>>>>>>
>>>>>>> What else should I try? I would revert the patch that git-bisect
>>>>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>>>>> merge problems when I try to do that, which I have not yet looked
>>>>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>>>>> we can see if the problem then goes away?
>>>>>>>
>>>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>>>
>>>>> Hello Jerome,
>>>>>
>>>>> Once again, thanks a lot for your help.
>>>>>
>>>>> Some progress but also a setback: Upgrading to the latest
>>>>> xf86-video-ati git gets rid of the stream command failures - No more
>>>>> error messages in dmesg(8). But then, now, rendering is completely
>>>>> messed up. Previously, it was mostly the window boundaries that were
>>>>> blurred/messed but now also entire windows and text so that you can't
>>>>> read anything from the desktop. (For example, the previous render
>>>>> problems would still allow me to use gnome-terminal even though its
>>>>> frames were completely blurred. Now the text withing gnome-terminal is
>>>>> also blurred/smudged)
>>>>>
>>>>
>>>> I should add that in this case rendering is completely messed up in
>>>> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
>>>> upon upgrading to the latext xf86-video-ati git HEAD.
>>>
>>> Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
>>> latest git. Jerome, many thanks for your help on this!
>>>
>>> So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
>>> distributions released around the same time) is fixed by:
>>>
>>> a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
>>> b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
>>> c) Upgrade mesa to latest GIT as of this writing (529476b)
>>>
>>> Now kernel 3.4 works on my laptop.
>>>
>>> Thanks!
>>>
>>> BGM.
>>
>> Brian can you please test patch below on 6.14.0 ddx and old mesa (ie
>> revert to ubuntu mesa & ddx) and report if it fix your issue. Thanks
>>
>> http://people.freedesktop.org/~glisse/0001-drm-radeon-fix-tiling-and-command-stream-checking-on.patch
>>
> ?OK. Will test and report back. Thanks!
>
> --
> Brian Gitonga Marete
> Toshnix Systems - http://toshnix.com
I uploaded a v3 version same url, the v2 won't work for you. v3 should
work (at least according to my local testing with same gpu as you and
same use case)
Cheers,
Jerome
On Fri, Jun 8, 2012 at 11:43 PM, Jerome Glisse <[email protected]> wrote:
> On Fri, Jun 8, 2012 at 4:28 PM, Brian Gitonga Marete <[email protected]> wrote:
>> On Fri, Jun 8, 2012 at 10:56 PM, Jerome Glisse <[email protected]> wrote:
>>> On Fri, Jun 8, 2012 at 6:13 AM, Brian Gitonga Marete <[email protected]> wrote:
>>>> On Fri, Jun 8, 2012 at 12:56 AM, Brian Gitonga Marete
>>>> <[email protected]> wrote:
>>>>> On Fri, Jun 8, 2012 at 12:44 AM, Brian Gitonga Marete
>>>>> <[email protected]> wrote:
>>>>>> On Thu, Jun 7, 2012 at 11:20 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>> On Thu, Jun 7, 2012 at 3:59 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>>>>>> On Thu, Jun 7, 2012 at 5:25 PM, Jerome Glisse <[email protected]> wrote:
>>>>>>>>>
>>>>>>>>> Update your libdrm to libdrm from git should fix your issue.
>>>>>>>>
>>>>>>>> Hello Jerome,
>>>>>>>>
>>>>>>>> Thanks for looking into this.
>>>>>>>>
>>>>>>>> I am afraid that even with the very latest libdrm (git 93a5117d), the
>>>>>>>> rendering is still broken.
>>>>>>>>
>>>>>>>> What else should I try? I would revert the patch that git-bisect
>>>>>>>> fingered (your patch, git 285484e2d, Linux mainline) but there are
>>>>>>>> merge problems when I try to do that, which I have not yet looked
>>>>>>>> into. Perhaps you can see if you can help me revert that patch so that
>>>>>>>> we can see if the problem then goes away?
>>>>>>>>
>>>>>>> What happen if you upgrade to xf86-video-ati from git ?
>>>>>>
>>>>>> Hello Jerome,
>>>>>>
>>>>>> Once again, thanks a lot for your help.
>>>>>>
>>>>>> Some progress but also a setback: Upgrading to the latest
>>>>>> xf86-video-ati git gets rid of the stream command failures - No more
>>>>>> error messages in dmesg(8). But then, now, rendering is completely
>>>>>> messed up. Previously, it was mostly the window boundaries that were
>>>>>> blurred/messed but now also entire windows and text so that you can't
>>>>>> read anything from the desktop. (For example, the previous render
>>>>>> problems would still allow me to use gnome-terminal even though its
>>>>>> frames were completely blurred. Now the text withing gnome-terminal is
>>>>>> also blurred/smudged)
>>>>>>
>>>>>
>>>>> I should add that in this case rendering is completely messed up in
>>>>> _both_ 3.3.x and 3.4. But the stream command failures in 3.4 go away
>>>>> upon upgrading to the latext xf86-video-ati git HEAD.
>>>>
>>>> Ok. All is fixed in kernel v3.4 if I additionally upgrade Mesa to the
>>>> latest git. Jerome, many thanks for your help on this!
>>>>
>>>> So to summarize, the 3.4 breakage in Ubuntu 11.04 (and probably other
>>>> distributions released around the same time) is fixed by:
>>>>
>>>> a) Upgrade libdrm to latest GIT as of this writing (93a5117d5)
>>>> b) Upgrade xf86-video-ati to latest GIT as of this writing (5888371)
>>>> c) Upgrade mesa to latest GIT as of this writing (529476b)
>>>>
>>>> Now kernel 3.4 works on my laptop.
>>>>
>>>> Thanks!
>>>>
>>>> BGM.
>>>
>>> Brian can you please test patch below on 6.14.0 ddx and old mesa (ie
>>> revert to ubuntu mesa & ddx) and report if it fix your issue. Thanks
>>>
>>> http://people.freedesktop.org/~glisse/0001-drm-radeon-fix-tiling-and-command-stream-checking-on.patch
>>>
>> ?OK. Will test and report back. Thanks!
>>
>> --
>> Brian Gitonga Marete
>> Toshnix Systems - http://toshnix.com
>
> I uploaded a v3 version same url, the v2 won't work for you. v3 should
> work (at least according to my local testing with same gpu as you and
> same use case)
OK. I actually hadn't gotten around to testing yet. Will do so later
today. About libdrm, should I test against git or the Ubuntu version?
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
>
> OK. I actually hadn't gotten around to testing yet. Will do so later
> today. About libdrm, should I test against git or the Ubuntu version?
The Ubuntu version please.
Dave.
On Sat, Jun 9, 2012 at 7:29 PM, Dave Airlie <[email protected]> wrote:
>>
>> OK. I actually hadn't gotten around to testing yet. Will do so later
>> today. About libdrm, should I test against git or the Ubuntu version?
>
> The Ubuntu version please.
OK.Will report results in a couple of hours :)
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Sat, Jun 9, 2012 at 7:33 PM, Brian Gitonga Marete <[email protected]> wrote:
> On Sat, Jun 9, 2012 at 7:29 PM, Dave Airlie <[email protected]> wrote:
>>>
>>> OK. I actually hadn't gotten around to testing yet. Will do so later
>>> today. About libdrm, should I test against git or the Ubuntu version?
>>
>> The Ubuntu version please.
>
> OK.Will report results in a couple of hours :)
Hello. Got around to this after some delay and after applying v3 of
them patch to 3.4, where it applied cleanly, I get this during build:
drivers/gpu/drm/radeon/evergreen_cs.c: In function
?evergreen_cs_track_validate_cb?:
drivers/gpu/drm/radeon/evergreen_cs.c:447:28: error: request for
member ?ptr? in something not a structure or union
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Sun, Jun 10, 2012 at 12:24 PM, Brian Gitonga Marete
<[email protected]> wrote:
> On Sat, Jun 9, 2012 at 7:33 PM, Brian Gitonga Marete <[email protected]> wrote:
>> On Sat, Jun 9, 2012 at 7:29 PM, Dave Airlie <[email protected]> wrote:
>>>>
>>>> OK. I actually hadn't gotten around to testing yet. Will do so later
>>>> today. About libdrm, should I test against git or the Ubuntu version?
>>>
>>> The Ubuntu version please.
>>
>> OK.Will report results in a couple of hours :)
>
> Hello. Got around to this after some delay and after applying v3 of
> them patch to 3.4, where it applied cleanly, I get this during build:
>
> drivers/gpu/drm/radeon/evergreen_cs.c: In function
> ?evergreen_cs_track_validate_cb?:
> drivers/gpu/drm/radeon/evergreen_cs.c:447:28: error: request for
> member ?ptr? in something not a structure or union
Can you change the -> to a . on that line
Dave.
On Sun, Jun 10, 2012 at 5:28 PM, Dave Airlie <[email protected]> wrote:
> On Sun, Jun 10, 2012 at 12:24 PM, Brian Gitonga Marete
> <[email protected]> wrote:
>> On Sat, Jun 9, 2012 at 7:33 PM, Brian Gitonga Marete <[email protected]> wrote:
>>> On Sat, Jun 9, 2012 at 7:29 PM, Dave Airlie <[email protected]> wrote:
>>>>>
>>>>> OK. I actually hadn't gotten around to testing yet. Will do so later
>>>>> today. About libdrm, should I test against git or the Ubuntu version?
>>>>
>>>> The Ubuntu version please.
>>>
>>> OK.Will report results in a couple of hours :)
>>
>> Hello. Got around to this after some delay and after applying v3 of
>> them patch to 3.4, where it applied cleanly, I get this during build:
>>
>> drivers/gpu/drm/radeon/evergreen_cs.c: In function
>> ?evergreen_cs_track_validate_cb?:
>> drivers/gpu/drm/radeon/evergreen_cs.c:447:28: error: request for
>> member ?ptr? in something not a structure or union
>
> Can you change the -> to a . on that line
Actually, the other way around :) Compilation has now passed that
point and will report on test results.
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com
On Sun, Jun 10, 2012 at 9:28 PM, Brian Gitonga Marete
<[email protected]> wrote:
> On Sun, Jun 10, 2012 at 5:28 PM, Dave Airlie <[email protected]> wrote:
>> On Sun, Jun 10, 2012 at 12:24 PM, Brian Gitonga Marete
>> <[email protected]> wrote:
>>> On Sat, Jun 9, 2012 at 7:33 PM, Brian Gitonga Marete <[email protected]> wrote:
>>>> On Sat, Jun 9, 2012 at 7:29 PM, Dave Airlie <[email protected]> wrote:
>>>>>>
>>>>>> OK. I actually hadn't gotten around to testing yet. Will do so later
>>>>>> today. About libdrm, should I test against git or the Ubuntu version?
>>>>>
>>>>> The Ubuntu version please.
>>>>
>>>> OK.Will report results in a couple of hours :)
>>>
>>> Hello. Got around to this after some delay and after applying v3 of
>>> them patch to 3.4, where it applied cleanly, I get this during build:
>>>
>>> drivers/gpu/drm/radeon/evergreen_cs.c: In function
>>> ?evergreen_cs_track_validate_cb?:
>>> drivers/gpu/drm/radeon/evergreen_cs.c:447:28: error: request for
>>> member ?ptr? in something not a structure or union
>>
>> Can you change the -> to a . on that line
>
> Actually, the other way around :) Compilation has now passed that
> point and will report on test results.
>
>
> --
> Brian Gitonga Marete
> Toshnix Systems - http://toshnix.com
Hello. I am happy to report that v3 of Jerome's patch works and fixes
the regressions. I have tested 3.4 with the patch against Ubuntu's
stock drm, radeon and mesa-glx packages.
A quick reminder that the patch needs the small fix detailed in my
exchange with David above.
Thanks very much to Jerome and David!
--
Brian Gitonga Marete
Toshnix Systems - http://toshnix.com