Commit f6d440da authored by Bjorn Helgaas's avatar Bjorn Helgaas Committed by Jesse Barnes

PCI: change resource collision messages from KERN_ERR to KERN_INFO

We can often deal with PCI resource issues by moving devices around.  In
that case, there's no point in alarming the user with messages like these.
There are many bug reports where the message itself is the only problem,
e.g., https://bugs.launchpad.net/ubuntu/+source/linux/+bug/413419 .
Signed-off-by: default avatarBjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: default avatarJesse Barnes <jbarnes@virtuousgeek.org>
parent 9dda696f
...@@ -97,16 +97,16 @@ int pci_claim_resource(struct pci_dev *dev, int resource) ...@@ -97,16 +97,16 @@ int pci_claim_resource(struct pci_dev *dev, int resource)
root = pci_find_parent_resource(dev, res); root = pci_find_parent_resource(dev, res);
if (!root) { if (!root) {
dev_err(&dev->dev, "no compatible bridge window for %pR\n", dev_info(&dev->dev, "no compatible bridge window for %pR\n",
res); res);
return -EINVAL; return -EINVAL;
} }
conflict = request_resource_conflict(root, res); conflict = request_resource_conflict(root, res);
if (conflict) { if (conflict) {
dev_err(&dev->dev, dev_info(&dev->dev,
"address space collision: %pR conflicts with %s %pR\n", "address space collision: %pR conflicts with %s %pR\n",
res, conflict->name, conflict); res, conflict->name, conflict);
return -EBUSY; return -EBUSY;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment