[Top] [All Lists]

RE: "Segfault/illegal instruction" - udevd - ntpd - glibc

To: <>
Subject: RE: "Segfault/illegal instruction" - udevd - ntpd - glibc
From: "Sadarul Firos" <>
Date: Mon, 18 Jun 2007 15:21:29 +0530
Cc: <>
Original-recipient: rfc822;
Thread-index: AcexAQS/8o5iaXsVRBW3fMJuu+ZjbAAiqDjwAACNqiA=
Thread-topic: "Segfault/illegal instruction" - udevd - ntpd - glibc
Thanks Ralf for the reply.

Regarding kernel, I am using the final release version of linux 2.6.18
kernel with some customizations. Out of the two boards which I have one
has MSP8150 Multi-Service Processor(MIPS 64) and the other has ITE 8172
system controller with RM7035C, 64-bit MIPS RISC microprocessor(MIPS V).

-----Original Message-----
From: Ralf Baechle [] 
Sent: Sunday, June 17, 2007 1:04 AM
To: Sadarul Firos
Subject: Re: "Segfault/illegal instruction" - udevd - ntpd - glibc

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
> reboot test on these boards. After some number of reboots (say 80) I
> getting "segmentaion fault/illegal instruction" while running udevd
> ntpd during bootup. Upon observing the core dump, it is noted that the
> segfault occured from the _init function of (in the case
> of ntpd) and (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
> 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

What 2.6.18 variant exactly are you running, that is where & when did
download it, what CPU?


<Prev in Thread] Current Thread [Next in Thread>