From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jan Vlietland <j.vlietland@nisi.nl>, "Moorestow...),
Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Moorestow...), Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Moorestow...), David Airlie" <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org
Subject: Re: i915 module results in total lockups without any dmesg trace on a NP900X5N Kaby Lake machine
Date: Wed, 02 Jan 2019 09:34:07 +0200 [thread overview]
Message-ID: <871s5vms28.fsf@intel.com> (raw)
In-Reply-To: <fb45fc15-1623-6f7e-e1a8-ef7f09fa7deb@nisi.nl>
On Tue, 01 Jan 2019, Jan Vlietland <j.vlietland@nisi.nl> wrote:
> First of all happy new year. Based on advice of Greg K-H herewith a mail
> about my continuous (frustrating) issue with my laptop.
>
> I installed various Kali linux versions up to Linux 4.20.0-rc7
> (downloaded, compiled and installed) on a Samsung NP900X5N laptop and
> have an issue with the driver after loading.
Please file a bug at [1], add drm.debug=14 module parameter, attach
dmesg from boot to desktop to the bug. If you can ssh into the machine
and get a dmesg after the screen goes black, great, but if not, let's
start with that.
BR,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-02 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 17:11 i915 module results in total lockups without any dmesg trace on a NP900X5N Kaby Lake machine Jan Vlietland
2019-01-02 7:34 ` Jani Nikula [this message]
2019-01-02 12:34 ` Jan Vlietland
2019-01-02 19:20 ` Jan Vlietland
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=871s5vms28.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=j.vlietland@nisi.nl \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.