From: Benjamin Herrenschmidt <bh40@calva.net>
To: Henry Worth <haworth@ncal.verio.com>,
Troy Benjegerdes <hozer@drgw.net>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: dual G4 time issues..
Date: Mon, 18 Sep 2000 11:07:10 +0200 [thread overview]
Message-ID: <20000918090710.14056@mailhost.mipsys.com> (raw)
In-Reply-To: <39C518A9.2BA320DA@ncal.verio.com>
>
>So far the main problem I'm seeing with the SMP G4 and smp
>2.2.18pre4-ben1 is the system hangs up occasionally in xpmac
>rev 10, usually when closing an app or logging out. But I've seen
>nearly as many xpmac hangs in 2.2.17pre20-ben1 on a Pismo, but
>there I can switch VT's and recover. Whereas, on the SMP G4, VT
>switches won't work (USB -vs- ADB/PMU?). But, I can't telnet in
>either, so maybe it is a hard hang (though enough is alive that it
>pings -- not that that means much). Of course, if I have already
>telnet'ed in, it never hangs... Will hopefully have time
>to build and give XF86 4.0.x a try in a few days.
>
>Other than that, the other problems are the general non-SMP
>Rage128 nits of the 2.2.18 fb backport (character rendering
>artifacts and occasional raster flickers that probably
>indicate non-optimal mclk/sclk settings).
>
>Currently, I've got the CPU load up in the 1.4-1.6 range with
>no impact on GUI responsiveness and XMMS playing a CD digitally
>without dropping a beat.
I had reports of pthread-intensive applications having the threads
randomly "hang" when running on the SMP 2.2.x kernel. This happens on PPC
only (works fine with the same kernel on x86) and it's fine on UP.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-18 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-17 19:16 dual G4 time issues Henry Worth
2000-09-18 9:07 ` Benjamin Herrenschmidt [this message]
2000-09-20 2:37 ` Henry Worth
2000-09-21 17:42 ` Michel Lanners
-- strict thread matches above, loose matches on Subject: below --
2000-08-12 18:46 rtc again Gabriel Paubert
2000-09-17 16:47 ` dual G4 time issues Troy Benjegerdes
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=20000918090710.14056@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=haworth@ncal.verio.com \
--cc=hozer@drgw.net \
--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).