Greg, Has something changed in the PCI code in the Linux-next tree - 2.6.39-rc1-12 with regards to irq allocation? Earlier (a few weeks ago), the vmbus driver would get the irq allocated as part of it being now a pci driver. Currently, however the system is setting pdev->irq to 0 and needless to say, request_irq() is failing. Thanks, K. Y -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20110412/61b2e432/attachment.htm
On Tue, Apr 12, 2011 at 11:57:22PM +0000, KY Srinivasan wrote:> Greg, > > > > Has something changed in the PCI code in the Linux-next tree ? 2.6.39-rc1-12 > with > > regards to irq allocation? Earlier (a few weeks ago), the vmbus driver would > get the irq allocated as part > > of it being now a pci driver. Currently, however the system is setting pdev-> > irq to > > 0 and needless to say, request_irq() is failing.{sigh} Please fix your email client... Anyway, I have no idea, please use 'git bisect' to track down the problem commit that causes this. thanks, greg k-h
Maybe Matching Threads
- irq allocation for pci drivers
- [PATCH]: Staging: hv: Allocate the vmbus irq dynamically
- [PATCH]: Staging: hv: Allocate the vmbus irq dynamically
- [PATCH ]:Staging: hv: Allocate the vmbus irq dynamically
- [PATCH ]:Staging: hv: Allocate the vmbus irq dynamically