From: Paul Fulghum <paulkf@microgate.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Linus Torvalds <torvalds@osdl.org>, Alan Cox <alan@redhat.com>
Subject: Re: Fwd: [Bug 3592] New: pppd "IPCP: timeout sending Config-Requests"
Date: Tue, 19 Oct 2004 09:17:48 -0500 [thread overview]
Message-ID: <1098195468.8467.7.camel@deimos.microgate.com> (raw)
In-Reply-To: <20041019131240.A20243@flint.arm.linux.org.uk>
On Tue, 2004-10-19 at 07:12, Russell King wrote:
> Software Environment: ppp-2.4.1 ( tested with ppp-2.4.2 - the same error )
> Problem Description: With 2.6.9-rc4 I'm getting the error when dialing to my
> provider. With older kernel versions everything works fine. After remote modem
> cosed the connection (rcvd [CHAP Success id=0x29 ""]) pppd keeps sending
> Config-Requests
This looks like the tty locking changes from Alan Cox.
The tty_io.c do_tty_hangup() no longer switches
the line discipline back to N_TTY, so ppp_async.c
is not aware of the hangup (ldisc->close not called).
The following is a snippet from tty_io.c:
/* Defer ldisc switch */
/* tty_deferred_ldisc_switch(N_TTY);
This should get done automatically when the port closes and
tty_release is called */
I'll setup a test connection and verify this.
--
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2004-10-19 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 12:12 Fwd: [Bug 3592] New: pppd "IPCP: timeout sending Config-Requests" Russell King
2004-10-19 14:17 ` Paul Fulghum [this message]
2004-10-19 15:32 ` Paul Fulghum
2004-10-20 21:57 ` Alan Cox
2004-10-20 23:42 ` Paul Fulghum
2004-10-20 23:46 ` Alan Cox
2004-10-21 0:00 ` Paul Fulghum
2004-11-20 13:11 ` Russell King
2004-11-20 12:34 ` Alan Cox
2004-11-20 14:21 ` Russell King
2004-11-20 15:09 ` Paul Fulghum
2004-11-20 16:57 ` Russell King
2004-11-20 18:48 ` Paul Fulghum
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=1098195468.8467.7.camel@deimos.microgate.com \
--to=paulkf@microgate.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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