From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@parisc-linux.org, Matthew Wilcox <willy@debian.org>
Subject: [parisc-linux] fork failed? protection id trap. All suspect.
Date: Sat, 8 Nov 2003 17:09:23 -0500 [thread overview]
Message-ID: <20031108220923.GK21080@systemhalted> (raw)
In-Reply-To: <3FAD5C01.7040302@tiscali.be>
On Sat, Nov 08, 2003 at 09:11:29PM +0000, Joel Soete wrote:
> all start fine until I point a mail to preview it in the preview's window.
> Then a child process failled, so Ctrl-C in gdb and bt:
> #0 0x4172005c in __pthread_sigsuspend () from /lib/libpthread.so.0
...
> #29 0x0009deb8 in main ()
> #30 0x41a1146c in __libc_start_main () from /lib/libc.so.6
> #31 0x00022e10 in _start ()
> ----------><----------
This is a trace from another thread. You need to attach to the thread
that is going to die and try to get a backtrace. This thread was happy
:) until you interrupted it's sleeping.
> At the console, I could always capture:
>
> request_module[net-pf-10]: fork failed, errno 1
> evolution (pid 879): Protection id trap (code 27)
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001000000000000001111 Not tainted
> r00-03 00000000 103b7524 1015352c 00282b28
> r04-07 00000000 00000000 00000001 11f27da0
> r08-11 00000000 00000001 13084548 fffffff2
> r12-15 419ee608 419ee718 419345a8 419345a8
> r16-19 419ee608 419345a8 00000070 1371d000
> r20-23 00000000 00000002 00282b2e 00000000
> r24-27 11f27da0 00000000 10d0b520 10304010
> r28-31 00000000 10314a60 130845c0 101532c8
> sr0-3 00000000 00000000 00000000 00000003
> sr4-7 00000000 00000000 00000000 00000000
>
> IASQ: 00000000 00000000 IAOQ: 10153658 1015365c
> IIR: 0ed4d240 ISR: 00000003 IOR: 00282b2e
> CPU: 0 CR30: 13084000 CR31: 103a8000
> ORIG_R28: 419345a8
>
> ----------><----------
I've never seen this perhaps some kernelish people would like to comment
on this?
> while I can still see processes:
> root 879 869 0 17:16 pts/2 00:00:00 [evolution] <defunct>
Try to find the thread that is going to die and attach to it.
c.
next prev parent reply other threads:[~2003-11-08 22: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
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 ` Carlos O'Donell [this message]
2003-11-08 22:36 ` [parisc-linux] fork failed? protection id trap. All suspect 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=20031108220923.GK21080@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@parisc-linux.org \
--cc=soete.joel@tiscali.be \
--cc=willy@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