Re: IRQ routing problem in 2.6.10-rc2

2005-07-24 Thread Pierre Ossman
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

Re: IRQ routing problem in 2.6.10-rc2

2005-07-24 Thread Jesper Juhl
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 > >>

Re: IRQ routing problem in 2.6.10-rc2

2005-07-24 Thread Jan Engelhardt
>> 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 >> *

Re: IRQ routing problem in 2.6.10-rc2

2005-07-24 Thread Jesper Juhl
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

Re: IRQ routing problem in 2.6.10-rc2

2005-07-24 Thread Pierre Ossman
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

Re: IRQ routing problem

2005-07-04 Thread Alexey Dobriyan
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 yo

RE: IRQ routing problem

2005-07-04 Thread Protasevich, Natalie
> 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

Re: IRQ (routing ?) problem [was Re: epic100 in current -ac kernels]

2001-02-26 Thread Arnd Bergmann
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 f

Re: IRQ (routing ?) problem [was Re: epic100 in current -ac kernels]

2001-02-15 Thread ARND BERGMANN
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