linux-kernel - Re: [2.6.18-git] Lost all PCI devices

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]

Message-Id: <200610010013.01390.ak@suse.de>
Date:	Sun, 1 Oct 2006 00:13:01 +0200
From:	Andi Kleen <ak@...e.de>
To:	Luca Tettamanti <kronos.it@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [2.6.18-git] Lost all PCI devices


> "pci_direct_probe conf*" printk are placed before calling into
> pci_check_type{1,2}, it doesn't call pci_sanity_check so it's the I/O
> check that fails.
> I can do further debugging if you're interested.

No I was just curious. It's strange that your system doesn't work without 
PCI BIOS though. Is it an older laptop? The assumption so far
was that everything modern can do type 1 without problems (except 
one broken Apple system). Apparently that's not universally true.

> ACPI: Access to PCI configuration space unavailable
> ACPI: Interpreter enabled
> ACPI: Using PIC for interrupt routing
> ------------[ cut here ]------------
> Kernel BUG at [verbose debug info unavailable]
> invalid opcode: 0000 [#1]
> PREEMPT
> CPU:    0
> EIP:    0060:[<c0233103>]    Not tainted VLI
> EFLAGS: 00010246   (2.6.18-g5ffd1a6a-dirty #20)
> EIP is at acpi_os_read_pci_configuration+0x4f/0x87

The patch I posted should have fixed that.

Although I think it might be better to do panic() instead of printk.

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