> > What happens if you don't include firewire_ohci?
>
> Yeah, deleting firewire_ohci fixed the problem (with "noapic" specified).
>
> > Must you use "noapic"? That can cause IRQ routing problems...
>
> Ok, I retested without "noapic" and, fortunately, everything worked just
> fine.
That is, wi
On Sun, 13 Jan 2008, Modestas Vainius wrote:
> If you are 100% sure that it was not usb-ohci fault (could be firewire_ohci's
> then), then let it be. However, reverting that patch _helped_ for me
> previously (with "noapic"). Hopefully, other people won't get bitten by the
> same problem.
Just
Hello,
2008 m. January 12 d., Saturday, David Brownell rašė:
> What happens if you don't include firewire_ohci?
Yeah, deleting firewire_ohci fixed the problem (with "noapic" specified).
> Must you use "noapic"? That can cause IRQ routing problems...
Ok, I retested without "noapic" and, fortunate
> kernel: irq 11: nobody cared (try booting with the "irqpoll" option)
> kernel: Pid: 1815, comm: modprobe Not tainted 2.6.24-rc7-rt2x00 #16
> kernel:
> kernel: Call Trace:
> kernel:[] __report_bad_irq+0x30/0x72
> kernel: [] note_interrupt+0x22a/0x26b
> kernel: [] handle_level_irq+0xac/0xe7
>
