From: Nuri Jawad <lkml@jawad.org>
To: Sven Schuster <schuster.sven@gmx.de>
Cc: Andi Kleen <ak@suse.de>,
Jesse Brandeburg <jesse.brandeburg@gmail.com>,
Andrew Morton <akpm@osdl.org>,
netdev@vger.kernel.org
Subject: Re: Fw: Bug: PPP dropouts in >=2.6.16
Date: Sat, 29 Apr 2006 02:05:29 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0604272330360.14398@pc> (raw)
In-Reply-To: <20060426060442.GA8875@zion.homelinux.com>
On Wed, 26 Apr 2006, Sven Schuster wrote:
> but don't hold your breath waiting for me, kernel compile
> takes more than two hours on my box :-)
Ouch. Takes 5/7 minutes here on the AMD64 resp. P4. Computer museum? :P
Anyhow, I tested PPP for 2.5 hours on the AMD64 the day before
yesterday with a bidirectional transfer that maxed out the upstream.
Last night, I additionally put some load on the CPU. Another 3 hours, no
problems whatsoever. Looks like the bug does not manifest on that system.
The next step will be to clone .config's settings as far as possible with
the different hardware and try again.
Regards,
Nuri
next prev parent reply other threads:[~2006-04-29 0:06 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
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 [this message]
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=Pine.LNX.4.64.0604272330360.14398@pc \
--to=lkml@jawad.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jesse.brandeburg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=schuster.sven@gmx.de \
/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