Bug 12250
Summary: | Not using MMCONFIG. Fatal: No config space access function found | ||
---|---|---|---|
Product: | Drivers | Reporter: | OliverR (oliii2007) |
Component: | PCI | Assignee: | Jesse Barnes (jbarnes) |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | acpi-bugzilla, jbarnes, spock |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.25-rc1 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
OliverR
2008-12-18 12:55:32 UTC
How about newer kernels? Does 2.6.27 or .28 work? I tried 2.6.28 last week and that didn't work either... 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... ;) 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? Auto detection works as well. I don't get any of the above mentioned problems. Ok, so this is just a config problem then... Yes, I think it was my fault...thanks for all the help!!! |