From: Joel Soete <soete.joel@tiscali.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Carlos O'Donell <carlos@baldric.uwo.ca>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] evolution (1.4.5-1) 'protection id trap' [was: do_page_fault?]
Date: Sun, 09 Nov 2003 00:11:39 +0000 [thread overview]
Message-ID: <3FAD863B.8010609@tiscali.be> (raw)
In-Reply-To: <20031108223304.GB28929@colo.lackof.org>
Grant Grundler wrote:
> On Sat, Nov 08, 2003 at 12:46:28PM +0000, Joel Soete wrote:
>
>>But if I launch it a second time no more pb???
>>Very strange isn't it?
>
>
> Sounds like a cache coherency/aliasing problem.
> Once you start looking at code, watch out for module loading
> and shared memory maps type stuff.
>
> grant
>
Thanks Grant,
I have to put it in my todo list (sorry not enough time in a day)
Joel
prev parent reply other threads:[~2003-11-09 0:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 22:17 [parisc-linux] evolution (1.4.5-1) do_page_fault? Joel Soete
2003-10-12 18:16 ` Carlos O'Donell
2003-10-12 18:42 ` Joel Soete
2003-10-12 20:02 ` Carlos O'Donell
2003-10-13 11:44 ` Joel Soete
2003-10-18 21:13 ` Joel Soete
2003-10-19 15:28 ` Joel Soete
2003-10-19 19:49 ` [parisc-linux] evolution (1.4.5-1) 'protection id trap' [was: do_page_fault?] Joel Soete
2003-10-19 23:10 ` Carlos O'Donell
2003-10-21 6:24 ` Joel Soete
2003-11-01 23:27 ` Joel Soete
2003-11-02 20:22 ` Carlos O'Donell
2003-11-03 9:11 ` Joel Soete
2003-11-08 12:46 ` Joel Soete
2003-11-08 15:52 ` Carlos O'Donell
2003-11-08 21:11 ` Joel Soete
2003-11-08 22:09 ` [parisc-linux] fork failed? protection id trap. All suspect Carlos O'Donell
2003-11-08 22:36 ` Joel Soete
2003-11-08 22:33 ` [parisc-linux] evolution (1.4.5-1) 'protection id trap' [was: do_page_fault?] Grant Grundler
2003-11-09 0:11 ` Joel Soete [this message]
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=3FAD863B.8010609@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=carlos@baldric.uwo.ca \
--cc=grundler@parisc-linux.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.