Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Oct 2005 17:56:46 -0700
From:      Nate Lawson <nate@root.org>
To:        Jung-uk Kim <jkim@FreeBSD.org>
Cc:        freebsd-acpi@FreeBSD.org, Mathieu Prevot <mathieu_prevot@yahoo.fr>
Subject:   Re: ACPI errors on amd64 (sempron)
Message-ID:  <4361774E.3010709@root.org>
In-Reply-To: <200510272029.48815.jkim@FreeBSD.org>
References:  <971FCB6690CD0E4898387DBF7552B90E0323D7B6@orsmsx403.amr.corp.intel.com> <200510271744.17558.jkim@FreeBSD.org> <43616BFF.1040709@root.org> <200510272029.48815.jkim@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Jung-uk Kim wrote:
> On Thursday 27 October 2005 08:08 pm, Nate Lawson wrote:
> 
>>Jung-uk Kim wrote:
>>
>>>It's already fixed in (soon to be imported) ACPICA-20051021 code.
>>
>>There's no way we can get acpi-ca tested in -current and MFC'd
>>before 6.0.  Instead, we should MFC just the logic Intel changed in
>>the header file to 6.0.
> 
> 
> IMHO, I think there's not enough time to do any fix at this point.  I 
> think we should fix it *after* 6.0-RELEASE because it only fixes half 
> of his problem.

I disagree.  It's very clear what the alignment requirements are on 
amd64 and that acpi-ca is being too strict, harming an actual 
implementation.

> In fact, I have seen somebody else had similar problem:
> 
> http://bsdforum.or.kr/viewtopic.php?p=5414#5414
> 
> It's Korean BSD User Forum but you may be able to read this:
> 
> pci_link26: BIOS IRQ 10 for -2145771032.1.INTA is invalid
> pci_link21: BIOS IRQ 11 for -2145771032.2.INTA is invalid
> pci_link27: BIOS IRQ 3 for -2145771032.2.INTB is invalid
> pci_link23: BIOS IRQ 10 for -2145771032.10.INTA is invalid
> pci_link24: BIOS IRQ 11 for -2145771032.4.INTA is invalid
> pci_link29: BIOS IRQ 11 for -2145771032.7.INTA is invalid
> pci_link30: BIOS IRQ 10 for -2145771032.8.INTA is invalid

Yes, I agree that this alone doesn't fix it.  This looks to me like the 
pci_link code is pointing the interrupt source at the wrong part of the 
resource descriptor.  Perhaps it is not incrementing the pointer 
correctly for 64-bit arches.

-- 
Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4361774E.3010709>