From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Sitsofe Wheeler <sitsofe@gmail.com>
Subject: Re: [Regression] BUG: unable to handle kernel NULL pointer dereference
Date: Sun, 1 Mar 2015 00:57:01 +0300 [thread overview]
Message-ID: <20150228215701.GA1732@nest> (raw)
In-Reply-To: <20150228211013.GB13459@nuc-i3427.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]
On 28 Feb, Chris Wilson wrote:
> On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote:
> > Unfortunately this is not the last bug, that breaks i915/drm working
> > on my laptop. Sometimes system successfully loads with couple warnings mentioned in
> > previous mail:
> >
> > [ 26.922953] WARNING: CPU: 1 PID: 767 at drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x13f/0x288 [i915]()
> > [ 26.922954] WARN_ON(obj->frontbuffer_bits)
>
> That's inocuous, but for the serious hang, you may want to try
> video=SVIDEO-1:d on the kernel commandline to workaround the hang. (Check
> /sys/class/drm/card/ for the actual name of the connector for TV). I
> think Ville mentioned he was looking/looked at the atomic-vs-load_detect
> changes that is at the heart of the issue here. (Admittedly he did say
> it was worthy of a drink or two.)
> -Chris
Thank you for the help. I've tried to add to the kernel command line
'video=card0-SVIDEO-1:d video=card0-VGA-1:d'. But despite of that
kernel crashes with 'BUG: unable to handle kernel NULL pointer
dereference at' occasionally.
--
Best regards,
Andrey Skvortsov
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-28 21:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 19:15 [regression in linux-next] i915: broken graphics on laptop Andrey Skvortsov
2015-02-03 20:21 ` [Intel-gfx] " Chris Wilson
2015-02-04 18:26 ` Andrey Skvortsov
2015-02-04 18:42 ` [Intel-gfx] " Chris Wilson
2015-02-23 20:10 ` [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object Andrey Skvortsov
2015-02-23 20:12 ` Andrey Skvortsov
2015-02-23 21:20 ` Chris Wilson
2015-02-23 23:42 ` [Intel-gfx] " Daniel Vetter
2015-02-28 12:20 ` Andrey Skvortsov
2015-02-28 21:10 ` [Intel-gfx] " Chris Wilson
2015-02-28 21:57 ` Andrey Skvortsov [this message]
2015-03-01 8:29 ` [Intel-gfx] [Regression] BUG: unable to handle kernel NULL pointer dereference Chris Wilson
2015-03-01 9:30 ` Andrey Skvortsov
2015-03-01 10:28 ` Chris Wilson
2015-03-05 14:27 ` [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object Steven Rostedt
2015-03-16 15:45 ` Steven Rostedt
2015-03-16 16:43 ` Daniel Vetter
2015-03-16 17:21 ` Steven Rostedt
2015-03-17 7:53 ` Daniel Vetter
2015-03-18 0:46 ` [Intel-gfx] " Steven Rostedt
2015-03-18 8:30 ` Jani Nikula
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=20150228215701.GA1732@nest \
--to=andrej.skvortzov@gmail.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).