From: Andi Kleen <ak@suse.de>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.18-git] Lost all PCI devices
Date: Sun, 1 Oct 2006 00:13:01 +0200 [thread overview]
Message-ID: <200610010013.01390.ak@suse.de> (raw)
In-Reply-To: <20060930220600.GA19990@dreamland.darkstar.lan>
> "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
next prev parent reply other threads:[~2006-09-30 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 17:42 [2.6.18-git] Lost all PCI devices Luca Tettamanti
2006-09-30 18:11 ` Andi Kleen
2006-09-30 20:22 ` Luca Tettamanti
2006-09-30 20:34 ` Andi Kleen
2006-09-30 22:06 ` Luca Tettamanti
2006-09-30 22:13 ` Andi Kleen [this message]
2006-10-01 15:46 ` Luca Tettamanti
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=200610010013.01390.ak@suse.de \
--to=ak@suse.de \
--cc=kronos.it@gmail.com \
--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