Linux PPP protocol development
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: pppd hangs on SIGHUP
Date: Wed, 20 Jan 2010 12:25:58 +0000	[thread overview]
Message-ID: <4B56F656.70407@workingcode.com> (raw)
In-Reply-To: <8D.DA.01403.892965B4@cdptpa-omtalb.mail.rr.com>

Leslie Rhorer wrote:
> nothing whatsoever.  The only way (of which I know) to release the terminal
> (/cev/ttyACM0) is to send a SIGKILL.  After doing so, /dev/ttyACM0 is
> released, and I can use a utility such as minicom to access the modem.  I
> can dial out and get a carrier.  I can see the ppp authentication request
> from the ISP.  What I cannot do, however, is get pppd to come back up.  If I
> start pppd again, it opens the /dev/ttyACM0 device and creates the lockfile,
> but it does not attempt to run chat or evidently do anything else other than
> refresh the lockfile if it is stale.  My only option at that point is to

If you attach a debugger to it, can you find out where it's stuck?  (Or
at least run "pstack `pgrep pppd`"?)

The symptoms sound like a kernel bug, but it's hard to tell.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  parent reply	other threads:[~2010-01-20 12:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  5:20 pppd hangs on SIGHUP Leslie Rhorer
2010-01-20  5:34 ` Bill Unruh
2010-01-20  5:43 ` James Cameron
2010-01-20  5:47 ` James Cameron
2010-01-20  5:53 ` Leslie Rhorer
2010-01-20  6:10 ` Leslie Rhorer
2010-01-20 12:25 ` James Carlson [this message]
2010-01-21  2:20 ` Leslie Rhorer
2010-01-21  2:47 ` Leslie Rhorer
2010-01-21 12:39 ` James Carlson
2010-01-21 15:19 ` Leslie Rhorer
2010-01-22  1:50 ` Leslie Rhorer
2010-01-22  2:13 ` James Cameron
2010-01-22  4:36 ` Leslie Rhorer
2010-01-23 17:40 ` Leslie Rhorer

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=4B56F656.70407@workingcode.com \
    --to=carlsonj@workingcode.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