[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080501130444.cc5c63e8.akpm@linux-foundation.org>
Date: Thu, 1 May 2008 13:04:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: ryan.roth@...m.com
Cc: bugme-daemon@...zilla.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 10586] New: High Number of Segfaults on
MacBook Starting With 2.6.24.5 Kernel
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Thu, 1 May 2008 12:30:18 -0700 (PDT)
bugme-daemon@...zilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10586
>
> Summary: High Number of Segfaults on MacBook Starting With
> 2.6.24.5 Kernel
> Product: Memory Management
> Version: 2.5
> KernelVersion: 2.6.24.5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: akpm@...l.org
> ReportedBy: ryan.roth@...m.com
>
>
> Latest working kernel version: 2.6.23?
> Earliest failing kernel version: 2.6.24.5
> Distribution: Fedora 8 x86_64
> Hardware Environment: MacBook
> Problem Description: Extremely high number of segfaults. Suspect that this
> may have to do with some sort of change in memory remapping changes in the
> kernel.
This report is a bit mysterious. I assume you're referring to x86's
"%s%s[%d]: segfault at %lx ip %08lx sp %08lx error %lx"
printk in the kernel logs?
Can you please send some examples of the log output?
Is there actually any observeable problem apart from the logs? Are
applications dying where they previously did not?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists