From: Lou Langholtz <ldl@chpc.utah.edu>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Takashi Oe <toe@unlserve.unl.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity]
Date: Fri, 01 Oct 1999 10:14:59 -0600 [thread overview]
Message-ID: <37F4DE03.F884047C@chpc.utah.edu> (raw)
In-Reply-To: 4.2.0.58.19991001150704.03c6b230@mail.lauterbach.com
Franz Sirl wrote:
> At 22:00 29.09.99 , Lou Langholtz wrote:
> >I just locked up my system and had to reboot. The above change then
> >doesn't seem
> >to fix the system hangs. On the other hand I never did see the "FB. overflow"
> >message at least.
>
> Hmm, in the recent kernels Paul changed the code to only print the FB
> message once! For me these lockups (I'm using vger nearly unmodified) are
> gone since quite a while, but I don't really know a reason why. The major
> specialties on my 7200/75 are:
>
> - disabled syslog's fsync'ing of /var/log/messages (this prevents the
> amplifying effect of the FB messages)
> - all major stuff is compiled with gcc-2.95.2pre
>
> Franz.
thats good to hear. you're using a kernel newer than 2.2.12 which has the fixes
i've been experimenting with plus others. like only printing the fb overflow
message the first time it occurs in the sequence rather than all the time. the
overflow may still be occuring but the message wont keep getting printed. this no
doubt makes a few things more usable but by itself shouldn't prevent the tcp slow
down to nothing over ppp nor the complete lock up. there's also a kernel memory
routine that has some ppc specific fixes to it which seems to greatly imprive ppp
performance. 2.2.12 still has some sti() calls in macserial.c which look
suspicious. the newer code has gotten rid of at least some of those and i'm now
running a kernel that has none of those in macserial.c. this seems to be running
much better but i haven't run long enough to have a high confidence that that was
particularly problematic.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-01 16:14 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
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 [this message]
[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=37F4DE03.F884047C@chpc.utah.edu \
--to=ldl@chpc.utah.edu \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.edu \
/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.