Ticket #2303 (new defect)

Opened 10 years ago

regulator_disable: not in use by this consumer

Reported by: lindi Owned by: Nytowl
Priority: normal Milestone:
Component: Distro Version: unspecified
Severity: minor Keywords: kernel gps regulator poweron power_on
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:


Steps to reproduce:
1) Not quite sure. Log shows I did

Aug 2 22:35:30 ginger sudo: lindi : TTY=pts/1 ; PWD=/home/lindi ; USER=root ; COMMAND=/bin/sh -c echo 0 > /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.7/neo1973-pm-gps.0/power_on

but this does not happen every time.

Expected results:
1) gps is powered down

Actual results:
1) gps is powered down but kernel prints

 regulator_disable: not in use by this consumer
 ------------[ cut here ]------------
 WARNING: at /local/lindi/neolinux/drivers/regulator/core.c:1108 regulator_disable+0x38/0x88()
 Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc fuse snd_soc_neo1973_gta02_wm8753 snd_soc_s3c24xx_i2s snd_soc_s3c24xx g_ether s3c2410_wdt ar6000 snd_soc_wm8753 s3cmci snd_soc_core snd_pcm snd_timer snd_page_alloc snd
 [<c02a9c5c>] (dump_stack+0x0/0x14) from [<c004ffd8>] (warn_slowpath+0x64/0x98)
 [<c004ff74>] (warn_slowpath+0x0/0x98) from [<c0180cf0>] (regulator_disable+0x38/0x88)
  r3:c6de7e18 r2:00000000
  r7:c0389238 r6:00000002 r5:00000000 r4:c799f5e0
 [<c0180cb8>] (regulator_disable+0x0/0x88) from [<c003e364>] (gps_pwron_set+0x98/0xa8)
  r5:c03b226c r4:00000000
 [<c003e2cc>] (gps_pwron_set+0x0/0xa8) from [<c003e500>] (power_gps_write+0x60/0xa4)
  r5:00000000 r4:c03336a2
 [<c003e4a0>] (power_gps_write+0x0/0xa4) from [<c019fca4>] (dev_attr_store+0x28/0x2c)
  r6:c6c0d160 r5:00000002 r4:c79a521c
 [<c019fc7c>] (dev_attr_store+0x0/0x2c) from [<c00f1cb0>] (sysfs_write_file+0x114/0x14c)
 [<c00f1b9c>] (sysfs_write_file+0x0/0x14c) from [<c00ad54c>] (vfs_write+0xb8/0x148)
 [<c00ad494>] (vfs_write+0x0/0x148) from [<c00ad6a4>] (sys_write+0x4c/0x7c)
  r7:00000004 r6:c1338760 r5:00000000 r4:00000000
 [<c00ad658>] (sys_write+0x0/0x7c) from [<c002eea0>] (ret_fast_syscall+0x0/0x2c)
  r6:00000001 r5:00000002 r4:00028238
 ---[ end trace 9a4e03ca1325e3f3 ]---

More info:
1) I am using andy-tracking 9ecc089861ab238e with wifi and ramconsole patches (should not affect this).

Note: See TracTickets for help on using tickets.