public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001696] New: cyg_ppp_up and cyg_wait_up sometimes never return
Date: Thu, 01 Nov 2012 18:27:00 -0000	[thread overview]
Message-ID: <bug-1001696-13@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001696

           Summary: cyg_ppp_up and cyg_wait_up sometimes never return
           Product: eCos
           Version: 3.0
          Platform: All
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: critical
          Priority: low
         Component: TCP/IP
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: kenkyee@excite.com
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Our application requires that we make multiple PPP connections to minimize
connection costs, so we have a pretty simple core bit of code that brings the
PPP line up and down.
Sometimes, eCos will hang during the cyg_ppp_up or cyg_ppp_wait_up calls.  The
only thing that shows up in the diag console is:
SYSLOG 08: Using interface ppp0
SYSLOG 04: Connect: ppp0 <--> /dev/ser0
SYSLOG 08: Connect time expired
SYSLOG 04: Connection terminated, connected for 1 minutes

The core loop is roughly like this:
    cyg_ppp_handle_t pppHandle = cyg_ppp_up(PPP_PORT, &options)
    if (pppHandle != 0) {
        int pppStatus = cyg_ppp_wait_up(pppHandle);
        if (pppStatus == 0) {
            // wait for connection to come down
            if (cyg_ppp_wait_up(pppHandle) == 0) {
                int pppTimeout = PPPMAXUPTIMESECS;    // PPP timeout in seconds
                while ((pppTimeout-- > 0) && (cyg_ppp_wait_up(pppHandle) == 0))
{
                    Thread::sleep(sec(1));
                }
            cyg_ppp_down(pppHandle);
        }
    }

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-11-01 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 18:27 bugzilla-daemon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-01 18:27 bugzilla-daemon

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=bug-1001696-13@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).