From: Andrew Morton <akpm@linux-foundation.org>
To: Ryan Roth <ryanroth@sbcglobal.net>
Cc: randy.dunlap@oracle.com, 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, 1 May 2008 17:15:20 -0700 [thread overview]
Message-ID: <20080501171520.38e2a478.akpm@linux-foundation.org> (raw)
In-Reply-To: <481A58A2.7070807@sbcglobal.net>
On Thu, 01 May 2008 16:56:18 -0700
Ryan Roth <ryanroth@sbcglobal.net> wrote:
> > May 1 16:15:01 kernel: proc_dir_entry 'info' already registered
> > May 1 16:15:01 kernel: Pid: 1099, comm: modprobe Not tainted 2.6.25-git16 #3
> > May 1 16:15:01 kernel:
> > May 1 16:15:01 kernel: Call Trace:
> > May 1 16:15:01 kernel: [<ffffffff81118269>] idr_get_new+0xb/0x28
> > May 1 16:15:01 kernel: [<ffffffff810d5e92>] proc_register+0xcb/0x14b
> > May 1 16:15:01 kernel: [<ffffffff810d5ec5>] proc_register+0xfe/0x14b
> > May 1 16:15:01 kernel: [<ffffffff810d5f96>] proc_create_data+0x84/0x9e
> > May 1 16:15:01 kernel: [<ffffffffa013dd37>]
> > :video:acpi_video_bus_add+0x98f/0xc6d
> > May 1 16:15:01 kernel: [<ffffffff8115d4d9>] acpi_device_probe+0x43/0x91
> > May 1 16:15:01 kernel: [<ffffffff81192564>] driver_probe_device+0xd0/0x14d
> > May 1 16:15:01 kernel: [<ffffffff81192627>] __driver_attach+0x46/0x6d
> > May 1 16:15:01 kernel: [<ffffffff811925e1>] __driver_attach+0x0/0x6d
> > May 1 16:15:01 kernel: [<ffffffff81191f09>] bus_for_each_dev+0x44/0x6f
> > May 1 16:15:01 kernel: [<ffffffff8119186e>] bus_add_driver+0xb2/0x1ff
> > May 1 16:15:01 kernel: [<ffffffff81192846>] driver_register+0x59/0xcd
> > May 1 16:15:01 kernel: [<ffffffffa00d803c>] :video:acpi_video_init+0x3c/0x5e
> > May 1 16:15:01 kernel: [<ffffffff81052db2>] sys_init_module+0x171a/0x1896
> > May 1 16:15:01 kernel: [<ffffffff8115d812>] acpi_bus_register_driver+0x0/0x3e
> > May 1 16:15:01 kernel: [<ffffffff81098831>] vfs_read+0xa6/0xfe
> > May 1 16:15:01 kernel: [<ffffffff8100bf3b>]
> > system_call_after_swapgs+0x7b/0x80
That's an acpi video problem - it won't be the cause of this regression.
I'll forward it separately.
> > ---
> > ~Randy
> >
> >
> The segfaults are still present causing apps to not work. I attached a
> boot log in case it was needed for more details. Should I not worry
> about the following message?
>
> May 1 16:15:01 kernel: PCI: MCFG configuration 0: base f0000000 segment
> 0 buses 0 - 255
> May 1 16:15:01 kernel: PCI: BIOS Bug: MCFG area at f0000000 is not
> reserved in ACPI motherboard resources
> May 1 16:15:01 kernel: PCI: Not using MMCONFIG.
Again, the mmconfig warnings will be unrelated to this bug.
next prev parent reply other threads:[~2008-05-02 0:16 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 [this message]
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=20080501171520.38e2a478.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Ryan.Roth@CH2M.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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