On Fri, Jan 06, 2017 at 07:35:03PM -0500, James Hastings wrote:
> > acpivideo0: unknown event 0xd0
> > Unsupported RegionSpace 0x5
> > 9630 Called: \\_SB_.WMID.ESDT
> > 96af Called: \\_SB_.WMID.ESDT
> > e755 Called: \\_SB_.PCI0.LPC0.EC0_._Q42
> > panic: aml_die aml_rwfield:2478
>
> RegionSpace 0x5 is defined as ACPI_OPREG_CMOS.
>
> Should this case be caught and ignored?
>
> Index: dev/acpi/dsdt.c
> ===================================================================
> RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
> retrieving revision 1.228
> diff -u -p -r1.228 dsdt.c
> --- dev/acpi/dsdt.c 18 Dec 2016 15:59:22 -0000 1.228
> +++ dev/acpi/dsdt.c 6 Jan 2017 21:55:12 -0000
> @@ -2473,6 +2473,8 @@ aml_rwfield(struct aml_value *fld, int b
> aml_rwgas(ref1, fld->v_field.bitpos + bpos, blen,
> val, mode, fld->v_field.flags);
> break;
> + case ACPI_OPREG_CMOS:
> + break;
> default:
> aml_die("Unsupported RegionSpace 0x%x",
> ref1->v_opregion.iospace);
>
os needs to implement the functionality for acpi ospm to work correctly.
newer hp laptops have BIOSes that updates rtc date/time registers via
ACPI.
if you just ignore this request kernel will stop crashing but clock will
have undefined behavior when you shutdown or (unsuccessfully)
suspend/resume.
