From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Adam Nielsen <a.nielsen@shikadi.net>, intel-gfx@lists.freedesktop.org
Subject: Re: System freeze apparently due to GPU memory exhaustion - why?
Date: Fri, 26 Feb 2016 12:30:06 +0200 [thread overview]
Message-ID: <1456482606.7316.7.camel@linux.intel.com> (raw)
In-Reply-To: <20160223205817.6df3cb23@korath.teln.shikadi.net>
On ti, 2016-02-23 at 20:58 +1000, Adam Nielsen wrote:
> >
> > Can you attach a full dmesg from boot until the problem appears?
> Attached, thanks for your reply.
>
> You can ignore the problem at T=1032000, that was a broken floppy disk
> in a USB floppy drive. The first possibly-GPU-related problem starts
> at T=2121945 then the same problem happens immediately following in the
> log at T=2128002.
>
That seems like a legit bug. If you can reproduce it with drm-intel-
nightly, could you please open a bug at freedesktop.org bugzilla?
Have you tried running the I-G-T testing suite on your hardware?
Regards, Joonas
> It may be of relevance to note that after a reboot it can take a while
> for the problem to surface, but if X crashes due to this issue and I
> restart X immediately, then it can be only a matter of minutes to
> hours until the problem happens again.
>
> Many thanks,
> Adam.
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-26 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 1:55 System freeze apparently due to GPU memory exhaustion - why? Adam Nielsen
2016-02-23 9:47 ` Joonas Lahtinen
2016-02-23 10:58 ` Adam Nielsen
2016-02-26 10:30 ` Joonas Lahtinen [this message]
2016-04-04 12:54 ` Adam Nielsen
2016-04-04 13:13 ` Adam Nielsen
2016-04-07 16:25 ` Marius Vlad
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=1456482606.7316.7.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=a.nielsen@shikadi.net \
--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;
as well as URLs for NNTP newsgroup(s).