From: Ralf Baechle <ralf@linux-mips.org>
To: Sadarul Firos <sadarul.firos@nestgroup.net>
Cc: linux-mips@linux-mips.org
Subject: Re: "Segfault/illegal instruction" - udevd - ntpd - glibc
Date: Sat, 16 Jun 2007 20:33:59 +0100 [thread overview]
Message-ID: <20070616193358.GA22195@linux-mips.org> (raw)
In-Reply-To: <9A1299C7A40D7447A108107E951450CA01C9E015@MAIL-TVM.tvm.nestgroup.net>
On Fri, Jun 15, 2007 at 09:23:34PM +0530, Sadarul Firos wrote:
> I am working with two MIPS based boards (one is MIPS and the other is
> MIPSEL) running linux-2.6.18/glibc-2.3.5. I am performing a consecutive
> reboot test on these boards. After some number of reboots (say 80) I am
> getting "segmentaion fault/illegal instruction" while running udevd and
> ntpd during bootup. Upon observing the core dump, it is noted that the
> segfault occured from the _init function of libnss_dns.so (in the case
> of ntpd) and libnss_compat.so (in the case of udevd). I assume that
> there might be a problem somewhere in the call_init function in
> glibc-2.3.5/elf/dl-init.c. After I put some printf statements for
> debugging in the call_init function, there is no segfault/illegal
> instruction in the reboot testing. I have also used gdb to debug the
> problem but the "segfault/illegal instruction" doesn't occur during the
> reboot test. Could anyone please help me to sort out this problem. The
> gdb output using coredump is attached.
Normally the address space layout and most other variables during a
program load should be identical each time so userspace should behave
identical. So I sense the scent of a TLB or more likely cache managment
problem.
What 2.6.18 variant exactly are you running, that is where & when did
download it, what CPU?
Ralf
next prev parent reply other threads:[~2007-06-17 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 15:53 "Segfault/illegal instruction" - udevd - ntpd - glibc Sadarul Firos
2007-06-15 15:53 ` Sadarul Firos
2007-06-16 19:33 ` Ralf Baechle [this message]
2007-06-19 18:17 ` [SPAM] " Markus Gothe
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 9:51 Sadarul Firos
2007-06-18 9:51 ` Sadarul Firos
2007-06-26 14:26 Sadarul Firos
2007-06-26 14:26 ` Sadarul Firos
2007-07-20 4:19 Shane McDonald
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=20070616193358.GA22195@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sadarul.firos@nestgroup.net \
/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