gpsd and uputronics HAB-GPSPI-NAN

Moderators: mdrjr, odroid

gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Mon Nov 14, 2016 3:25 pm

Problem with gpsd 3.16. If I start it the way I'm understanding it should be started, the systems barfs and needs a hard reset. Details below.

thoughts? what simple obvious thing am I missing?

Thanks,



* ppstest /dev/pps0 shows pps working
* Only two serial ports /dev/ttyS0 and /dev/ttyS1
* cat /dev/ttyS1 shows GPS data coming in.
(most internet discussion says GPS data should be coming from /dev/ttyS2, but there isn't a ttyS2)

From https://lists.ntpsec.org/pipermail/deve ... 00762.html
> # ./gpsd -n -N -D 5 /dev/ttyS2 /dev/pps0

Except use /dev/ttyS1

# /usr/sbin/gpsd -n -N -D 5 /dev/ttyS1 /dev/pps0


Gives the following, and then the machine is unresponsive and needs a hard reboot

root@odroid64:~# /usr/sbin/gpsd -n -N -D 5 /dev/ttyS1 /dev/pps0
gpsd:INFO: launching (Version 3.16)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTP: shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTP: shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTP: shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTP: shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: NTP: shmat(131076,0,0) succeeded, segment 4
gpsd:PROG: NTP: shmat(163845,0,0) succeeded, segment 5
gpsd:PROG: NTP: shmat(196614,0,0) succeeded, segment 6
gpsd:PROG: NTP: shmat(229383,0,0) succeeded, segment 7
gpsd:PROG: shmget(0x47505344, 8936, 0666) for SHM export succeeded
gpsd:PROG: shmat() for SHM export succeeded, segment 262152
gpsd:INFO: stashing device /dev/ttyS1 at slot 0
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS1'
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:PROG: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:INFO: gpsd_activate(2): activated GPS (fd 5)
gpsd:PROG: PPS:/dev/ttyS1 chrony socket /var/run/chrony.ttyS1.sock doesn't exist
gpsd:INFO: KPPS:/dev/ttyS1 cannot set PPS line discipline Invalid argument
gpsd:WARN: KPPS:/dev/ttyS1 kernel PPS unavailable, PPS accuracy will suffer
gpsd:PROG: PPS:/dev/ttyS1 thread launched
gpsd:INFO: PPS:/dev/ttyS1 ntpshm_link_activate: 1
gpsd:INFO: device /dev/ttyS1 activated
gpsd:INFO: stashing device /dev/pps0 at slot 1
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:PROG: switch_driver(PPS) called...
gpsd:PROG: selecting PPS driver...
gpsd:PROG: PPS:/dev/pps0 chrony socket /var/run/chrony.pps0.sock doesn't exist
gpsd:INFO: KPPS:/dev/pps0 RFC2783 path:/dev/pps0, fd is 6



gear:
odroid C2, new, about 2 weeks ago.
uputronics HAB-GPSPI-NAN
ubuntu64-16.04-minimal-odroid-c2-20160815.img on sdcard
$ uname -an
Linux odroid64 3.14.79-93 #1 SMP PREEMPT Tue Nov 8 20:30:12 BRST 2016 aarch64 aarch64 aarch64 GNU/Linux



Code: Select all
$ /usr/sbin/gpsd -V
/usr/sbin/gpsd: 3.16 (revision 3.16)

joeblow@odroid64:~$ /usr/sbin/gpsd -L
/usr/sbin/gpsd: invalid option -- 'L'  # yes I know.  I wanted to show the compiled in options.
usage: gpsd [-b] [-n] [-N] [-D n] [-F sockfile] [-G] [-P pidfile] [-S port] [-h] device...
  Options include:
  -b                  = bluetooth-safe: open data sources read-only
  -n             = don't wait for client connects to poll GPS
  -N             = don't go into background
  -F sockfile          = specify control socket location
  -G                   = make gpsd listen on INADDR_ANY
  -P pidfile                = set file to record process ID
  -D integer (default 0)    = set debug level
  -S integer (default 2947) = set port for daemon
  -h                  = help message
  -V             = emit version and exit.
A device may be a local serial device for GPS input, or a URL in one
of the following forms:
     tcp://host[:port]
     udp://host[:port]
     {dgpsip|ntrip}://[user:passwd@]host[:port][/stream]
     gpsd://host[:port][/device][?protocol]
in which case it specifies an input source for device, DGPS or ntrip data.

The following driver types are compiled into this gpsd instance:
            NMEA0183
            Ashtech
            Delorme TripMate
            Pre-2003 Delorme EarthMate
            Furuno Electric GH-79L4
n            Garmin NMEA
      c      MTK-3301
            OceanServer OS5000
            San Jose Navigation FV18
   b         True North
      c      Jackson Labs Fury
         *   AIVDM
n   b   c   *   EverMore
n         *   Garmin Serial binary
         *   Garmin USB binary
n   b      *   GeoStar
         *   iTalk
         *   Motorola Oncore
   b      *   Navcom NCT
n   b      *   SiRF
n   b      *   SuperStarII
n   b      *   Trimble TSIP
n   b   c   *   u-blox
   b      *   Zodiac
         *   NMEA2000
         *   RTCM104V2
         *   RTCM104V3
         *   Garmin Simple Text
         *   JSON slave driver
            PPS
# n: mode switch, b: speed switch, c: rate switch, *: non-NMEA packet type.
# Socket export enabled.
# Shared memory export enabled.
# Time service features enabled.
# PPS enabled.



Code: Select all
$ sudo ppstest /dev/pps0
[sudo] password for joeblow:
trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
ok, found 1 source(s), now start fetching data...
source 0 - assert 1479093033.999998311, sequence: 2198 - clear  0.000000000, sequence: 0
source 0 - assert 1479093034.999997559, sequence: 2199 - clear  0.000000000, sequence: 0
source 0 - assert 1479093035.999997803, sequence: 2200 - clear  0.000000000, sequence: 0
source 0 - assert 1479093036.999998045, sequence: 2201 - clear  0.000000000, sequence: 0
source 0 - assert 1479093037.999998285, sequence: 2202 - clear  0.000000000, sequence: 0
source 0 - assert 1479093038.999999516, sequence: 2203 - clear  0.000000000, sequence: 0
^C




Code: Select all
$ ls -la /dev/ttyS
ttyS0  ttyS1



Code: Select all
joeblow@odroid64:~$ ls -la /dev/ttyS1
crw-rw---- 1 root dialout 242, 1 Feb 11  2016 /dev/ttyS1
joeblow@odroid64:~$ cat /dev/ttyS1
b�b��bªb��b�ºb��b²b��b���b��bºb��b���bbʚb��b���bR��j
$GNGLL,6112.35383,N,14950.22516,W,031855.00,A,D*6B

$GNTXT,01,01,01,NMEA unknown msg*46

$GNTXT,01,01,01,NMEA unknown msg*46

$GNTXT,01,01,01,NMEA unknown msg*46

$GNRMC,031856.00,A,6112.35377,N,14950.22521,W,0.369,,141116,,,D*70

$GNVTG,,T,,M,0.369,N,0.682,K,D*38

$GNGGA,031856.00,6112.35377,N,14950.22521,W,2,12,0.69,24.7,M,11.3,M,,0000*6A

$GNGSA,A,3,23,09,06,03,26,16,07,48,02,,,,1.49,0.69,1.32*18

$GNGSA,A,3,86,69,70,79,68,78,85,,,,,,1.49,0.69,1.32*1B

$GPGSV,4,1,15,02,32,299,26,03,19,144,31,05,01,309,,06,36,254,20*79

$GPGSV,4,2,15,07,27,199,27,09,73,237,38,16,28,094,14,22,04,141,26*7C

$GPGSV,4,3,15,23,65,106,34,26,30,061,21,29,13,003,12,31,02,042,12*77

$GPGSV,4,4,15,46,09,124,,48,19,161,30,51,12,134,*41

$GLGSV,3,1,12,68,36,119,28,69,88,259,21,70,28,298,27,77,16,027,*67

$GLGSV,3,2,12,78,60,076,20,79,48,157,30,80,00,189,,84,00,244,*69

^C
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby rooted » Mon Nov 14, 2016 4:42 pm

ltgcc wrote:Problem with gpsd 3.16. If I start it the way I'm understanding it should be started, the systems barfs and needs a hard reset. Details below.

thoughts? what simple obvious thing am I missing?


I don't see anything that jumps out, do you have the UART so we can see what's happening when the kernel locks?
User avatar
rooted
 
Posts: 5680
Joined: Fri Dec 19, 2014 9:12 am
Location: Gulf of Mexico, US
languages_spoken: english
ODROIDs: C1, C1+, C2
XU3 Lite, XU4
N1
VU7+
HiFi Shield 2
Smart Power (original)

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby odroid » Mon Nov 14, 2016 6:04 pm

/dev/ttyS1 is correct one. Don't worry.
http://odroid.com/dokuwiki/doku.php?id= ... dware_uart

Do you use the PPS input on #12 of 40pin header?
http://odroid.com/dokuwiki/doku.php?id=en:c2_gpio_pps
User avatar
odroid
Site Admin
 
Posts: 28859
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 15, 2016 4:18 am

Thank you for the replies.

> I don't see anything that jumps out, do you have the UART so we can see what's happening when the kernel locks?

By UART, I assume you mean the 4pin 'serial console' output? No I don't. I did not get the level shifter for this SBC as it was being purchased for a single (supposedly) simple well defined purpose. I do have an old nokia 2102 USB adapter that I've used for other SBC's. I'll give it a try if I need to.

> /dev/ttyS1 is correct one. Don't worry.

Excellent. Thank you.

> Do you use the PPS input on #12 of 40pin header?

Yes. In fact, that is the wikipage I used to set PPS up. PPS appears to be working per ppstest /dev/pps0

Thank you.
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby odroid » Tue Nov 15, 2016 12:57 pm

I just tried this instruction with our USB GPS and the gpsd seems to be working well. But it has no pps option.
http://odroid.com/dokuwiki/doku.php?id=en:c1_usb_gps
So the "gpsd" package should be okay.

What happens if you run gpsd without "/dev/pps0" option?
User avatar
odroid
Site Admin
 
Posts: 28859
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 15, 2016 3:59 pm

Code: Select all
root@odroid64:~# /usr/sbin/gpsd -N -n -D 5 /dev/ttyS1
gpsd:INFO: launching (Version 3.16)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTP: shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTP: shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTP: shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTP: shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: NTP: shmat(131076,0,0) succeeded, segment 4
gpsd:PROG: NTP: shmat(163845,0,0) succeeded, segment 5
gpsd:PROG: NTP: shmat(196614,0,0) succeeded, segment 6
gpsd:PROG: NTP: shmat(229383,0,0) succeeded, segment 7
gpsd:PROG: shmget(0x47505344, 8936, 0666) for SHM export succeeded
gpsd:PROG: shmat() for SHM export succeeded, segment 262152
gpsd:INFO: stashing device /dev/ttyS1 at slot 0
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS1'
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0aroot@odroid64:~
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:PROG: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:INFO: gpsd_activate(2): activated GPS (fd 5)
gpsd:PROG: PPS:/dev/ttyS1 chrony socket /var/run/chrony.ttyS1.sock doesn't exist
gpsd:INFO: KPPS:/dev/ttyS1 cannot set PPS line discipline Invalid argument
gpsd:WARN: KPPS:/dev/ttyS1 kernel PPS unavailable, PPS accuracy will suffer
gpsd:PROG: PPS:/dev/ttyS1 thread launched
gpsd:INFO: PPS:/dev/ttyS1 ntpshm_link_activate: 1
gpsd:INFO: device /dev/ttyS1 activated


...and......nothing. No ping responses, no update, cannot ^C, have to unplug/replug.

One thing I did try, based on somebody's (satsignal.eu?) discussion was to put thick paper between the uputronics and the C2 heatsink in case there was some weird short or proximity condition. No difference.

Another thing I tried is I stopped ntp before starting gpsd, just on the thought that something in ntp may have been interfering:


Code: Select all
root@odroid64:~# service ntp stop
root@odroid64:~# /usr/sbin/gpsd -n -N -D 5 /dev/ttyS1
gpsd:INFO: launching (Version 3.16)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTP: shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTP: shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTP: shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTP: shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: NTP: shmat(131076,0,0) succeeded, segment 4
gpsd:PROG: NTP: shmat(163845,0,0) succeeded, segment 5
gpsd:PROG: NTP: shmat(196614,0,0) succeeded, segment 6
gpsd:PROG: NTP: shmat(229383,0,0) succeeded, segment 7
gpsd:PROG: shmget(0x47505344, 8936, 0666) for SHM export succeeded
gpsd:PROG: shmat() for SHM export succeeded, segment 262152
gpsd:INFO: stashing device /dev/ttyS1 at slot 0
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS1'
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:PROG: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:INFO: gpsd_activate(2): activated GPS (fd 5)
gpsd:PROG: PPS:/dev/ttyS1 chrony socket /var/run/chrony.ttyS1.sock doesn't exist
gpsd:INFO: KPPS:/dev/ttyS1 cannot set PPS line discipline Invalid argument
gpsd:WARN: KPPS:/dev/ttyS1 kernel PPS unavailable, PPS accuracy will suffer
gpsd:PROG: PPS:/dev/ttyS1 thread launched
gpsd:INFO: PPS:/dev/ttyS1 ntpshm_link_activate: 1
gpsd:INFO: device /dev/ttyS1 activated


aaaand....hung again. Unplug. Repeat.
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 15, 2016 4:09 pm

removed my scons gpsd, and performed apt-get install gpsd to get the older gpsd straight from the repository:

Code: Select all
root@odroid64:~# /usr/sbin/gpsd -N -n -D5 /dev/ttyS1
gpsd:INFO: launching (Version 3.15)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTP: shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTP: shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTP: shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTP: shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: NTP: shmat(131076,0,0) succeeded, segment 4
gpsd:PROG: NTP: shmat(163845,0,0) succeeded, segment 5
gpsd:PROG: NTP: shmat(196614,0,0) succeeded, segment 6
gpsd:PROG: NTP: shmat(229383,0,0) succeeded, segment 7
gpsd:PROG: successfully connected to the DBUS system bus
gpsd:PROG: shmget(0x47505344, 8936, 0666) for SHM export succeeded
gpsd:PROG: shmat() for SHM export succeeded, segment 262152
gpsd:INFO: stashing device /dev/ttyS1 at slot 0
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS1'
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:PROG: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: Probing "Garmin USB binary" driver...
gpsd:PROG: Probe not found "Garmin USB binary" driver...
gpsd:PROG: Probing "GeoStar" driver...
gpsd:PROG: Sent GeoStar packet id 0xc1
gpsd:IO: => GPS: 5053474700c100010000000050924746
gpsd:PROG: Probe not found "GeoStar" driver...
gpsd:PROG: Probing "Trimble TSIP" driver...
gpsd:INFO: speed 9600, 8O1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:PROG: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:PROG: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: Probe not found "Trimble TSIP" driver...
gpsd:PROG: no probe matched...
gpsd:INFO: gpsd_activate(2): activated GPS (fd 6)
gpsd:PROG: PPS:/dev/ttyS1 chrony socket /var/run/chrony.ttyS1.sock doesn't exist
gpsd:INFO: KPPS:/dev/ttyS1 cannot set PPS line discipline Invalid argument
gpsd:WARN: KPPS:/dev/ttyS1 kernel PPS unavailable, PPS accuracy will suffer
gpsd:PROG: PPS:/dev/ttyS1 thread launched
gpsd:INFO: PPS:/dev/ttyS1 ntpshm_link_activate: 1
gpsd:INFO: device /dev/ttyS1 activated


hung. Unplug. Rinse. Repeat.
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 15, 2016 4:12 pm

I do wonder... The gpsd debug keeps bellyaching about chrony, but I'm not using chrony; it's not even installed. I've assumed that gpsd is simply checking for chrony, or setting up in case it's there, but otherwise not relevant. Maybe that's a wrong assumption (and no, I don't want to use chrony except maybe as a test case; i don't think ntp is the problem. I'm not even getting that far in the chain of what needs to happen)
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 15, 2016 4:21 pm

I ran gpsd again, this time leaving out the /dev/ttyS1. It didn't hang. The debug did show some interesting looking issues though. But the point is that it didn't hang, and I'm still able to interact with the shell. No reboot required.
This seems to indicate to me that there's some problem or conflict involving /dev/ttyS1. But I don't know how to pursue this further at this time.

Code: Select all
root@odroid64:~# /usr/sbin/gpsd -N -n -D5 /dev/pps0
gpsd:INFO: launching (Version 3.15)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTP: shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTP: shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTP: shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTP: shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: NTP: shmat(131076,0,0) succeeded, segment 4
gpsd:PROG: NTP: shmat(163845,0,0) succeeded, segment 5
gpsd:PROG: NTP: shmat(196614,0,0) succeeded, segment 6
gpsd:PROG: NTP: shmat(229383,0,0) succeeded, segment 7
gpsd:PROG: successfully connected to the DBUS system bus
gpsd:PROG: shmget(0x47505344, 8936, 0666) for SHM export succeeded
gpsd:PROG: shmat() for SHM export succeeded, segment 262152
gpsd:INFO: stashing device /dev/pps0 at slot 0
gpsd:PROG: switch_driver(PPS) called...
gpsd:PROG: selecting PPS driver...
gpsd:PROG: PPS:/dev/pps0 chrony socket /var/run/chrony.pps0.sock doesn't exist
gpsd:INFO: KPPS:/dev/pps0 RFC2783 path:/dev/pps0, fd is 6
gpsd:INFO: KPPS:/dev/pps0 pps_caps 0x1151
gpsd:INFO: KPPS:/dev/pps0 have PPS_CANWAIT
gpsd:WARN: KPPS:/dev/pps0 missing PPS_CAPTURECLEAR, pulse may be offset
gpsd:INFO: KPPS:/dev/pps0 kernel PPS will be used
gpsd:PROG: PPS:/dev/pps0 thread launched
gpsd:INFO: PPS:/dev/pps0 ntpshm_link_activate: 0
gpsd:INFO: device /dev/pps0 activated
gpsd:INFO: KPPS:/dev/pps0 gps_fd:-2 not a tty
gpsd:ERROR: KPPS:/dev/pps0 kernel PPS failed Interrupted system call
gpsd:ERROR: KPPS:/dev/pps0 kernel PPS failed Interrupted system call
gpsd:ERROR: KPPS:/dev/pps0 kernel PPS failed Interrupted system call
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 110
gpsd:INFO: startup at 2016-02-11T16:29:40.000Z (1455208180)
gpsd:PROG: KPPS:/dev/pps0 assert  1455208181.455031000, sequence: 101, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle: 247126199, duration:       0 @  1455208181.455031000
gpsd:PROG: PPS:/dev/pps0 Assert cycle: 247126199, duration:       0 @  1455208181.455031000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208182.455002000, sequence: 102, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208182.455002000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208182.455002000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208183.454973000, sequence: 103, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208183.454973000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208183.454973000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208184.454945000, sequence: 104, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999972, duration:       0 @  1455208184.454945000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999972, duration:       0 @  1455208184.454945000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208185.454916000, sequence: 105, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208185.454916000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208185.454916000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208186.454887000, sequence: 106, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208186.454887000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999971, duration:       0 @  1455208186.454887000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208187.454861000, sequence: 107, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999974, duration:       0 @  1455208187.454861000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999974, duration:       0 @  1455208187.454861000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208188.454830000, sequence: 108, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999969, duration:       0 @  1455208188.454830000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999969, duration:       0 @  1455208188.454830000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1455208189.454802000, sequence: 109, clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle:  999972, duration:       0 @  1455208189.454802000
gpsd:PROG: PPS:/dev/pps0 Assert cycle:  999972, duration:       0 @  1455208189.454802000
gpsd:PROG: PPS:/dev/pps0 Assert rejected missing last_fixtime
^C*** buffer overflow detected ***: /usr/sbin/gpsd terminated
Aborted
root@odroid64:~#
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 15, 2016 4:23 pm

