From: Grover, A. <and...@in...> - 2002-09-19 22:27:08
|
> From: P. Christeas [mailto:p_c...@ho...] > > With ACPI enabled X gets slow. I mean REALLY SLOW! It needs up to 20 > > seconds to start and then consumes as much CPU time as > possible. It's an > > adventure to try to hit something with the mouse pointer. > > Everything is funktioning perfectly without ACPI. > > Perhaps an interrupt problem. ACPI shares an interrupt with > a bttv card. > > The GeForce has it's own interrupt. > Huh! You just mentioned a magic word: bttv. I do have a bt878 > card, I have to > look if that is the problem after all. > > To A. Grover: if the trouble lies in the bttv driver, the > kernel will be > considered broken until both drivers co-exist.. When you cat /proc/interrupts, is there a huge and ever-increasing number of interrupts listed for the shared irq? (Wait, I thought video devices weren't interrupt driven? Or is that only video out, not video-in, like bt878?) My understanding was, when an interrupt is shared, the OS calls *all* the interrupt service routines (ISRs) for devices on that interrupt - it is then up to the ISR to determine whether its device interrupted and handle it, or whether just to return. You might start your investigations by looking at drivers/acpi/events/evsci.c acpi_ev_sci_handler(). Regards -- Andy |