[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150316095121.GE30817@ulmo.nvidia.com>
Date: Mon, 16 Mar 2015 10:51:22 +0100
From: Thierry Reding <treding@...dia.com>
To: Paul Bolle <pebolle@...cali.nl>
CC: Dave Airlie <airlied@...ux.ie>, <torvalds@...ux-foundation.org>,
<linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm fixes
On Fri, Mar 13, 2015 at 12:36:04PM +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.
There should be a patch in v4.0-rc4 (046d669c62f3 "drm/mm: Fix support 4
GiB and larger ranges") that presumably fixes this. Does it work for you
as well?
Thierry
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists