Re: AMD SUMO vs Xorg 7.7

2016-12-05 Thread Michel Dänzer
On 05/12/16 05:19 PM, Alexander Konotop wrote:
> В Mon, 5 Dec 2016 16:39:31 +0900
> Michel Dänzer  пишет:
> 
>> On 03/12/16 12:24 AM, Alexander Konotop wrote:
>>> Here it is.
>>> I think it might be xserver-xorg-video-radeon:amd64 (at line 360).  
>>
>> In the November 25-27 window you mentioned, xserver-xorg-video-radeon
>> was upgraded from 1:7.8.0-1 to 1:7.8.0-1+b1. That's a binary-only NMU,
>> i.e. the same package version was just recompiled against the newer
>> version of xserver-xorg-core, which was upgraded from 2:1.18.4-2 to
>> 2:1.19.0-2. The problem is more likely due to the latter than the former.
>>
>> Can you try confirming this using http://snapshot.debian.org/ ?
> 
> Yes, it looks like +b1 is the only upgrade since mid november.
> I run dist-upgrade quite often, so the same version but without +b1 most 
> likely was installed
> before. The same should be actual for xserver-xorg-core, 2:1.19.0-2 is 
> currently installed.

What I mean is: Can you go back to xserver-xorg-core 2:1.18.4-2 +
xserver-xorg-video-radeon 1:7.8.0-1, and see if the problem occurs with
that combination?


P.S. In the meantime, enabling glamor and DRI3 might avoid the hangs.

-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


Re: AMD SUMO vs Xorg 7.7

2016-12-05 Thread Alexander Konotop
В Mon, 5 Dec 2016 16:39:31 +0900
Michel Dänzer  пишет:

> On 03/12/16 12:24 AM, Alexander Konotop wrote:
> > Here it is.
> > I think it might be xserver-xorg-video-radeon:amd64 (at line 360).  
> 
> In the November 25-27 window you mentioned, xserver-xorg-video-radeon
> was upgraded from 1:7.8.0-1 to 1:7.8.0-1+b1. That's a binary-only NMU,
> i.e. the same package version was just recompiled against the newer
> version of xserver-xorg-core, which was upgraded from 2:1.18.4-2 to
> 2:1.19.0-2. The problem is more likely due to the latter than the former.
> 
> Can you try confirming this using http://snapshot.debian.org/ ?
> 
> 

Yes, it looks like +b1 is the only upgrade since mid november.
I run dist-upgrade quite often, so the same version but without +b1 most likely 
was installed
before. The same should be actual for xserver-xorg-core, 2:1.19.0-2 is 
currently installed.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


Re: AMD SUMO vs Xorg 7.7

2016-12-04 Thread Michel Dänzer
On 03/12/16 12:24 AM, Alexander Konotop wrote:
> Here it is.
> I think it might be xserver-xorg-video-radeon:amd64 (at line 360).

In the November 25-27 window you mentioned, xserver-xorg-video-radeon
was upgraded from 1:7.8.0-1 to 1:7.8.0-1+b1. That's a binary-only NMU,
i.e. the same package version was just recompiled against the newer
version of xserver-xorg-core, which was upgraded from 2:1.18.4-2 to
2:1.19.0-2. The problem is more likely due to the latter than the former.

Can you try confirming this using http://snapshot.debian.org/ ?


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


Re: AMD SUMO vs Xorg 7.7

2016-12-04 Thread Alexander Konotop
Here it is.
I think it might be xserver-xorg-video-radeon:amd64 (at line 360).


В Fri, 2 Dec 2016 17:56:17 +0900
Michel Dänzer  пишет:

> On 02/12/16 05:05 PM, Alexander Konotop wrote:
> > I've attached the log.
> > I tried looking at the Xorg.0.log using "tail -f" while starting a browser 
> > and waiting for it to
> > freeze. Nothing happened, no new messages in Xorg.0.log. As well as in 
> > syslog and dmesg.  
> 
> Let's try to narrow down which package upgrade introduced the problem.
> Your post on https://forum.siduction.org/index.php?topic=6469 talks
> about a /var/log/apt/history.log attachment, but I can't seem to access
> that from there. Can you attach it here?
> 
> 


