[ILUG] Bad EIP value

[Paul Jakma]

On Mon, 23 Aug 2004, Brendan Halpin wrote:

> FWIW, "strace ls -l" finishes as follows:
>
> -------------------------------------------------------------------
> open("/etc/localtime", O_RDONLY)        = 3
> fstat64(3, {st_mode=S_IFREG|0644, st_size=1285, ...}) = 0
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40021000
> read(3, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\n\0\0\0\n\0"..., 4096) = 1285
> close(3)                                = 0
> munmap(0x40021000, 4096)                = 0
> clock_gettime(0,  <unfinished ...>
> +++ killed by SIGSEGV +++
> -------------------------------------------------------------------
>
> "strace df" as follows:
> -------------------------------------------------------------------
> open("/usr/share/locale/en.iso885915/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/usr/share/locale/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
> fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40018000
> write(1, "Filesystem           1K-blocks  "..., 67Filesystem           1K-blocks      Used Available Use% Mounted on
> ) = 67
> statfs64("/", 84,  <unfinished ...>
> +++ killed by SIGSEGV +++
> -------------------------------------------------------------------

Is the syscall it SEGV's in different each time? Or not consistent?

Is this after reboot? (you cant trust a kernel after it has oopsed, 
reboot at earliest convenience)

If after reboot, and syscall it SEGVs in is not consistent (and those 
are strange calls to get legit SEGVs in, esp if they didnt return..) 
it's very likely hardware is foobared. Run memtest86 for a few hours 
at least (if not overnight) to see if it produces memory errors.

regards,
-- 
Paul Jakma	paul at clubi.ie	paul at jakma.org	Key ID: 64A2FF6A
Fortune:
The world is not octal despite DEC.