Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Latest 2.6.13-rc6-pa2 test pr :_(
Date: Sun, 21 Aug 2005 14:37:38 +0000	[thread overview]
Message-ID: <430891B2.1010507@tiscali.be> (raw)
In-Reply-To: <200508201751.j7KHpqIH017505@hiauly1.hia.nrc.ca>



John David Anglin wrote:
>>>TOC:
>>>
>>>r2	__handle_mm_fault+0x68  (return from call to pte_alloc_map)
>>>IIA	__handle_mm_fault+0x190
>>>
>>>It looks as if this might have been caused by Process_3.exe in the
>>>libjava GCC testsuite.
>>
>>Does it always hang in the same place? How much RAM/swap do you have in 
>>your system? Does it hang more/less if you disable swap?
> 
> 
> Had another hang last night.  Here is the TOC for it:
> 
> r2	intr_check_sig+0
> IIA	handle_interruption+0x30
> r26,r5	code = 0x1a = 26 => Data Memory Access Rights Trap
> 
mmm, from pure user point of view that sounds a bit like a segv?

and btw in traps.c still stand some other
[...]
     479 void handle_interruption(int code, struct pt_regs *regs)
     480 {
[...]
     737                 force_sig_info(SIGSEGV, &si, current);
[...]
     781                 force_sig_info(SIGSEGV, &si, current);
[...]

This last one is specialy interesting as (if I well understand) ending handle_interruption() for case 26.

Unfortunately, not yet find how to fix it:
	o as tausq did for signal.c
	o s/force_sig_info(SIGSEGV, &si, current)/force_sig(SIGSEGV, current)/

Joel

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

  reply	other threads:[~2005-08-21 14:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4305FA88.9040404@tausq.org>
2005-08-19 18:41 ` [parisc-linux] Latest 2.6.13-rc6-pa2 test pr :_( John David Anglin
2005-08-20 17:51 ` John David Anglin
2005-08-21 14:37   ` Joel Soete [this message]
2005-08-21 15:47     ` John David Anglin
2005-08-21 15:53   ` Randolph Chung
2005-08-21 16:46     ` John David Anglin
     [not found] <200508261342.j7QDgMCk015398@hiauly1.hia.nrc.ca>
2005-08-27 14:40 ` Randolph Chung
2005-08-27 17:38   ` John David Anglin
2005-08-26 16:18 Joel Soete
     [not found] <ILU3F9$C3BA108CF7E2FE4DECDD367F36FD15E5@scarlet.be>
2005-08-26 15:29 ` John David Anglin
     [not found] <200508241530.j7OFUFwS005854@hiauly1.hia.nrc.ca>
2005-08-25 15:59 ` Randolph Chung
2005-08-25 17:04   ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2005-08-18 16:01 Joel Soete
2005-08-18 17:24 ` John David Anglin
2005-08-18 23:49 ` Randolph Chung

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=430891B2.1010507@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.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