Start-Date: 2016-11-01  10:44:00
Commandline: apt-get dist-upgrade
Requested-By: alexander (1000)
Install: linux-image-4.8.6-towo.1-siduction-amd64:amd64 (4.8-13, automatic), liblirc-client0:amd64 (0.9.4c-4, automatic)
Upgrade: cryptsetup-bin:amd64 (2:1.7.2-5, 2:1.7.3-1), linux-image-siduction-amd64:amd64 (4.8-12, 4.8-13), bluez:amd64 (5.41-1, 5.43-1), libservlet3.1-java:amd64 (8.0.38-1, 8.0.38-2), git-gui:amd64 (1:2.10.1-1, 1:2.10.2-1), libumfpack5:amd64 (1:4.5.3-1, 1:4.5.3-2), iw:amd64 (3.17-1, 4.7-0.1), libnet-ssleay-perl:amd64 (1.77-1+b1, 1.78-1), linux-libc-dev:amd64 (4.7.8-1, 4.8.5-1), libxml2-utils:amd64 (2.9.4+dfsg1-2, 2.9.4+dfsg1-2.1), git-man:amd64 (1:2.10.1-1, 1:2.10.2-1), whois:amd64 (5.2.12, 5.2.13), grub-common:amd64 (2.02~beta3-1, 2.02~beta3-2), libgd3:amd64 (2.2.3-3+b1, 2.2.3-87-gd0fec80-1), libkmod2:amd64 (22-1.1, 23-1), libmysql-java:amd64 (5.1.39-1, 5.1.40-1), at-spi2-core:amd64 (2.22.0-2, 2.22.0-3), libccolamd2:amd64 (1:4.5.3-1, 1:4.5.3-2), libcgi-pm-perl:amd64 (4.32-1, 4.35-1), git:amd64 (1:2.10.1-1, 1:2.10.2-1), grub2-common:amd64 (2.02~beta3-1, 2.02~beta3-2), xfce4-notifyd:amd64 (0.3.3-1, 0.3.3-2), libsuitesparseconfig4:amd64 (1:4.5.3-1, 1:4.5.3-2), grub-pc:amd64 (2.02~beta3-
 1, 2.02~beta3-2), libamd2:amd64 (1:4.5.3-1, 1:4.5.3-2), kmod:amd64 (22-1.1, 23-1), libnet-smtp-ssl-perl:amd64 (1.03-1, 1.04-1), pandoc:amd64 (1.17.2~dfsg-1+b5, 1.17.2~dfsg-2), grub-pc-bin:amd64 (2.02~beta3-1, 2.02~beta3-2), gitk:amd64 (1:2.10.1-1, 1:2.10.2-1), libtiff5:amd64 (4.0.6-2, 4.0.6-3), python-ipaddress:amd64 (1.0.16-1, 1.0.17-1), libatspi2.0-0:amd64 (2.22.0-2, 2.22.0-3), tar:amd64 (1.29b-1, 1.29b-1.1), libcolamd2:amd64 (1:4.5.3-1, 1:4.5.3-2), libio-socket-ip-perl:amd64 (0.37-1, 0.38-1), libjs-jquery-ui:amd64 (1.10.1+dfsg-1, 1.12.1+dfsg-1), liblircclient0:amd64 (0.9.0~pre1-1.2, 0.9.4c-4), libcryptsetup4:amd64 (2:1.7.2-5, 2:1.7.3-1), python-libxml2:amd64 (2.9.4+dfsg1-2, 2.9.4+dfsg1-2.1), bluez-obexd:amd64 (5.41-1, 5.43-1), libcamd2:amd64 (1:4.5.3-1, 1:4.5.3-2), libxml2:amd64 (2.9.4+dfsg1-2, 2.9.4+dfsg1-2.1), libcholmod3:amd64 (1:4.5.3-1, 1:4.5.3-2), node-graceful-fs:amd64 (3.0.2-1, 4.1.9-1), libgnutls30:amd64 (3.5.5-4, 3.5.5-6), libpcap0.8:amd64 (1.8.1-1, 1.8.1-2), poedit:amd
 64 (1.8.11-1, 1.8.11-2), pandoc-data:amd64 (1.17.2~dfsg-1, 1.17.2~dfsg-2), bluetooth:amd64 (5.41-1, 5.43-1), poedit-common:amd64 (1.8.11-1, 1.8.11-2), libopts25:amd64 (1:5.18.12-2, 1:5.18.12-3), libbluetooth3:amd64 (5.41-1, 5.43-1), tiled-daily:amd64 (0+git20161028~20~ubuntu16.04.1, 0+git20161031~20~ubuntu16.04.1), cryptsetup:amd64 (2:1.7.2-5, 2:1.7.3-1), git-core:amd64 (1:2.10.1-1, 1:2.10.2-1), libxslt1.1:amd64 (1.1.29-1, 1.1.29-2), git-doc:amd64 (1:2.10.1-1, 1:2.10.2-1), libdouble-conversion1:amd64 (2.0.1-3, 2.0.1-4)
End-Date: 2016-11-01  10:45:29

