From: "Giacomo A. Catenazzi" <cate@cateee.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Panic with 2.6.19-rc3-ga7aacdf9: Invalid opcode at acpi_os_read_pci_configuration
Date: Tue, 31 Oct 2006 11:29:15 +0100 [thread overview]
Message-ID: <4547257B.7090101@cateee.net> (raw)
In-Reply-To: <20061031021810.dd48361f.akpm@osdl.org>
Andrew Morton wrote:
> On Tue, 31 Oct 2006 09:23:44 +0100
> Giacomo Catenazzi <cate@cateee.net> wrote:
>
>> Since few days I have this bug (not sure if it
>> caused by changed configuration or if it is a regretion).
>> The fololowing trace is from last git.
>>
>> ...
>>
>>
>> [ 0.012497] Brought up 4 CPUs
>> [ 0.174941] migration_cost=19,713
>> [ 0.215588] NET: Registered protocol family 16
>> [ 0.268807] ACPI: bus type pci registered
>> [ 0.316660] PCI: Fatal: No config space access function found
>
> That looks pretty bad.
>
>> [ 0.385262] Setting up standard PCI resources
>> [ 0.452566] ACPI: Access to PCI configuration space unavailable
>> [ 0.527856] ACPI: Interpreter enabled
>> [ 0.571564] ACPI: Using IOAPIC for interrupt routing
>> [ 0.631370] ACPI: PCI Root Bridge [PCI0] (0000:00)
>> [ 0.690684] ------------[ cut here ]------------
>> [ 0.745825] kernel BUG at drivers/acpi/osl.c:461!
>
> And acpi keeled over as a result.
>
> Do you have CONFIG_PCI_MULTITHREAD_PROBE=y? If so, try disabling it.
No:
# CONFIG_PCI_MULTITHREAD_PROBE is not set
The config is in:
http://www.cateee.net/kernel/config
and for reference hte kernel log:
http://www.cateee.net/kernel/kern
ciao
cate
next prev parent reply other threads:[~2006-10-31 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 8:23 Panic with 2.6.19-rc3-ga7aacdf9: Invalid opcode at acpi_os_read_pci_configuration Giacomo Catenazzi
2006-10-31 10:18 ` Andrew Morton
2006-10-31 10:29 ` Giacomo A. Catenazzi [this message]
2006-10-31 10:41 ` Andrew Morton
2006-10-31 19:50 ` Giacomo Catenazzi
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=4547257B.7090101@cateee.net \
--to=cate@cateee.net \
--cc=akpm@osdl.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