From: Alexandru Chirvasitu <achirvasub@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5
Date: Wed, 3 Jan 2018 11:31:31 -0500 [thread overview]
Message-ID: <20180103163131.GD2118@chirva-void> (raw)
In-Reply-To: <151499122583.21495.1963140337943422469@mail.alporthouse.com>
Thank you for that!
I'd been getting used to seeing warnings to that effect, so got
complacent and stopped checking for errors..
In any case, it's now compiled and installed, and I will report back
with any new logs if / when another hang occurs.
On Wed, Jan 03, 2018 at 02:53:45PM +0000, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-03 14:48:26)
> > Here's the log for the make bzImage and modules without ccache.
> >
> > I ran it with j8 still because otherwise it would take very long, but
> > if I run out of options I'll try plain too..
> >
> > In the meantime I'd like to try some other configs; maybe specific
> > drivers are messing me up.
> >
> > I swear to god it was working all right yesterday..
>
> drivers/gpu/drm/i915/intel_dpio_phy.c:442:1: error: the frame size of
> 1168 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
>
> Go into the kconfig compiler options and increase the limit or disable
> the warning. See CONFIG_FRAME_WARN.
> -Chris
next prev parent reply other threads:[~2018-01-03 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 17:31 PROBLEM: i915 causes complete desktop freezes in 4.15-rc5 Alexandru Chirvasitu
2017-12-31 15:54 ` Chris Wilson
2017-12-31 16:52 ` Alexandru Chirvasitu
[not found] ` <151473925492.2051.3326119747183075981@mail.alporthouse.com>
2017-12-31 23:17 ` Alexandru Chirvasitu
2018-01-01 21:13 ` Alexandru Chirvasitu
[not found] ` <151491202515.21495.4275099714898982160@mail.alporthouse.com>
2018-01-02 21:39 ` Alexandru Chirvasitu
2018-01-03 0:14 ` Alexandru Chirvasitu
[not found] ` <151498375040.21495.10909014868670557680@mail.alporthouse.com>
2018-01-03 13:46 ` Alexandru Chirvasitu
[not found] ` <151498727661.21495.7545852848027242671@mail.alporthouse.com>
2018-01-03 14:03 ` Alexandru Chirvasitu
[not found] ` <151498852791.21495.13313443882665791372@mail.alporthouse.com>
2018-01-03 14:48 ` Alexandru Chirvasitu
[not found] ` <151499122583.21495.1963140337943422469@mail.alporthouse.com>
2018-01-03 16:31 ` Alexandru Chirvasitu [this message]
2018-01-03 21:53 ` Alexandru Chirvasitu
[not found] ` <151517474548.6838.1821139419472614998@mail.alporthouse.com>
2018-01-05 19:37 ` Alexandru Chirvasitu
[not found] ` <151518186129.6838.5497512563650996948@mail.alporthouse.com>
2018-01-05 19:58 ` Alexandru Chirvasitu
[not found] ` <151518256891.6838.7870621097092357743@mail.alporthouse.com>
2018-01-05 20:08 ` Alexandru Chirvasitu
2018-01-05 22:05 ` Alexandru Chirvasitu
2018-01-05 22:24 ` Alexandru Chirvasitu
[not found] ` <151523540026.6838.8552050096058843898@mail.alporthouse.com>
2018-01-06 13:24 ` Alexandru Chirvasitu
2018-01-06 16:38 ` Alexandru Chirvasitu
[not found] ` <151526009137.23681.11777101661125249780@mail.alporthouse.com>
2018-01-06 18:44 ` Alexandru Chirvasitu
[not found] ` <151527210085.23681.13693584447068529774@mail.alporthouse.com>
2018-01-06 21:01 ` Alexandru Chirvasitu
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=20180103163131.GD2118@chirva-void \
--to=achirvasub@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox