segfaults suddenly appearing
From: Jakob Oestergaard
Date: Wed Jun 08 2005 - 08:42:50 EST
On Mon, Jun 06, 2005 at 11:08:25AM -0700, Linus Torvalds wrote:
>
> It's being uploaded right now, the git tree is already up-to-date, and by
> the time this hits the mailing list the mirroring of the tar-ball will
> hopefully be done too.
...
Guys, here's a (yes I know, fairly vague) error report - I'm just
beginning to narrow this down. Any suggestions would be greatly
appreciated.
Dual opteron (Sun Fire v20z), 2G RAM, untainted x86_64 kernels (no
preempt or other fancy stuff, just plain and simple K8 NUMA ACPI
configs);
Problem with 2.6.11.11: Machine hangs during backup (amanda) - right
after the estimates are done the box will freeze hard, nothing on
console.
Tried 2.6.12-rc6 in the hope that it would at least print out a panic or
oops for me: Haven't tried the backup yet, but I got the following in
the logs which I've never seen before:
gcc[18818]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffba4c error 6
klogd[3116]: segfault at 000000003ef1b373 rip 000000000804a3b3 rsp 00000000ffffbbe0 error 4
gcc[18857]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffbedc error 6
gcc[19049]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffaefc error 6
gcc[19097]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffb1fc error 6
gcc[19251]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffc9dc error 6
gcc[19272]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffb1bc error 6
gcc[1569]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffb56c error 6
gcc[16458]: segfault at 00000000332c8e54 rip 000000005555a0a8 rsp 00000000ffffc9ac error 6
So, with 2.6.12-rc6 all of the sudden klogd and gcc starts
segfaulting...
No ECC errors or other anormalities reported via the service processor.
Anything you want me to try? Need more information?
--
/ jakob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/