From: Robert Voigt <robert.voigt@thalesatm.com>
To: linux-ppp@vger.kernel.org
Subject: No packets get through after a while
Date: Fri, 30 Nov 2007 11:18:58 +0000 [thread overview]
Message-ID: <1196421538.2082.89.camel@sls6bk> (raw)
Hi everybody,
here is a strange problem that I can't solve:
I have a ppp connection from an embedded board with Fedora 7 (ppp 2.4.4,
stock kernel-2.6.21) over null modem cable to a FC6 PC (ppp 2.4.4,
kernel 2.6.18). I'm pinging from the board to the PC. After a while, it
can be a few minutes or several hours, no packets from ping or anything
else get through. It works again when I restart pppd on the board.
I'm starting pppd on the board in /etc/inittab:
pp:2345:respawn:/usr/sbin/pppd lock persist nodetach crtscts debug
kdebug 7 192.168.1.2:192.168.1.1 /dev/ttyS2 38400
And on the PC:
pp:2345:respawn:/usr/sbin/pppd lock persist nodetach crtscts
192.168.1.1:192.168.1.2 /dev/ttyS1 38400
I don't get any log messages when this happens. (I have
daemon.* /var/log/ppp-log in /etc/syslog.conf)
The only thing I notice is when I start pppd on the commandline, when it
hangs and I Ctrl-C it, it does not return. On the second Ctrl-C it says:
tcsetattr: Interrupted system call (line 1001)
It returns on the third Ctrl-C.
When I Ctrl-C it when it does not hang, it returns correctly after
terminating.
I have tried a debug version of ppp 2.4.4. When it hangs the backtrace
shows the last line in ppp code is sys-linux.c:1051
void wait_input(struct timeval *timo)
{
...
n = select(max_in_fd + 1, &ready, NULL, &exc, timo);
...
}
But that seems to be always the place where it waits after
initialization. Is it in the kernel part of ppp then?
I will be grateful for any advice.
Robert
next reply other threads:[~2007-11-30 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 11:18 Robert Voigt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-01 18:18 No packets get through after a while James Carlson
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=1196421538.2082.89.camel@sls6bk \
--to=robert.voigt@thalesatm.com \
--cc=linux-ppp@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