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
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
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
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 this
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,
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.
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
** workaround,
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 a
On Sunday 03 July 2005 15:16, Marko Kohtala wrote:
> irq 20: nobody cared (try booting with the "irqpoll" option)
I've filed a bug at kernel bugzilla so your report won't be lost.
See http://bugme.osdl.org/show_bug.cgi?id=4843
You can register at http://bugme.osdl.org/createaccount.cgi and add
> I've been having interrupt problems. 2.6.12 worked fine, but
> soon after it got broken and was still broken just now that I
> checked git version.
>
> Interrupts get somehow misrouted.
>
> Here is a part from the syslog showing the problem:
>
> Jul 3 13:17:09 kohtala kernel: USB Universal
I've been having interrupt problems. 2.6.12 worked fine, but
soon after it got broken and was still broken just now that I
checked git version.
Interrupts get somehow misrouted.
Here is a part from the syslog showing the problem:
Jul 3 13:17:09 kohtala kernel: USB Universal Host
On Sunday 03 July 2005 15:16, Marko Kohtala wrote:
irq 20: nobody cared (try booting with the irqpoll option)
I've filed a bug at kernel bugzilla so your report won't be lost.
See http://bugme.osdl.org/show_bug.cgi?id=4843
You can register at http://bugme.osdl.org/createaccount.cgi and add
I noticed that there have been updates to epic100 again and just wanted
to note that the problem remains:
2.4.2-ac3 still crashes, but it works fine when I use the epic100.c
from 2.4.0-test9, which was the last working version for me.
Arnd <><
On Thu, 15 Feb 2001, ARND BERGMANN wrote:
> Sorry
I noticed that there have been updates to epic100 again and just wanted
to note that the problem remains:
2.4.2-ac3 still crashes, but it works fine when I use the epic100.c
from 2.4.0-test9, which was the last working version for me.
Arnd
On Thu, 15 Feb 2001, ARND BERGMANN wrote:
Sorry for
Sorry for the delay, I could not get physical access to the machine
for the last days.
I was able to do some more testing today and found this:
- The problem is not the IRQ /sharing/, after getting rid of all the
other PCI cards, the problem was still there.
- The only thing that seems to have
Sorry for the delay, I could not get physical access to the machine
for the last days.
I was able to do some more testing today and found this:
- The problem is not the IRQ /sharing/, after getting rid of all the
other PCI cards, the problem was still there.
- The only thing that seems to have
18 matches
Mail list logo
