From: Andrew Morton <akpm@linux-foundation.org>
To: ryan.roth@ch2m.com
Cc: bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 10586] New: High Number of Segfaults on MacBook Starting With 2.6.24.5 Kernel
Date: Thu, 1 May 2008 13:04:44 -0700 [thread overview]
Message-ID: <20080501130444.cc5c63e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10586-10286@http.bugzilla.kernel.org/>
(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@bugzilla.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@osdl.org
> ReportedBy: ryan.roth@ch2m.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.
next parent reply other threads:[~2008-05-01 20:05 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 ` Andrew Morton [this message]
2008-05-01 20:09 ` [Bugme-new] [Bug 10586] New: High Number of Segfaults onMacBook Starting With 2.6.24.5 Kernel 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
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=20080501130444.cc5c63e8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan.roth@ch2m.com \
/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