From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tuncer Ayaz <tuncer.ayaz@gmail.com>
Cc: alexander.levin@verizon.com,
"daniel.vetter\@intel.com" <daniel.vetter@intel.com>,
"seanpaul\@chromium.org" <seanpaul@chromium.org>,
"airlied\@linux.ie" <airlied@linux.ie>,
"dri-devel\@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable\@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 4.1 EOL
Date: Wed, 15 Nov 2017 12:04:47 +0200 [thread overview]
Message-ID: <87zi7n7t8g.fsf@intel.com> (raw)
In-Reply-To: <CAOvwQ4iSf=Yic=sw+DEbFqG6xz9C-L4qOCLQqgq=ii9QjTkXmg@mail.gmail.com>
On Tue, 14 Nov 2017, Tuncer Ayaz <tuncer.ayaz@gmail.com> wrote:
> On 11/14/17, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>>
>> Tuncer, where's your bug report? Can't find one. Please file your
>> bug at the fdo bugzilla.
>
> I'm sorry if this wasn't clear.
>
> I didn't file a bug report since others have already done so,
> reporting the same symptoms. I did sign up yesterday to confirm this
> in the most recent bug report. And I don't think it makes sense to
> re-file the exact same report.
>
> The way I arrived there is via another post in a forum post related to
> x220 regressions, but it doesn't look exclusive to Sandybridge GPUs.
The freedesktop.org bugs you reference are for rather different
platforms than yours. There's nothing there to indicate v4.1 being the
last known good kernel like for you. There is no exact same report.
Please file the bug. Please run v4.14 or drm-tip branch from [1]. Please
remove all other module parameters, but add drm.debug=14, and attach the
dmesg from boot to the problem. Please attach the GPU error state if you
get a GPU hang. Please let us decide if we've seen the bug before or
not.
We've been continuously improving our CI and test assets and expanding
the hardware pool we run the tests on for years now. Even so, bugs
obviously slip through. And it's really *really* hard to revert anything
or fix regressions when we get the reports about two years or a dozen
kernel releases after we've broken stuff. :(
BR,
Jani.
[1] https://cgit.freedesktop.org/drm/drm-tip
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-11-15 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOvwQ4i_VTLg_P-mCTesTvUENYmtix1MfbmFQ=WTC6UUT-DroA@mail.gmail.com>
[not found] ` <20171111200025.hz6zbcqy7uacqd2s@sasha-lappy>
[not found] ` <CAOvwQ4hsy1CSKGCwm_Y+j-VGpmXMAF_vhg+WnifphhxVd3ur8A@mail.gmail.com>
2017-11-13 21:00 ` 4.1 EOL alexander.levin
2017-11-14 8:46 ` Jani Nikula
2017-11-14 21:41 ` Tuncer Ayaz
2017-11-15 10:04 ` Jani Nikula [this message]
2017-11-15 17:00 ` Tuncer Ayaz
2017-11-16 9:13 ` Jani Nikula
2017-11-17 7:42 ` Tuncer Ayaz
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=87zi7n7t8g.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=alexander.levin@verizon.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tuncer.ayaz@gmail.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;
as well as URLs for NNTP newsgroup(s).