From: Jun Sun <jsun@mvista.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: OOps - very obscure
Date: Thu, 25 Jan 2001 10:59:07 -0800 [thread overview]
Message-ID: <3A70777B.F86123A5@mvista.com> (raw)
In-Reply-To: 20010125134331.A11489@paradigm.rfc822.org
Florian,
What is the kernel version? Your symptom seems to remind me the corrupted s0
bug in several syscalls. The bug is fixed around test9 I believe. Check for
"save_static_function(sys_sigsuspend);" statement in arch/mips/kernel/signal.c
file. If you have it, then you don't have the bug.
Jun
Florian Lohoff wrote:
>
> On Wed, Jan 24, 2001 at 04:59:19PM +0100, Florian Lohoff wrote:
>
> > Decoded this is:
>
> > >>RA; 00000000 Before first symbol
> > >>PC; 00000000 Before first symbol
> > Trace; 88028344 <sys_nanosleep+190/24c>
> > Trace; 8800fa88 <stack_done+1c/38>
>
> I am trying to track this down a bit more:
>
> with strace (very old version)
>
> rt_sigaction(34, {SIG_DFL}, NULL, 16) = 0
> rt_sigprocmask(SIG_BLOCK, [], NULL, 16) = 0
> sysmips(0x7d1, 0x2ac95d24, 0x1, 0) = 4149
> sched_yield(0x7d1, 0x2ac95d24, 0x1, 0, 0x2acfad50) = 0
> sysmips(0x7d1, 0x2ac95d24, 0x1, 0) = 4149
> sched_yield(0x7d1, 0x2ac95d24, 0x1, 0, 0x2acfad50) = 0
> sysmips(0x7d1, 0x2ac95d24, 0x1, 0) = 4149
> sched_yield(0x7d1, 0x2ac95d24, 0x1, 0, 0x2acfad50) = 0
> sysmips(0x7d1, 0x2ac95d24, 0x1, 0) = 4149
> sched_yield(0x7d1, 0x2ac95d24, 0x1, 0, 0x2acfad50) = 0
> sysmips(0x7d1, 0x2ac95d24, 0x1, 0) = 4149
> [... repeated this 2 lines ...]
>
> Every 1000 lines or something:
>
> nanosleep({0, 2000001}, NULL) = 0
>
> But with strace it doesnt crash it seems at least not within 10 Minutes
> i let it run ...
>
> Flo
> --
> Florian Lohoff flo@rfc822.org +49-5201-669912
> Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-01-25 19:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 15:30 OOps - very obscure Florian Lohoff
2001-01-24 15:59 ` Florian Lohoff
2001-01-24 16:22 ` Florian Lohoff
2001-01-24 21:18 ` Keith Owens
2001-01-25 12:43 ` Florian Lohoff
2001-01-25 18:59 ` Jun Sun [this message]
2001-01-25 19:22 ` Florian Lohoff
2001-01-25 15:55 ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Florian Lohoff
2001-01-25 15:55 ` Florian Lohoff
2001-01-25 16:34 ` Origin 200 crash nick
2001-01-25 18:28 ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Joe deBlaquiere
2001-01-25 19:35 ` Joe deBlaquiere
2001-01-25 22:19 ` Ralf Baechle
2001-01-26 0:53 ` Joe deBlaquiere
2001-01-26 10:21 ` Maciej W. Rozycki
2001-01-26 15:41 ` Joe deBlaquiere
2001-01-26 21:16 ` Ralf Baechle
2001-01-27 7:20 ` Maciej W. Rozycki
2001-01-26 21:15 ` Ralf Baechle
2001-01-27 7:28 ` Maciej W. Rozycki
2001-01-27 19:42 ` Ralf Baechle
2001-01-29 15:03 ` Maciej W. Rozycki
2001-01-26 20:01 ` Jun Sun
2001-01-26 20:38 ` Joe deBlaquiere
2001-01-26 21:02 ` Jun Sun
2001-04-04 22:13 ` Florian Lohoff
2001-02-19 13:11 ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Wichert Akkerman
2001-02-19 19:52 ` newbie question Can Altineller
2001-02-20 7:06 ` David Jez
2001-02-20 20:26 ` Mike McDonald
2001-02-20 20:30 ` nick
2001-02-20 20:53 ` Ralf Baechle
2001-02-20 20:41 ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Ralf Baechle
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=3A70777B.F86123A5@mvista.com \
--to=jsun@mvista.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
/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.