From: BenH <bh40@calva.net>
To: Brian C Burke <bcburke@socrates.berkeley.edu>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: v2.2.1 and serial fixes
Date: Wed, 10 Feb 1999 14:20:25 +0100 [thread overview]
Message-ID: <19990210142025.007673@mail.mipsys.com> (raw)
In-Reply-To: <v04020a00b2e6f5596238@[136.152.65.18]>
On Wed, Feb 10, 1999, Brian C Burke <bcburke@socrates.berkeley.edu> wrote:
>Over the last few weeks I seen reference to BenH fixing some serial driver
>bugs that may be involved in ppp hangs. I grapped the 2.2.1 kernel in hopes
>that these fixes were incorporated. Unfortunatelly I'm still finding ppp
>connections often hang and the only fix is to reboot. If I boot into
>mklinux ppp is stone reliable, so the problem is in linuxppc Were the
>serial fixes incorporated in 2.2 or do I need to get the latest sources?
I'm not 100% sure I have have fixed _all_ the problems, but PPP works
reliably for me using the internal modem of the PowerBook. The fixes are
currently in vger or in Paul's kernel. I beleive the binary snapshot on
samba.anu.edu.au do have them. Are you using a kernel.org kernel distrib
? This one may lack the latest PPC patches.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-10 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-10 8:44 v2.2.1 and serial fixes Brian C Burke
1999-02-10 13:20 ` BenH [this message]
[not found] <199902040559.XAA07089@lists.linuxppc.org>
1999-02-06 21:55 ` Brian C Burke
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=19990210142025.007673@mail.mipsys.com \
--to=bh40@calva.net \
--cc=bcburke@socrates.berkeley.edu \
--cc=linuxppc-dev@lists.linuxppc.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.