From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Saarinen, Jani" <jani.saarinen@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] BUG: i915: flickering/temporary artifacts after resume
Date: Mon, 7 Nov 2022 11:48:44 +0000 [thread overview]
Message-ID: <Y2jwnKfG9xFpMTHS@shell.armlinux.org.uk> (raw)
In-Reply-To: <DM8PR11MB56555D7E8598D31998F5010AE03C9@DM8PR11MB5655.namprd11.prod.outlook.com>
On Mon, Nov 07, 2022 at 09:29:33AM +0000, Saarinen, Jani wrote:
> Hi Russell,
> Can you make new gitlab: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs ?
Hi,
Unfortunately, I can't get any more information, and trying to get a
photo of the problem is utterly impossible, beacuse it's almost always
a momentary corruption - out of all the cases, I have only seen it
remain on-screen once.
Also, it can take months of suspend/resume cycles for it to occur,
which makes it difficult to reproduce using the "latest" kernel -
beacuse by the time the latest kernel has shown the problem, there's
a more modern kernel!
Using the intel reg dumper may provide some useful information.
That said, running it from the debian stable repository gives me:
(intel_reg:338236) intel_mmio-CRITICAL: Test assertion failure function
intel_mmio_use_pci_bar, file ../lib/intel_mmio.c:146:
(intel_reg:338236) intel_mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_reg:338236) intel_mmio-CRITICAL: Last errno: 1, Operation not
permitted
(intel_reg:338236) intel_mmio-CRITICAL: Couldn't map MMIO region
Test (null) failed.
**** DEBUG ****
(intel_reg:338236) intel_chipset-DEBUG: Test requirement passed: pci_dev
(intel_reg:338236) intel_mmio-CRITICAL: Test assertion failure function
intel_mmio_use_pci_bar, file ../lib/intel_mmio.c:146:
(intel_reg:338236) intel_mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_reg:338236) intel_mmio-CRITICAL: Last errno: 1, Operation not
permitted
(intel_reg:338236) intel_mmio-CRITICAL: Couldn't map MMIO region
(intel_reg:338236) igt_core-INFO: Stack trace:
(intel_reg:338236) igt_core-INFO: #0 [__igt_fail_assert+0x113]
(intel_reg:338236) igt_core-INFO: #1 [intel_mmio_use_pci_bar+0xc4]
(intel_reg:338236) igt_core-INFO: #2 [intel_register_access_init+0x1b]
(intel_reg:338236) igt_core-INFO: #3 [<unknown>+0xec025c3a]
(intel_reg:338236) igt_core-INFO: #4 [<unknown>+0xec0246f6]
(intel_reg:338236) igt_core-INFO: #5 [__libc_start_main+0xea]
(intel_reg:338236) igt_core-INFO: #6 [<unknown>+0xec0247ba]
**** END ****
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2022-11-07 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 15:17 [Intel-gfx] BUG: i915: flickering/temporary artifacts after resume Russell King (Oracle)
2022-11-07 9:29 ` Saarinen, Jani
2022-11-07 11:48 ` Russell King (Oracle) [this message]
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=Y2jwnKfG9xFpMTHS@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.