[lkml]   [2011]   [Jan]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps
On Sat, 22 Jan 2011 11:18:53 +0000, Chris Clayton <> wrote:
> On Saturday 22 January 2011, Chris Wilson wrote:
> > Signed-off-by: Chris Wilson <>
> > ---
> >
> > Chris, does this help?
> >
> Sorry Chris, X still doesn't start with this patch applied. The symptoms are
> slightly different in that the monitor doesn't go into power saving mode, but
> the screen is still black and I have to recycle the power to get the machine
> back.
> The messages in the log file has changed though.We now have:

Despite appearances to the contrary, it is a step forward. We have the
crash under control, and now need to tackle the underlying problem.

However, I'm worried by the fact that no CRTCs are attached. Is this not
using KMS?

> > If you can convert the address to a line number that would pinpoint the
> Not done that before and nothing jumped out of my search on google, so how do I
> go about getting the line number for you, please?

Something like:

$ gdb drivers/gpu/drm/drm.ko
(gdb) list *drm_calc_vbltimestamp_from_scanoutpos+0x3e

should do the trick (if compiled as a module, vmlinux otherwise)

Chris Wilson, Intel Open Source Technology Centre

 \ /
  Last update: 2011-01-22 19:05    [W:0.071 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site