Reply
Thread Tools
Posts: 9 | Thanked: 1 time | Joined on Sep 2013
#11
Deleted everything in ~/.thumbnails, ran tracker-processes -r and apt-get remove kernel-power-settings. Put it into offline mode and power-cycled. Still pretty much the same results.
Code:
Powertop 1.13.3
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 20691us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |   0.2% |          |  1150 MHz |   nan% |
     C1 |   0.0% |          | 
     C2 |  18.3% |  103.9ms | 
     C3 |   2.8% |  284.1ms | 
     C4 |  78.6% | 2948.7ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     56 |        164 |           INTC | i2c_omap
     57 |         58 |           INTC | i2c_omap
     11 |         44 |           INTC | prcm
     37 |         26 |           INTC | gp

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
    750 |         12 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
      0 |         10 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
     38 |          9D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    750 |          6 |      bme_RX-51 | schedule_timeout (process_timeout)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    750 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    711 |          2 |           dsme | do_nanosleep (hrtimer_wakeup)
    711 |          2 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
      0 |          1 |  <kernel core> | hrtimer_start (tick_sched_timer)
   1082 |          1 |          iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
    789 |          1 |           hald | schedule_hrtimeout_range (hrtimer_wakeup)
   1633 |          1 |       powertop | do_nanosleep (hrtimer_wakeup)

Power domain activity breakdown
Domain  | % of time spent in states
--------+---------+---------+---------+---------+----------
usbhost |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    sgx |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    per |OFF:   0%|RET:  99%|INA:   0%| ON:   0%| now:(ON)
    dss |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    cam |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
   core |OFF:   0%|RET:   0%|INA:   0%| ON: 100%| now:(ON)
   neon |OFF:  78%|RET:   2%|INA:  18%| ON:   0%| now:(ON)
    mpu |OFF:  78%|RET:   2%|INA:  18%| ON:   0%| now:(ON)
   iva2 |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)

Clock activity breakdown at end of period
Domain  | Active clocks
--------+---------------+---------------+------------------
   core |          SDRC | HSOTGUSB_IDLE |      OMAPCTRL 
        |     MAILBOXES |         UART2 |
  core3 |       USBTLL
   wkup |          GPT1 |       32KSYNC |         GPIO1 
        |          WDT1 |           SR1 |           SR2 
        |
  ckgen |          CORE |          PERI |           96M 
        |           48M |           12M |           54M 
        |      EMU_CORE |
    per |         GPIO2 |         GPIO3 |         GPIO4 
        |         GPIO5 |         GPIO6 |

Total wakeups   342,  11.4/s | IRQ  292,   9.7/s | Timers   50,   1.7/s
HW wakeups       44,   1.5/s |     Real gp_timers expired   26,   0.9/s
 
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#12
@Beeswax,

Are you using kernel-power? which version?
If so, please post the output of "kernel-config show" (as root).

Please post also the output of /etc/pmconfig.
Thank you.
 
Community Council | Posts: 680 | Thanked: 1,227 times | Joined on Sep 2010 @ Mbabane
#13
This is interesting, as I've noticed almost the same behaviour on mine. I'm on CSSU-S + KP52. Even though I'm on KP, I'm using default settings.
 
Posts: 9 | Thanked: 1 time | Joined on Sep 2013
#14
I'm currently running KP52 although I had KP51 when the problem started, I upgraded after it started hoping to fix it but it didn't.
I had to reinstall kernel-power-settings to get kernel-config back, this is what kernel-config show outputs.
Code:
current kernel configuration:
current frequency: 600
supported frequencies: 125 250 500 550 600 720 805 850 900 950 1000 1100 1150 
min. frequency: 250
max. frequency: 600
avoid frequencies: 125 
active frequencies: 250:38,180 500:48,360 550:48,400 600:42,430 720:54,430 805:54,430 850:54,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520 
SmartReflex VDD1=0, VDD2=0
governor ondemand: ignore nice load= 0, up threshold= 75, sampling rate= 150000, powersave bias= 0
And this is /etc/pmconfig;
Code:
# Power management configuration file
enable_off_mode 1
sleep_while_idle 1
sr_vdd1_autocomp 1
sr_vdd2_autocomp 1
clocks_off_while_idle 1
voltage_off_while_idle 1
scaling_governor ondemand
scaling_max_freq 600000
scaling_min_freq 125000
sleep_ind 1
EDIT::
Just remembered that I am unable to remove kernel-power as kernel-power-uninstall fails with the following message,
Code:
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 5 not upgraded.
Need to get 2046kB of archives.
After this operation, 0B of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  kernel-flasher kernel
E: There are problems and -y was used without --force-yes
Could forcing kernel and kernel-flasher to install restore the Nokia kernel?

