Hi Bill,
Interesting results. The first time I ran it under control of gdb WSJT-X
started up properly. I gracefully ended it and then re-started. Below is the
output you requested. I noticed that, on the first, successful attempt, there
were six threads started after the last ALSA warning. On the failure attempt,
it died with a memory access failure after the first thread had started. Is
this indicative of a bad Raspberry Pi card? Not having this issue anywhere
else...
(gdb) r
Starting program: /usr/local/bin/wsjtx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
libEGL warning: DRI2: failed to authenticate
[New Thread 0x705fa3d0 (LWP 4278)]
[New Thread 0x6fdfa3d0 (LWP 4279)]
[New Thread 0x6f5fa3d0 (LWP 4280)]
[New Thread 0x6edfa3d0 (LWP 4281)]
[New Thread 0x6e5bc3d0 (LWP 4282)]
[New Thread 0x6ca873d0 (LWP 4283)]
[New Thread 0x6c02c3d0 (LWP 4284)]
ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports only
playback stream
ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports only
playback stream
ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports only
playback stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
[New Thread 0x675bd3d0 (LWP 4307)]
^CCannot access memory at address 0x5
Program received signal SIGINT, Interrupt.
Cannot access memory at address 0x5
0x76457bc4 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
(gdb) info threads
Id Target Id Frame
9 Thread 0x675bd3d0 (LWP 4307) "QThread" 0x75a74c80 in poll ()
at ../sysdeps/unix/syscall-template.S:81
8 Thread 0x6c02c3d0 (LWP 4284) "threaded-ml" 0x75a74c80 in poll ()
at ../sysdeps/unix/syscall-template.S:81
7 Thread 0x6ca873d0 (LWP 4283) "Qt bearer threa" 0x75a74c80 in poll ()
at ../sysdeps/unix/syscall-template.S:81
6 Thread 0x6e5bc3d0 (LWP 4282) "QXcbEventReader" 0x75a74c80 in poll ()
at ../sysdeps/unix/syscall-template.S:81
5 Thread 0x6edfa3d0 (LWP 4281) "llvmpipe-3" 0x75af97a4 in
__pthread_cond_wait (cond=0x3cbdf60, mutex=0x3cbdf48) at pthread_cond_wait.c:187
4 Thread 0x6f5fa3d0 (LWP 4280) "llvmpipe-2" 0x75af97a4 in
__pthread_cond_wait (cond=0x3cbde50, mutex=0x3cbde38) at pthread_cond_wait.c:187
3 Thread 0x6fdfa3d0 (LWP 4279) "llvmpipe-1" 0x75af97a4 in
__pthread_cond_wait (cond=0x3cbdd40, mutex=0x3cbdd28) at pthread_cond_wait.c:187
2 Thread 0x705fa3d0 (LWP 4278) "llvmpipe-0" 0x75af97a4 in
__pthread_cond_wait (cond=0x3cbdc30, mutex=0x3cbdc18) at pthread_cond_wait.c:187
* 1 Thread 0x735f9000 (LWP 4277) "wsjtx" Cannot access memory at address 0x5
0x76457bc4 in ?? ()
from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
(gdb) bt
#0 0x76457bc4 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
#1 0x00000000 in ?? ()
(gdb)
73, Jim / W6JHB
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Monday, May 30, 2016 2:48 AM
Subject: Re: [wsjt-devel] WSJT-X r6707 Startup Problems
On 30/05/2016 05:18, Jim Bennett wrote:
> Need some help or suggestions here - running a compiled r6707 version
> on a Raspberry Pi 3 under Raspian Jessie. I start WSJT-X via a
> terminal session. During startup I usually get several ALSA "error"
> messages like "the dmix plugin supports only playback stream" or "the
> dsnoop plugin supports only capture stream". There are normally six to
> eight of them and then WSJT-X starts up. Occasionally, after those
> messages appear on the terminal, WSJT-X does NOT start; it just sits
> there doing nothing. I have to do a CTRL-C to kill it. I try again and
> it starts up OK.
>
> Well, now it does not start. I've tried it a bazillion times. Same
> problem - just sits there. CPU utilization is sitting right around 25%
> which is what I usually see when WSJT-X is running. Have booted the
> RPi several times - no luck.
>
> Any ideas what I can do to get this fixed so I can get the application
> running again?
Hi Jim,
are you sure that there is not a window hiding somewhere waiting for a
response. For example if you killed a previous instance there may be a
stale lock file which WSJT-X will ask for confirmation before deleting
it and carrying on with its start up.
If that doesn't get you going I can explain how to determine where it is
getting hung up.
73
Bill
G4WJS.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
