From: Andrew Morton <akpm@osdl.org>
To: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
Cc: netdev@vger.kernel.org, lkml@jawad.org
Subject: Re: Fw: Bug: PPP dropouts in >=2.6.16
Date: Fri, 21 Apr 2006 11:56:37 -0700 [thread overview]
Message-ID: <20060421115637.3ca7cfce.akpm@osdl.org> (raw)
In-Reply-To: <4807377b0604211015j16b40cccpe215668f8fdcfc24@mail.gmail.com>
"Jesse Brandeburg" <jesse.brandeburg@gmail.com> wrote:
>
> On 4/21/06, Andrew Morton <akpm@osdl.org> wrote:
> >
> > We do seem to have had a few reports of ppp regressions around this
> > timeframe.
>
> me too. I couldn't use 2.6.16 at home on my pppoe connected router
> because it was so slow. I didn't have time to debug. I can probably
> try patches and provide more data too. Tell me what is needed.
probably git-bisect, sorry. It's the sort of thing you can do while
reading a good book ;)
> Is there a bugzilla on this?
I don't think so. Bubgzilla records which I'm folowing which mention ppp
are:
http://bugzilla.kernel.org/show_bug.cgi?id=5695
http://bugzilla.kernel.org/show_bug.cgi?id=6197
http://bugzilla.kernel.org/show_bug.cgi?id=6402
Perhaps the final one is related.
next prev parent reply other threads:[~2006-04-21 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 8:08 Fw: Bug: PPP dropouts in >=2.6.16 Andrew Morton
2006-04-21 17:15 ` Jesse Brandeburg
2006-04-21 18:56 ` Andrew Morton [this message]
2006-04-22 0:02 ` Andi Kleen
2006-04-24 7:41 ` Sven Schuster
2006-04-26 0:36 ` Nuri Jawad
2006-04-26 6:04 ` Sven Schuster
2006-04-29 0:05 ` Nuri Jawad
2006-04-26 21:25 ` Sven Schuster
2006-04-26 22:07 ` Andrew Morton
2006-04-27 5:48 ` Sven Schuster
2006-04-30 4:31 ` Fw: Bug: PPP dropouts in >=2.6.16 - updates Nuri Jawad
[not found] <Pine.LNX.4.58.0604202217450.4014@pc>
2006-04-30 11:43 ` Fw: Bug: PPP dropouts in >=2.6.16 theosch
2006-04-30 12:05 ` theosch
2006-04-30 14:10 ` Nuri Jawad
2006-05-02 20:55 ` Nuri Jawad
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=20060421115637.3ca7cfce.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jesse.brandeburg@gmail.com \
--cc=lkml@jawad.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).