Bug 469159
Summary: | Warning during XO boot: Invalid iomem size. You may experince problems | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jiri Pechanec <jpechane> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | jeffrey.atkinson, kernel-maint, pierre-bugzilla, quintela |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-11-13 16:09:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 461806 |
Description
Jiri Pechanec
2008-10-30 11:06:31 UTC
This is also present in the base OLPC kernel and doesn't seem to cause any problems. I wonder if we should just drop it from being an error to being lower priority (warning or debug). The length of the bar on the olpc is longer than expected which really seems like it shouldn't be an error case. Something like diff --git a/drivers/mmc/host/sdhci-pci.c b/drivers/mmc/host/sdhci-pci.c index 9bd7026..b0dce16 100644 --- a/drivers/mmc/host/sdhci-pci.c +++ b/drivers/mmc/host/sdhci-pci.c @@ -506,7 +506,7 @@ static struct sdhci_pci_slot * __devinit sdhci_pci_probe_slot( } if (pci_resource_len(pdev, bar) != 0x100) { - dev_err(&pdev->dev, "Invalid iomem size. You may " + pr_debug(&pdev->dev, "Invalid iomem size. You may " "experience problems.\n"); } Pierre -- do you have any ideas here? Things are definitely working fine, the warning during boot just isn't pretty. You can remove the warning for OLPC kernels (where it has been verified to be ok), but in the general case it should stay. It should probably be downgraded to a dev_warn() though. |