From: Cathryn Mataga <cathryn@junglevision.com>
To: linux-hams@vger.kernel.org
Cc: bernard.pidoux@upmic.fr
Subject: Re: xfbbd oddness.
Date: Fri, 12 Nov 2010 13:23:50 -0800 [thread overview]
Message-ID: <4CDDB066.4040801@junglevision.com> (raw)
In-Reply-To: <4CDA0972.40108@junglevision.com>
Actually, I think ignoring the SIGPIPE and other signals
does fix a real problem. I changed this, and I ran
about a day with no SIGPIPE faults -- that is with
frequent connects from an actual RF-based AX25 connection.
No functionality is lost by ignore these signals, so I think
I will send in a patch for this at some point.
With this one patch, I think xfbbd is basically usable for
me on RF connections.
There still is a bug. After awhile, I start seeing...
select: Bad file descriptor
select: Bad file descriptor
select: Bad file descriptor
select: Bad file descriptor
and then the system bugs out. The script normally restarts
it, though I'm running from gdb myself so for me it just dies.
Via google, I see someone reported this bug back in 2004. That
was 6 years ago, so it is obviously a very old bug.
At least it's consistent, I suppose.
next prev parent reply other threads:[~2010-11-12 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 12:33 [PATCH 4/11] drivers/net/hamradio: Eliminate a NULL pointer dereference Julia Lawall
2010-05-27 12:33 ` Julia Lawall
2010-05-27 23:29 ` [PATCH 4/11] drivers/net/hamradio: Eliminate a NULL pointer David Miller
2010-05-27 23:29 ` [PATCH 4/11] drivers/net/hamradio: Eliminate a NULL pointer dereference David Miller
2010-11-09 19:09 ` xfbbd oddness Cathryn Mataga
2010-11-10 2:54 ` Cathryn Mataga
2010-11-12 21:23 ` Cathryn Mataga [this message]
2010-11-14 6:52 ` Cathryn Mataga
2010-11-14 6:58 ` [PATCH] xfbbd: Fix issue with xfbbd and AX25 radio connections Cathryn Mataga
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=4CDDB066.4040801@junglevision.com \
--to=cathryn@junglevision.com \
--cc=bernard.pidoux@upmic.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.