one more note:

I'm pretty sure the uputronics is fine because:
* cat /dev/ttyS1 streams NMEA strings
* ppstest /dev/pps0 streams right looking strings
* this uputronics card was in a rpi3 for a while and worked in that setup.

Thanks.
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 15, 2016 4:39 pm

you know, I'm an idiot. I could enable rsyslog and see if anything gets dumped into messages when the odroid hangs. But it's late. I'll do that if I get time later this week.
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 22, 2016 6:42 pm

tl;dr to my untrained eye it looks like a problem between gpsd and ttyS1

nothing related in rsyslog.

i've attached the following for anyone interested in pursuing this further:

strace gpsd -N -n -D 5 /dev/ttyS1 /dev/pps0

strace gpsd -N -n -D 5 /dev/ttyS1

strace gpsd -N -n /dev/ttyS1 (no -D 5)

A pic of the screen after strace gpsd -N -n /dev/ttyS1 caused the keyboard and nic to become unresponsive. I don't have the level shifting serial console adapter
Attachments
20161122_002529_resized.jpg
pic of screen after gpsd barf
(225.53 KiB) Downloaded 727 times
odroid-c2-strace-gpsd-dev-ttyS1.txt
strace gpsd ttyS1 no -D 5
(78.85 KiB) Downloaded 59 times
strace-gpsd-dev-ttyS1-no-pps0.log
strace gpsd ttyS1 no pps0
(95.28 KiB) Downloaded 52 times
strace-gpsd-dev-ttyS1-and-pps0.log
strace gpds ttyS1 pps0
(95.67 KiB) Downloaded 55 times
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Tue Nov 22, 2016 6:45 pm

