From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Rainey <ckrzen@gmail.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: 8086:0f31_freezes_totally
Date: Wed, 14 Oct 2015 10:11:52 +0300 [thread overview]
Message-ID: <87fv1d3ow7.fsf@intel.com> (raw)
In-Reply-To: <87io6a2adg.fsf@intel.com>
On Wed, 14 Oct 2015, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Tue, 13 Oct 2015, Chris Rainey <ckrzen@gmail.com> wrote:
>> [1.] One line summary of the problem: 8086:0f31_freezes_totally
>>
>> [2.] Full description of the problem/report: Total lockup(cannot even
>> switch to console via Alt-F1, F2, etc.). Bug is most easily
>> reproducible via Chromium browser when opening multiple
>> background-tabs(middle-button(wheel) mouse-clicks) and when using
>> ALT-TAB to switch between browser and Xterms, etc. Very difficult to
>> pin due to randomness(i.e. system may run for 30-seconds, 30-minutes
>> or 30-hours before freeze). However -- it rarely runs stable for more
>> that 24-48/hrs without a lockup.
>
> Please file a bug at [1] running drm-intel-nightly.
Ermh, I meant to say, and attach dmesg from boot with drm.debug=14
module parameter set.
J.
>
> BR,
> Jani.
>
>
> [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
>
>
> --
> Jani Nikula, Intel Open Source Technology Center
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-10-14 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 17:42 8086:0f31_freezes_totally Chris Rainey
2015-10-14 7:10 ` 8086:0f31_freezes_totally Jani Nikula
2015-10-14 7:11 ` Jani Nikula [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=87fv1d3ow7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ckrzen@gmail.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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