All of lore.kernel.org
 help / color / mirror / Atom feed
From: bfc <chappaquasuite@yahoo.com>
To: linux-ppp@vger.kernel.org
Subject: Re: modem session behavior
Date: Tue, 22 Apr 2008 16:08:12 +0000	[thread overview]
Message-ID: <16824945.post@talk.nabble.com> (raw)
In-Reply-To: <16169308.post@talk.nabble.com>


The problem was that sometimes the serial driver wouldn't send the data
loaded into
the FIFO.  Conversations with the modem would hang (and chat would
eventually time
out) -- or the connection would be made between modems, but I'd get a LCP
timeout
error -- from the same cause.

You may only get bit by this with particular UART hardware -- ours was
detected
(correctly) as a 16550A.  You should be able to find out what yours is by
either
grep 'serial' from /var/log/messages, or setserial -a /dev/ttyS0.  The
problem
did not occur on another machine with a NS16550A detected.

The problem kernel we had was 2.6.18 (and various minor versions up to
2.6.18-89).



cfowler-2 wrote:
> 
> I'm running ppp on a dual core P4.  I'm interested to know what problems
> you are seeing.  I run ppp in demand mode.  We use it heavily.  I was
> running it on FC2 with 2.6.10 but now I've switched to CentOS 5
> 2.6.18.... kernel.
> 
> In demand mode we have a program that is ran as if-down and if-up.  This
> is because another device can call in and gain the same address as the
> interface waiting.  The program downs the other interface and will up a
> down interface when ppp dies.  It is hard to explain but it makes 2
> devices work in demand mode with each other.
> 
> 
> On Fri, 2008-04-18 at 11:41 -0700, bfc wrote:
>> I should follow this up for search purposes.  This was Redhat bug 440121,
>> a problem with the serial driver on SMP machines.  That explains all the
>> troubles I posted about.  I'm sure it affects other distros, too, but
>> I suspect not many people are using higher end machines for PPP?
>> 
>> 
>> James Cameron-2 wrote:
>> > 
>> > ATH hangs up.  Perhaps the loss of CTS and DSR from the modem causes
>> the
>> > kernel and your terminal emulator to see nothing more.
>> > 
>> > Either configure the system to ignore the loss of CTS and DSR, or
>> > configure the modem not to drop CTS and DSR during a hangup.  Then try
>> > again.
>> > 
>> > I've no idea why you want to see anything more after ATH though.
>> > 
>> > -- 
>> > James Cameron
>> > http://ftp.hp.com.au/sigs/jc/
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> > 
>> > 
>> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

-- 
View this message in context: http://www.nabble.com/modem-session-behavior-tp16169308p16824945.html
Sent from the linux-ppp mailing list archive at Nabble.com.


  parent reply	other threads:[~2008-04-22 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  1:04 modem session behavior bfc
2008-03-20  2:32 ` James Cameron
2008-04-18 18:41 ` bfc
2008-04-18 18:56 ` Chris Fowler
2008-04-22 16:08 ` bfc [this message]
2008-04-22 16:18 ` Chris Fowler

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=16824945.post@talk.nabble.com \
    --to=chappaquasuite@yahoo.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 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.