https://bugzilla.novell.com/show_bug.cgi?id=558740 https://bugzilla.novell.com/show_bug.cgi?id=558740#c78 Angela Bayley <amb@jb.man.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|amb@jb.man.ac.uk | --- Comment #78 from Angela Bayley <amb@jb.man.ac.uk> 2011-01-11 16:01:12 UTC --- (In reply to comment #77)
(In reply to comment #75)
We have to disable ACPI in order for VME interrupts to work!
Hmm, that seems like an overkill. What's the problem exactly? Is there a bug entry somewhere?
(In reply to comment #76)
output from hexdump -Cv /sys/bus/pci/devices/0000\:00\:1f.0/config
Hmm, ACPI_EN is 1 which means enabled but it shouldn't when ACPI is off -- is ACPI off in BIOS or only in the kernel?
I can certainly file a bug for the interference of ACPI with VME interrupts. The reason I haven't is because it is hard to provide sufficient evidence without assuming a knowledge of the Tundra VME-PCI Bridge chip. Please note that for the XYCOM XVME-6200 processor http://www.xembedded.com/content/vme/processors/xvme-6200.php we have also to disable APIC in addition to ACPI in order for VME interrupts to be received. We disable ACPI/APIC both in the BIOS and in the kernel ("belt and braces"). It doesn't matter which method we use, either or both produces the required state - VME interrupts are received correctly. If APIC/ACPI are enabled both in the BIOS and in the kernel, VME interrupts, generated correctly by the VME bridge chip are lost and not received by the processor. I believe this is due to a software fault in the Linux kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.