Bug 12250 - Not using MMCONFIG. Fatal: No config space access function found
Summary: Not using MMCONFIG. Fatal: No config space access function found
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCI (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jesse Barnes
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-18 12:55 UTC by OliverR
Modified: 2009-06-17 06:00 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.25-rc1
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description OliverR 2008-12-18 12:55:32 UTC
Latest working kernel version: 2.6.24-rc8
Earliest failing kernel version: 2.6.25-rc1
Distribution: Gentoo

Problem Description:
Invalid phys_base_ptr is reported by the Video BIOS for all modes.

Further information: http://bugs.gentoo.org/show_bug.cgi?id=233815

git bisect:
b6ce068a1285a24185b01be8a49021827516b3e1 is first bad commit
commit b6ce068a1285a24185b01be8a49021827516b3e1
Author: Matthew Wilcox <matthew@wil.cx>
Date:   Sun Feb 10 09:45:28 2008 -0500

    Change pci_raw_ops to pci_raw_read/write

    We want to allow different implementations of pci_raw_ops for standard
    and extended config space on x86.  Rather than clutter generic code with
    knowledge of this, we make pci_raw_ops private to x86 and use it to
    implement the new raw interface -- raw_pci_read() and raw_pci_write().

    Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

:040000 040000 37d93a98a615234529e980755a88c05cc1a5dfb3
0b0e3a803a908659f9952e872b65a532853bfd42 M      arch
:040000 040000 1fbea4ab6a9f98c4a0930491f9e742c7288b42ed
22d078ce9c816d4b3c738a77ce198118f4a8ab47 M      drivers
:040000 040000 aa7650863cb046eb3f20c63db246739a3dd59403
34603b3c47eb462b0eecaac626d724385ce946f4 M      include


dmesg extract:
###
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 63
PCI: Not using MMCONFIG.
PCI: Fatal: No config space access function found
ACPI: EC: Look up EC in DSDT
ACPI Exception (evregion-0419): AE_ERROR, Returned by Handler for [PCI_Config]
[20080609]
ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.LNKA._STA]
(Node f7816f78), AE_ERROR
ACPI Error (uteval-0232): Method execution failed [\_SB_.PCI0.LNKA._STA] (Node
f7816f78), AE_ERROR
ACPI Exception (evregion-0419): AE_ERROR, Returned by Handler for [PCI_Config]
[20080609]
####
Comment 1 Jesse Barnes 2009-01-27 11:29:59 UTC
How about newer kernels?  Does 2.6.27 or .28 work?
Comment 2 OliverR 2009-01-27 23:45:56 UTC
I tried 2.6.28 last week and that didn't work either...
Comment 3 OliverR 2009-06-16 18:09:54 UTC
Here I have some more information. I got the 2.6.30 kernel running, with framebuffer enabled and the following kernel configuration

CONFIG_PCI_GOBIOS=y
# CONFIG_PCI_GOMMCONFIG is not set

But when I select  

CONFIG_PCI_GOMMCONFIG=y

together with

CONFIG_PM=y
CONFIG_ACPI=y

#Config ACPI automatically sets
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_X86_PM_TIMER=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
CONFIG_PNPACPI=y
###

I get the original error from above.

HOWEVER!!!!

when I disable PM und ACPI (CONFIG_PM is not set) and still use

CONFIG_PCI_GOMMCONFIG=y

I get a kernel panic saying something like, 

Pid: 1, comm: swapper Not tainted 2.6.30 #2 .... Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block...

Anyway, now I have the new kernel running... ;)
Comment 4 Jesse Barnes 2009-06-16 18:13:15 UTC
So if mmconfig is rejected on your machine and that's the only PCI config space method you have enabled, your machine probably won't work.

Do you see the bug when you enable PCI config space access auto detection?
Comment 5 OliverR 2009-06-16 18:50:41 UTC
Auto detection works as well. I don't get any of the above mentioned problems.
Comment 6 Jesse Barnes 2009-06-16 18:58:45 UTC
Ok, so this is just a config problem then...
Comment 7 OliverR 2009-06-17 06:00:48 UTC
Yes, I think it was my fault...thanks for all the help!!!

Note You need to log in before you can comment on or make changes to this bug.