linux-kernel - Re: Panic with 2.6.19-rc3-ga7aacdf9: Invalid opcode at acpi_os_read_pci

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Oct 2006 02:18:10 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Giacomo Catenazzi <cate@...eee.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Panic with 2.6.19-rc3-ga7aacdf9: Invalid opcode at
 acpi_os_read_pci_configuration

On Tue, 31 Oct 2006 09:23:44 +0100
Giacomo Catenazzi <cate@...eee.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.

-
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/