Bug 77941 - Bug with intel_pm fills my logs
Summary: Bug with intel_pm fills my logs
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: x86-64 Linux
: P3 normal
Assignee: Chris Wilson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-15 12:22 UTC by contact
Modified: 2014-06-16 09:35 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.14.6-1-ARCH
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description contact 2014-06-15 12:22:06 UTC 
This bug writes a trace in my logs every second and fills them dangerously..

Here is what is written every second:

juin 15 14:06:37 djipey-laptop kernel: WARNING: CPU: 2 PID: 492 at drivers/gpu/drm/i915/intel_pm.c:3019 gen6_set_rps+0x391/0x3e0 [i915]()
juin 15 14:06:37 djipey-laptop kernel: Modules linked in: fuse bluetooth 6lowpan_iphc msr bbswitch(O) nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter iptable_mangle ip_tables x_tables joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev mousedev media intel_rapl x86_pkg_temp_thermal arc4 intel_powerclamp iTCO_wdt iTCO_vendor_support kvm snd_hda_codec_hdmi mxm_wmi iwldvm crct10dif_pclmul snd_hda_codec_via led_class snd_hda_codec_generic mac80211 crc32_pclmul i915 crc32c_intel ghash_clmulni_intel iwlwifi aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel microcode snd_hda_codec snd_hwdep evdev cfg80211 mac_hid snd_pcm psmouse serio_raw i2c_i801 r8169 rtsx_pci_ms mii memstick lpc_ich rfkill drm_kms_helper snd_timer snd soundcore battery drm tpm_tis
juin 15 14:06:37 djipey-laptop kernel:  video tpm wmi mei_me thermal ac intel_gtt i2c_algo_bit mei i2c_core shpchp button processor vboxnetflt(O) vboxnetadp(O) vboxdrv(O) coretemp hwmon ext4 crc16 mbcache jbd2 hid_logitech_dj usbhid hid sd_mod crc_t10dif crct10dif_common usb_storage rtsx_pci_sdmmc mmc_core atkbd libps2 ahci libahci libata scsi_mod ehci_pci xhci_hcd ehci_hcd rtsx_pci usbcore usb_common i8042 serio
juin 15 14:06:37 djipey-laptop kernel: CPU: 2 PID: 492 Comm: X Tainted: G        W  O 3.14.6-1-ARCH #1
juin 15 14:06:37 djipey-laptop kernel: Hardware name: CLEVO CO.                        W2xxHSQ                         /W2xxHSQ                         , BIOS 4.6.4 12/09/2011
juin 15 14:06:37 djipey-laptop kernel:  0000000000000000 00000000b8a62e31 ffff8801292d1b88 ffffffff81509d4e
juin 15 14:06:37 djipey-laptop kernel:  0000000000000000 ffff8801292d1bc0 ffffffff8106aa1d ffff8800c5e4c000
juin 15 14:06:37 djipey-laptop kernel:  0000000000000007 ffff8800c528e800 0000000000000000 ffff8800c528e800
juin 15 14:06:37 djipey-laptop kernel: Call Trace:
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff81509d4e>] dump_stack+0x4d/0x6f
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff8106aa1d>] warn_slowpath_common+0x7d/0xa0
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff8106ab4a>] warn_slowpath_null+0x1a/0x20
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa0a1cec1>] gen6_set_rps+0x391/0x3e0 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa0a1d28c>] gen6_rps_boost+0x4c/0x70 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa09cf783>] __wait_seqno+0x503/0x550 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa09d0399>] ? __i915_add_request+0x1f9/0x2b0 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa09da2ad>] ? i915_gem_do_execbuffer.isra.19+0x3ed/0x12a0 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff813fbcec>] ? sock_recvmsg+0x8c/0xd0
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff811ce4a0>] ? poll_select_copy_remaining+0x150/0x150
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff810b3ec0>] ? __wake_up_sync+0x20/0x20
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff812a8fa8>] ? __sg_page_iter_next+0x18/0x20
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa09d6a48>] ? i915_gem_pwrite_ioctl+0x168/0xad0 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa09d755a>] i915_gem_set_domain_ioctl+0x1aa/0x260 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa058ecf2>] drm_ioctl+0x4f2/0x600 [drm]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffffa09d73b0>] ? i915_gem_pwrite_ioctl+0xad0/0xad0 [i915]
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff81402c0f>] ? sock_getsockopt+0x14f/0x890
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff811cd860>] do_vfs_ioctl+0x2d0/0x4b0
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff811d7d0e>] ? __fget+0x6e/0xb0
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff811cdac1>] SyS_ioctl+0x81/0xa0
juin 15 14:06:37 djipey-laptop kernel:  [<ffffffff81517b29>] system_call_fastpath+0x16/0x1b
juin 15 14:06:37 djipey-laptop kernel: ---[ end trace df7483128c852178 ]---


And you can find a bit more infos ("journalctl --no-pager -b" performed after the boot) here: http://sprunge.us/LDfA
Comment 1 contact 2014-06-15 15:41:25 UTC 
Actually, the powerdown service, with (likely) this line was responsible:

for i in /sys/kernel/debug/dri/*/i915_max_freq; do opt "$i" 350; done

Bug solved.
Comment 2 Jani Nikula 2014-06-16 08:29:30 UTC 
(In reply to contact from comment #1)
> Actually, the powerdown service, with (likely) this line was responsible:
> 
> for i in /sys/kernel/debug/dri/*/i915_max_freq; do opt "$i" 350; done

Uhm, what? Where is this from exactly?
Comment 3 contact 2014-06-16 08:53:02 UTC 
Oh sorry, it's from the powerdown script. It should be located at /usr/bin/powerdown, on Archlinux.
Comment 4 Jani Nikula 2014-06-16 09:35:55 UTC 
We've added better bounds checks for debugfs in v3.15, which means you'll no longer see the warns in dmesg.

*However* the magic 350 in the powerdown service will still be as much bogus as it ever was. Maybe it was something that worked for the author's machine at some point in time, but really it's debugfs and all bets are off.

Similarly for various power tuning i915 module parameters (fbc, rc6, etc). They have safe per platform defaults for a reason.
Note You need to log in before you can comment on or make changes to this bug.