From: Chris Holvenstot <cholvenstot@comcast.net>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Unexpected segfaults with 2.6.23-rc-8-git4
Date: Sun, 30 Sep 2007 09:10:30 -0500 [thread overview]
Message-ID: <1191161430.6517.26.camel@localhost> (raw)
In-Reply-To: <1191159712.6517.12.camel@localhost>
I forgot to mention it in my initial post - although I am running an
AMD64 CPU - I am using the 32 bit version of the system
On Sun, 2007-09-30 at 08:41 -0500, Chris Holvenstot wrote:
> Good Morning -
>
> This morning I built the 2.6.23-rc8-git4 version of the kernel. After
> rebooting I was unable to keep my mail client (evolution) up and running
> for more than a few minutes at a time.
>
> A look in the log shows the following message when evolution aborts:
>
> kernel: [ 1716.971128] evolution[10212]: segfault at 00000054 eip
> b74bbf63 esp bfc84b20 error 4
>
> kernel: [ 1835.797215] evolution[10335]: segfault at 00000056 eip
> b745ef63 esp bfd9db20 error 4
>
> kernel: [ 1854.752324] evolution[10565]: segfault at 0000045f eip
> b747ef63 esp bfa9c140 error 4
>
> After falling back to 2.6.23-rc8-git3 I am no longer seeing this failure
> (at least not yet)
>
> My system is built on an AMD 64 X2 4600+ with 2 gig of memory, two SATA
> and three PATA drives. I am running what is basically a UBUNTU 7.04
> system.
>
> I am a certified dummy when it comes to diagnosing kernel issues so if
> there is some additional information which would be useful let me know,
> I would be happy to provide it. Just be sure to send instructions on
> how to gather it.
>
> Thanks
>
> Chris
>
prev parent reply other threads:[~2007-09-30 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 13:41 Unexpected segfaults with 2.6.23-rc-8-git4 Chris Holvenstot
2007-09-30 14:10 ` Chris Holvenstot [this message]
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=1191161430.6517.26.camel@localhost \
--to=cholvenstot@comcast.net \
--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.