linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Lou Langholtz <ldl@chpc.utah.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity]
Date: Wed, 29 Sep 1999 19:02:22 +0200	[thread overview]
Message-ID: <19990929190222.023648@mailhost.mipsys.com> (raw)
In-Reply-To: <37F241DB.94C9BF00@chpc.utah.edu>


On Wed, Sep 29, 1999, Lou Langholtz <ldl@chpc.utah.edu> wrote:

>This is pretty much the kernel I'm running now. I haven't had the "FB.
>overflow"
>message yet nor system-freeze but I've experienced the TCP slowdown already.
>Evidence that we've got other problems as well (IMO). It's only been 20 hours
>or
>so with new kernel so not enough time for me to feel confident though about
>these
>results.

I've added another fix to the kernel on my test page
(http://calvaweb.calvacom.fr/bh40/test.html). It may fix the hang on
close. I don't think it will fix anything related to a slowdown however.

-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-09-29 17:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37F1AD4B.585E99AB@chpc.utah.edu>
1999-09-29  7:11 ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Geert Uytterhoeven
1999-09-29  7:16 ` Takashi Oe
1999-09-29  7:40   ` Geert Uytterhoeven
1999-09-29  9:13   ` Benjamin Herrenschmidt
1999-09-30  0:46     ` Takashi Oe
1999-09-30  8:50       ` Benjamin Herrenschmidt
1999-09-30 16:21         ` Takashi Oe
1999-09-30 16:35           ` Benjamin Herrenschmidt
1999-10-06  5:33             ` update on macserial/DMA Takashi Oe
1999-10-06  8:35               ` Benjamin Herrenschmidt
1999-10-06 13:47                 ` Takashi Oe
1999-10-06 16:25                   ` Benjamin Herrenschmidt
1999-10-06 16:50                     ` Benjamin Herrenschmidt
1999-10-08  7:13               ` Lou Langholtz
1999-10-09 17:57                 ` Lou Langholtz
     [not found]             ` <Pine.LNX.3.96LJ1.1b7.991005234830.1210A-100000@ofey.inetne br.com>
1999-10-07  9:48               ` Franz Sirl
1999-10-07 15:37                 ` phandel
1999-10-12  7:20       ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Lou Langholtz
1999-09-29 16:44   ` Lou Langholtz
1999-09-29 17:02     ` Benjamin Herrenschmidt [this message]
1999-09-29 18:08       ` Lou Langholtz
1999-09-29 18:46   ` Lou Langholtz
1999-09-29 20:00   ` Lou Langholtz
1999-09-30  1:14     ` Takashi Oe
1999-09-30  5:33     ` Geert Uytterhoeven
1999-10-01 13:26     ` Franz Sirl
1999-10-01 13:46       ` Alvin Brattli
     [not found]       ` <Pine.OSF.3.96.991001153658.16772E-100000@mitra.phys.uit.no >
1999-10-01 14:08         ` Franz Sirl
1999-10-01 16:14       ` Lou Langholtz
     [not found] <37F1C0A3.B9F25580@chpc.utah.edu>
1999-09-29  7:39 ` Geert Uytterhoeven
1999-09-10 16:51 Lou Langholtz

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=19990929190222.023648@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=ldl@chpc.utah.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 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).