Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jurij Smakov <jurij@wooyd.org>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	Kurt Roeckx <kurt@roeckx.be>,
	pkern@debian.org, debian-hppa@lists.debian.org,
	linux-parisc@vger.kernel.org, debian-release@lists.debian.org,
	Adam C Powell IV <hazelsct@debian.org>
Subject: Re: HPPA and Squeeze
Date: Sun, 5 Jul 2009 14:44:31 +0100	[thread overview]
Message-ID: <20090705134431.GA6598@droopy.oc.cox.net> (raw)
In-Reply-To: <4A506D2C.6080801@gmx.de>

On Sun, Jul 05, 2009 at 11:06:52AM +0200, Helge Deller wrote:
> On 07/05/2009 01:34 AM, John David Anglin wrote:
>>> On Fri, Jul 03, 2009 at 09:28:00PM +0200, Philipp Kern wrote:
>>>> On Fri, Jul 03, 2009 at 08:57:56PM +0200, Kurt Roeckx wrote:
>>>>> Did something change to peri?  I'm currently only seeing them on
>>>>> penalosa.
>>>> UP kernel, maybe?
>>> Both peri and penalosa run 2.6.29-2-parisc64-smp and from what I
>>> can tell run on identical hardware.
>>
>> I tried a SMP kernel (2.6.30.1 with the patch set posted earlier) on
>> my rp34404.  Fired up a GCC build.  It didn't take more than a few
>> minutes to trigger a couple of segvs in /bin/sh.  On the other hand,
>> I ran a UP version of 2.6.30 for more than a week without any major
>> problems.
>
> So, instead of just complaining, wouldn't it be useful if someone with
> root access would install a UP kernel (and disable nscd) for the time
> being on the build servers?
> That way we all would avoid debian build problems and could concentrate
> on solving the issues with the SMP kernel itself.
>
> In the meantime, all (IMHO) major kernel patches have now been included
> in Linus' 2.6.31-rc2 kernel and I plan to backport and send them to the
> stable-kernel team for inclusion into 2.6.29 and 2.6.30 stable
> kernel series.

HPPA folks, can you please convert at least one buildd to a UP
configuration? I have another example of extreme buildd flakiness mentioned
in bug #529485. Adam C Powell IV <hazelsct@debian.org> writes:

  That's too bad.  I saw 6 attempts to do 3.0.0-X of which two passed the
  first try and four failed.  At that rate (1/3), it would take nine
  attempts to have a decent chance of passing both rounds (debug static
  and optimized shared/static).

HPPA is the only arch for which petsc failed to build, and currently this
blocks petsc transition.

