All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: New " Unclaimed read from register 0x1f0034" in 4.12-rc1
Date: Fri, 04 Aug 2017 15:25:56 +0300	[thread overview]
Message-ID: <87vam3frjf.fsf@nikula.org> (raw)
In-Reply-To: <09ba5618-d4f0-0fbf-fe13-220157900212@redhat.com>

On Thu, 18 May 2017, Hans de Goede <hdegoede@redhat.com> wrote:
> Ok, so after rebuilding everything I get more sensible results,
> the "RPM wakelock ref not held during HW access" error now is
> the same one as I reported before in the
> "New "RPM wakelock ref not held during HW access" in 4.12-rc1 ?"
> thread. Now that I can reproduce it again, I will try the fixes
> suggested there.
>
> The "Unclaimed read from register 0x1f0034" error now has this
> stacktrace:

Replying to an old mail, the bug report is
https://bugs.freedesktop.org/show_bug.cgi?id=101705

BR,
Jani.


>
> [   56.955016] PM: early resume of devices complete after 1068.631 msecs
> [   56.956396] pcieport 0000:00:1c.0: System wakeup disabled by ACPI
> [   56.957697] rtc_cmos 00:04: System wakeup disabled by ACPI
> [   56.958261] Suspended for 0.888 seconds
> [   56.964250] Unclaimed read from register 0x1f0034
> [   56.964347] ------------[ cut here ]------------
> [   56.964428] WARNING: CPU: 2 PID: 1799 at drivers/gpu/drm/i915/intel_uncore.c:801 __unclaimed_reg_debug+0x4e/0x60 [i915]
> ...
> [   56.964590] Workqueue: events_unbound async_run_entry_fn
> [   56.964594] task: ffff89ad698b0000 task.stack: ffff9ba401454000
> [   56.964662] RIP: 0010:__unclaimed_reg_debug+0x4e/0x60 [i915]
> ...
> [   56.964688] Call Trace:
> [   56.964758]  fwtable_read32+0x17a/0x1d0 [i915]
> [   56.964818]  vlv_program_watermarks+0x3c4/0x610 [i915]
> [   56.964883]  ? intel_hdmi_get_hw_state+0x27/0xd0 [i915]
> [   56.964941]  vlv_optimize_watermarks+0x95/0xb0 [i915]
> [   56.965008]  intel_atomic_commit_tail+0x2e2/0x1030 [i915]
> [   56.965016]  ? tracing_record_cmdline+0x32/0x120
> [   56.965022]  ? __schedule+0x23e/0x860
> [   56.965090]  intel_atomic_commit+0x399/0x4b0 [i915]
> [   56.965125]  ? drm_atomic_check_only+0x37f/0x540 [drm]
> [   56.965155]  drm_atomic_commit+0x4b/0x50 [drm]
> [   56.965174]  drm_atomic_helper_commit_duplicated_state+0xc2/0xd0 [drm_kms_helper]
> [   56.965245]  __intel_display_resume+0x85/0xc0 [i915]
> [   56.965312]  intel_display_resume+0xf7/0x120 [i915]
> [   56.965370]  i915_drm_resume+0xe1/0x180 [i915]
> [   56.965427]  i915_pm_resume+0x1e/0x30 [i915]
> [   56.965434]  pci_pm_resume+0x65/0xa0
> [   56.965440]  dpm_run_callback+0x57/0x140
> [   56.965444]  ? pci_pm_thaw+0x90/0x90
> [   56.965447]  device_resume+0xe1/0x200
> [   56.965450]  async_resume+0x1d/0x50
> [   56.965455]  async_run_entry_fn+0x39/0x170
> [   56.965460]  process_one_work+0x193/0x3c0
> ...
> [   57.062736] PM: resume of devices complete after 107.709 msecs
> [   57.063468] PM: resume devices took 0.108 seconds
> [   57.063478] PM: Finishing wakeup.
>
> Regards,
>
> Hans
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-08-04 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 12:20 New " Unclaimed read from register 0x1f0034" in 4.12-rc1 Hans de Goede
2017-05-18 12:31 ` Chris Wilson
2017-05-18 12:52   ` Hans de Goede
2017-08-04 12:25     ` Jani Nikula [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=87vam3frjf.fsf@nikula.org \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=hdegoede@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.