RE: qtmoko lagging after 2nd boot - was: qtmoko v28

2010-10-28 Thread Gennady Kupava
В Срд, 27/10/2010 в 23:48 +0200, Ugo Raffaele Piemontese пишет:
 Thank you everyone for your tips!
 
 Here you are some logs taken via ssh during a slowdown:
 
 1 (see attachments) - dmesg output
 2 (see attachments) - interrupts output (only s3c24xx-adc is growing fast)
 - time frame between them: 1 second
 3 - top screenshot: http://img168.imageshack.us/img168/2848/topmt.png
 

top, and interrupts seem fine. s3c24xx-adc count is ok too.

I don't know what's this:
[  210.165000] AR6000 disconnected
[  220.17] AR6000 disconnected
[  230.165000] AR6000 disconnected

May be it is ok, but why not to try to disable wifi and check if problem
remain?

Gennady.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


qtmoko lagging after 2nd boot - was: qtmoko v28

2010-10-27 Thread Ugo Raffaele Piemontese
Hi everyone,
I am writing here because I'm having some serious usability issues with 
the latest qtmoko version, v28.

After flashing it to NAND, its speed was impressive: ultra-fast boot, 
great responsiveness and absolutely no lags. I set up my wifi network, 
installed 2 or 3 packages and shutdown the phone since it was slowing down.
At first I tought this could be a RAM problem, but booting my Freerunner 
again after some time (~2 hours) I noticed a general slowness and 
frequent lags from the beginning.
For example, kinetic scrolling is now quite unresponsive (it stops and 
only after few seconds - 2 or 3 - completes the scrolling) and I can't 
write a text message because the keyboard takes a lot of time to reply 
to my input on the touchscreen. Btw, I am absolutely sure this is not a 
problem related to packages installed: they are all games or simple 
utilities. Also, logging service is off.

Is someone experiencing the same problems?

Kind regards,
Ugo Raffaele Piemontese

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: qtmoko lagging after 2nd boot - was: qtmoko v28

2010-10-27 Thread Radek Polak
On Wednesday 27 October 2010 12:14:44 Ugo Raffaele Piemontese wrote:

 Hi everyone,
 I am writing here because I'm having some serious usability issues with
 the latest qtmoko version, v28.
 
 After flashing it to NAND, its speed was impressive: ultra-fast boot,
 great responsiveness and absolutely no lags. I set up my wifi network,
 installed 2 or 3 packages and shutdown the phone since it was slowing down.
 At first I tought this could be a RAM problem, but booting my Freerunner
 again after some time (~2 hours) I noticed a general slowness and
 frequent lags from the beginning.
 For example, kinetic scrolling is now quite unresponsive (it stops and
 only after few seconds - 2 or 3 - completes the scrolling) and I can't
 write a text message because the keyboard takes a lot of time to reply
 to my input on the touchscreen. Btw, I am absolutely sure this is not a
 problem related to packages installed: they are all games or simple
 utilities. Also, logging service is off.
 
 Is someone experiencing the same problems?

Is it reproducible and always or just occasional? It would be worth to connect 
freerunner to PC and check from SSH if top shows some extra cpu usage or maybe 
there is some hint in dmesg.

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


RE: qtmoko lagging after 2nd boot - was: qtmoko v28

2010-10-27 Thread Ugo Raffaele Piemontese
On Wednesday 27 October 2010 13:10:43 Radek Polak wrote:


  Is it reproducible and always or just occasional? It would be worth to 
 connect
  freerunner to PC and check from SSH if top shows some extra cpu usage or 
 maybe
  there is some hint in dmesg.



Hi Radek,

top and dmesg show nothing interesting... Maximum cpu usage is about 40% and 
ram usage is 38% max.
Gpe process uses most resources during slowdowns (24% cpu, 27.7% ram).

Kind regards,
Ugo Raffaele Piemontese





___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


RE: qtmoko lagging after 2nd boot - was: qtmoko v28

2010-10-27 Thread Ugo Raffaele Piemontese
On Wednesday 27 October 2010 13:30:23 Ugo Raffaele Piemontese wrote:

  On Wednesday 27 October 2010 13:10:43 Radek Polak wrote:


   Is it reproducible and always or just occasional? It would be worth to 
 connect
   freerunner to PC and check from SSH if top shows some extra cpu usage or 
 maybe
   there is some hint in dmesg.



  Hi Radek,

  top and dmesg show nothing interesting... Maximum cpu usage is about 40% and 
 ram usage is 38% max.
  Gpe process uses most resources during slowdowns (24% cpu, 27.7% ram).


ERRATA CORRIGE

I double-checked, rebooting and connecting the Freerunner to my pc: during 
slowdowns QPE process (sorry, I wrote Gpe before) takes about 80% of cpu!
Is it regular? I hope not...

Kind regards,
Ugo Raffaele Piemontese


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: qtmoko lagging after 2nd boot - was: qtmoko v28

2010-10-27 Thread Radek Polak
On Wednesday 27 October 2010 13:56:36 Ugo Raffaele Piemontese wrote:

 ERRATA CORRIGE
 
 I double-checked, rebooting and connecting the Freerunner to my pc: during
 slowdowns QPE process (sorry, I wrote Gpe before) takes about 80% of cpu!
 Is it regular? I hope not...

