<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@runner@aborted - fail - TAINT_BAD_PAGE: Bad page reference or an unexpected page flags."
href="https://bugs.freedesktop.org/show_bug.cgi?id=110586#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@runner@aborted - fail - TAINT_BAD_PAGE: Bad page reference or an unexpected page flags."
href="https://bugs.freedesktop.org/show_bug.cgi?id=110586">bug 110586</a>
from <span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span></b>
<pre>Please don't do this, by usual bug filing standards our reports here are
completely unactionable and this might as well sound like a bad machine or our
driver bug.
If you want to file a bug with a foreign subsystem please make damn sure you
have solid proof it's a bug with them, and not just a hunch.
Quick comment from Dave Airlie on irc:
* airlied also guesses it's memory corrupt or some pages ending up in wrong
state
<airlied> I doubt mm is at fault
<danvet> yeah
<airlied> we marked something unvevictable and freed it?
See the dmesg backtrace
<4>[ 114.390971] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set
<1>[ 114.390972] bad because of flags: 0x100000(unevictable)
drm/i915 does mark pages as unevictable, so this very much could be our own
bug. Or bad hw.
Internally it's not a big deal if our triaging doesn't really analyze the bug,
but that stops being fun as soon as we involve non-intel people.
Lakshmi, can you pls close the kernel bugzilla entry with a quick "oops sry,
need to look at this more first internally".
Thanks, Daniel</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>