Date: Thu, 30 Apr 2015 13:57:25 +0930 From: "O'Connor, Daniel" <darius@dons.net.au> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: pps_ioctl panic Message-ID: <50B95BBC-2C51-4380-AA7D-66EE2C02B4EC@dons.net.au> In-Reply-To: <55412972.8090709@selasky.org> References: <6CC431C0-2E54-4B49-94D0-D6B7A5919CD3@dons.net.au> <553F3833.5050600@selasky.org> <80538BF0-EBF5-4C58-A17A-5D8122BC6399@dons.net.au> <55412972.8090709@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 30 Apr 2015, at 04:26, Hans Petter Selasky <hps@selasky.org> wrote: >=20 > On 04/29/15 06:58, O'Connor, Daniel wrote: >>=20 >>> On 28 Apr 2015, at 17:05, Hans Petter Selasky <hps@selasky.org> = wrote: >>>=20 >>> On 04/28/15 09:08, O'Connor, Daniel wrote: >>>> Hi all, >>>> I'm trying to get gpsd + PPS working on a Beaglebone Black but when = I start gpsd I get the panic at the bottom of the email. >>>>=20 >>>> I've run ntpd to the same device with PPS without problems. >>>>=20 >>>> I haven't had a more detailed look yet though. >>>=20 >>> Hi, >>>=20 >>> Try to set "pps.mtx =3D &ttymx" before "pps_init()". >>=20 >> I tried adding both.. >> sc->pps.mtx =3D &ttymx; >> and >> sc->pps.mtx =3D &ttymtx; >>=20 >> but neither mutex exist. I had a look in the TTY code = (sys/kern/tty.c) and I couldn't see a likely candidate. >>=20 > Have a look in "sys/dev/usb/serial/usb_serial.c" OK I see. I had a better look and it seems odd. am335x_dmtimer.c doesn't have any = locks that I can see - certainly not TTY ones. I don't understand how the thread still has a TTY lock when the dmtpps = device isn't a TTY :( -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B95BBC-2C51-4380-AA7D-66EE2C02B4EC>