All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Joel Soete <soete.joel@tiscali.be>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] but still panic: [WAS: 2.6.10-rc1-pa15 boot fine on n4k but still	annoying bactrace]
Date: 25 Nov 2004 14:39:05 -0600	[thread overview]
Message-ID: <1101415152.2020.21.camel@mulgrave> (raw)
In-Reply-To: <418A80E800005C38@mail-6-bnl.tiscali.it>

On Mon, 2004-11-22 at 08:10, Joel Soete wrote:
> IASQ: 0000000000000000 0000000000000000 IAOQ: 000000001016a7cc 000000001016a7d0
>  IIR: 527401a0    ISR: 0000000000000000  IOR: 00000000000000d0
>  CPU:        0   CR30: 000000004d5a0000 CR31: 00000000105f0000
>  ORIG_R28: 000000001010d18c
>  IAOQ[0]: update_one_process+0x74/0x168
>  IAOQ[1]: update_one_process+0x78/0x168
>  RP(r2): update_one_process+0x6c/0x168

As best I can tell, this is in kernel/timer.c here:

        if (p->signal && !unlikely(p->state & (EXIT_DEAD|EXIT_ZOMBIE))
&&
            psecs / HZ >= p->signal->rlim[RLIMIT_CPU].rlim_cur) {

The problem seems to be that p->signal is null, but it wasn't null when
the processor began the evaluation of the condition.  0xd0 is the 64 bit
offset of rlim[RLIMIT_CPU].rlim_cur.

If you look at the code, p->signal should be in r19 which is zero.

I have no explanation for this (other than some weird race in the signal
handling code somewhere).

James


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

       reply	other threads:[~2004-11-25 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <418A80E800005C38@mail-6-bnl.tiscali.it>
2004-11-25 20:39 ` James Bottomley [this message]
2004-11-26  7:22   ` [parisc-linux] but still panic: [WAS: 2.6.10-rc1-pa15 boot fine on n4k but still annoying bactrace] Joel Soete
2004-12-16 14:19   ` 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=1101415152.2020.21.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=parisc-linux@lists.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 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.