From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Dual opteron various segfaults with 2.6.14.2 and earlier kernels
Date: Wed, 23 Nov 2005 22:55:57 +0000 [thread overview]
Message-ID: <200511232255.57716.andrew@walrond.org> (raw)
In-Reply-To: <200511231537.49320.cova@ferrara.linux.it>
On Wednesday 23 November 2005 14:37, Fabio Coatti wrote:
> Hi all,
> I'm seeing several segfaults on a couple of HP DL585 Dual Opterons, 8Gb ram
> each.
>
> The segfaults are like this:
> factorial[17031]: segfault at 0000000000020f31 rip 00000000004035ae rsp
> 00007fffffe287e0 error 4
> factorial[17034]: segfault at 0000000000020f31 rip 00000000004035ae rsp
> 00007fffffc6f450 error 4
> factorial[17038]: segfault at 0000000000020f31 rip 00000000004035ae rsp
> 00007fffffdbd060 error 4
> factorial[17044]: segfault at 0000000000020f31 rip 00000000004035ae rsp
> 00007fffffb48fa0 error 4
> factorial[17046]: segfault at 0000000000020f31 rip 00000000004035ae rsp
> 00007fffffc2a7f0 error 4
> ld[3997]: segfault at 0000000000000020 rip 00002aaaaad1a525 rsp
> 00007fffffa8e960 error 4
> ld[4234]: segfault at 0000000000000020 rip 00002aaaaad1a525 rsp
> 00007fffffc3a1e0 error 4
>
> This is only an example; often during some "make", also sed segfaults (!).
> I've seen this with 2.6.12, 2.6.13.4, 2.6.14.2
>
The symtoms look just like the TLB flush filter errata which affected SMP
x86_64 kernels upto (at least) 2.6.13.4. IIRC it was fixed for 2.6.14 (at
least I stopped using the patch after 2.6.13.4).
Are you sure you saw this with 2.6.14+ ?
Andrew Walrond
next prev parent reply other threads:[~2005-11-23 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 14:37 Dual opteron various segfaults with 2.6.14.2 and earlier kernels Fabio Coatti
2005-11-23 14:41 ` Arjan van de Ven
2005-11-23 15:49 ` Fabio Coatti
2005-11-23 22:55 ` Andrew Walrond [this message]
2005-11-23 23:26 ` Fabio Coatti
2005-11-24 0:03 ` Andrea Arcangeli
2005-11-24 8:07 ` Andrew Walrond
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=200511232255.57716.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
/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.