LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps
Date: Sun, 23 Jan 2011 08:56:42 +0000	[thread overview]
Message-ID: <201101230856.42744.chris2553@googlemail.com> (raw)
In-Reply-To: <0d30dc$kr3ing@orsmga001.jf.intel.com>

On Saturday 22 January 2011, Chris Wilson wrote:
> On Sat, 22 Jan 2011 11:18:53 +0000, Chris Clayton <chris2553@googlemail.com> 
wrote:
> > On Saturday 22 January 2011, Chris Wilson wrote:
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > ---
> > >
> > > 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?
>

No KMS is not configured in. I found that under an earlier version of the kernel 
it caused my kernel to lock up, so I configured it out. I meant to investigate 
further and report it, but then forgot. I'll turn KMS on and report the 
outcome.

> > > 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)

Thanks for the tutoring. I get

(gdb) list *drm_calc_vbltimestamp_from_scanoutpos+0x3e
0x6afe is in drm_calc_vbltimestamp_from_scanoutpos 
(drivers/gpu/drm/drm_irq.c:590).
585                     DRM_ERROR("Called from driver w/o 
get_scanout_position()!?\n");
586                     return -EIO;
587             }
588
589             mode = &refcrtc->hwmode;
590             vtotal = mode->crtc_vtotal;
591             vdisplay = mode->crtc_vdisplay;
592
593             /* Durations of frames, lines, pixels in nanoseconds. */
594             framedur_ns = refcrtc->framedur_ns;


Chris
> -Chris

-- 
The more I see, the more I know. The more I know, the less I understand. 
Changing Man - Paul Weller

  reply	other threads:[~2011-01-23  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <:201101220935.03623.chris2553@googlemail.com>
2011-01-22 10:11 ` Chris Wilson
2011-01-22 11:18   ` Chris Clayton
2011-01-22 18:01     ` Chris Wilson
2011-01-23  8:56       ` Chris Clayton [this message]
2011-01-23  9:32         ` Chris Clayton
2011-01-23 10:50           ` [PATCH] drm/i915: Disable high-precision vblank timestamping for UMS Chris Wilson
2011-01-23 11:28             ` Chris Clayton
2011-01-23 12:44               ` Chris Wilson
2011-01-23 12:55                 ` Chris Clayton
2011-01-23 13:06               ` [PATCH] drm/i915: Handle the no-interrupts case for UMS by polling Chris Wilson
2011-01-23 15:38                 ` Chris Clayton
2011-01-23 15:59                   ` Chris Wilson
2011-02-10 19:58                     ` Chris Clayton
2011-02-10 20:37                       ` Chris Wilson
2011-01-23 10:52           ` [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201101230856.42744.chris2553@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).