From: Arno Verhoeven <pe1icq@pi8zaa.ampr.org>
To: linux-hams@vger.kernel.org
Subject: Re: PROBLEM: gMFSK v0.5 locks up.
Date: Sun, 13 Jul 2003 22:15:02 +0200 [thread overview]
Message-ID: <3F11BDC6.2080306@pi8zaa.ampr.org> (raw)
In-Reply-To: <1058027447.1273.58.camel@oh2bns.ampr.org>
Tomi Manninen wrote:
>On Sat, 2003-07-12 at 11:04, Arno Verhoeven wrote:
>
>
>
>>Until now I didn't get it to produce any sound yet. (sound works on that
>>system. Other applications can use the sound card)
>>
>>
>
>Are you getting any sound input? I mean does the waterfall show any
>noise?
>
No, nothing shows up.
>>1. click the "Abort transmission immediately" button.
>>2. click the "Mode" pull-down menu and try to select another mode.
>>
>>
>
>This would indicate that the current RX thread is stuck somewhere
>(and the rest of the program is waiting for it to complete). It could
>be a blocked open() or read(). Are you sure no-one else is having the
>sound card open?
>
I have no other program running that would use the sound card. Th elock
ups also occur when I use a simple windowmanger like twm.
(trying to avoid kde's sound server from interfering...)
>Edson's idea is also good. Knowing where exactly it is stuck is
>valuable information.
>
This is the last bit of output from strace after I try to select another
mode.
ead(3, "\7\4b\23i\v@\1:\0\0\0002\0 \0034\0 \3f\2X\0!\0\3\0\20\0"..., 32) = 32
read(3, "\7\3b\23i\v@\1:\0\0\0004\0 \3\0\0\0\0f\2X\0\37\0\1\0\20"..., 32) = 32
read(3, "\22\0d\23\216\1 \3\216\1 \3\0\16\217\10\216\1 \3\0\0\0"..., 32) = 32
read(3, "\10\3e\23i\v@\1:\0\0\0\37\0 \3\0\0\0\0f\2X\0I\0D\0\20\0"..., 32) = 32
read(3, "\7\4e\23i\v@\1:\0\0\0002\0 \0034\0 \3f\2X\0!\0\3\0\20\0"..., 32) = 32
read(3, "\7\3e\23i\v@\1:\0\0\0004\0 \3\0\0\0\0f\2X\0\37\0\1\0\20"..., 32) = 32
read(3, "\t\3f\23\4\0 \3\2\364\377\277\37I\f\10\310\22`\10\3002"..., 32) = 32
read(3, "\1\2g\23\0\0\0\0\4\0 \3\0\0\0\0\0\0\0\0\1\0\0\0\0\327\332"..., 32) = 32
rt_sigprocmask(SIG_SETMASK, NULL, [RTMIN], 8) = 0
rt_sigsuspend([]
>Oh, does the CPU load increase when gmfsk is locked up?
>
>
No, the CPU load doesn't go up.
--
73, PE1ICQ Arno Verhoeven
--------------------------------
AX.25 pe1icq@pi8zaa.#nbo.nld.eu
smtp pe1icq@pi8zaa.ampr.org
inet pe1icq@amsat.org
prev parent reply other threads:[~2003-07-13 20:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 18:58 ANNOUNCE: gMFSK v0.5 Tomi Manninen
2003-04-20 2:37 ` Hamish Moffatt
2003-04-20 9:32 ` Gérard Parat / F6FGZ
2003-07-11 20:29 ` Arno Verhoeven
2003-07-11 21:11 ` Tomi Manninen
2003-07-12 10:40 ` Wilbert Knol
2003-07-11 21:25 ` Aleksandar Ilic
2003-07-11 21:50 ` Arno Verhoeven
2003-07-12 8:04 ` PROBLEM: gMFSK v0.5 locks up Arno Verhoeven
2003-07-12 8:13 ` Hamish Moffatt
2003-07-12 15:07 ` Arno Verhoeven
2003-07-12 15:12 ` Edson Pereira
2003-09-11 7:51 ` SOLVED (Re: PROBLEM: gMFSK v0.5 locks up.) Arno Verhoeven
2003-07-12 16:30 ` PROBLEM: gMFSK v0.5 locks up Tomi Manninen
2003-07-13 20:15 ` Arno Verhoeven [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F11BDC6.2080306@pi8zaa.ampr.org \
--to=pe1icq@pi8zaa.ampr.org \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox