public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Roth <ryanroth@sbcglobal.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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: Thu, 01 May 2008 17:04:36 -0700	[thread overview]
Message-ID: <481A5A94.2080400@sbcglobal.net> (raw)
In-Reply-To: <20080501170239.9b740877.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Thu, 01 May 2008 16:29:58 -0700
> Ryan Roth <ryanroth@sbcglobal.net> wrote:
>
>   
>>> OK, worried.  This is a huge bug.  But afaik you're the only person 
>>> who has
>>> hit it, so there must be something special in your setup which is
>>> triggering it.  This could be hard.
>>>
>>>       
>> OK here is what I get with the git16 kernel.  On boot I get this error:
>>
>> PCI: Not using MMCONFIG
>> PCI: BIOS Bug: MCFG area at f0000000 is not reserved in ACPI motherboard 
>> resources
>> PCI: Not using MMCONFIG
>>     
>
> yeah, mmconfig is a problem.  It should be harmless.  Probably you're
> better off with it disabled ;)
>
>   
>> Attached is a complete log after this boot
>>     
>
> I see no 'segfault' messages in there?
>
>   
Since this last boot I have only got these:

> May 1 16:26:25 kernel: gnome-power-man[3112]: segfault at 0 ip 410fda 
> sp 7fff4712c870 error 4 in gnome-power-manager[400000+47000]
> May 1 16:26:25 kernel: gnome-power-man[3116]: segfault at 0 ip 410fda 
> sp 7fff2959cce0 error 4 in gnome-power-manager[400000+47000]
> May 1 16:26:25 kernel: gnome-power-man[3119]: segfault at 0 ip 410fda 
> sp 7fffc7671db0 error 4 in gnome-power-manager[400000+47000]


  reply	other threads:[~2008-05-02  0:06 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 [this message]
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=481A5A94.2080400@sbcglobal.net \
    --to=ryanroth@sbcglobal.net \
    --cc=Ryan.Roth@CH2M.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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