From owner-freebsd-x11@freebsd.org Fri Jan 4 05:44:52 2019 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4687E141A682 for ; Fri, 4 Jan 2019 05:44:52 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 77C368215E for ; Fri, 4 Jan 2019 05:44:51 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3B20E141A680; Fri, 4 Jan 2019 05:44:51 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 187DF141A67F for ; Fri, 4 Jan 2019 05:44:51 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89A678215D for ; Fri, 4 Jan 2019 05:44:50 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi1-x22f.google.com with SMTP id v6so29573691oif.2 for ; Thu, 03 Jan 2019 21:44:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7JqykP3629ns/3PESDQ2r3X9UV8EVrHq35K3cdo56WQ=; b=A5q8if0djAJikcu87hOX9RNXlL4c4ceUwS/+/VqHLYuTuyJHugrbEitRXc0+ESCjh6 XjPQ/Sq64JbFov3PbCNtZFA7bWTltf04WeUnEhtT+sQG2xmRVg+Sp8opQ0Rbydmt+BSa WPq7FjjXiqaam/Rs4dKoSQ5aIdTsKNEjn+lviy2MtX1NdX44grAHc3RHo+T1qIQ2zglt VGgZwFw2iT6a/wpRDYf7FX0uQUCkE+JTiMYibqEPXHHQBZBPIEE1Bv4Nvdw10PfsnrYK GLn2ZxWsp+dW08eKvOu3UGfEWEzTSd8xprejwHurq93MlcPP6cqeMuOlKT13HfTedRRm gN/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7JqykP3629ns/3PESDQ2r3X9UV8EVrHq35K3cdo56WQ=; b=Z/hZY0+F3vQ874mXK9SYninEF/LYUoljGX0NXMbzIQ9vWL+nKYW2F4gPtsphDczQZK cMya8iurwxZI/jNTj6UvjpDV/lC9K/t3+1ZuDvv0e+hMsGm2ompuXdlgPKwc4024l2xM fKmN06Arx8CESZ8GOCxV0VDpkLbGBEGvazzfK9HWW1+wd/mhFffNrfUMux6XntPMsUoj csJKGtpMOtL+vIzYg9K1iIAg2s8mVhNcFb+QETEpXFvtG0a2F2qanY2y5eKVgDhzDRLR Ddb84M1bL94z92dGjzRXqatwyGqDriRYbpe1xjynGTiJRt+ZO84reMI7+aWoQlZz81er O4fA== X-Gm-Message-State: AJcUukearX56S1kLsJS1hjvrDAFoNHnNmtCBEmRgfWNOAqhVSJiTnhBL 6IGpbiDroRouEHcK2gVL+FL6oL/9l/Q2VWcpB1A= X-Google-Smtp-Source: ALg8bN41lrApeRd7iQZ56ALMDQqyrBfiitWrhqf/TilSRKnRWqSpQdf8XoE4B5tUWy+rsViyZ0LDNvtvo2PkYh+z/tM= X-Received: by 2002:aca:4489:: with SMTP id r131mr304905oia.296.1546580689590; Thu, 03 Jan 2019 21:44:49 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Thu, 3 Jan 2019 21:44:32 -0800 Message-ID: Subject: Re: GPU hang on ThinkPad T420 with drm-kmod on 12.0-RELEASE To: Kevin Zheng Cc: Pete Wright , "freebsd-x11@freebsd.org" X-Rspamd-Queue-Id: 89A678215D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.95 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_SHORT(-0.95)[-0.950,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2019 05:44:52 -0000 On Thu, Jan 3, 2019 at 5:08 PM Kevin Zheng wrote: > On 1/3/19 7:01 PM, Pete Wright wrote: > > Can you test out the drm-legacy-kmod pkg and see if that resolves these > > issues? There was a recent user report that Ivy Bridge was working with > > the drm-kmod package, but it's possible I was mistaken there. > > Sorry, yes, to be clear, I don't get these hangs with drm-legacy-kmod. > > drm-kmod also "works," except when it does hang. It takes a bit of use > to shake out the hang, and I'd also like to track down what's going on. > > I also thought to ask here, if any other Ivy Bridge users are noticing > the same thing. > > -- > Kevin Zheng > kevinz5000@gmail.com | kevinz@berkeley.edu | PGP: 0xC22E1090 > I am running on 12.0-STABLE r342382 on my T500 with Sandy Bridge. Other than screen size, I believe that it is identical with the T420. Are you sure that yours is ivy Bridge? Maybe later T420schanged processors? I just discovered that it is essential that I run with the modesetting driver, not xf86-video-intel. Are you running modesetting? Using he older driver triggered several issues for me.I also am running mesa 18.3.1 which is currently under test (and will hopefully be in ports soon). You can find the patches to 18.2.8 and then to 18.2.8 is covered in bug 230298 and 18.3.1 in bug 233034 . Patches must be applied in sequence and with the -E option. I have now been running on the system for over a day with no issues, but I need to give it more time before I pronounce it satisfactory. I also use Firefox, but I will give chromium a shot now and see if there is a problem. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683