public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: linux@eikelenboom.it, Daniel Vetter <daniel.vetter@intel.com>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] Linux 4.8-rc?: WARNING: at drivers/gpu/drm/i915/intel_pm.c:7866 sandybridge_pcode_write Missing switch case (16) in gen6_check_mailbox_status
Date: Tue, 06 Sep 2016 12:25:11 +0300	[thread overview]
Message-ID: <87mvjlxtvs.fsf@intel.com> (raw)
In-Reply-To: <a6921c29362d397a9fa5315c40cf61a7@eikelenboom.it>

On Tue, 06 Sep 2016, linux@eikelenboom.it wrote:
> L.S.,
>
> Since one of the last 4.8 RC's i'm getting the warning below when 
> booting on my sandybridge based thinkpad.
>  From what it seems the machine still works fine though.

What does 'lspci -nns 2' say for you?

BR,
Jani.


>
> --
> Sander
>
> [    2.846265] ------------[ cut here ]------------
> [    2.846280] WARNING: CPU: 0 PID: 4 at 
> drivers/gpu/drm/i915/intel_pm.c:7866 sandybridge_pcode_write+0x104/0x1e0
> [    2.846282] Missing switch case (16) in gen6_check_mailbox_status
> [    2.846284] Modules linked in:
> [    2.846289] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 
> 4.8.0-rc5-x220-20160905+ #1
> [    2.846290] Hardware name: LENOVO 42912ZU/42912ZU, BIOS 8DET69WW 
> (1.39 ) 07/18/2013
> [    2.846297] Workqueue: events intel_gen6_powersave_work
> [    2.846302]  0000000000000000 ffffffff8138bd84 ffff88030fd7bd78 
> 0000000000000000
> [    2.846305]  ffffffff81062d84 ffff88030d490000 ffff88030fd7bdc8 
> 0000000000000000
> [    2.846308]  ffff88030d49a438 ffff88030d498830 0000000000000000 
> ffffffff81062dea
> [    2.846309] Call Trace:
> [    2.846319]  [<ffffffff8138bd84>] ? dump_stack+0x5c/0x78
> [    2.846324]  [<ffffffff81062d84>] ? __warn+0xb4/0xd0
> [    2.846328]  [<ffffffff81062dea>] ? warn_slowpath_fmt+0x4a/0x50
> [    2.846333]  [<ffffffff814edf44>] ? 
> sandybridge_pcode_write+0x104/0x1e0
> [    2.846338]  [<ffffffff814eefd3>] ? 
> intel_gen6_powersave_work+0x2a3/0x1400
> [    2.846344]  [<ffffffff810781ea>] ? process_one_work+0x1ba/0x3d0
> [    2.846348]  [<ffffffff81078445>] ? worker_thread+0x45/0x4e0
> [    2.846351]  [<ffffffff81078400>] ? process_one_work+0x3d0/0x3d0
> [    2.846355]  [<ffffffff8107d678>] ? kthread+0xb8/0xd0
> [    2.846362]  [<ffffffff817cc8df>] ? ret_from_fork+0x1f/0x40
> [    2.846365]  [<ffffffff8107d5c0>] ? kthread_worker_fn+0x180/0x180
> [    2.846368] ---[ end trace da7b2ca8a6654bfa ]---
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

  parent reply	other threads:[~2016-09-06  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  7:49 Linux 4.8-rc?: WARNING: at drivers/gpu/drm/i915/intel_pm.c:7866 sandybridge_pcode_write Missing switch case (16) in gen6_check_mailbox_status linux
2016-09-06  9:12 ` [Intel-gfx] " Jani Nikula
2016-09-06  9:25 ` Jani Nikula [this message]
2016-09-06 10:11   ` linux
2016-09-07 14:49     ` Jani Nikula
2016-09-07 21:18       ` Sander Eikelenboom

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=87mvjlxtvs.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    /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