[drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.

[Thomas Hotz]

I always get this error when I start up my Thinkpad Edge E530. This error was introduced with kernel 3.6.

[drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.7.0-2-generic 3.7.0-2.8
ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
Uname: Linux 3.7.0-2-generic x86_64
ApportVersion: 2.6.2-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thomas 1723 F.... pulseaudio
Date: Sun Nov 18 15:37:02 2012
HibernationDevice: RESUME=UUID=2ed6d9e9-3bcb-43c5-83a8-6e1160e90e8e
InstallationDate: Installed on 2012-11-15 (2 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: LENOVO 3259HLG
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=3896c606-f33c-4988-b0b5-2bed433a4910 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.7.0-2-generic N/A
 linux-backports-modules-3.7.0-2-generic N/A
 linux-firmware 1.97
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: H0ET35WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3259HLG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrH0ET35WW(1.17):bd07/25/2012:svnLENOVO:pn3259HLG:pvrThinkPadEdge:rvnLENOVO:rn3259HLG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3259HLG
dmi.product.version: ThinkPad Edge
dmi.sys.vendor: LENOVO

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc6-raring/

[Joseph Salisbury (jsalisbury)]

I'd like to perform a kernel bisect if this bug still exists in v3.7-rc6.

[Thomas Hotz (thotz-deactivatedaccount)]

I was able to reproduce the bug with the kernel from the mainline ppa v3.7-rc6.

[Joseph Salisbury (jsalisbury)]

I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

v3.5.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7-quantal/
v3.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/
v3.7-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

[Thomas Hotz (thotz-deactivatedaccount)]

Maybe you should look here:

http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/15041

[Joseph Salisbury (jsalisbury)]

Thanks for the pointer. I don't see that this patch was accepted into the mainline tree as of yet.

[Thomas Hotz (thotz-deactivatedaccount)]

Joseph as you can see from gmane there is the patch you would simply have to add, but I don't know how to do this.

[Hendy Irawan (ceefour)]

Still happens on Linux amanah.dev 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 19:40:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

This log message is happening regularly, occasionally up to 6 times a second:

[ 2528.142604] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2528.162762] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2528.171561] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2528.763476] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2529.237792] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2530.242584] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2530.949200] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2531.800353] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.009235] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.015757] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.026394] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.031999] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.043710] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.051739] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.109300] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.115821] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.131006] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.137830] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2532.147635] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2535.393405] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2535.402836] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2535.603173] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2538.541232] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2541.393475] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2541.427454] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2541.438513] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2541.444745] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 2541.468727] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear...

[Thomas Hotz (thotz-deactivatedaccount)]

For me this bug is fixed. Maybe you should create a new bug report. It's currently a problem to work here on your specific bug. Thank you!

[Hendy Irawan (ceefour)]

This error message seems to be completely gone after upgrading from default raring kernel (3.8.0.29.47) to the saucy one:

Linux amanah.dev 3.11.0-4-generic #9-Ubuntu SMP Mon Aug 26 15:21:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

although with the saucy kernel I got a strange dmesg : (where should I report this?)

[ 65.004941] ------------[ cut here ]------------
[ 65.004970] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.11.0/net/sched/sch_generic.c:260 dev_watchdog+0x26a/0x280()
[ 65.004971] NETDEV WATCHDOG: usb0 (rndis_host): transmit queue 0 timed out
[ 65.004972] Modules linked in: btrfs(F) raid6_pq(F) zlib_deflate(F) xor(F) ufs(F) qnx4 hfsplus hfs minix ntfs msdos(F) jfs xfs(F) libcrc32c(F) reiserfs ext2(F) kvm_intel(F) kvm(F) bnep rfcomm bluetooth arc4(F) snd_hda_codec_hdmi snd_hda_codec_via snd_hda_intel rt2800usb snd_hda_codec rt2x00usb rt2800lib rt2x00lib snd_hwdep(F) snd_pcm(F) mac80211 snd_page_alloc(F) gpio_ich ppdev(F) snd_seq_midi(F) snd_seq_midi_event(F) cfg80211 snd_rawmidi(F) crc_ccitt(F) snd_seq(F) rndis_host cdc_ether snd_seq_device(F) snd_timer(F) usbnet parport_pc(F) psmouse(F) mii(F) snd(F) serio_raw(F) soundcore(F) mei_me mei lpc_ich mac_hid lp(F) parport(F) hid_generic usbhid hid i915 atl1c video(F) i2c_algo_bit drm_kms_helper ahci(F) drm libahci(F)
[ 65.005004] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GF 3.11.0-4-generic #9-Ubuntu
[ 65.005005] Hardware name: BIOSTAR Group H61MHB/H61MHB, BIOS 4.6.4 07/26/2012
[ 65.005006] 0000000000000009 ffff88023fa03d88 ffffffff816f0f71 ffff88023fa03dd0
[ 65.005008] ffff88023fa03dc0 ffffffff81061cfd ffff88022dba0000 0000000000000000
[ 65.005010] 0000000000000000 ffff88022d2ff880 ffff88022d2ff800 ffff88023fa03e20
[ 65.005012] Call Trace:
[ 65.005014] <IRQ> [<ffffffff816f0f71>] dump_stack+0x45/0x56
[ 65.005025] [<ffffffff81061cfd>] warn_slowpath_common+0x7d/0xa0
[ 65.005027] [<ffffffff81061d6c>] warn_slowpath_fmt+0x4c/0x50
[ 65.005031] [<ffffffff81619f0a>] dev_watchdog+0x26a/0x280
[ 65.005033] [<ffffffff81619ca0>] ? dev_deactivate_queue.constprop.32+0x60/0x60
[ 65.005036] [<ffffffff8106e7e6>] call_timer_fn+0x36/0x110
[ 65.005038] [<ffffffff81619ca0>] ? dev_deactivate_queue.constprop.32+0x60/0x60
[ 65.005041] [<ffffffff8106f8bd>] run_timer_softirq+0x1fd/0x2b0
[ 65.005043] [<ffffffff810672d7>] __do_softirq+0xf7/0x240
[ 65.005049] [<ffffffff810675cd>] irq_exit+0xcd/0xe0
[ 65.005052] [<ffffffff817031c5>] smp_apic_timer_interrupt+0x45/0x60
[ 65.005055] [<ffffffff81701b5d>] apic_timer_interrupt+0x6d/0x80
[ 65.005056] <EOI> [<ffffffff8159cdd2>] ? cpuidle_enter_state+0x52/0xc0
[ 65.005062] [<ffffffff8159cf09>] cpuidle_idle_call+0xc9/0x210
[ 65.005066] [<ffffffff8101ba2e>] arch_cpu_idle+0xe/0x30
[ 65.005070] [<ffffffff810b56ee>] cpu_startup_entry+0xce/0x280
[ 65.005080] [<ffffffff816e0287>] rest_init+0x77/0x80
[ 65.005084] [<ffffffff81d28efc>] start_kernel+0x40f/0x41b
[ 65.005086] [<ffffffff81d288f6>] ? repair_env_string+0x5c/0x5c
[ 65.005089] [<ffffffff81d28120>] ? early_idt_handlers+0x120/0x120
[ 65.005091] [<ffffffff81d285de>] x86_64_start_reservations+0x2a/0x2c
[ 65.005093] [<ffffffff81d2...