Neo - high load average after 1 -2 days on?
Cindy Mottershead
cindy at mottershead.us
Wed Apr 30 01:57:31 CEST 2008
I have seen the same thing. It definitely happens if I leave tangogps
running. I have assumed that it is running out of disk space possibly
from log files. It behaves similarly to other linux systems when they
approach 99% disk space and need to write in the log or tmp files. It
semi-freezes but you can get a response on an existing ssh session if
you are patient enough. I have been leaving it run today and plan on
doing a df when it hangs.
I notice that the /var/volatile/tmp/x.log file is increasing on my neo
at a rate which could fill up the /var/volatile space in a day or so. A
tail of the x.log file has the following:
root at om-gta01:/media/mmcblk0/root# tail -f /var/volatile/tmp/x.log
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
** (matchbox-panel-2:1227): DEBUG: usb_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
connection to gpsd SUCCEEDED
** (matchbox-panel-2:1227): DEBUG: battery_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
** (matchbox-panel-2:1227): DEBUG: usb_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
Rcvd: GPSD,R=1
$GPRMC,235117.00,A,4230.629309,N,07119.656232,W,000.0,294.0,290408,,,A*4D
** (matchbox-panel-2:1227): DEBUG: battery_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
** (matchbox-panel-2:1227): DEBUG: usb_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
connection to gpsd SUCCEEDED
Rcvd: GPSD,R=1
$GPGGA,235123.00,4230.629309,N,07119.656232,W,1,07,0.5,041.0,M,0.184001,M,0.0210515,*57
** (matchbox-panel-2:1227): DEBUG: battery_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
** (matchbox-panel-2:1227): DEBUG: usb_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
** (matchbox-panel-2:1227): DEBUG: battery_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
** (matchbox-panel-2:1227): DEBUG: usb_applet: signal_filter
** (matchbox-panel-2:1227): DEBUG: (unknown dbus message, ignoring)
Cindy
Torfinn Ingolfsen wrote:
> Hello,
> I'm using the 2004-04-24 snapshot image with my Neo.
> It seems that if the Neo is left on for more than one day, it will get
> a high load average.
> Like this:
>
> root at om-gta01:~# uptime
> 00:27:25 up 9 min, 1 user, load average: 1.49, 1.52, 1.01
> root at om-gta01:~# uptime
> 07:36:58 up 1 day, 7:19, 1 user, load average: 1.02, 1.10, 1.14
> root at om-gta01:~# uptime
> 18:04:25 up 1 day, 17:46, 1 user, load average: 10.78, 8.97, 7.51
>
> As you can see, the two firs ones are in the same range. But the third
> one is unusual high, at least I have no other machines with this high
> load average. :-)
> The gui on the phone (touchscreen) isn't responsive at all, the
> buttons gives a very delayed response.
> Responses to ping are good, but as you can imagine, trying to use the
> ssh shell (via usb) requires large amounts of patience.
> I'm currently trying to use psax to find out what processes are running.
> some time later:
> root at om-gta01:~# ps ax
> PID TTY STAT TIME COMMAND
> 1 ? Ss 5:44 init [5]
> 2 ? S< 0:00 [kthreadd]
> 3 ? S< 0:00 [ksoftirqd/0]
> 4 ? S< 0:00 [watchdog/0]
> 5 ? S< 0:00 [events/0]
> 6 ? S< 0:00 [khelper]
> 57 ? S< 0:00 [kblockd/0]
> 63 ? S< 0:00 [ksuspend_usbd]
> 69 ? S< 0:00 [khubd]
> 72 ? S< 0:00 [kseriod]
> 78 ? S< 0:00 [kmmcd]
> 107 ? D 0:07 [pdflush]
> 108 ? S 0:08 [pdflush]
> 109 ? D< 3:38 [kswapd0]
> 110 ? S< 0:00 [aio/0]
> 129 ? S< 0:00 [kapmd]
> 157 ? S< 0:00 [mtdblockd]
> 178 ? S< 0:00 [spi_s3c24xx_gpi]
> 220 ? D< 0:00 [SDIO Helper]
> 227 ? S< 0:00 [rpciod/0]
> 233 ? S< 0:08 [mmcqd]
> 315 ? S<s 0:01 udevd --daemon
> 834 ? S< 0:00 [kjournald]
> 853 ? SN 0:14 [jffs2_gcd_mtd4]
> 888 ? S< 0:00 [krfcommd]
> 1027 ? Ss 0:00 /sbin/portmap
> 1065 ? Ss 0:42 /usr/sbin/dropbear -r
> /etc/dropbear/dropbear_rsa_host_key -p 22
> 1075 ? Ss 0:00 /usr/sbin/apmd -P /etc/apm/apmd_proxy
> --proxy-timeout 30
> 1088 ? Ss 2:44 /usr/bin/dbus-daemon --system
> 1094 ? Rs 33:38 /usr/sbin/hald
> 1095 ? S 0:00 hald-runner
> 1102 ? S 0:09 hald-addon-keyboard: listening on /dev/input/event0
> 1103 ? S 0:10 hald-addon-keyboard: listening on /dev/input/event0
> 1104 ? S 0:08 hald-addon-keyboard: listening on /dev/input/event2
> 1107 ? S 0:01 hald-addon-keyboard: listening on /dev/input/event1
> 1114 ? Ss 3:23 /sbin/syslogd -n -C64 -m 20
> 1116 ? Ss 0:00 /sbin/klogd -n
> 1125 ? Ss 0:00 avahi-daemon: running [om-gta01.local]
> 1142 ? Ss 0:00 /sbin/hcid -s -f /etc/bluetooth/hcid.conf
> 1145 ? S 0:00 /usr/lib/bluetooth/bluetoothd-service-input
> 1168 ? S<s 35:28 gpsd -n /tmp/nmeaNP
> 1201 ? R 96:22 lib/ld-linux.so.2 --library-path
> /home/root/gllin/lib:/home/root/glli
> 1202 ? Ss 5:21 /usr/sbin/gsmd gsmd -p /dev/ttySAC0 -s
> 115200 -F -d -l syslog
> 1203 ? S<sl 61:15 /usr/bin/pulseaudio --no-cpu-limit
> --resample-method=trivial -D -nF /
> 1218 tty1 Ss+ 0:00 /sbin/getty 38400 tty1
> 1223 ? S 0:00 xinit /etc/X11/Xsession -- /usr/bin/Xfbdev
> :0 -pn -dpi 285 -screen 48
> 1228 ? S< 50:04 /usr/bin/Xfbdev :0 -pn -dpi 285 -screen
> 480x640 -hide-cursor -root-pp
> 1235 ? S 0:00 /bin/sh /etc/X11/Xsession
> 1240 ? Ss 0:02 /usr/bin/dbus-daemon --fork --print-pid 4
> --print-address 6 --session
> 1244 ? S 0:00 run-parts /etc/X11/Xsession.d
> 1248 ? S 0:20 /usr/libexec/gconfd-2
> 1252 ? S 0:00 /usr/bin/settings-daemon
> 1254 ? S 0:01 multitap-pad -d
> 1256 ? Rl 2:56 neod
> 1257 ? Z 38:43 [openmoko-today] <defunct>
> 1258 ? Sl 23:02 phone-kit
> 1259 ? S 21:00 matchbox-window-manager -use_titlebar yes
> -use_desktop_mode decorated
> 1260 ? D 46:01 matchbox-panel-2 --start-applets
> systray,startup --end-applets openmo
> 1263 ? S 0:03 /usr/libexec/e-calendar-factory
> 1268 ? S 0:00 /usr/libexec/e-addressbook-factory
> 1275 ? Ss 3:00 /usr/sbin/dropbear -r
> /etc/dropbear/dropbear_rsa_host_key -p 22
> 1276 pts/0 Ss 0:29 -sh
> 1292 ? S 0:02 /usr/libexec/notification-daemon
> 1321 ? R 81:09 tangogps
> 1327 pts/0 R+ 1:23 ps ax
>
> And now the load average is down too:
> root at om-gta01:~# uptime
> 20:05:09 up 1 day, 19:47, 1 user, load average: 1.22, 1.10, 1.20
>
>
> Any clues as to what is causing this?
> --
> Regards,
> Torfinn Ingolfsen
>
>
>
>
More information about the device-owners
mailing list
