From: Phil Oester <kernel@linuxace.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ryan Roth <ryanroth@sbcglobal.net>,
Ryan.Roth@CH2M.com, bugme-daemon@bugzilla.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 10586] New: High Number of Segfaults onMacBookStarting With 2.6.24.5 Kernel
Date: Fri, 2 May 2008 05:19:45 -0700 [thread overview]
Message-ID: <20080502121945.GA18667@linuxace.com> (raw)
In-Reply-To: <20080501192838.8ecb81c2.akpm@linux-foundation.org>
On Thu, May 01, 2008 at 07:28:38PM -0700, Andrew Morton wrote:
> On Thu, 1 May 2008 19:08:15 -0700 Phil Oester <kernel@linuxace.com> wrote:
>
> > FWIW, I recently upgraded some boxes to 2.6.24.x, and started seeing tons of
> > qmail segfaults, which look remarkably similar to the above problem. 2.6.21
> > did not exhibit this issue.
> >
> > May 1 22:06:03 mail80 kernel: qmail-smtpd[5319]: segfault at 0 ip 4884b473 sp fffeec1c error 4 in libc-2.6.so[487dd000+14e000]
> > May 1 22:06:03 mail80 kernel: qmail-smtpd[5491]: segfault at 0 ip 4884b473 sp ffb7179c error 4 in libc-2.6.so[487dd000+14e000]
> > May 1 22:06:03 mail80 kernel: qmail-smtpd[4669]: segfault at 0 ip 4884b473 sp fff3135c error 4 in libc-2.6.so[487dd000+14e000]
> > May 1 22:06:05 mail80 kernel: qmail-smtpd[5906]: segfault at 0 ip 4884b473 sp ffe1b24c error 4 in libc-2.6.so[487dd000+14e000]
> > May 1 22:06:07 mail80 kernel: qmail-smtpd[5898]: segfault at 0 ip 4884b473 sp ffe4e27c error 4 in libc-2.6.so[487dd000+14e000]
> > May 1 22:06:11 mail80 kernel: qmail-smtpd[5840]: segfault at 0 ip 4884b473 sp ffe04a2c error 4 in libc-2.6.so[487dd000+14e000]
> >
>
> Can you try fiddling with the norandmaps boot option and
> /proc/sys/kernel/randomize_va_space?
echo 0 > /proc/sys/kernel/randomize_va_space does not make any difference (and
is equivalent to norandmaps boot option according to docs).
Unless you have other ideas, I can try to bisect this later today.
Phil
next prev parent reply other threads:[~2008-05-02 12:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10586-10286@http.bugzilla.kernel.org/>
2008-05-01 20:04 ` [Bugme-new] [Bug 10586] New: High Number of Segfaults on MacBook Starting With 2.6.24.5 Kernel Andrew Morton
2008-05-01 20:09 ` [Bugme-new] [Bug 10586] New: High Number of Segfaults onMacBook " Ryan.Roth
2008-05-01 20:30 ` Andrew Morton
[not found] ` <86A21F45FFA48B408A65E67054362EB621C948@CULEBRA.amr.ch2m.com>
2008-05-01 23:29 ` [Bugme-new] [Bug 10586] New: High Number of Segfaults onMacBookStarting " Ryan Roth
2008-05-01 23:48 ` Randy Dunlap
2008-05-01 23:56 ` Ryan Roth
2008-05-02 0:15 ` Andrew Morton
2008-05-02 0:02 ` Andrew Morton
2008-05-02 0:04 ` Ryan Roth
2008-05-02 0:12 ` Randy Dunlap
2008-05-02 0:21 ` Ryan Roth
2008-05-02 0:34 ` Andrew Morton
2008-05-02 0:37 ` Ryan Roth
2008-05-02 0:57 ` Ryan Roth
2008-05-02 1:42 ` Andrew Morton
2008-05-02 1:47 ` Ryan Roth
2008-05-02 2:08 ` Phil Oester
2008-05-02 2:28 ` Andrew Morton
2008-05-02 12:19 ` Phil Oester [this message]
2008-05-02 13:10 ` Andrew Morton
2008-05-03 15:59 ` Phil Oester
2008-05-03 16:14 ` Bernd Eckenfels
2008-05-04 1:06 ` Lee Revell
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=20080502121945.GA18667@linuxace.com \
--to=kernel@linuxace.com \
--cc=Ryan.Roth@CH2M.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryanroth@sbcglobal.net \
/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