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: Sat, 3 May 2008 08:59:09 -0700 [thread overview]
Message-ID: <20080503155909.GA23105@linuxace.com> (raw)
In-Reply-To: <20080502061018.5557d067.akpm@linux-foundation.org>
On Fri, May 02, 2008 at 06:10:18AM -0700, Andrew Morton wrote:
> Traditionally i386 never printed that message (in fact neither architecture
> should - it allows poeple to spam the logs, but it is at least
> ratelimited).
>
> In 2.6.23, i386 _does_ generate that message, in arch/i386/mm/fault.c
>
> In 2.6.24 the i386 and x86_64 fault handlers were renamed to
> arch/x86/mm/fault_[32|64].c and both versions generated the message.
>
> In 2.6.25 they were unified into a single arch/x86/mm/fault.c, and both
> architectures print the message.
>
> So afacit 2.6.23 _should_ be printing the message if qmail is indeed
> generating a segfault. But there's always the possibility that the
> message-printing code was simply broken in 2.6.23, and that your qmail has
> always been generating segfaults.
That is the most likely scenario. I tried out 2.6.23, and it generates
the segfaults also. And we're running a patched qmail-smtpd, so it likely
has been segfaulting "forever", but only became noticable in 2.6.23+.
Sorry for the noise.
Phil
next prev parent reply other threads:[~2008-05-03 15:59 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
2008-05-02 13:10 ` Andrew Morton
2008-05-03 15:59 ` Phil Oester [this message]
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=20080503155909.GA23105@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