Best regards,
-- 
Jurij Smakov                                           jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC

  reply	other threads:[~2009-07-05 13:44 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  6:05 HPPA and Squeeze Luk Claes
2009-06-19 15:15 ` Kurt Roeckx
2009-06-19 15:43   ` Philipp Kern
2009-06-20 22:44     ` John David Anglin
2009-07-03 18:57     ` Kurt Roeckx
2009-07-03 19:28       ` Philipp Kern
2009-07-03 22:15         ` Kurt Roeckx
2009-07-04 23:34           ` John David Anglin
2009-07-05  9:06             ` Helge Deller
2009-07-05 13:44               ` Jurij Smakov [this message]
2009-07-05 14:01                 ` Philipp Kern
2009-07-05 17:19               ` John David Anglin
2009-07-05 18:01                 ` John David Anglin
2009-07-05 23:07                 ` John David Anglin
2009-07-06  0:03                   ` Carlos O'Donell
2009-07-06  0:17                     ` John David Anglin
2009-07-06  1:06                       ` James Bottomley
2009-07-06  1:43                         ` John David Anglin
2009-07-06  5:38                           ` Randolph Chung
2009-07-06 13:28                             ` John David Anglin
2009-07-06 16:36                               ` Carlos O'Donell
2009-07-06 18:45                                 ` John David Anglin
2009-07-06 21:43                                   ` Kyle McMartin
2009-07-07  1:47                                     ` John David Anglin
2009-07-07  2:43                                       ` dann frazier
2009-07-07 13:57                                         ` Carlos O'Donell
2009-07-07 14:11                                       ` James Bottomley
2009-07-07 16:21                                         ` John David Anglin
2009-07-07 20:42                                           ` Carlos O'Donell
2009-07-07 22:07                                             ` John David Anglin
2009-07-07 22:17                                               ` Carlos O'Donell
2009-07-07 22:39                                                 ` John David Anglin
2009-07-07 14:22                                     ` James Bottomley
2009-07-05 23:59                 ` Carlos O'Donell
2009-07-06  2:25                   ` John David Anglin
2009-07-04 19:52       ` John David Anglin
2009-07-04 21:03         ` Kurt Roeckx
2009-07-04 23:30           ` Kurt Roeckx
2009-06-20 14:33   ` Kurt Roeckx
2009-06-20 16:02     ` John David Anglin
2009-06-20 17:48       ` Kurt Roeckx
2009-06-20 21:57         ` Grant Grundler
2009-06-20 22:25           ` John David Anglin
2009-06-20 23:07             ` Grant Grundler
2009-06-20 23:25               ` John David Anglin
2009-06-20 14:39   ` Kurt Roeckx
2009-06-20 14:51     ` Thibaut VARENE
     [not found] <20090602140734.GC26721@mx0.halon.org.uk>
2009-06-06 18:36 ` Grant Grundler
2009-06-08 21:26   ` Neil McGovern
2009-06-08 23:44     ` Thibaut VARENE
2009-06-09  9:29       ` Neil McGovern
2009-06-09 10:38         ` Thomas Bogendoerfer
2009-06-09 16:47         ` Aioanei Rares
2009-06-09 17:06           ` John David Anglin
     [not found]       ` <slrnh2scj5.720.nospam@sshway.ssh.pusling.com>
2009-06-09 19:11         ` Helge Deller
2009-06-17  2:37           ` John David Anglin
2009-06-15 16:26     ` Grant Grundler
2009-06-15 17:32       ` Helge Deller
2009-06-12  6:49   ` Luk Claes
2009-06-12  7:53     ` Bart Schelstraete
2009-06-12  7:55       ` Bart Schelstraete
2009-06-12 14:16         ` James Bottomley
2009-06-12 15:35           ` dann frazier
2009-06-13 12:19             ` Brian Szymanski
2009-06-14 18:29             ` Thibaut VARENE
2009-06-14 18:39               ` dann frazier
2009-06-15 17:31     ` Grant Grundler
2009-06-16  6:25       ` Lucas Nussbaum
2009-06-16 19:08         ` Helge Deller
2009-06-16 19:13           ` Aurelien Jarno
2009-06-17 11:14             ` Carlos O'Donell
2009-06-21 22:55             ` Carlos O'Donell
2009-07-12 12:30               ` Aurelien Jarno
2009-07-12 14:52                 ` Carlos O'Donell
2009-07-13 13:30                   ` Carlos O'Donell
2009-06-16 20:50         ` Grant Grundler
2009-06-16 21:35           ` dann frazier
2009-06-17 23:54       ` Matthias Klose
2009-06-18  1:35         ` John David Anglin
2009-06-18  6:33           ` Luk Claes
2009-06-18  9:40             ` Randolph Chung
2009-06-18 18:19               ` Luk Claes
2009-06-18 10:16             ` Thibaut VARENE
2009-06-18 18:16               ` Luk Claes
2009-06-18 15:03             ` John David Anglin
2009-06-18  6:29         ` Luk Claes
2009-06-24 23:32           ` Matthias Klose

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=20090705134431.GA6598@droopy.oc.cox.net \
    --to=jurij@wooyd.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=debian-hppa@lists.debian.org \
    --cc=debian-release@lists.debian.org \
    --cc=deller@gmx.de \
    --cc=hazelsct@debian.org \
    --cc=kurt@roeckx.be \
    --cc=linux-parisc@vger.kernel.org \
    --cc=pkern@debian.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