I added the 3 lines. Not anymore errors. However there is still "invalid" adresses or links:
ACPI APIC Table: <VIAK8 AWRDACPI> ioapic0 <Version 0.3> irqs 0-23 on motherboard acpi0: <VIAK8 AWRDACPI> on motherboard acpi0: Power Button (fixed) pci_link0: <ACPI PCI Link LNKA> irq 11 on acpi0 pci_link1: <ACPI PCI Link LNKB> irq 5 on acpi0 pci_link2: <ACPI PCI Link LNKC> irq 10 on acpi0 pci_link3: <ACPI PCI Link LNKD> on acpi0 pci_link4: <ACPI PCI Link LNKE> on acpi0 pci_link5: <ACPI PCI Link LNKF> on acpi0 pci_link6: <ACPI PCI Link LNK0> on acpi0 pci_link7: <ACPI PCI Link LNK1> on acpi0 pci_link8: <ACPI PCI Link ALKA> irq 0 on acpi0 pci_link9: <ACPI PCI Link ALKB> irq 0 on acpi0 pci_link10: <ACPI PCI Link ALKC> irq 0 on acpi0 pci_link11: <ACPI PCI Link ALKD> irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: <ACPI CPU> on acpi0 acpi_button0: <Power Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci_link9: BIOS IRQ 11 for -2145777912.16.INTA is invalid pci_link9: BIOS IRQ 5 for -2145777912.16.INTB is invalid pci_link10: BIOS IRQ 10 for -2145777912.17.INTC is invalid pci_link11: BIOS IRQ 11 for -2145777912.18.INTA is invalid pci0: <ACPI PCI bus> on pcib0
full verbose boot dmesg etc are joined.
MP
Attachment:
acpidump-t-d
Description: Binary data
Attachment:
dmesgverbose
Description: Binary data
Attachment:
hw.acpi
Description: Binary data
Le 21 oct. 05 à 15:54, John Baldwin a écrit :
On Friday 21 October 2005 02:38 am, Mathieu Prevot wrote:
I think that the generation of the OS for Amd64 needs to set this define:
#define ACPI_MISALIGNED_TRANSFERS
I will look into doing this automatically in the actypes.h header
To confirm, the same output on the same system but with 6.0RC1i386GENERIC:
I think Robert's point is a patch like the following hack would shut up the
warnings:
Index: actypes.h =================================================================== RCS file: /usr/cvs/src/sys/contrib/dev/acpica/actypes.h,v retrieving revision 1.1.1.29 diff -u -r1.1.1.29 actypes.h --- actypes.h 1 Dec 2004 23:13:39 -0000 1.1.1.29 +++ actypes.h 21 Oct 2005 13:52:22 -0000 @@ -194,6 +194,9 @@ typedef UINT64 ACPI_SIZE;
#define ALIGNED_ADDRESS_BOUNDARY 0x00000008 /* No hardware
alignment support in IA64 */
+#ifdef __amd64__
+#define ACPI_MISALIGNED_TRANSFERS
+#endif
#define ACPI_USE_NATIVE_DIVIDE /* Native 64-bit
integer support */
#define ACPI_MAX_PTR ACPI_UINT64_MAX
#define ACPI_SIZE_MAX ACPI_UINT64_MAX
The problem is that currently the actypes.h header assumes that the only
64-bit platform it runs on is IA-64, but it also runs on amd64 and amd64
allows for unaligned accesses just like i386.
I'm not sure if ALIGNED_ADDRESS_BOUNDARY should be 0x4 for amd64 either,
probably not though.
-- John Baldwin <jhb_(_at_)_FreeBSD_(_dot_)_org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
_______________________________________________ freebsd-acpi_(_at_)_freebsd_(_dot_)_org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe_(_at_)_freebsd_(_dot_)_org"