Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: List Parisc <parisc-linux@parisc-linux.org>,
	Matthew Wilcox <matthew@wil.cx>
Subject: Re: [parisc-linux] 2.6.11-rc3-pa3 smp "Segmentation fault" but not up
Date: Sun, 16 Jan 2005 00:32:26 +0000	[thread overview]
Message-ID: <41E9B61A.5060204@tiscali.be> (raw)
In-Reply-To: <20050115224118.GC10070@colo.lackof.org>

Hello Grant,

Sorry for delay but the n stand in the office and join it from home i need to use vpn connection which deasable my local lan (and 
also my pop3 access to my isp :-( and obviously irc)

Grant Grundler wrote:
> On Sat, Jan 15, 2005 at 10:11:54PM +0000, Joel Soete wrote:
> 
>>this patch:
>><http://cvs.parisc-linux.org/linux-2.6/arch/parisc/kernel/pacache.S?r1=1.9&r2=1.10> ?
> 
> 
> I don't think willy is refering to any particular issue.
> 
> 
>>Well in doubt I revert all changes since:
>><http://cvs.parisc-linux.org/*checkout*/linux-2.6/arch/parisc/kernel/pacache.S?rev=1.9.20.2>
>>
>>Btw what do you suspect that Grant (and I) could have missed (just divid by 
>>2 the number of loop thanks to dword insn)?
> 
> 
> No - I mangled that. The code you submitted was correct in this regard.
Agree (but what could we imagine on a system which only have one atomic insn iirc?)

> I fixed the off-by-2x bug in the next commit:
> http://cvs.parisc-linux.org/linux-2.6/arch/parisc/kernel/pacache.S?r1=1.10&r2=1.11
> 
> My suspicion is the prefetching might be causing problems since it's going
> past the end of the page. The kernel tmp alias pages might be causing problems
> since we don't flush past the end of those. (Or something like that).
> 
sorry I didn't have yet understand all details of prefetching

> Can you remove only the prefetching in that algorithm?
> 
Yes, I did and already run one occurence of the loop without pb, .. so we have to be patient to see if first mentioned pb (failures 
after some loop occurence: about 50 last time) :-)

> 
>>But already strange results:
> 
> ...
> 
>>and after those first 11 failed it seems to continue??
> 
> 
> Do you mean after restarting the make the build completed?

No, just let continue the loop (that doesn't make sense to me but in fact I already encounter this case with 2.6.10-paXX but don't 
have time to report it).

Is nicol also encounter the same pb (just in case of small diff in hw config)?

Thanks,
	Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2005-01-16  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 14:02 [parisc-linux] 2.6.11-rc3-pa3 smp "Segmentation fault" but not up Joel Soete
2005-01-15 14:41 ` Matthew Wilcox
     [not found]   ` <41E9952A.1000907@tiscali.be>
     [not found]     ` <20050115224118.GC10070@colo.lackof.org>
2005-01-16  0:32       ` Joel Soete [this message]
2005-01-25 13:56         ` Same pb on b2k 64bit + 2.6.11-rc2-pa0 [Was: [parisc-linux] 2.6.11-rc3-pa3 smp "Segmentation fault" but not up] Joel Soete

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=41E9B61A.5060204@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=grundler@parisc-linux.org \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@parisc-linux.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