public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug 1001696] New: cyg_ppp_up and cyg_wait_up sometimes never return
@ 2012-11-01 18:27 bugzilla-daemon
0 siblings, 0 replies; 2+ messages in thread
From: bugzilla-daemon @ 2012-11-01 18:27 UTC (permalink / raw)
To: ecos-bugs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug 1001696] New: cyg_ppp_up and cyg_wait_up sometimes never return
@ 2012-11-01 18:27 bugzilla-daemon
0 siblings, 0 replies; 2+ messages in thread
From: bugzilla-daemon @ 2012-11-01 18:27 UTC (permalink / raw)
To: unassigned
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 the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-11-01 18:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-11-01 18:27 [Bug 1001696] New: cyg_ppp_up and cyg_wait_up sometimes never return bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2012-11-01 18:27 bugzilla-daemon
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).