From: Jani Nikula <jani.nikula@linux.intel.com>
To: Helmut Grohne <helmut@subdivi.de>, intel-gfx@lists.freedesktop.org
Subject: Re: WARN_ON(atomic_read(&obj->frontbuffer_bits))
Date: Wed, 23 May 2018 13:00:18 +0300 [thread overview]
Message-ID: <8736yin13h.fsf@intel.com> (raw)
In-Reply-To: <20180522195435.GA3286@alf.mars>
On Tue, 22 May 2018, Helmut Grohne <helmut@subdivi.de> wrote:
> after upgrading a Debian jessie system to Debian stretch, I've seen the
> following output in my kern.log once. The system was responding to
> network pings, but not to anything else (keyboard, ssh, ...). The hang
> happened during boot (which includes starting a display manager). Most
> boots don't hang.
I suggest updating to a more recent kernel. You can get v4.16 from
stretch-backports.
If the problem persists, please file a bug over at [1].
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
prev parent reply other threads:[~2018-05-23 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 19:54 WARN_ON(atomic_read(&obj->frontbuffer_bits)) Helmut Grohne
2018-05-23 10:00 ` 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=8736yin13h.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=helmut@subdivi.de \
--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