From owner-freebsd-current@FreeBSD.ORG Wed Mar 4 16:28:33 2015 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD980717; Wed, 4 Mar 2015 16:28:32 +0000 (UTC) Received: from pmta2.delivery3.ore.mailhop.org (pmta2.delivery3.ore.mailhop.org [54.213.22.21]) by mx1.freebsd.org (Postfix) with ESMTP id AF63CC3A; Wed, 4 Mar 2015 16:28:32 +0000 (UTC) Received: from smtp1.ore.mailhop.org (172.31.18.134) by pmta2.delivery1.ore.mailhop.org id huspcc20u50j; Wed, 4 Mar 2015 16:28:47 +0000 (envelope-from ) Received: from pool-71-255-170-26.bstnma.east.verizon.net ([71.255.170.26] helo=homobox.opal.com) by smtp1.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YTC9p-0006V9-Cr; Wed, 04 Mar 2015 16:28:25 +0000 Received: from shibato (ip51cd975c.adsl-surfen.hetnet.nl [81.205.151.92]) (authenticated bits=0) by homobox.opal.com (8.14.9/8.14.9) with ESMTP id t24GSIuB049528 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Wed, 4 Mar 2015 11:28:19 -0500 (EST) (envelope-from fbsd@opal.com) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 71.255.170.26 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1/FYTcpF2gPFE7uT30PyVS9 Date: Wed, 4 Mar 2015 17:28:02 +0100 From: "J.R. Oldroyd" To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8 (take #2) Message-ID: <20150304172802.0b285585@shibato> In-Reply-To: <54F636B3.90701@FreeBSD.org> References: <54F636B3.90701@FreeBSD.org> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/gieHqjGF_8F4qJdiTq5hhuf"; protocol="application/pgp-signature" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (homobox.opal.com [71.255.170.26]); Wed, 04 Mar 2015 11:28:21 -0500 (EST) X-Spam-Status: No, score=3.1 required=5.0 tests=AWL,BAYES_00, FSL_HELO_NON_FQDN_1,OPAL_URI_COUNT_5_9,RCVD_IN_PBL shortcircuit=no autolearn=no autolearn_force=no version=3.4.0 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on homobox.opal.com Cc: Hans Petter Selasky , freebsd-x11@FreeBSD.org, freebsd-current@FreeBSD.org, Ed Maste X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2015 16:28:33 -0000 --Sig_/gieHqjGF_8F4qJdiTq5hhuf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, 03 Mar 2015 23:33:23 +0100 Jean-S=C3=A9bastien P=C3=A9dron wrote: > > Hi! >=20 > Here is a new patch to based on HEAD r279508: > https://people.freebsd.org/~dumbbell/graphics/drm-update-38.i.patch >=20 > You can apply it to a Subversion checkout using the following command: > svn patch drm-update-38.i.patch >=20 > There are few changes: > o The panic reported by J.R. Oldroyd is fixed, but not the CP init > problem. > o A lock assert was added, suggested by Konstantin Belousov >=20 Tested as requested: svn update to r279508 and applied the 38i patch. Mixed results. The first boot, done as a warm "reboot" command while running 10-stable shows that the CP init failed again and I am back to the mtx_lock panic. I then let it auto-reboot back into 10-stable (this is an old 10-stable at the time of r271969 10.1-BETA2 but it is one in which the ring CP init still works). That shows it boots fine and ring CP inits OK - even as a warm reboot after the previous failure. I then thought to try a power-off cold reboot into r279508. This works, both ring CP inits OK and no mtx_lock panic. In fact, I am using it now to send this report. So, perhaps the previous fix for the mtx_lock panic wasn't right, but just seemed to work because I happened to cold-boot those times. The pattern that's emerging here is that older (mid-2014) kernels boot and init fine, warm or cold. The CP init problem started somewhere mid-2014. The mtx_lock panic is new, so I am guessing related to the drm2-38 update. BOTH CP init and mtx_lock problems go away when cold booting. I've uploaded info here: http://opal.com/jr/freebsd/panic/r279508M/dmesg.txt http://opal.com/jr/freebsd/panic/r279508M/core.txt.7 The dmesg shows the three boot sequences with annotations to make it clear which is which. Above is system with ATI Radeon RS690 X1270 IGP, RS690. BTW, I now also have the ring CP init failure on a second system that was just updated to 10.1-RELEASE-p6. It has ATI Radeon HD 4200 which is RS780 and it also shows the ring init failure at CAFEDEAD but in r600_ting_test(). Unfortunately, this system is a production one so I can't easily play with it. Note, no mtx_lock panic here. Fortunately, the graphics not working isn't a problem on this system. -jr --Sig_/gieHqjGF_8F4qJdiTq5hhuf Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlT3MpoACgkQls33urr0k4m5/wCfQyQVzh4EDNupOpX1D5/CRWtN DnwAnR72NiQ2VMElT6LQhHUtAOMW1S2N =MWKE -----END PGP SIGNATURE----- --Sig_/gieHqjGF_8F4qJdiTq5hhuf--