[lkml]   [2005]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: IRQ routing problem in 2.6.10-rc2
On 7/24/05, Jan Engelhardt <> wrote:
> >> PCI: Using ACPI for IRQ routing
> >> ** PCI interrupts are no longer routed automatically. If this
> >> ** causes a device to stop working, it is probably because the
> >> ** driver failed to call pci_enable_device(). As a temporary
> >> ** workaround, the "pci=routeirq" argument restores the old
> >> ** behavior. If this argument makes the device work again,
> >> ** please email the output of "lspci" to
> >> ** so I can fix the driver.
> >Have you tried the suggestion given "... As a temporary workaround,
> >the "pci=routeirq" argument..." ?
> >You could also try the pci=noacpi boot option to see if that changes anything.
> Hi,
> and what's the proper fix for pci=routeirq? I got a driver that is only
> maintained by myself and would like to fix up the issue.
While I don't /know/ exactely what the proper fix is I'll venture a
guess based on the information in the text above : The driver probably
doesn't call pci_enable_device().
Quoting the message at bootup time "If this causes a device to stop
working, it is probably because the driver failed to call
Also, the Kernel Janitors TODO list
( has this to say about
pci_enable_device() :
- ALL PCI drivers should call pci_enable_device --before-- reading
pdev->irq or pdev->resource[]. irq and resource[] may not have correct
values until after PCI hotplug setup occurs at pci_enable_device()
time. Many PCI drivers need to be evaluated and checked for this.

Jesper Juhl <>
Don't top-post
Plain text mails only, please
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-07-24 18:14    [W:0.024 / U:45.524 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site