Re: Qtmoko v52-armhf : Issue to resume
Hello! Finally, I had time to come back on the error of this thread (fail resume on SMS reception). I was able to strace dbus (see [1]) and to check dmesg (see [2]). I've tried to send same sms just after I've seen the bug, but it didn't appear again (so that's not because of the text message). I'll try to see if I can have more log messages next time. Maybe should I check pulseaudio log ? I think about that because GTA02 doesn't have the bug and GTA04 didn't had it early last year. HTH, Adrien [1]: https://pbin.adorsaz.ch/?69452a9cad905b6a#6N2UOxkrfGWJl02dlp1OFNjb3jy43xl4mL6YywAE6H4= [2]: https://pbin.adorsaz.ch/?9872c8f76ec94350#3X4diX9NkU2d +++bhHNBXXKBJhjgvaB57MZ1SKmQXGo= signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
On 02/15/2013 09:48 PM, Adrien Dorsaz wrote: > > In fact, I was dist-upgrading with cable plugged and I had some error > with apt-get (I didn't take time to read the log, because navit isn't > very important for me). I don't know if it's wired with these errors. > Hi, had the same issue - try rebooting then dist-upgrading again. Benedikt > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
Hello, So this evening I had the black screen bug. In this case, dbus daemon is down too, but I didn't received any SMS. In fact, I was dist-upgrading with cable plugged and I had some error with apt-get (I didn't take time to read the log, because navit isn't very important for me). I don't know if it's wired with these errors. In the same time, in another ssh connexion, I was trying to run another version of ics2qtcal application to fix bug reported in this mailing list. And that's when I wanted to see result on the screen that I've seen the black screen. I let you my syslog and my apt-log in attachements. Hope that help, Adrien cat term.log Log started: 2013-02-15 20:21:12 (Reading database ... 32519 files and directories currently installed.) Preparing to replace libcurl3-gnutls:armhf 7.26.0-1 (using .../libcurl3-gnutls_7.26.0-1+wheezy1_armhf.deb) ... Unpacking replacement libcurl3-gnutls:armhf ... Selecting previously unselected package libgfortran3:armhf. Unpacking libgfortran3:armhf (from .../libgfortran3_4.7.2-5_armhf.deb) ... Selecting previously unselected package python-support. Unpacking python-support (from .../python-support_1.0.15_all.deb) ... Preparing to replace libertas-firmware 9.70.7.p0.0-1 (using .../libertas-firmware_9.70.7.p0.0-2_all.deb) ... Unpacking replacement libertas-firmware ... Selecting previously unselected package firmware-libertas. Unpacking firmware-libertas (from .../firmware-libertas_0.36+wheezy.1_all.deb) ... Selecting previously unselected package gpsd. Unpacking gpsd (from .../archives/gpsd_3.6-4_armhf.deb) ... Selecting previously unselected package python-gps. Unpacking python-gps (from .../python-gps_3.6-4_armhf.deb) ... Selecting previously unselected package libblas3. Unpacking libblas3 (from .../libblas3_1.2.20110419-5_armhf.deb) ... Selecting previously unselected package libblas3gf. Unpacking libblas3gf (from .../libblas3gf_1.2.20110419-5_all.deb) ... Selecting previously unselected package liblapack3. Unpacking liblapack3 (from .../liblapack3_3.4.1-6_armhf.deb) ... Selecting previously unselected package liblapack3gf. Unpacking liblapack3gf (from .../liblapack3gf_3.4.1-6_all.deb) ... Selecting previously unselected package python-numpy. Unpacking python-numpy (from .../python-numpy_1%3a1.6.2-1_armhf.deb) ... Selecting previously unselected package python-cairo. Unpacking python-cairo (from .../python-cairo_1.8.8-1_armhf.deb) ... Selecting previously unselected package python-gobject-2. Unpacking python-gobject-2 (from .../python-gobject-2_2.28.6-10_armhf.deb) ... Selecting previously unselected package python-gtk2. Unpacking python-gtk2 (from .../python-gtk2_2.24.0-3+b1_armhf.deb) ... Selecting previously unselected package gpsd-clients. Unpacking gpsd-clients (from .../gpsd-clients_3.6-4_armhf.deb) ... Preparing to replace qtmoko-gta04 52-1 (using .../qtmoko-gta04_53-1_armhf.deb) ... Unpacking replacement qtmoko-gta04 ... Preparing to replace qtmoko-navit 37-1 (using .../qtmoko-navit_37-1_armhf.deb) ... Unpacking replacement qtmoko-navit ... QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused dpkg: warning: subprocess old post-removal script returned error exit status 1 dpkg: trying script from the new package instead ... QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused dpkg: error processing /var/cache/apt/archives/qtmoko-navit_37-1_armhf.deb (--unpack): subprocess new post-removal script returned error exit status 1 QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused QWSSocket::connectToLocalFile could not connect:: Connection refused dpkg: error while cleaning up: subprocess new post-removal script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/qtmoko-navit_37-1_armhf.deb Log ended: 2013-02-15 20:25:24 Log started: 2013-02-15 20:30:09 dpkg: error processing qtmoko-navit (--purge): Package is in a very bad inconsistent state - you should reinstall it
Re: Qtmoko v52-armhf : Issue to resume
Hello! > But we have /opt/qtmoko/bin/after-resume.sh - this is script > (currently unused), which is executed after resume. So you can easily > add check there. > > > > If dbus is for some reason crashing or is stopped then we have to > figure out why. I guess QtMoko cant work much without dbus, since it's > used for bluetooth and maybe other things... > I think that's better because, it seems that restarting dbus permit to run qpe, but yesterday I've seen that QtMoko wasn't well responding when I did it. I've just enabled logging and hope to have the bug as soon as possible. Thanks, Adrien signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
On Wednesday, February 13, 2013 03:55:55 PM Adrien Dorsaz wrote: > Hello, > > I've had again this issue this afternoon and I've noticed that dbus > wasn't running (using "service dbus status"). > > I don't know how the resume works in QtMoko for qpe service, but I've > seen in /etc/init.d/qtmoko-gta04 that dbus is already marked in required > services. Should the dbus requirement checked in the /opt/qtmoko/qpe.sh > or in /opt/qtmoko/bin/qpe to be sure it's runing at resume ? Hi, qpe.sh is only launched during boot - and at that point it does not make much sense to check dbus. If it is not running QtMoko does not start at all. But we have /opt/qtmoko/bin/after-resume.sh - this is script (currently unused), which is executed after resume. So you can easily add check there. If dbus is for some reason crashing or is stopped then we have to figure out why. I guess QtMoko cant work much without dbus, since it's used for bluetooth and maybe other things... I think we should also be running QtMoko with logging enabled - there can be interesting message in log then. To enable logging edit /opt/qtmoko/qpe.sh and add logging_start.sh after . /opt/qtmoko/qpe.env line. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
Hello, I've had again this issue this afternoon and I've noticed that dbus wasn't running (using "service dbus status"). I don't know how the resume works in QtMoko for qpe service, but I've seen in /etc/init.d/qtmoko-gta04 that dbus is already marked in required services. Should the dbus requirement checked in the /opt/qtmoko/qpe.sh or in /opt/qtmoko/bin/qpe to be sure it's runing at resume ? The verification could be simply made using service dbus status with something like : service dbus status if [ $? -eq 0 ]; then service dbus start fi Regards, Adrien Le mardi 12 février 2013 à 07:58 +0100, Adrien Dorsaz a écrit : > Hello, > > Le vendredi 08 février 2013 à 17:37 +0100, Radek Polak a écrit : > > On Friday, February 08, 2013 04:08:06 PM Adrien Dorsaz wrote: > > > > > Hello! > > > > > > I've noticed two issues when I resume my phone from suspend : > > > > > > * Sometimes my screen kept black and I'm only able to shut down my > > > phone with power button (I didn't have my computer at these > > > times, so I don't know if I was able to connect with ssh) > > > * Sometimes the screen display the last qtmoko image with screen > > > lock, but it's stuck. Eg, now my screen dipslays 2pm (last > > > suspend I think), but here I'm at 3 pm now. The only one > > > interaction possible is to press Aux and see the "^@" strings > > > displayed. > > > > Hmm i guess we need to reproduce it somehow. Maybe automatic suspend resume > > cycles using rtc alarm could reproduce it - but IIRC i tried it and had no > > luck. > > > > I didn't have this issue since some days, but it appeared this morning > again, after this situation : > * I'v made a call in the train > * An interruption appeared because the swiss gsm network in trains > is really bad > * So my correspondant called me back (she was in another train), > but I wasn't able to answer (I'm pretty sure it's because of our > gsm network again, we had same errors using proprietary phones) > * Finally I've called her again and we were able to finish our > discussion normally. > > Furthermore, after each call end, I receive an SMS from my gsm operator > to say me how many credits I've on my SIM card. > > That's not really easy to reproduce... > > I've straced again qpe process and I've seen same error with (Q)Debus. > So I've stopped qtmoko-gta04 service, then I've restarted dbus service > and started qtmoko-gta04 service again and all works fine. > > I didn't think to strace dbus process, so it's not really relevant, but > this workaround seems to work. > > I hope to have this bug again to be able to produce more straces. > > See you, > Adrien > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
I also noticed that an incoming SMS will wake up the phone, but not restore the screen. Unfortunately, I didn't have USB at hand, so I did an accutectomy :-) Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
On Tuesday, February 12, 2013 07:58:43 AM Adrien Dorsaz wrote: > Hello, > > Le vendredi 08 février 2013 à 17:37 +0100, Radek Polak a écrit : > > On Friday, February 08, 2013 04:08:06 PM Adrien Dorsaz wrote: > > > Hello! > > > > > > I've noticed two issues when I resume my phone from suspend : > > > * Sometimes my screen kept black and I'm only able to shut down > > > my > > > > > > phone with power button (I didn't have my computer at these > > > times, so I don't know if I was able to connect with ssh) > > > > > > * Sometimes the screen display the last qtmoko image with screen > > > > > > lock, but it's stuck. Eg, now my screen dipslays 2pm (last > > > suspend I think), but here I'm at 3 pm now. The only one > > > interaction possible is to press Aux and see the "^@" strings > > > displayed. > > > > Hmm i guess we need to reproduce it somehow. Maybe automatic suspend > > resume cycles using rtc alarm could reproduce it - but IIRC i tried it > > and had no luck. > > I didn't have this issue since some days, but it appeared this morning > again, after this situation : > * I'v made a call in the train > * An interruption appeared because the swiss gsm network in trains > is really bad > * So my correspondant called me back (she was in another train), > but I wasn't able to answer (I'm pretty sure it's because of our > gsm network again, we had same errors using proprietary phones) > * Finally I've called her again and we were able to finish our > discussion normally. > > Furthermore, after each call end, I receive an SMS from my gsm operator > to say me how many credits I've on my SIM card. > > That's not really easy to reproduce... > > I've straced again qpe process and I've seen same error with (Q)Debus. > So I've stopped qtmoko-gta04 service, then I've restarted dbus service > and started qtmoko-gta04 service again and all works fine. > > I didn't think to strace dbus process, so it's not really relevant, but > this workaround seems to work. > > I hope to have this bug again to be able to produce more straces. Right now as i was reading this mail i received SMS. It should wake the phone up - which happened, but the screen was black - just the LED was blinking indicating unread SMS. So i plugged USB and logged in. I have checked screen brightness: root@neo:~# cat /sys/class/backlight/pwm-backlight/brightness 0 so it looks that the brighness is not restored correctly. So i did: root@neo:~# echo 100 > /sys/class/backlight/pwm-backlight/brightness and the screen went all white. After some time the phone went to sleep and i woken it this time with AUX button and the phone is working ok now. This was on qtmoko v52 armel. Attached is dmesg. I will try to collect more info when it happens next time. Regards Radek [ 4402.448577] Restarting tasks ... done. [ 4402.466461] td028ttec1_panel_resume() [ 4402.818328] gta04_enable_lcd() [ 4402.903198] mmc1: new SDIO card at address 0001 [ 4404.089141] libertas_sdio mmc1:0001:1 (unregistered net_device): 00:19:88:42:96:39, fw 9.70.7p0, cap 0x0303 [ 4404.159912] libertas_sdio mmc1:0001:1 (unregistered net_device): PREP_CMD: command 0x00a3 failed: 2 [ 4404.181091] libertas_sdio mmc1:0001:1 wlan0: Marvell WLAN 802.11 adapter [ 4412.688934] GPS SET to 1 [ 4412.692108] GPS SET to 1 [ 4412.694793] GPS down [ 4412.728454] GPS up [ 4412.744049] GPS idle [ 4412.892608] GPS SET to 1 [ 4416.974243] gadget: high-speed config #1: CDC Ethernet (ECM) [ 4417.310150] twl4030_bci twl4030_bci: VBUS overvoltage [ 4417.316375] twl4030_bci twl4030_bci: VBUS overvoltage [ 4417.339538] twl4030_bci twl4030_bci: VBUS overvoltage [17155.277618] PM: NOT Syncing filesystems ... td028ttec1_panel_suspend() [17155.309204] gta04_disable_lcd() [17155.312866] Freezing user space processes ... (elapsed 0.02 seconds) done. [17155.341308] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. [17155.372619] Suspending console(s) (use no_console_suspend to debug) [17155.393188] mmc1: card 0001 removed [17155.526214] GPS off for suspend 1 1 [17155.549072] GPS SET to 0 [17155.549438] PM: suspend of devices complete after 169.433 msecs [17155.550048] PM: late suspend of devices complete after 0.610 msecs [17155.557159] GPS SET to 0 [17155.557312] PM: noirq suspend of devices complete after 7.232 msecs [17155.557556] Successfully put all powerdomains to target state [17155.581390] GPS SET to 0 [17155.600738] PM: noirq resume of devices complete after 42.785 msecs [17155.601531] PM: early resume of devices complete after 0.427 msecs [17155.602447] Bluetooth: Frame Reassembly Failed [17155.602508] GPS SET to 1 [17155.602539] GPS SET to 1 [17155.602813] GPS resuming 1 0 [17155.602844] GPS down [17155.611419] GPS up [17155.627136] GPS idle [17156.260742] PM: resume of devices complete after 659.088 msecs [17156.346099] Unhandled fa
Re: Qtmoko v52-armhf : Issue to resume
Hello, Le vendredi 08 février 2013 à 17:37 +0100, Radek Polak a écrit : > On Friday, February 08, 2013 04:08:06 PM Adrien Dorsaz wrote: > > > Hello! > > > > I've noticed two issues when I resume my phone from suspend : > > > > * Sometimes my screen kept black and I'm only able to shut down my > > phone with power button (I didn't have my computer at these > > times, so I don't know if I was able to connect with ssh) > > * Sometimes the screen display the last qtmoko image with screen > > lock, but it's stuck. Eg, now my screen dipslays 2pm (last > > suspend I think), but here I'm at 3 pm now. The only one > > interaction possible is to press Aux and see the "^@" strings > > displayed. > > Hmm i guess we need to reproduce it somehow. Maybe automatic suspend resume > cycles using rtc alarm could reproduce it - but IIRC i tried it and had no > luck. > I didn't have this issue since some days, but it appeared this morning again, after this situation : * I'v made a call in the train * An interruption appeared because the swiss gsm network in trains is really bad * So my correspondant called me back (she was in another train), but I wasn't able to answer (I'm pretty sure it's because of our gsm network again, we had same errors using proprietary phones) * Finally I've called her again and we were able to finish our discussion normally. Furthermore, after each call end, I receive an SMS from my gsm operator to say me how many credits I've on my SIM card. That's not really easy to reproduce... I've straced again qpe process and I've seen same error with (Q)Debus. So I've stopped qtmoko-gta04 service, then I've restarted dbus service and started qtmoko-gta04 service again and all works fine. I didn't think to strace dbus process, so it's not really relevant, but this workaround seems to work. I hope to have this bug again to be able to produce more straces. See you, Adrien signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
On Friday, February 08, 2013 05:37:51 PM Radek Polak wrote: > Btw i have been for some time running 3.7 kernel with debugfs mounted - > maybe there is some different timing so that this problem is inhibited. > You can try yourself. Just add somewhere in statup scripts (e.g. > /opt/qtmoko/qpe.sh): > > mount -t debugfs none /sys/kernel/debug Hmm you can forget this. Same problem happened to me also with debugfs. Btw i though that it's just brightness that is not restored - so i added a hack to restore brightness on pressing POWER button: https://github.com/radekp/qtmoko/commit/f4270be1f4702774b6400146c5da09a1e4a872c1 but for some reason it does not help... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qtmoko v52-armhf : Issue to resume
On Friday, February 08, 2013 04:08:06 PM Adrien Dorsaz wrote: > Hello! > > I've noticed two issues when I resume my phone from suspend : > > * Sometimes my screen kept black and I'm only able to shut down my > phone with power button (I didn't have my computer at these > times, so I don't know if I was able to connect with ssh) > * Sometimes the screen display the last qtmoko image with screen > lock, but it's stuck. Eg, now my screen dipslays 2pm (last > suspend I think), but here I'm at 3 pm now. The only one > interaction possible is to press Aux and see the "^@" strings > displayed. Hmm i guess we need to reproduce it somehow. Maybe automatic suspend resume cycles using rtc alarm could reproduce it - but IIRC i tried it and had no luck. Btw i have been for some time running 3.7 kernel with debugfs mounted - maybe there is some different timing so that this problem is inhibited. You can try yourself. Just add somewhere in statup scripts (e.g. /opt/qtmoko/qpe.sh): mount -t debugfs none /sys/kernel/debug Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
