From: Phil Mayers <p.mayers@imperial.ac.uk>
To: linux-ppp@vger.kernel.org
Subject: Re: pppd stuck in ioctl(TIOCSETD) in Linux 2.6.15.4+
Date: Tue, 27 Jun 2006 23:03:06 +0000 [thread overview]
Message-ID: <44A1B92A.1050608@imperial.ac.uk> (raw)
In-Reply-To: <004b01c69a3a$6b80c660$0201a8c0@athlon64>
Jorge Daniel Sequeira Matias wrote:
>
> Hi everyone,
>
> I'm running a PPTP VPN Server for almost 4 years now. This server is
> running in a Debian Linux (unstable).
> The configuration for the last 1 year and a half was the following:
>
> Computer 2x Intel Xeon 2.6GHz and 512MB RAM
> Linux v2.6.11.6 (vanilla) with MPPE patch
> After the upgrade to a Linux v2.6.15.4 (vanilla) with no patches to
There were a couple of bugs recently in the TTY layer related to poptop
and running pppd on PTYs, but I believe 2.6.15 did not contain them
(though I find the git logs incomprehensible so could be wrong). See:
http://bugzilla.kernel.org/show_bug.cgi?idd02
http://bugzilla.kernel.org/show_bug.cgi?ide30
Just in case, you should definitely try the latest kernel - 2.6.17.1 is
stable.
If that doesn't solve it and if you can reliably reproduce it you could
do a "git bisect" to track the bug down (tedious though):
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/
next prev parent reply other threads:[~2006-06-27 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 22:38 pppd stuck in ioctl(TIOCSETD) in Linux 2.6.15.4+ Jorge Daniel Sequeira Matias
2006-06-27 22:43 ` Patrick McHardy
2006-06-27 22:50 ` Jorge Daniel Sequeira Matias
2006-06-27 23:03 ` Phil Mayers [this message]
2006-06-27 23:30 ` Jorge Daniel Sequeira Matias
2006-06-29 20:06 ` Jorge Daniel Sequeira Matias
2006-06-29 23:26 ` Paul Mackerras
2006-07-11 12:18 ` Jorge Daniel Sequeira Matias
2006-07-11 22:53 ` James Cameron
2006-07-12 11:46 ` Jorge Daniel Sequeira Matias
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=44A1B92A.1050608@imperial.ac.uk \
--to=p.mayers@imperial.ac.uk \
--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