Start-Date: 2016-11-02  19:37:40
Commandline: apt-get upgrade
Requested-By: alexander (1000)
Upgrade: vlc-bin:amd64 (1:2.2.4-dmo6, 1:2.2.4-dmo7), libreoffice-math:amd64 (1:5.2.3~rc1-4, 1:5.2.3~rc3-1), vlc-plugin-video-output:amd64 (1:2.2.4-dmo6, 1:2.2.4-dmo7), libreoffice-report-builder-bin:amd64 (1:5.2.3~rc1-4, 1:5.2.3~rc3-1), libges-1.0-0:amd64 (1.8.3-1, 1.10.0-1), libgroupsock8:amd64 (2:2016.09.22-dmo1, 2:2016.10.29-dmo1), iw:amd64 (4.7-0.1, 4.9-0.1), python-samba:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1), libreoffice-gtk3:amd64 (1:5.2.3~rc1-4, 1:5.2.3~rc3-1), libreoffice-java-common:amd64 (1:5.2.3~rc1-4, 1:5.2.3~rc3-1), vlc-plugin-qt:amd64 (1:2.2.4-dmo6, 1:2.2.4-dmo7), libwbclient0:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1), grub-common:amd64 (2.02~beta3-2, 2.02~beta3-3), libreoffice-base:amd64 (1:5.2.3~rc1-4, 1:5.2.3~rc3-1), gstreamer1.0-plugins-good:amd64 (1.8.3-1+b1, 1.10.0-1), libreoffice-core:amd64 (1:5.2.3~rc1-4, 1:5.2.3~rc3-1), samba:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1), gir1.2-ges-1.0:amd64 (1.8.3-1, 1.10.0-1), zlib1g:amd64 (1:1.2.8.dfsg-2+b1, 1:1.2.8.dfsg-2+b3), vlc-
 l10n:amd64 (1:2.2.4-dmo6, 1:2.2.4-dmo7), google-chrome-stable:amd64 (54.0.2840.71-1, 54.0.2840.90-1), libvlc5:amd64 (1:2.2.4-dmo6, 1:2.2.4-dmo7), grub2-common:amd64 (2.02~beta3-2, 2.02~beta3-3), gstreamer1.0-plugins-base:amd64 (1.8.3-1, 1.10.0-1), zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1, 1:1.2.8.dfsg-2+b3), libreoffice-l10n-ru:amd64 (1:5.2.3~rc1-4, 1:5.2.3~rc3-1), grub-pc:amd64 (2.02~beta3-2, 2.02~beta3-3), python3-uno:amd64 (1:5.2.3~rc1-4, 

Re: AMD SUMO vs Xorg 7.7

2016-12-02 Thread Michel Dänzer
On 02/12/16 05:05 PM, Alexander Konotop wrote:
> I've attached the log.
> I tried looking at the Xorg.0.log using "tail -f" while starting a browser 
> and waiting for it to
> freeze. Nothing happened, no new messages in Xorg.0.log. As well as in syslog 
> and dmesg.

Let's try to narrow down which package upgrade introduced the problem.
Your post on https://forum.siduction.org/index.php?topic=6469 talks
about a /var/log/apt/history.log attachment, but I can't seem to access
that from there. Can you attach it here?


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


Re: AMD SUMO vs Xorg 7.7

2016-12-02 Thread Alexander Konotop
I've attached the log.
I tried looking at the Xorg.0.log using "tail -f" while starting a browser and 
waiting for it to
freeze. Nothing happened, no new messages in Xorg.0.log. As well as in syslog 
and dmesg.


В Fri, 2 Dec 2016 10:35:15 +0900
Michel Dänzer  пишет:

> On 02/12/16 05:18 AM, Alexander Konotop wrote:
> > Hello! It looks like I've found a radeon driver bug.
> > 
> > Distro:
> > Debian Sid(Unstable).
> > 
> > Hardware:
> > * SUMO (integrated in AMD A4 APU)
> > * CAICOS (external)
> > 
> > Problem:
> > All webkit browsers freeze in few moments after startup while 
> > loading/opening or closing tabs.
> > It happens only whith an integrated card (SUMO).
> > Either propagating --disable-gpu to a browser or running on CAICOS using 
> > DRI_PRIME=1 eliminates
> > freezing.
> > Also running sauerbraten on SUMO causes freezing in few seconds after game 
> > starts, in menu.
> > Switching to a terminal and back (ctrl+alt+f1 and then ctrl+alt+f7) 
> > unfreezes the game for few
> > seconds and then it freezes again.  
> 
> Please provide the corresponding Xorg log file.
> 
> 

[ 9.429] 
X.Org X Server 1.19.0
Release Date: 2016-11-15
[ 9.429] X Protocol Version 11, Revision 0
[ 9.429] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 9.429] Current Operating System: Linux jager 4.8.11-towo.3-siduction-amd64 #1 SMP PREEMPT siduction 4.8-20 (2016-11-28) x86_64
[ 9.429] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.8.11-towo.3-siduction-amd64 root=UUID=5b027533-c09b-4df9-873c-a2fa2bb2b1d1 ro quiet resume=UUID=edc157fa-fd31-4e8a-98c8-80c795887235
[ 9.429] Build Date: 23 November 2016  07:20:23PM
[ 9.429] xorg-server 2:1.19.0-2 (https://www.debian.org/support) 
[ 9.429] Current version of pixman: 0.34.0
[ 9.429] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 9.429] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 9.429] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec  2 08:43:27 2016
[ 9.432] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 9.435] (==) No Layout section.  Using the first Screen section.
[ 9.435] (==) No screen section available. Using defaults.
[ 9.435] (**) |-->Screen "Default Screen Section" (0)
[ 9.435] (**) |   |-->Monitor ""
[ 9.438] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[ 9.438] (==) Automatically adding devices
[ 9.438] (==) Automatically enabling devices
[ 9.438] (==) Automatically adding GPU devices
[ 9.438] (==) Max clients allowed: 256, resource mask: 0x1f
[ 9.446] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 9.446] 	Entry deleted from font path.
[ 9.450] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[ 9.450] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 9.450] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 9.450] (II) Loader magic: 0x56036f77fe00
[ 9.450] (II) Module ABI versions:
[ 9.450] 	X.Org ANSI C Emulation: 0.4
[ 9.450] 	X.Org Video Driver: 23.0
[ 9.450] 	X.Org XInput driver : 24.1
[ 9.450] 	X.Org Server Extension : 10.0
[ 9.451] (++) using VT number 7

