Linux PARISC architecture development
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Thibaut VARENE <T-Bone@parisc-linux.org>
Cc: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
	dann frazier <dannf@dannf.org>,
	carlos@systemhalted.org, linux-parisc@vger.kernel.org
Subject: Re: debian hppa
Date: Thu, 07 Jul 2011 12:16:43 -0400	[thread overview]
Message-ID: <4E15DBEB.9040703@bell.net> (raw)
In-Reply-To: <CA+DQjFgygVS0YQ_zUfQG=BkTb_zrSN+yYxGyTU6ufC-PV7dBxA@mail.gmail.com>

On 7/7/2011 11:49 AM, Thibaut VARENE wrote:
>
> I have no problem with this, the only "active" user of the rp3440 is
> Aur=C3=A9lien, so I suppose it wouldn't be a problem. Yet, my underst=
anding
> is that the rp3440 is extremely slow at building anything (much slowe=
r
> than my other machines, it seems) because of the cache flush issues.
> AIUI that's why Debian stuck to J6700 for buildds, because those
> machines were a lot faster.

The rp3440 isn't bad for non trivial compilations.  At -j4, my 800 MHz=20
rp3440 is the fastest
machine that I have for building GCC.  It stumbles running the testsuit=
e=20
where it falls behind
my c3750.  The cache flush problem slows forks.  If this could be=20
resolved, the machine
could handle significantly larger loads than the J6700.

> Other than that, the rp3440 currently runs unstable with 2.6.22.19, s=
o
> I suppose a complete reinstall would be in order, and I'm not sure I
> have time to deal with that just yet. I'd be happy to provide remote
> access to the machine though, if someone steps up. FWIW, the only
> machine I have left running lenny is a J5000, 2x440MHz PA8500,
> previously used as an autobuilder for debian-multimedia.org.
The kernel on the rp3440 needs updating.  2.6.22.19 is not stable under=
=20
load.  To do this,
remote access to the console would be needed.  Many bugs have been fixe=
d=20
since
2.6.22.19, and I think many packages may not test successfully without=20
updating the
kernel and build environment.

I have done this manually on my rp3440 for quite a few packages.

Dave

--=20
John David Anglin    dave.anglin@bell.net

--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
 in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-07-07 16:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110525211710.GA1562@hiauly1.hia.nrc.ca>
     [not found] ` <BANLkTikFc1Euw-c+qiUaUznMg7b_1a+4Hg@mail.gmail.com>
     [not found]   ` <20110525234205.GB2556@dannf.org>
     [not found]     ` <20110526012304.GB1912@hiauly1.hia.nrc.ca>
     [not found]       ` <20110526144610.GC2556@dannf.org>
     [not found]         ` <20110526152900.GA5200@hiauly1.hia.nrc.ca>
     [not found]           ` <20110526160951.GA19134@dannf.org>
     [not found]             ` <BANLkTimmzyQWPD0BribiDgM7W6yvOJwUJA@mail.gmail.com>
     [not found]               ` <20110527145656.GB21744@dannf.org>
     [not found]                 ` <BANLkTi=BODRACq5N1XBrN+JovNjE2VTibQ@mail.gmail.com>
2011-05-27 16:24                   ` debian hppa John David Anglin
2011-05-27 16:29                     ` James Bottomley
2011-05-27 16:37                       ` dann frazier
2011-05-27 16:35                     ` dann frazier
2011-05-27 18:18                       ` John David Anglin
2011-05-27 19:49                         ` dann frazier
2011-05-27 20:20                           ` John David Anglin
2011-05-27 21:35                             ` dann frazier
2011-05-27 23:37                               ` John David Anglin
2011-05-28  0:58                                 ` Thibaut VARENE
2011-06-01  2:10                                   ` John David Anglin
2011-06-02 21:35                                     ` Grant Grundler
2011-06-29 19:33                                       ` John David Anglin
2011-07-03  0:43                                         ` Grant Grundler
     [not found]                                           ` <7C0BBECE-2ED2-49B0-8371-569191EF3028@nrc-cnrc.gc.ca>
2011-07-03 15:33                                             ` rick jones
2011-07-03 23:27                                               ` John David Anglin
2011-06-13 22:19                                     ` Thibaut VARENE
2011-07-06 23:20                                       ` John David Anglin
2011-07-07 15:49                                         ` Thibaut VARENE
2011-07-07 16:03                                           ` Carlos O'Donell
2011-07-07 21:59                                             ` Aurelien Jarno
2011-07-07 23:02                                               ` Carlos O'Donell
2011-07-17 22:03                                                 ` Aurelien Jarno
2011-07-07 16:16                                           ` John David Anglin [this message]
2011-07-07 17:51                                             ` Thibaut VARENE
2011-07-07 16:18                                           ` dann frazier
2011-07-07 17:26                                             ` John David Anglin
2011-07-07 16:16                               ` Carlos O'Donell

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=4E15DBEB.9040703@bell.net \
    --to=dave.anglin@bell.net \
    --cc=T-Bone@parisc-linux.org \
    --cc=carlos@systemhalted.org \
    --cc=dannf@dannf.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=linux-parisc@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