From: P. C. <p_c...@ho...> - 2002-09-22 13:17:32
|
> > 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.. > > > Jochen > > > > > > I have tried the 2.4.20-pre7 + acpi-20020918 patch on a single Athlon > > > > XP 1.7+, VIA VT8637 KT266 chipset. The system boots and displays some > > > > ACPI info that looks fine. > > > > However, the proprietary NVidia video driver (I have a Geforce 2 MX > > > > card and the newest 1.0.3123 proprietary driver) fails to start the X > > > > system. I strongly suspect (although I don't have enough debug info > > > > yet) that the acpi patch is the one that makes NVidia fail. The > > > > 2.4.19 worked until the acpi patch was applied to it. > > > > > > Ducrot Bruno: > > > I suspect an interrupt trouble. Could you 'lspci -xxx -vvv' the device > > > with and without acpi? > > Please hold a bit as the system in question is my 'stable' one and I don't > want to debug it too often. I will certainly do that, but it may take a > couple of days. > > I managed to do some initial tests to that machine. The raw conclusion is that the machine runs (including NVidia-X) when the pci=noacpi is set. The fact that there is a way (pci=noacpi) to let the NVidia users upgrade to 2.4.20+acpi means that there is no reason not to merge the ACPI patch anymore. There is definitely some trouble when ACPI sets the irq's for PCI. As seen in the attached files, ACPI maps the nvidia to irq 11 (instead of 10 as in noacpi), where other cards are mapped to, also. The bttv card does work, even with ACPI. Thus, the problem lies in the NVidia driver. It's their call now to fix that. We shall notify them. One more point is that the 'stable' configuration cannot sleep. Is that normal, since the "pci=notacpi" is set? When I 'echo [1|4] > /proc/acpi/sleep' the speaker beeps, nothing gets logged and nothing happens. Here's the tests: I booted 2.4.20-pre7 + acpi 20020918, runlevel 3 (with ACPI irq) -->"irq-noX.log", "pci-noX.log" I ran a tv prog (to a remote display, still no X server on the system). The bttv was used and I could watch to tv. -->"irq-noX.2.log" I re-booted the same (with ACPI irq), runlevel 5. The kernel was alive, X was frozen. This is when the system is in trouble: --> "irq.log", "pci.log" I re-booted w/o acpi (pci=noacpi), runlevel 5 System was up, with X running OK --> "irq-noacpi.log", "pci-noacpi.log" I started the bttv, watched tv --> "irq-noacpi.2.log" Please ask any more question you want. |