From: Ferris McCormick <fmccor@gentoo.org>
To: gentoo-sparc@lists.gentoo.org
Cc: Jameel Akari <jakari@bithose.com>, sparclinux@vger.kernel.org
Subject: Re: [gentoo-sparc] kernel-2.6.15-r4 (in)stability on U2-SMP, etc.
Date: Wed, 15 Feb 2006 14:01:34 +0000 [thread overview]
Message-ID: <1140012094.4844.49.camel@polylepis.inforead.com> (raw)
In-Reply-To: <Pine.OSF.4.63.0602150821370.682@poptart.bithose.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Wed, 2006-02-15 at 08:28 -0500, Jameel Akari wrote:
> On Wed, 15 Feb 2006, Ferris McCormick wrote:
>
> > However, U2-SMP(2x450) is not. As is the case with ALL 2.6.xx kernels,
> > 2.6.15-r4 cannot handle the sort of disk activity which portage requires
>
> Just as a data point, you do realize that the 450MHz CPU was never
> actually supported in the Ultra-2? While it may boot, it wasn't made to
> work together nor was it sold as an upgrade. You may be tripping on some
> marginal timing issue.
>
> If you have 400MHz/2MB CPUs sitting around it may be worth testing with
> them to isolate that as a cause.
>
As is too often the case, I mistyped. The stable system is U60(2x450);
the unstable system is U2(2x400). Thanks for catching this.
>
> --
> #!/jameel/akari
> sleep 4800;
> make clean && make breakfast
Regards,
Ferris (who sometimes expects way too much ESP support from his readers)
--
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Sparc, Devrel)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-15 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 13:09 [gentoo-sparc] kernel-2.6.15-r4 (in)stability on U2-SMP, etc Ferris McCormick
2006-02-15 13:28 ` Jameel Akari
2006-02-15 14:01 ` Ferris McCormick [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-17 18:15 Leif Sawyer
2006-02-18 5:48 ` Jurij Smakov
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=1140012094.4844.49.camel@polylepis.inforead.com \
--to=fmccor@gentoo.org \
--cc=gentoo-sparc@lists.gentoo.org \
--cc=jakari@bithose.com \
--cc=sparclinux@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