Opened 12 years ago
Last modified 4 years ago
#869 assigned defect/bug
Navit will not work on a TomTom One Device
Reported by: | me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152 | Owned by: | xenos1984 |
---|---|---|---|
Priority: | critical | Milestone: | version 0.6.0 |
Component: | port/tomtom | Version: | git master |
Severity: | Keywords: | tomtom, crash | |
Cc: |
Description
Hello,
I have a TomTom? One (V2) Device an would use it to run navit.
I have installed the precompiled Version 4300 as on http://wiki.navit-project.org/index.php/Navit_on_TomTom descripted.
I can start navit an play around, all works fine _without_ a _valid_ GPS-Signal.
When I have a valid GPS-Signal, then the application will be killed after 2 or 3 minutes from the watchdog and the device will be reboot.
I have modified the startup-script and the watchdog feeding. I have two logfiles: the normal log and the wrapper-log.
Attachments (9)
Change History (18)
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
the wrapper-logfile
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
the modified navit-startup-script
comment:1 Changed 12 years ago by mhohmann
Could you provide a more detailed navit-log file? I recommend increasing the debug levels for "vehicle_file" and "navit" in your xml config file (which should be navit/share/config/tomtom320.xml on your TomTom?) from "0" to "5". You can find the debug level settings close to the start of the file (search for '<debug name="'). The generated output will be quite large, so you better post only the last ~20-50 lines of the file.
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
navit-wrapper.log from 2001-jun-04
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
navit.log from 2011-jun-04, the last 350 lines
comment:2 Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
Hello,
I have change the debug-level for navit and vehicle_file from 0 to 5 and running navit on my TomTom?. It's was very slow, but navit was not killed by watchdog. After 30 minutes I have regular exit navit.
From the logfile navit.log I have added the last 350 lines and the navit-wrapper.log with timestamps and loads. Maybe it's helps.
Sorry for my bad English.
comment:3 Changed 12 years ago by mhohmann
Hm... This is strange. The log file looks perfectly fine to me, I can't see any problems - so I have no clue what could be causing the crash. The only thing I could imagine is that Navit consumes a lot of CPU time and thus "blocks" the wrapper script, so it cannot trigger the watchdog before its period expires.
comment:4 Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
Hello,
I repeated the test and wait until the application is killed by the watchdog. It took 1 hour min 30. My TomTom? had a good GPS signal and was not moved.
I will attach the log wrapper completely. From navit-log only the last 100 lines. Strangely, the time difference is between two logs exactly 2 hours. Using the navit-log UTC?
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
navit-wrapper.log from 2001-jun-05
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
navit.log from 2011-jun-05, the last 4 minutes
comment:5 Changed 12 years ago by mhohmann
Yes, the timestamps in the navit log are UTC.
Again, the navit log looks perfectly fine... The same is true for the wrapper log. No increase in CPU load, no error messages, no unexpected data... Everything looks fine, there are no hints what may be causing the crash.
So here's another idea how we might get some hint what's happening: Set the debug levels back to "0" in the config file (these won't help us anyway), and set the debug level of "segv" to "1". When navit crashes, this should use the GNU debugger (gdb, included in the Navit on TomTom? binary package) to print a "stack trace", which should appear in the log file. The stack trace can show what exactly navit is doing when the crash occurs. I hope it works...
comment:6 Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
Ok, I have changed the logging for navit and vehicle_file to 0 and segv to 1. Then I have started my TT and wait for a long time for a valid GPS-Signal. Then I have started navit and 2 minutes later was it's kills by watchdog.
I will added the navit.log and navit-wrapper.log, but the navit.log contains no stack trace. :-(
I wondering about the load in the navit-wrapper.log: it rises to over 3. With logging-level 5 for navit and vehicle_file the maximum value was about 2 in the last and the last 5 minutes.
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
navit.log from 2011-jun-05, log-level 0 for navit und vehicle_file and 1 for segv
Changed 12 years ago by me.yahoo.com/a/jya23di6w_0a00d6zazcw88xiiakhiu91aw-#78152
navit-wrapper.log from 2011-jun-05, log-level 0 for navit und vehicle_file and 1 for segv
comment:7 Changed 10 years ago by usul
- Component changed from core to port/tomtom
- Keywords tomtom crash added
- Milestone set to version 0.5.1
- Priority changed from major to critical
comment:8 Changed 10 years ago by xenos1984
- Owner changed from KaZeR to xenos1984
- Status changed from new to assigned
comment:9 Changed 4 years ago by http://wiki.navit-project.org/index.php/user:jkoan
- Milestone changed from version 0.5.1 to version 0.6.0
Ticket retargeted after milestone closed
The normal navit-log-file