Re: [Bugme-new] [Bug 10586] New: High Number of SegfaultsonMacBookStarting With 2.6.24.5 Kernel

[Andrew Morton]

On Fri, 2 May 2008 05:19:45 -0700 Phil Oester <kernel@xxxxxxxxxxxx> wrote:

> 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@xxxxxxxxxxxx> 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.

No, I can't suggest anything else to try, sorry.

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.

Are any other problems observeable?  Does qmail continue to operate
normally in 2.6.24?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/