10-07-2012, 03:26 PM | #541 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
3 seconds for the quick boot ey. okay. well let's have a look at your long one next then when its ready.
|
10-07-2012, 03:37 PM | #542 |
Enthusiast
Posts: 35
Karma: 11764
Join Date: Jul 2009
Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG
|
Hi,
3 seconds is the fast wake-up (6 was the time measured by two bob). I will measure the time taken for a long wake-up (assuming it will happen with an active usbNetwork). When I say 10-15s, this is the time taken for the screensaver image to disappear, from my log above, this happens in 1s (210226-210225), 210226 being the point at which the titlebar spinner starts rotating. The biggest jump in the log is this: 121007:210226 cvm[3214]: I MainView:Information::The device has WAN module so skip popping up the WiFi dialog. 121007:210228 cvm[3214]: I ContentCatalogImpl:ItemIterator:index=0,items=32,v olumes=6,time=601:Catalog Iteration done Something to do with checking for WiFi? The K3 had WiFi of course, and the DX never had one, maybe there is an unneeded check being performed when the wake-up takes 10-15s? My DXG is asleep right now, cat messages indicates that the log has been rolled, with no new events since the rollover: 121007:213003 syslog-ng[807]: new configuration initialized 121007:213007 system: I tinyrot:def::Rotating file /var/log/odotlite with max size 2048 121007:213007 system: I tinyrot:def::No file to rotate: /var/log/odotlite |
Advert | |
|
10-07-2012, 03:46 PM | #543 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
I just noticed that also, it took a whole 2/3rds of the time dealing with the wifi -
I thought **everything** had wifi, it was only 3G that was optional. |
10-07-2012, 04:44 PM | #544 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
nup. the DX's do indeed have zippo Wifi.
Well perhaps that's the case. would seem sensible. might be the stupid request to amazon failing. IN WHICH CASE simply add the URL that the DX searches for (it's well documented I forget) in /etc/hosts and make the thing DIE, MUCH FASTER It's only a guess but I think resolving the DNS and killing it to some localhost would be faster than failing the DNS lookup. HTH |
10-07-2012, 06:25 PM | #545 |
Enthusiast
Posts: 35
Karma: 11764
Join Date: Jul 2009
Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG
|
Waited a bit over three hours, woke it up, it came up immediately. Oh well, just when you want something to happen, it doesn't. Anyway, it's getting late, off to bed now. I'll update this tomorrow.
|
Advert | |
|
10-07-2012, 06:40 PM | #546 |
Enthusiast
Posts: 35
Karma: 11764
Join Date: Jul 2009
Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG
|
Looking back through the whole 'showlog' log (thanks NiLuJe!), I do see the following:
121007:201249 cvm[6491]: I MainView:Information::The device has WAN module so skip popping up the WiFi dialog. 121007:201259 cvm[6491]: I LipcService:EventArrived:source=com.lab126.powerd, name=battLevelChanged,arg0=91,arg1=<None>: At various points in the log, a 10 second delay after the 'skip popping up the WiFi dialog', the next log line is different from one case to the next, the delay seems to be connected to the 'skip popping up the WiFi dialog' line. So there may be something in twobob's theory. Where do I look to find the URL which twobob refers to? |
10-08-2012, 02:02 AM | #547 |
Enthusiast
Posts: 35
Karma: 11764
Join Date: Jul 2009
Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG
|
Tried it again this morning, about 8 hours since the last try. SSH'd in first, then did the wake-up. It came up immediately. Damn. Is it because I SSH'd or is it because of the active usbNetwork? Updates to follow.
|
10-08-2012, 07:36 AM | #548 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Neither of those work without the kernel being awake, so it had to wake up before you could see any response. You can connect to the operator's console serial port and (receive only) monitor that while the kernel is asleep. The console port is re-initialized very early in both the boot sequence and in the wake-up sequence. |
|
10-08-2012, 07:53 AM | #549 |
Enthusiast
Posts: 35
Karma: 11764
Join Date: Jul 2009
Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG
|
Ok, after disconnecting the USB I got a long (11s) wake-up. Here is the log via showlog. There seems to be a stackdump near the start that causes all sorts of recovery activity, which seems to take up most of the wake-up time?
Code:
121008:134229 powerd[2113]: I def:pbpress:time=1349696549.888:Power button pressed 121008:134229 powerd[2113]: I lipc:evts:name=outOfScreenSaver, origin=com.lab126.powerd, fparam=1:Event sent 121008:134229 powerd[2113]: I def:statech:prev=SCREEN SAVER, next=ACTIVE:State change: SCREEN SAVER -> ACTIVE 121008:134229 powerd[2113]: I def:acc::Turn acc port on 121008:134229 mxc_keyb: I def:unlocked2:status=unlocked: 121008:134229 fiveway: I def:unlock2:status=unlocked: 121008:134229 powerd[2113]: E def:usbfs::Failed to open sys entry for USB FS ONLINE 121008:134229 accelerometer: I def:unlock::status=unlocked 121008:134229 cvm[3214]: I HTTPUtil:clearDNSCache:cache_size=0:clearing DNS cacheMap 121008:134230 lipc-send-event[12789]: I lipc:evts:name=orientationUp, origin=com.lab126.hal:Event sent 121008:134230 system: I dump-stack:dumpstack:cmd:pid=3518:begin native threads ============================== 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: Using host libthread_db library "/lib/libthread_db.so.1". 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134230 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134231 system: I dumpstack:cmd:pid=3518: [Thread debugging using libthread_db enabled] 121008:134231 system: I dumpstack:cmd:pid=3518: [New Thread 1073881104 (LWP 3518)] 121008:134231 system: I dumpstack:cmd:pid=3518: [New Thread 1110348944 (LWP 3522)] 121008:134231 system: I dumpstack:cmd:pid=3518: [New Thread 1101960336 (LWP 3521)] 121008:134231 system: I dumpstack:cmd:pid=3518: [New Thread 1093571728 (LWP 3520)] 121008:134231 system: I dumpstack:cmd:pid=3518: [New Thread 1085183120 (LWP 3519)] 121008:134231 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134231 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134231 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134231 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134231 system: I dumpstack:cmd:pid=3518: (no debugging symbols found) 121008:134231 system: I dumpstack:cmd:pid=3518: 0x4029e260 in pthread_cond_wait@@GLIBC_2.4 () from /lib/libpthread.so.0 121008:134231 system: I dumpstack:cmd:pid=3518: Thread 5 (Thread 1085183120 (LWP 3519)): 121008:134231 system: I dumpstack:cmd:pid=3518: #0 0x4029e260 in pthread_cond_wait@@GLIBC_2.4 () from /lib/libpthread.so.0 121008:134231 system: I dumpstack:cmd:pid=3518: #1 0x4024153c in pthread_cond_wait@@GLIBC_2.4 () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #2 0x0001274c in ?? () 121008:134231 system: I dumpstack:cmd:pid=3518: Thread 4 (Thread 1093571728 (LWP 3520)): 121008:134231 system: I dumpstack:cmd:pid=3518: #0 0x40206124 in nanosleep () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #1 0x40241aac in __libc_enable_asynccancel () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #2 0x4029102c in __after_morecore_hook () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: Backtrace stopped: frame did not save the PC 121008:134231 system: I dumpstack:cmd:pid=3518: Thread 3 (Thread 1101960336 (LWP 3521)): 121008:134231 system: I dumpstack:cmd:pid=3518: #0 0x40205c04 in waitpid () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #1 0x4017592c in sdump_log_stack_for () from /usr/lib/libstackdump.so.0 121008:134231 system: I dumpstack:cmd:pid=3518: #2 0x40175aac in handle_crash_signal () from /usr/lib/libstackdump.so.0 121008:134231 system: I dumpstack:cmd:pid=3518: #3 <signal handler called> 121008:134231 system: I dumpstack:cmd:pid=3518: #4 0x401e7a00 in strcmp () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #5 0x0000ddb4 in ?? () 121008:134231 system: I dumpstack:cmd:pid=3518: Thread 2 (Thread 1110348944 (LWP 3522)): 121008:134231 system: I dumpstack:cmd:pid=3518: #0 0x4022fee0 in select () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #1 0x40241aac in __libc_enable_asynccancel () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #2 0x00000000 in ?? () 121008:134231 system: I dumpstack:cmd:pid=3518: Thread 1 (Thread 1073881104 (LWP 3518)): 121008:134231 system: I dumpstack:cmd:pid=3518: #0 0x4029e260 in pthread_cond_wait@@GLIBC_2.4 () from /lib/libpthread.so.0 121008:134231 system: I dumpstack:cmd:pid=3518: #1 0x4024153c in pthread_cond_wait@@GLIBC_2.4 () from /lib/libc.so.6 121008:134231 system: I dumpstack:cmd:pid=3518: #2 0x0000e988 in ?? () 121008:134231 system: I dumpstack:cmd:pid=3518: #0 0x4029e260 in pthread_cond_wait@@GLIBC_2.4 () from /lib/libpthread.so.0 121008:134231 system: I dump-stack:dumpstack:cmd:pid=3518:end native threads ================================ 121008:134232 system: I tinyrot:def::Rotating file /var/log/messages with max size 256 121008:134232 syslog-ng[807]: SIGHUP received, restarting syslog-ng 121008:134233 arcotg_udc: I def:fs::dr_controller_setup - force_fs = 0 121008:134233 arcotg_udc: I def:uri::resume_irq - resume_irq: usb_slave_regs->usbintr:157 121008:134233 arcotg_udc: I def:udsc::chgdisc_event - USB disconnected 121008:134233 arcotg_udc: I def:usi::suspend_irq - suspend_irq: usb_slave_regs->usbintr:157 121008:134233 arcotg_udc: I def:udsc::chgdisc_event - USB disconnected 121008:134233 syslog-ng[807]: new configuration initialized 121008:134233 lipc-send-event[12924]: I lipc:evts:name=usbPlugOut, origin=com.lab126.hal:Event sent 121008:134233 lipc-send-event[12929]: I lipc:evts:name=usbPlugOut, origin=com.lab126.hal:Event sent 121008:134236 system: I tinyrot:def::Rotating file /var/log/odotlite with max size 2048 121008:134236 system: I tinyrot:def::No file to rotate: /var/log/odotlite 121008:134239 crond[2919]: USER root pid 12965 cmd /usr/sbin/checkpmond 121008:134239 crond[2919]: USER root pid 12966 cmd /usr/sbin/tinyrot 121008:134239 crond[2919]: USER root pid 12967 cmd /usr/sbin/loginfo powerdcheck 121008:134239 cvm[3214]: E lipc:pto::Timed out waiting for sync prop access to complete 121008:134239 cvm[3214]: W lipc:perf:prop=interfaceProperties, source=com.lab126.cmd, ms=10001:lipc property access time in millisecond 121008:134239 cvm[3214]: E ConnectionService:ExceptionCaught::Cannot get interface properties 121008:134239 cvm[3214]: I WirelessImpl:SettingProxyInfo:interface=none:Setting up proxies 121008:134239 cvm[3214]: I URLUtil:UpdateGlobalsTrace::before updating the map 121008:134239 cvm[3214]: I URLUtil:UpdateGlobalsTrace::after updating the map 121008:134239 cvm[3214]: I URLUtil:UpdateGlobalsTrace::before updating the map 121008:134239 cvm[3214]: I URLUtil:UpdateGlobalsTrace::after updating the map 121008:134239 cvm[3214]: I URLUtil:UpdateGlobalsTrace::before updating the map 121008:134239 cvm[3214]: I URLUtil:UpdateGlobalsTrace::after updating the map 121008:134239 cvm[3214]: I SettingsPage:Information::The current view is not the Settings so skip refresh the WiFi widget 121008:134239 cvm[3214]: I LipcService:EventArrived:source=com.lab126.powerd,name=outOfScreenSaver,arg0=1,arg1=<None>: 121008:134239 cvm[3214]: I PowerImpl:Information::handlePowerStateChangeEvent 3 1 121008:134239 cvm[3214]: I lipc:sip:prop=Volume, source=com.lab126.audio, value=7:Set int property 121008:134239 cvm[3214]: I ScreenSaverBooklet:SSB_TRACE_USB_EXPORT:delayUSBExport=false:Password disabled 121008:134239 cvm[3214]: I ScreenSaverBooklet:IncrementSSImage::Incrementing the screen saver image index 121008:134239 cvm[3214]: I ScreenSaverBooklet:SwitchingToLastBooklet:lastBooklet=Home:Switching to last booklet 121008:134239 cvm[3214]: I BookletManager:SwitchingBooklets:from=ScreenSaverBooklet,to=Home: 121008:134239 audioServer[2691]: I volume:set:vol = 7:Setting the volume 121008:134239 audioServer[2691]: E def:mo::Failed to set volume (No master output) 121008:134240 cvm[3214]: W SystemBarImpl:SPIN:spinCount=0:count <=0 when stopSpinner() called 121008:134240 cvm[3214]: I ContentCatalogImpl:ItemIterator:index=0,items=32,volumes=6,time=53:Catalog Iteration done 121008:134240 cvm[3214]: I MainView:Information::The device has WAN module so skip popping up the WiFi dialog. |
10-08-2012, 08:15 AM | #550 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
That problem will most likely have to be referred out to the author of your replacement system.
It would be interesting to see just who/what pid=3518 is, that is, explore: /proc/3518 portion of the tree with 'list' and 'cat' if that thread ID is still around after the event. hmm... 3519 .. 3522 might still be around, and it looks like they would have the same parent (ppid) since they where dump'd as members of the same group. |
10-08-2012, 08:20 AM | #551 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
Right I think I can field this one now then.
a) the stack dump. not sure what PID 3518 is at that moment. But raising the log level to something higher would possibly help determine that. also running this: Code:
ps.procps -A > /mnt/us/Documents/WhatWasRunningBefore.txt; dbus-send --system /default com.lab126.powerd.resuming int32:1 Spoiler:
So that would give you something to give us Looking at why it MIGHT be a few seconds slower anyway Your log rotate stuff happens after the crash and it takes a while. That would explain probably why mine takes a few seconds less: The size of the logs. Mine are hacked to be 0 size, so they just wipe, whereas you are making genuine tar.gz's or w/e of your activity. That would take a little bit more time I would imagine also. Well, hope that helps. |
10-08-2012, 02:42 PM | #552 |
Enthusiast
Posts: 35
Karma: 11764
Join Date: Jul 2009
Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG
|
The stackdump happens at every long wake-up. I tried twobob's "ps.procps -A" method to find the pid. Alas the pid of the object causing the stacktrace is not in the WhatWasRunningBefore.txt. Damn.
So close, and yet, not so close. |
10-08-2012, 03:13 PM | #553 | |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
really? well that sounds like its a process that is spawning "at wake up" then.
My first thought is something related to the wifi. And now I have been thinking about this more I am FAIRLY certain that YIFAN LU even goes as far to mention some of this in his original conversion notes. Certainly something about wifi fails. My next thought would be to dig in the AT_WAKE_UP script (I have zero idea what that exactly might be) http://upstart.ubuntu.com/cookbook/upstart_cookbook.pdf WARNING! DO NOT MESS THOSE SCRIPTS UP OR YOU WILL PROBABLY BRICK THE DEVICE I think that was fairly clear. be careful. ALSO: seems like simply trying the URL wangle wouldn't hurt none either. I'll go hunt down that thread, one sec. EDIT: Sigh, or not... well its on here somewhere FROM https://www.mobileread.com/forums/sho...d.php?t=188439 POST: https://www.mobileread.com/forums/sho...59&postcount=3 You want that bit: Quote:
Last edited by twobob; 10-08-2012 at 03:22 PM. Reason: https://www.mobileread.com/forums/showpost.php?p=2190459&postcount=3 |
|
10-08-2012, 04:58 PM | #554 |
Enthusiast
Posts: 35
Karma: 11764
Join Date: Jul 2009
Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG
|
I was unable to find the AT_WAKE_UP script, even after reading the pdf, however, I did find a reference to /mnt/us/WIFIOFF in /etc/init.d/pre-wifid, if the file WIFIOFF is present in the user root, the wifi is disabled. I will try this, and report tomorrow. After that I am away for a few days on a work related trip, so it will be the weekend before I can try anything else. Anyway thanks for your help so far twobob!
|
10-08-2012, 05:02 PM | #555 | ||
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
no at_wake_up was a pseudonym for a file I did not know the name of.
I should have made that clearer. I don't actually know which script runs at wake up or I would have just named it. Others may know, I currently don't - you may indeed have found the script. I should go look.. Quote:
One more option is of course to elevate the logging level lipc-probe -a reveals a loglevel rw string for each service. Quote:
Possibly elevate them all to the highest level, try it again and trawl the logs? I honestly don't know exactly how to do that... heh... but roughly: dbus-send --system /default com.lab126.powerd.logLevel string:"all" I think - you should check that. all of it so yeah, elevate logs... read them... share them... : ) hope something falls out Last edited by twobob; 10-08-2012 at 05:13 PM. |
||
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
images for Kindle & ipad Kindle (or tablets) | hapax legomenon | Kindle Formats | 0 | 03-10-2011 10:54 PM |
Kindle & Tech formatted kindle books? | Ncage1974 | Amazon Kindle | 7 | 02-09-2011 10:03 AM |
Possible Kindle for PC & Kindle for iPhone Issue(s) | Nyssa | Amazon Kindle | 6 | 12-31-2010 03:58 PM |
Kindle vs Kindle for PC vs print books & old lady eyes | bert501 | Amazon Kindle | 30 | 11-19-2010 08:59 PM |
did kindle 2 get updated with kindle 3 zoom and contrast adjustment software? | med007 | Amazon Kindle | 1 | 10-15-2010 10:08 AM |