LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: chris2553@googlemail.com
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 10:52:56 +0000	[thread overview]
Message-ID: <b7da2f$q7auf0@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <201101230932.49998.chris2553@googlemail.com>

On Sun, 23 Jan 2011 09:32:49 +0000, Chris Clayton <chris2553@googlemail.com> wrote:
> On Sunday 23 January 2011, Chris Clayton wrote:
> > 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.
> >
> 
> Mmmm, I get a lock up when turning KMS on in 2.3.38-rc2+ and it looks like KMS 
> is inducing a crash in X. The Xorg log contains:
> 
> Backtrace:
> 0: /usr/X11/bin/X(xorg_backtrace+0x3b) [0x81352db]
> 1: /usr/X11/bin/X(xf86SigHandler+0x51) [0x80ba0b1]
> 2: [0xb78b5400]
> 3: /usr/X11R6/lib/libdrm_intel.so.1(+0x624b) [0xb72d024b]
> 4: /usr/X11R6/lib/libdrm_intel.so.1(drm_intel_bo_unreference+0x16) [0xb72cb446]
> 5: /usr/X11/lib/xorg/modules/drivers//intel_drv.so(intel_batch_flush+0xb6) 
> [0xb72ec876]
> 6: /usr/X11/lib/xorg/modules/drivers//intel_drv.so(+0x4b5d0) [0xb73215d0]
> 7: /usr/X11/lib/xorg/modules/drivers//intel_drv.so(uxa_fill_region_tiled+0x264) 
> [0xb7338fc4]
> 8: /usr/X11/lib/xorg/modules/drivers//intel_drv.so(+0x6343b) [0xb733943b]
> 9: /usr/X11/bin/X() [0x817b8c6]
> 10: /usr/X11/bin/X(miPaintWindow+0x1cb) [0x811484b]
> 11: /usr/X11/bin/X(miWindowExposures+0xbf) [0x8114bbf]
> 12: /usr/X11/bin/X() [0x80b364f]
> 13: /usr/X11/bin/X(MapWindow+0x3a8) [0x8072cc8]
> 14: /usr/X11/bin/X(InitRootWindow+0x10c) [0x8072dfc]
> 15: /usr/X11/bin/X(main+0x40a) [0x806be0a]
> 16: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7412b86]
> 17: /usr/X11/bin/X() [0x806b2c1]

This looks more like typical memory corruption, and the usual requests to
make sure you have the latest stable drivers apply: Xorg-1.9,
xf86-video-intel-2.14, libdrm-2.4.23, [mesa-7.10].
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      parent reply	other threads:[~2011-01-23 10:53 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
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           ` Chris Wilson [this message]

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='b7da2f$q7auf0@fmsmga001.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=chris2553@googlemail.com \
    --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).