From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] evolution (1.4.5-1) 'protection id trap' [was: do_page_fault?]
Date: Sun, 19 Oct 2003 19:10:15 -0400 [thread overview]
Message-ID: <20031019231015.GH8642@systemhalted> (raw)
In-Reply-To: <3F92EAB4.7070802@tiscali.be>
On Sun, Oct 19, 2003 at 07:49:08PM +0000, Joel Soete wrote:
> Hi pa,
>
> Please apologies, I forget to mentioned an important matter:
> with 2.6.0-test-pa1 it is not anymore a do_page_fault() but:
> evolution (pid 2454): Protection id trap (code 27)
Do not wrap lines like this.
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001000000000000001111 Not
> tainted r00-03
You should really run evolution through gdb. Remember to use "handle all
nostop" and "handle all pass".
c.
next prev parent reply other threads:[~2003-10-19 23:14 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 [this message]
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
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=20031019231015.GH8642@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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