No it looks like the problem, but hard to tell what is happening. One 
possibility is gdb and break the qpe process and see something from 
stacktrace, or maybe running strace could also tell what is happening. Anyway 
it's might be not easy :-(

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


RE: qtmoko lagging after 2nd boot - was: qtmoko v28

2010-10-27 Thread Ugo Raffaele Piemontese
Thank you everyone for your tips!

Here you are some logs taken via ssh during a slowdown:

1 (see attachments) - dmesg output
2 (see attachments) - interrupts output (only s3c24xx-adc is growing fast)
- time frame between them: 1 second
3 - top screenshot: http://img168.imageshack.us/img168/2848/topmt.png

Kind regards,
Ugo Raffaele Piemontese


[0.00] Linux version 2.6.34.2-v28 (ra...@rp-skunk) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #2 Thu Oct 21 21:50:20 CEST 2010
[0.00] CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
[0.00] CPU: VIVT data cache, VIVT instruction cache
[0.00] Machine: GTA02
[0.00] Memory policy: ECC disabled, Data cache writeback
[0.00] On node 0 totalpages: 32768
[0.00] free_area_init_node: node 0, pgdat c04068c0, node_mem_map c045b000
[0.00]   Normal zone: 256 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 32512 pages, LIFO batch:7
[0.00] CPU S3C2442B (id 0x32440aab)
[0.00] S3C24XX Clocks, Copyright 2004 Simtec Electronics
[0.00] S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
[0.00] CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[0.00] Kernel command line: loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro  mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(qi),0x0004(depr-ub-env),0x0080(kernel),0x000a(depr),0x0004(identity-ext2),0x0f6a(rootfs)  g_ether.dev_addr=00:1F:11:01:44:44 g_ether.host_addr=00:1F:11:01:44:45  rootfstype=ubifs  ubi.mtd=6,2048  root=ubi0:om-gta02-rootfs 
[0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
[0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[0.00] Memory: 128MB = 128MB total
[0.00] Memory: 125492k/125492k available, 5580k reserved, 0K highmem
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xfff0 - 0xfffe   ( 896 kB)
[0.00] DMA : 0xffc0 - 0xffe0   (   2 MB)
[0.00] vmalloc : 0xc880 - 0xe000   ( 376 MB)
[0.00] lowmem  : 0xc000 - 0xc800   ( 128 MB)
[0.00] modules : 0xbf00 - 0xc000   (  16 MB)
[0.00]   .init : 0xc0008000 - 0xc0029000   ( 132 kB)
[0.00]   .text : 0xc0029000 - 0xc03df000   (3800 kB)
[0.00]   .data : 0xc03e - 0xc0406ec0   ( 156 kB)
[0.00] Hierarchical RCU implementation.
[0.00] NR_IRQS:134
[0.00] irq: clearing pending ext status 000912f0
[0.00] irq: clearing pending ext status 000900d0
[0.00] irq: clearing subpending status 0180
[0.00] irq: clearing subpending status 0080
[0.00] timer tcon=, tcnt a2c1, tcfg 0200,, usec 1eb8
[0.00] Console: colour dummy device 80x30
[0.00] console [tty0] enabled
[0.00] console [ttySAC2] enabled
[0.00] Calibrating delay loop... 199.47 BogoMIPS (lpj=498688)
[0.095000] Mount-cache hash table entries: 512
[0.095000] CPU: Testing write buffer coherency: ok
[0.095000] devtmpfs: initialized
[0.10] regulator: core version 0.5
[0.105000] NET: Registered protocol family 16
[0.12] S3C Power Management, Copyright 2004 Simtec Electronics
[0.14] S3C2442: Initialising architecture
[0.14] S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
[0.14] DMA channel 0 at c8808000, irq 33
[0.14] DMA channel 1 at c8808040, irq 34
[0.14] DMA channel 2 at c8808080, irq 35
[0.14] DMA channel 3 at c88080c0, irq 36
[0.14] S3C244X: Clock Support, DVS off
[0.145000] s3c-adc s3c24xx-adc: attached adc driver
[0.145000] s3c24xx-pwm s3c24xx-pwm.0: tin at 2500, tdiv at 2500, tin=divclk, base 0
[0.145000] s3c24xx-pwm s3c24xx-pwm.1: tin at 2500, tdiv at 2500, tin=divclk, base 8
[0.145000] s3c24xx-pwm s3c24xx-pwm.2: tin at 833, tdiv at 833, tin=divclk, base 12
[0.145000] s3c24xx-pwm s3c24xx-pwm.3: tin at 833, tdiv at 833, tin=divclk, base 16
[0.22] bio: create slab bio-0 at 0
[0.225000] usbcore: registered new interface driver usbfs
[0.225000] usbcore: registered new interface driver hub
[0.23] usbcore: registered new device driver usb
[0.23] s3c-i2c s3c2440-i2c: slave address 0x10
[0.23] s3c-i2c s3c2440-i2c: bus frequency set to 97 KHz
[0.255000] pcf50633 0-0073: Probed device version 19 variant 132
[0.305000] wake enabled for irq 53
[0.36] regulator: auto: 3300 mV normal 
[0.37] regulator: down1: 1300 -- 1600 mV at 1300 mV normal 
[0.40]