From owner-freebsd-current@FreeBSD.ORG Sat Mar 7 16:13:33 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 958F760C; Sat, 7 Mar 2015 16:13:33 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46A922DE; Sat, 7 Mar 2015 16:13:33 +0000 (UTC) Received: by qcxr5 with SMTP id r5so57676328qcx.10; Sat, 07 Mar 2015 08:13:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type; bh=utGUAhu9ygBcnN3FyJkFTkbhluPwJAHWhEYG4lryuO8=; b=Ck6E0h3iqG5YWdfBhKeq9dklHzuwfar3x8W+bL5J1c1tkWjtRmbj13PWO5KZwP37Os ROcj2xf0nPxxMBngF73L2D8jZDCivirYOfK3vexCnAm4ZhwB1lhsROSfJ6G/Xc8nDLNH 9CBp4SBrKFFP5+lSXrX1KpslFxk1riAXqK7BI/oB+tpj3qU4vu9Kj81SmtGKm56SYNB8 9ochrutuUZTSRbwpuyuiYcy91AQrgAS6M3789C3VR8AuQTS6h73+uAfupgljBuP43T37 bW4Ju/GouwhuHrZf/+xOJiL+kBuy40LUhxYR02c9t0Ka5Xlr6Qy0CpdjyLZCACkHTfmC cVHg== X-Received: by 10.140.151.74 with SMTP id 71mr26498595qhx.15.1425744812107; Sat, 07 Mar 2015 08:13:32 -0800 (PST) Received: from kan ([2601:6:6780:7e0:226:18ff:fe00:232e]) by mx.google.com with ESMTPSA id y69sm7996150qgy.6.2015.03.07.08.13.30 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Mar 2015 08:13:31 -0800 (PST) Date: Sat, 7 Mar 2015 11:13:05 -0500 From: Alexander Kabaev To: =?KOI8-R?Q?Jean-S'ebastien_P'edron?= Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8 (take #2) Message-ID: <20150307111305.10d7678d@kan> 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-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/v4bwYYgoWMpVU4b8bvEXJ/2"; protocol="application/pgp-signature" 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: Sat, 07 Mar 2015 16:13:33 -0000 --Sig_/v4bwYYgoWMpVU4b8bvEXJ/2 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On Tue, 03 Mar 2015 23:33:23 +0100 Jean-S'ebastien P'edron 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 > I had several panics ("Stray timeout") with a taskqueue used by TTM, > but it didn't occur in the past 6 days. Maybe it was a problem > outside of DRM. >=20 > I would like people to test again and report :) If something fails, > please post a full dmesg, taken after loading the relevant *kms > module, or the core.txt.$N file if it's a panic. >=20 > Hans Petter and Ed, I couldn't reproduce neither of your problems > (HDMI hotplug events storm and VT-switch misbehaviour). However, they > both involve callouts, like the "Stray timeout" panic I had with TTM. > I suspect there was a transient problem with callouts in HEAD at the > same time. Could you please test again with this patch and a very > recent HEAD? >=20 > Thank you to everyone! >=20 > --=20 > Jean-S'ebastien P'edron >=20 Just as a data point, 'stray timeout' happens in clean -current without new patch as well. So whatever that is, it is not caused by the patch. --=20 Alexander Kabaev --Sig_/v4bwYYgoWMpVU4b8bvEXJ/2 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlT7I5IACgkQQ6z1jMm+XZZgCACcC3+fHhPOuv9OG4Mg+Hf0Itz0 ZHoAoIkRP41U111b/+kS2WBZauCM/SC/ =v9HE -----END PGP SIGNATURE----- --Sig_/v4bwYYgoWMpVU4b8bvEXJ/2--