[ 9.451] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 9.452] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 9.472] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 9.477] (--) PCI:*(0:0:1:0) 1002:9648:103c:168c rev 0, Mem @ 0xb000/268435456, 0xd810/262144, I/O @ 0x7000/256, BIOS @ 0x/131072
[ 9.477] (--) PCI: (0:1:0:0) 1002:6760:103c:168c rev 0, Mem @ 0xc000/268435456, 0xd800/131072, I/O @ 0x6000/256, BIOS @ 0x/131072
[ 9.477] (II) LoadModule: "glx"
[ 9.483] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 9.514] (II) Module glx: vendor="X.Org Foundation"
[ 9.514] 	compiled for 1.19.0, module version = 1.0.0
[ 9.514] 	ABI class: X.Org Server Extension, version 10.0
[ 9.514] (==) Matched ati as autoconfigured driver 0
[ 9.514] (==) Matched ati as autoconfigured driver 1
[ 9.514] (==) Matched ati as autoconfigured driver 2
[ 9.514] (==) Matched modesetting as autoconfigured driver 3
[ 9.514] (==) Matched fbdev as autoconfigured driver 4
[ 9.514] (==) Matched vesa as autoconfigured driver 5
[ 9.514] (==) Assigned the driver to the xf86ConfigLayout
[ 9.514] (II) LoadModule: "ati"
[ 9.515] (II) Load

Re: AMD SUMO vs Xorg 7.7

2016-12-01 Thread Michel Dänzer
On 02/12/16 05:18 AM, Alexander Konotop wrote:
> Hello! It looks like I've found a radeon driver bug.
> 
> Distro:
> Debian Sid(Unstable).
> 
> Hardware:
> * SUMO (integrated in AMD A4 APU)
> * CAICOS (external)
> 
> Problem:
> All webkit browsers freeze in few moments after startup while loading/opening 
> or closing tabs.
> It happens only whith an integrated card (SUMO).
> Either propagating --disable-gpu to a browser or running on CAICOS using 
> DRI_PRIME=1 eliminates
> freezing.
> Also running sauerbraten on SUMO causes freezing in few seconds after game 
> starts, in menu.
> Switching to a terminal and back (ctrl+alt+f1 and then ctrl+alt+f7) unfreezes 
> the game for few
> seconds and then it freezes again.

Please provide the corresponding Xorg log file.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


AMD SUMO vs Xorg 7.7

2016-12-01 Thread Alexander Konotop
Hello! It looks like I've found a radeon driver bug.

Distro:
Debian Sid(Unstable).

Hardware:
* SUMO (integrated in AMD A4 APU)
* CAICOS (external)

Problem:
All webkit browsers freeze in few moments after startup while loading/opening 
or closing tabs.
It happens only whith an integrated card (SUMO).
Either propagating --disable-gpu to a browser or running on CAICOS using 
DRI_PRIME=1 eliminates
freezing.
Also running sauerbraten on SUMO causes freezing in few seconds after game 
starts, in menu.
Switching to a terminal and back (ctrl+alt+f1 and then ctrl+alt+f7) unfreezes 
the game for few
seconds and then it freezes again.
No problems for sauerbraten with DRI_PRIME=1 on CAICOS.

Here's a forum topic which I started before I determined that the browsers 
problem is caused by
videocard:
https://forum.siduction.org/index.php?topic=6469
But there's not much useful debug info actually.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati