On 11 March 2011 18:03, phonelouse <[email protected]> wrote: > Hi everyone, > first I want to apologize for making a 2nd post, but my original one was > bounced because of its size a week ago and I didn't hear anything since then > nor am I able to cancel the message now. By attached all logs the message got > too big. > Now to the problem: > Symptom: > after a pretty random amount of time (experienced between 30 minutes and 2.5 > days) the phone will become unresponsive to any action. The screen is then > dark black (not backlit) and the power button will not wake up the phone like > usual. Connecting over usb to a computer at least shows the usb gadget, but > getting a ssh connection is impossible then. Also, getting calls is not > possibe in this state, caller experiences the same as if I had turned gsm off. > The only possibility to get the phone to work again is taking out the > battery, putting it back in and restart the phone. This is rather annoying, I > find myself checking all two minutes if it's still there and I miss calls on > a regular basis. Browsing the logs i can't see anything unusual in them (like > eg read/write errors on rootfs). > > What phone and what's on it: > A7+, purchased one in Jan which had pixel errors, got this one as replacement. > bootloader: tried uboot and qi (the qi 2-4-2 linked to on the debian > freerunner wiki), same with both. > Running the latest (2011.1) shr-t in nand including a kernel upgrade that > came in the last two weeks, had the problem before the upgrade, too. > The problem was already present after a fresh install. > > What have I done to trace it: > I mounted a sdcard and added a log/ directory to it, removed /var/log and > linked /media/card/log to /var/log (like someone on irc suggested). > This left the logdir empty the whole time, so I figured I should perhaps > restart some services. Restarting (in this order) fsodeviced fsotdld > frameworkd phonefsod atd xserver-nodm populated my log - but also made the > phone quite unstable, being overall slower and sometimes not bringing gsm up. > Btw those are the too-long-logs I tried to attach to my first mail.
Normally, /var/log is a symlink to /var/volatile/log. I always remove that symlink and make a plain directory /var/log. Then I used to edit /etc/syslog.conf to my needs, in the meantime this file is now named /etc/default/busybox-syslog, to have the following contents: DESTINATION="file" # log destinations (buffer file remote) MARKINT=20 # interval between --mark-- entries [min] REDUCE=no # reduced-size logging BUFFERSIZE=64 # buffer: size of circular buffer [kByte] LOGFILE=/var/log/messages # file: where to log ROTATESIZE=512 # file: rotate log if grown beyond X [kByte] (busybox 1.2+) ROTATEGENS=5 # file: keep X generations of rotated logs (busybox 1.2+) REMOTE=loghost:514 # remote: where to log FOREGROUND=no # run in foreground (don't use!) Then I do "killall -HUP syslogd" and the logfiles appear in /var/log and they are there after a reboot. Some files like fsodeviced.log will grow day by day, you need to chop them manually or they will flood your rootfs.. _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
