Bug 38122 - 3.0-rc3 WARNING: at drivers/gpu/drm/i915/i915_drv.c:340 gen6_gt_force_wake_put+0x29/0x52 [i915]()
Summary: 3.0-rc3 WARNING: at drivers/gpu/drm/i915/i915_drv.c:340 gen6_gt_force_wake_pu...
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri-intel@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks: 7216 36912
  Show dependency tree
 
Reported: 2011-06-23 18:17 UTC by Maciej Rutecki
Modified: 2011-06-27 19:17 UTC (History)
6 users (show)

See Also:
Kernel Version: 3.0-rc3
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
cropped syslog that with a suspend cycle including those messages (165.82 KB, text/plain)
2011-06-24 20:26 UTC, Martin Steigerwald
Details

Description Maciej Rutecki 2011-06-23 18:17:02 UTC
Subject    : 3.0-rc3 WARNING: at drivers/gpu/drm/i915/i915_drv.c:340 gen6_gt_force_wake_put+0x29/0x52 [i915]()
Submitter  : "Kan-Ru Chen" <kanru@kanru.info>
Date       : 2011-06-14 12:12
Message-ID : 874o3sd33i.fsf@isil.kanru.info
References : http://marc.info/?l=linux-kernel&m=130805412314680&w=2

This entry is being used for tracking a regression from 2.6.39. Please don't
close it until the problem is fixed in the mainline.
Comment 1 Martin Steigerwald 2011-06-24 20:20:18 UTC
See also:

Subject    : WARNING: at drivers/gpu/drm/i915/i915_drv.c:344 gen6_gt_force_wake_put+0x58/0x60()
Submitter  : Jens Axboe <jaxboe@fusionio.com>
Date       : 30.05.2011 20:32
Message-ID : <4DE3E2C9.6060207@fusionio.com>
References : https://lkml.org/lkml/2011/5/30/261


As well as:

Bug 712593 - [abrt] kernel: WARNING: at drivers/gpu/drm/i915/i915_drv.c:322 gen6_gt_force_wake_get+0xe4/0xf0(): TAINTED Warning Issued
https://bugzilla.redhat.com/show_bug.cgi?id=716372


I can confirm this on my new ThinkPad T520 with Intel SandyBridge GPU:

martin@merkaba:~> cat /proc/version
Linux version 3.0.0-rc4-amd64 (Debian 3.0.0~rc4-1~experimental.1) (maks@debian.org) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Tue Jun 21 13:22:03 UTC 2011
martin@merkaba:~> lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)


Has been in 3.0.0-rc3 and according to Jens in 3.0.0-rc1 already.

Did certainly not happen in 2.6.39-2-amd64. I am using Debian GNU/Linux kernels at the moment, but that should not matter.

It happens on every suspend-to-disk or resume-from-disk - a lot of them. It did not see it on regular boot or on suspend-to-ram.

I have seen no other effect, so this might just be some quite verbose debugging message?
Comment 2 Martin Steigerwald 2011-06-24 20:26:46 UTC
Created attachment 63432 [details]
cropped syslog that with a suspend cycle including those messages

It seems on resume the messages come before the resume kernel switches to the hibernated kernel and are thus not in the logs.
Comment 3 Martin Steigerwald 2011-06-24 20:31:45 UTC
Hmmm, I am not so sure about my assumption on whether those messages are from suspend to resume. See for yourself. Thanks.
Comment 4 Rafael J. Wysocki 2011-06-26 21:37:08 UTC
Date : 2011-06-14 12:12
Comment 5 Keith Packard 2011-06-26 22:40:08 UTC
This should be fixed in 483f1798998ede75b2575cc1813c3d89ba64a34e which has been merged to master.
Comment 6 Rafael J. Wysocki 2011-06-27 19:17:52 UTC
On Monday, June 27, 2011, Jens Axboe wrote:
> On 2011-06-26 23:23, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.39.  Please verify if it still should be listed and let the
> tracking team
> > know (either way).
> > 
> > 
> > Bug-Entry   : http://bugzilla.kernel.org/show_bug.cgi?id=38122
> > Subject             : 3.0-rc3 WARNING: at
> drivers/gpu/drm/i915/i915_drv.c:340 gen6_gt_force_wake_put+0x29/0x52 [i915]()
> > Submitter   : Jens Axboe <jaxboe@fusionio.com>
> > Date                : 2011-06-14 12:12 (13 days old)
> 
> By the looks of it, commit 483f1798 should fix it.

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