Jesper Juhl wrote:
>
>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.
>
>
No, I missed that one. The machine works fine with either of those two
options. I sent
On 7/24/05, Jan Engelhardt <[EMAIL PROTECTED]> 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
> >>
>> 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
>> *
On 7/24/05, Pierre Ossman <[EMAIL PROTECTED]> wrote:
> Sorry about reporting this error so late but the machine in question had
> gone some time without upgrades.
>
> The problem I'm seeing is that IRQs stop working for one of the IRQ
> slots on the machine. It's only that slot, not the entire IRQ
Pierre Ossman wrote:
> ** 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 thi
5 matches
Mail list logo
