Bug 203557 - igt@runner@aborted - fail - TAINT_BAD_PAGE: Bad page reference or an unexpected page flags
Summary: igt@runner@aborted - fail - TAINT_BAD_PAGE: Bad page reference or an unexpect...
Status: RESOLVED INVALID
Alias: None
Product: Memory Management
Classification: Unclassified
Component: Page Allocator (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Andrew Morton
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-09 07:44 UTC by Lakshminarayana Vudum
Modified: 2020-02-28 17:23 UTC (History)
0 users

See Also:
Kernel Version: 5.1.0-rc7
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Dmesg log (1.13 MB, text/plain)
2019-05-09 07:44 UTC, Lakshminarayana Vudum
Details
Run log (2.81 KB, text/plain)
2019-05-09 07:46 UTC, Lakshminarayana Vudum
Details

Description Lakshminarayana Vudum 2019-05-09 07:44:53 UTC
Created attachment 282683 [details]
Dmesg log

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_272/fi-icl-y/igt@runner@aborted.html

Aborting.
Previous test: kms_plane_scaling (pipe-c-scaler-with-clipping-clamping)
Next test: i915_pm_rps (min-max-config-idle)

Kernel badly tainted (0x60) (check dmesg for details):
	(0x20) TAINT_BAD_PAGE: Bad page reference or an unexpected page flags.

Above igt test (igt@runner@aborted) has been failed on ICL platform the platform which is yet to release. The failure happens only on one particular machine fi-icl-y.
Comment 1 Lakshminarayana Vudum 2019-05-09 07:46:18 UTC
This bug was originally created https://bugs.freedesktop.org/show_bug.cgi?id=110586. I was asked to create a new bug under memory management. Attched Run log and dmesg.
Comment 2 Lakshminarayana Vudum 2019-05-09 07:46:44 UTC
Created attachment 282685 [details]
Run log
Comment 3 Lakshminarayana Vudum 2019-05-13 06:02:28 UTC
oops sorry, need to look at this more first internally. Closing this bug as invalid for now.
Comment 4 cibuglog 2020-02-28 17:23:00 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

Note You need to log in before you can comment on or make changes to this bug.