From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753132AbbCPJrC (ORCPT ); Mon, 16 Mar 2015 05:47:02 -0400 Received: from cpsmtpb-ews10.kpnxchange.com ([213.75.39.15]:63331 "EHLO cpsmtpb-ews10.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750736AbbCPJq7 (ORCPT ); Mon, 16 Mar 2015 05:46:59 -0400 Message-ID: <1426499217.26437.7.camel@x220> Subject: Re: [git pull] drm fixes From: Paul Bolle To: Dave Airlie Cc: Thierry Reding , torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org Date: Mon, 16 Mar 2015 10:46:57 +0100 In-Reply-To: <1426246564.22063.11.camel@tiscali.nl> References: <1426246564.22063.11.camel@tiscali.nl> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Mar 2015 09:46:57.0683 (UTC) FILETIME=[24AAF630:01D05FCE] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2015-03-13 at 12:36 +0100, Paul Bolle wrote: > Dave Airlie schreef op vr 06-03-2015 om 21:52 [+0000]: > > Thierry Reding (1): > > drm/mm: Support 4 GiB and larger ranges > > Yesterday the screen on my (outdated) ThinkPad X41 went, well, black > while it was busy compiling something unattended. I eventually had to > power cycle that laptop to regain control. I found a drm related BUG() > in the logs (pasted at the end of the message). > > I only have three months worth of logs (a diagnoising session pushed > most of the logs into /dev/null a few weeks ago). But this is the only > time I saw that BUG in that period. Now that commit is the last thing > touching that code, and the various unsigned long to u64 conversions > _might_ just have gone wrong for 32 bits. I didn't spot anything utterly > obvious in that commit, but point a finger at it just in case. Surely fixed by commit 046d669c62f3 ("[PATCH] drm/mm: Fix support 4 GiB and larger ranges"). It corrects a mistake introduced by the commit quoted above. So at least I pointed a finger at the right commit. Thanks, Paul Bolle