Linux PARISC architecture development
 help / color / mirror / Atom feed
From: dann frazier <dannf@dannf.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	Helge Deller <deller@gmx.de>,
	dave.anglin@nrc-cnrc.gc.ca, linux-parisc@vger.kernel.org,
	kyle@mcmartin.ca, James.Bottomley@hansenpartnership.com
Subject: Re: vfork test case.
Date: Thu, 17 Dec 2009 09:45:16 -0700	[thread overview]
Message-ID: <20091217164516.GD10487@lackof.org> (raw)
In-Reply-To: <119aab440912170624p58d6f19fk9e6feaab11f6f1a3@mail.gmail.com>

On Thu, Dec 17, 2009 at 09:24:05AM -0500, Carlos O'Donell wrote:
> On Wed, Dec 16, 2009 at 4:35 PM, John David Anglin
> <dave@hiauly1.hia.nrc.ca> wrote:
> >> On 12/15/2009 11:21 PM, John David Anglin wrote:
> >> >> I have constructed a vfork test case which shows some of the problems
> >> >> I have using vfork reliably. This fails every time on my PA8700 system
> >> >> running 2.6.32-rc6. It appears as though r28 (ret0) in the parent is
> >> >> being corrupted.
> >> >
> >> > The test doesn't fail on two of my builds:
> >> > Linux mx3210 2.6.31.7 #5 Wed Dec 9 22:49:53 EST 2009 parisc64
> >> > Linux hiauly6 2.6.31.7 #18 Wed Dec 9 21:34:36 EST 2009 parisc
> >>
> >> I did tested your testcase on my c3000 too but it didn't failed for me either.
> >> This was on some 2.6.32-rc candidate.
> >
> > I think it must be because Carlos is building SMP kernels.
> 
> Yes, I'm trying to shake out some SMP bugs.
> 
> Dan, you said that the emacs32 failure went away when you upgraded to
> 2.6.32 stable on the buildds. Are they running SMP kernels?

Nope. When I initially took over these buildds I tried SMP kernels and
found them to be far less stable, so we're sticking w/ UP.

That means that some emacs23 build attempts may have been on SMP, but
most were not. Kernel versions should be available in the build logs.
smp kernels should all have 'smp' in their uname output.

> Could you try the vfork test case there?

dannf@penalosa:/tmp$ cat /proc/version
Linux version 2.6.32-trunk-parisc64 (Debian 2.6.32-1) (waldi@debian.org) (gcc version 4.3.4 (GCC) ) #1 Tue Dec 8 04:07:32 UTC 2009
dannf@penalosa:/tmp$ gcc -O1 -g -o vfork-01 vfork.c
dannf@penalosa:/tmp$ gcc -O0 -g -o vfork-00 vfork.c
dannf@penalosa:/tmp$ ./vfork-01
child != 0
child is 0x10c8
dannf@penalosa:/tmp$ total 28
-rwxr-xr-x 1 dannf Debian  9333 Dec 17 16:41 vfork-00
-rwxr-xr-x 1 dannf Debian 10383 Dec 17 16:40 vfork-01
-rw-r--r-- 1 dannf Debian   380 Dec 17 16:40 vfork.c

dannf@penalosa:/tmp$ ./vfork-00 
child != 0
child is 0x1101
dannf@penalosa:/tmp$ total 28
-rwxr-xr-x 1 dannf Debian  9333 Dec 17 16:41 vfork-00
-rwxr-xr-x 1 dannf Debian 10383 Dec 17 16:40 vfork-01
-rw-r--r-- 1 dannf Debian   380 Dec 17 16:40 vfork.c

> Test case is here:
> http://article.gmane.org/gmane.linux.ports.parisc/2403
> 
> Cheers,
> Carlos.
> 

-- 
dann frazier


  reply	other threads:[~2009-12-17 16:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 21:19 vfork test case Carlos O'Donell
2009-12-15 22:21 ` John David Anglin
2009-12-16 13:24   ` Carlos O'Donell
2009-12-16 21:22   ` Helge Deller
2009-12-16 21:35     ` John David Anglin
2009-12-17 14:24       ` Carlos O'Donell
2009-12-17 16:45         ` dann frazier [this message]
2009-12-17 19:12       ` Helge Deller
2009-12-17 20:39         ` Carlos O'Donell
2009-12-19 20:44           ` Grant Grundler
2009-12-17 21:40 ` Berthold Gunreben
2009-12-17 21:59   ` Carlos O'Donell
2010-06-20  4:28 ` John David Anglin
2010-06-22 15:17   ` Carlos O'Donell
2010-06-22 15:39     ` Carlos O'Donell
2010-06-22 22:50       ` John David Anglin
2010-06-27 15:41         ` Carlos O'Donell
2010-06-22 16:26     ` John David Anglin
2010-06-22 18:34       ` Carlos O'Donell
2010-06-22 18:44         ` John David Anglin
2010-06-22 19:53           ` Carlos O'Donell
2010-06-22 20:20             ` John David Anglin
2010-06-22 21:13               ` 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=20091217164516.GD10487@lackof.org \
    --to=dannf@dannf.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=carlos@systemhalted.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=deller@gmx.de \
    --cc=kyle@mcmartin.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