Linux PARISC architecture development
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: dann frazier <dannf@dannf.org>
Cc: Thibaut VARENE <T-Bone@parisc-linux.org>,
	John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
	carlos@systemhalted.org, linux-parisc@vger.kernel.org
Subject: Re: debian hppa
Date: Thu, 07 Jul 2011 13:26:52 -0400	[thread overview]
Message-ID: <4E15EC5C.10702@bell.net> (raw)
In-Reply-To: <20110707161810.GC12243@dannf.org>

On 7/7/2011 12:18 PM, dann frazier wrote:
> On Thu, Jul 07, 2011 at 05:49:36PM +0200, Thibaut VARENE wrote:
>> On Thu, Jul 7, 2011 at 1:20 AM, John David Anglin
>> <dave.anglin@nrc-cnrc.gc.ca>  wrote:
>>> Hi Thibaut,
>>>
>>> On 13-Jun-11, at 6:19 PM, Thibaut VARENE wrote:
>>>
>>>>> I would say your other machines need updating even if the process is
>>>>> somewhat rocky as that's the only way a broadbased release can be tested.
>>>> Well I can assign one machine (the a500, being easy to reboot/fix as
>>>> it is) to testing kernels, but for a stable kernel suitable for the
>>>> machines I'm e.g. assigning to the GCC Compile Farm[0], what would be
>>>> a good SMP kernel version to choose? I'm looking for the same level of
>>>> hassle-freeness as 2.6.22.19 since these machines are under relatively
>>>> heavy load and I cannot afford to tend to their care on a daily basis
>>>> ;-)
>>> Sorry for the delay in responding.  I think assigning the a500 to the GCC
>>> farm
>>> provides good visibility.  For GCC, the kernel version doesn't matter much.
>>>   The
>>> main issue is stability.
>> OK, so I suppose it's fine to stick with 2.6.22.19? I thought there
>> were issues with un-implemented syscalls and such, so I don't really
>> know...
>>
This comment was specific to building and testing GCC.  It currently 
takes slightly over
24 hours to build and test GCC trunk on my c3750.

> Honestly, the most reliable build machine I've used is my
> C3700. I don't recall ever having any build issues with
> that. Anything it gives up in speed is definitely outweighed by
> having to e.g. retry gcc 5 times before succeeding. By the end of the
> port, I'd normally handbuild new gcc uploads here to avoid thrashing
> on the real buildds. If given the option, I'd recommend 3 of those
> boxes for a buildd ring.
>
Based on my testing, it's no longer necessary to try 5 times before 
succeeding with rp3440.
I agree that the C37XX machines are very stable and don't suffer from 
the SMP/cache
issues present in the servers.  If the ring above could be arranged, 
that would be excellent.

Dave

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


  reply	other threads:[~2011-07-07 17:26 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
2011-07-07 17:51                                             ` Thibaut VARENE
2011-07-07 16:18                                           ` dann frazier
2011-07-07 17:26                                             ` John David Anglin [this message]
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=4E15EC5C.10702@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