one last thing. For what it's worth, all of the above was done with the ubuntu-minimal image. When I was messing with this early last week, I got similar results with the DietPi C2 image.
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby odroid » Wed Nov 23, 2016 11:41 am

I couldn't find any clue in the log files.

I just guess the gpsd was calling a unsupported UART IOCTL and it caused the kernel panic.
But it is not easy to trace the root cause since we have no UART type GPS module on our hands. Sorry about that.
User avatar
odroid
Site Admin
 
Posts: 28859
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby rooted » Wed Nov 23, 2016 3:10 pm

I suggest compiling gpsd 1.19 from source on the C2 and trying it, maybe a bug in 1.18
User avatar
rooted
 
Posts: 5680
Joined: Fri Dec 19, 2014 9:12 am
Location: Gulf of Mexico, US
languages_spoken: english
ODROIDs: C1, C1+, C2
XU3 Lite, XU4
N1
VU7+
HiFi Shield 2
Smart Power (original)

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby ltgcc » Thu Nov 24, 2016 2:34 pm

do you mean gpsd ver 3.xx? or <something else> ver 1.19? the latest gpsd i see at http://download.savannah.gnu.org/releases/gpsd/ is 3.16.

thanks,
ltgcc
 
Posts: 11
Joined: Mon Nov 14, 2016 11:48 am
languages_spoken: english
ODROIDs: C2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby t3uKVg » Thu Dec 21, 2017 9:54 am

