Re: [acpi-jp 3129] ACPI (_PRS has invalid type 7) problem / regression

On Mon, 22 Mar 2004 12:09:46 -0800 (PST)
Nate Lawson <nate_at_root.org> wrote:

> On Mon, 22 Mar 2004, Ion-Mihai Tetcu wrote:
> > On Mon, 22 Mar 2004 11:33:36 -0800 (PST)
> > Nate Lawson <nate_at_root.org> wrote:
> > > > The change must have happen between 2004_03_04 and 2004_03_18.
> > >
> > > I don't think it was the _PRS changes on 3/18 and 3/20.  I'm suspecting
> > > the ACPI-CA import of 0311.  You can revert all changes to acpi_pcib.c by
> > > copying this file over sys/dev/acpica/acpi_pcib.c and recompiling your
> > > kernel:
> > >
> > > http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/acpica/acpi_pcib.c?rev=1.36&content-type=text/plain
> > >
> > > I suspect it won't change anything for you but please test this to be
> > > sure.
> >
> > I'm doing it right now, thank you.
> > (Recompiling the acpi.ko wouldn't be enough ?)
> 
> Yes, recompiling just the acpi kernel module would be fine.

Done. It's OK now, thanks.

> > > Your ASL returns a different interrupt link resource based on an external
> > > variable DEID.  It may be thinking it's in PIC mode and returning the IRQ
> > > resource instead of APIC mode and the Interrupt resource.  See the section
> > > for ALKC to see what I'm talking about.
> >
> > Where do I find this section ?
> 
> Device (ALKC) in your ASL.
> 
> One other thing you might try if reverting acpi_pcib.c doesn't help is to
> set hw.acpi.serialize_method=0 at the loader prompt.  If that doesn't
> work, set hw.acpi.osi_name=0 at the prompt.  Then try both.

Makes no difference, both for the old (non-working) and new (patched,
working).
The dmesg's can be found at http://people.tecnik93.com/acpi/
dmesg_new_o_n=0 means old (sic!) kernel with hw.acpi.osi_name=0
dmesg_good_s_m=0 means patched kernel with hw.acpi.serialize_method=0
etc.

What should I do next to help ?


-- 
IOnut
Unregistered ;) FreeBSD user