Last edited by Beeswax; 2013-09-26 at 19:23.
 
peterleinchen's Avatar
Posts: 4,117 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#15
Do you have backup-menu installed?
And really want to know what is going on?

Just what I would do:
make a backup of rootfs and optfs, preferably on SD card
backup your MyDocs on PC
reflash completely (you may try first time only firmware, i.e. combined rootfs/optfs, but I'd suggest full flash eMMC also)
boot Maemo, let it opt (move parts from rootfs to optfs), let it settle (maybe tracker will run awhile)
and test it again.

If it still shows same weirdness, then it seems lile HW failure.
If not, I wish you good hunting (but no idea where/how to start)

Before restoring the backup, you need to install same kernel (kp52), else you will have a reboot loop.
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 
Posts: 9 | Thanked: 1 time | Joined on Sep 2013
#16
Welp.
Reflashed it with the stock kernel. Powertop shows the same usage of 100% on core. Also I'm now having problems with the touchscreen, it will randomly stop working and it can sometimes be for seconds or minutes. When it works its fine and as accurate as ever. So I'm guessing that somewhere there's a hardware fault which is a real shame as I've loved having this phone and I don't think there's anything even remotely like it out there.
Thanks for all your help guys but it seems like this was probably a lost cause.

tldr; phone borked, you're all great for trying.
 

The Following User Says Thank You to Beeswax For This Useful Post:
Community Council | Posts: 680 | Thanked: 1,227 times | Joined on Sep 2010 @ Mbabane
#17
I wonder if you're not giving up too quickly... what does `dmesg` indicate? syslog?

Also, when you say you reflashed.. you reflashed rootfs? did you restore anything? I ask because you could easily be having an issue with the modules (/lib/modules)

if it really is hardware, most likely going on IRC will let you contact those who know the N900 very well, and who might be able to help you hunt down the offending hardware. you might just find it's a silly thing, eg lost magnet, lol
 
Posts: 9 | Thanked: 1 time | Joined on Sep 2013
#18
I reflashed using "RX-51_2009SE_20.2010.36-2.203.1_PR_COMBINED_203_ARM.bin" and then reinstalled powertop to see what it was saying. From a quick google I assume to check syslog I need to install syslogd?
dmesg gives me nothing obvious other than a lot of this
Code:
[12499.185943] tsc2005 spi1.0: TSC not responding, resetting.
[12507.186004] tsc2005 spi1.0: TSC not responding, resetting.
[12515.186004] tsc2005 spi1.0: TSC not responding, resetting.
[12523.186126] tsc2005 spi1.0: TSC not responding, resetting.
[12531.186126] tsc2005 spi1.0: TSC not responding, resetting.
[12539.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12547.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12555.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12563.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12571.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12579.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12587.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12595.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12603.186218] tsc2005 spi1.0: TSC not responding, resetting.
[12611.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12619.186035] tsc2005 spi1.0: TSC not responding, resetting.
[12627.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12635.186065] tsc2005 spi1.0: TSC not responding, resetting.
[12643.186065] tsc2005 spi1.0: TSC not responding, resetting.
Google lead me here which is obviously why the touchscreen is not working correctly as the driver is constantly crashing for some reason.

If it is something in /lib/modules what would I need to be looking for?
 
peterleinchen's Avatar
Posts: 4,117 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#19
ksyslog(d) from tools repo.

It was a full reflash, right? Not only kernel?
Please do it again and flash also eMMC (first).
Do you have a SD card inside? Please remove and try again.
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#20
could potentially be an unseated ribbon cabe.

The ribbon that connects the screen to the main body can sometimes come loose. When it does, all sorts of weird **** happens.

Check yer ribbon cable before you fling that n900 in the trash.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 

The Following 2 Users Say Thank You to vi_ For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 21:01.