did you have any luck making this work - Im seeing the same issues as you reported above with latest ubuntu minimal install (http://odroid.in/ubuntu_16.04lts) and gpsd.
I also see NTP fail just trying to use the NMEA #20 reference driver without GPSD too.
I confirm both pps0 is displaying PPS timing beacons and /dev/gps0 is displaying the correct NMEA sentences.
t3uKVg
 
Posts: 1
Joined: Thu Dec 14, 2017 4:41 pm
languages_spoken: english
ODROIDs: c2

Re: gpsd and uputronics HAB-GPSPI-NAN

Unread postby eddy » Tue May 29, 2018 10:09 pm

Darn, I'm having this exact issue as well...

I can't start gpsd without it locking up and requiring a power-cycle of the C2.

Running kernel 3.16.56+ (on a C2 via DietPi) and gpsd 3.16-4.

Code: Select all
root@timekeeper:~# apt-cache showpkg gpsd
Package: gpsd
Versions:
3.16-4 (/var/lib/apt/lists/deb.debian.org_debian_dists_stretch_main_binary-arm64_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/deb.debian.org_debian_dists_stretch_main_binary-arm64_Packages
                  MD5: c27e4861a82769d7dbf1f60e97926430

I do have /dev/pps0 displaying PPS timing beacons (via ppstest) and /dev/gps0 (which is just a symlink to ttyS1) displaying NMEA sentences.

Has there been any more work in tracking down what gpsd is doing that is causing this kernel hang?
eddy
 
Posts: 4
Joined: Tue May 29, 2018 9:52 pm
languages_spoken: english
ODROIDs: C2


Return to Ubuntu

Who is online

Users browsing this forum: No registered users and 2 guests