From: "Andrey Falko" <ma3oxuct@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Random segfaults with kernel 2.6.27
Date: Thu, 20 Nov 2008 17:07:20 -0800 [thread overview]
Message-ID: <350fc7cf0811201707y638930ddy4f2cc9bd4caabab7@mail.gmail.com> (raw)
In-Reply-To: <gg50od$stq$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
On 11/20/08, Nikos Chantziaras <realnc@arcor.de> wrote:
>
> I upgraded to kernel 2.6.27 (gentoo-sources-2.6.27-r3) yesterday. Today I
> experienced random segfaults during an emerge (twice during emerging
> mozilla-thunderbird; one time "as" (assembler) segfaulted, on the second try
> python segfaulted at the end of the emerge).
>
> Anyone noticing something similar? I'm reverting back to 2.6.26 for now.
>
>
>
You do not see these segfaults on 2.6.26, right? When I had the symptoms you
described, it turned out that my RAM voltage needed to be raised in the
BIOS. Do you run the proprietary nvidia-drivers? If you don't, run any
software that taints the kernel, I'd file a bug with upstream kernel people:
http://bugzilla.kernel.org/
[-- Attachment #2: Type: text/html, Size: 1088 bytes --]
next prev parent reply other threads:[~2008-11-21 1:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 0:52 [gentoo-user] Random segfaults with kernel 2.6.27 Nikos Chantziaras
2008-11-21 1:07 ` Andrey Falko [this message]
2008-11-21 1:24 ` [gentoo-user] " Nikos Chantziaras
2008-11-21 1:58 ` Dale
2008-11-21 2:27 ` Nikos Chantziaras
2008-11-21 5:39 ` Dale
2008-11-21 2:20 ` Andrey Falko
2008-11-21 2:36 ` Nikos Chantziaras
2008-11-21 3:16 ` Nikos Chantziaras
2008-11-21 3:51 ` Mike
2008-11-21 3:59 ` Mike
2008-11-21 3:53 ` Iain Buchanan
2008-11-21 4:39 ` Nikos Chantziaras
2008-11-21 5:03 ` Iain Buchanan
2008-11-21 5:20 ` Nikos Chantziaras
2008-11-21 5:22 ` Andrey Falko
2008-11-21 5:50 ` Nikos Chantziaras
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=350fc7cf0811201707y638930ddy4f2cc9bd4caabab7@mail.gmail.com \
--to=ma3oxuct@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox