Bug 10745
Summary: | PCI: resource allocation failures | ||
---|---|---|---|
Product: | Drivers | Reporter: | Jon Daniel (jopadan) |
Component: | PCI | Assignee: | Jesse Barnes (jbarnes) |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | alan, bjorn.helgaas, jopadan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.26-rc2 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg
lspci -v /proc/iomem /proc/interrupts |
Description
Jon Daniel
2008-05-18 11:49:32 UTC
Created attachment 16184 [details]
dmesg
Created attachment 16185 [details]
lspci -v
Is this a regression? Is the orinoco card known to be working, i.e., it's not just a broken card? I can't tell whether the orinoco problem is related to the cardbus mem resource allocation problem. You might be able to learn something by instrumenting hermes_init() to see where and why it returns -ENODEV. Please attach the /proc/iomem and /proc/interrupts contents. Created attachment 16193 [details]
/proc/iomem
Created attachment 16194 [details]
/proc/interrupts
I don't think this is a regression it seems to be around for some time I just plugged in new hardware and it popped up. I have to check if it also occurs without the voodoo 5. Maybe the orinoco card isn't working at all but I think the problem is related to the error message above because there are posts of other people around with the same problem. I've updated to 2.6.26-rc3 and removed the Voodoo 5 card and plugged some otherones in now the orinoco firmware bug is gone and I only get one: PCI: region 0000:01:08.0/9 too large: 0x0000000000000000-0x0000000003ffffff PCI: Failed to allocate mem resource #10:4000000@fc000000 for 0000:01:08.0 I still have to try it with the voodoo 5 again. IIRC TJ is working on some resource allocation changes that may help with stuff like this. I'll ping him... FYI, TJ wrote up some nice documentation on a new PCI resource allocation scheme he's been working on, maybe you could try out his stuff to see if it works for you? http://tjworld.net/wiki/Linux/PCIDynamicResourceAllocationManagement Is this one dead Jesse ? Looks like it. There's a bunch of new resource code about to land that could address this anyway (if it's not already fixed). I'll close it out. |