http://bugzilla.kernel.org/show_bug.cgi?id=8896





------- Comment #29 from [EMAIL PROTECTED]  2007-08-29 01:17 -------
           Device (ALKD)
            {
                Name (_HID, EisaId ("PNP0C0F"))
                Name (_UID, 0x08)
                Method (_PRS, 0, NotSerialized)
                {
                    Name (A47D, ResourceTemplate ()
                    {
                        Interrupt (ResourceConsumer, Level, ActiveLow, Shared,
,, )
                        {
                            0x00000015,
                        }
                    })
                    Return (A47D)
                }

                Method (_STA, 0, NotSerialized)
                {
                    Return (0x0B)
                }

                Method (_DIS, 0, NotSerialized)
                {
                }

                Method (_CRS, 0, NotSerialized)
                {
                    Return (0x00)
                }

                Method (_SRS, 1, NotSerialized)
                {
                }
            }

This is a second BIOS bug on this box.
_CRS for ALKD is indeed not returning a valid resource template.

Is this system running with defaults in BIOS SETUP?
Are there any ACPI or IO-APIC settings in BIOS SETUP?
Does Windows run on this box and do the IRQ settings it uses
show that it is using IOAPIC mode?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to