Messages in this thread | | | Subject | RE: ACPI 100002 IRQ 9 problem. | Date | Wed, 25 Jun 2003 10:20:15 -0700 | From | "Grover, Andrew" <> |
| |
> From: Joshua Schmidlkofer [mailto:menion@asylumwear.com] > First is there a different list for ACPI questions?
From MAINTAINERS:
ACPI P: Andy Grover M: andrew.grover@intel.com L: acpi-devel@lists.sourceforge.net W: http://sf.net/projects/acpi/ S: Maintained
> For the sake of disclosure, the dump I am reporting is 2.5.73, plus > the Davide Libenzis' SiS-96x patch. I also am currently using the > nvidia driver, I was able to reproduce this in vanilla 2.5.72 (no > nvidia), and I will try tomorrow with a vanilla setup of 2.5.73-bk3. > [unless bk4 is available]. > > I have a Soyo P4S-645D, with the SiS 645 chipset. I have had some > problems w/ the IRQ routing, but 2.5.7[123] have sorted it > out (mostly) > I am having problems ACPI, it is better if I say > 'pci=noacpi', but what > happens is when the ACPI interrupt count hit 100002, then I get the > following message on all consoles: > > menion kernel: Disabling IRQ #9 > > Then, I have the following as part of dmesg: > > Call Trace: [<c010cad4>] [<c010cbad>] [<c010ce46>] [<c010880e>] > [<c010880e>] [<c010b320>] [<c010880e>] [<c010880e>] [<c0108832>] > [<c010889a>] [<c0105000>] [<c041c6bd>] [<c041c41e>] > [<c0247446>] > Warning (Oops_read): Code line not seen, dumping what data is > available
There is a known, as-yet-unfixed problem, but the usual symptom is you hit 100000 interrupts and then it gets nicely disabled - I'm not sure why your system oopses.
Regards -- Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |