http://bugzilla.novell.com/show_bug.cgi?id=516818 User trenn@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516818#c1 --- Comment #1 from Thomas Renninger 2009-06-26 06:51:02 MDT --- iasl -sa DSDT.dsl output concerning this warning (happening more than 10 times on this table): DSDT.dsl 1692: Method (_S5D, 0, NotSerialized) Warning 1098 - Unknown reserved name ^ (_S5D) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516818 User trenn@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516818#c3 --- Comment #3 from Thomas Renninger 2009-06-26 09:18:48 MDT --- JFI: I just verified that the warning still appears in latest 20090625 version (some related changes appeared in the changelog, about _SxW functions). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516818 User trenn@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516818#c5 --- Comment #5 from Thomas Renninger 2009-06-29 03:21:54 MDT --- I opened the bug for 2 reasons: - Let Rafael be aware that there are machines which provide _S5D functions, even they are not listed in the specs. I do not know whether they are needed, and I am not sure it makes sense to consider them at all? - ACPICA: Currently using the function in a DSDT table makes iasl compiler complain about the not known _XXX function. All functions starting with _ have to be functions specified in the ACPI spec. I wonder whether this not defined in spec function should be made known to ACPICA to avoid the compiler warning. Eventually a not yet seen S5W function also? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516818 User rjw@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516818#c6 --- Comment #6 from Rafael Wysocki 2009-06-29 17:04:18 MDT --- In principle, since the spec doesn't mention these functions, we shouldn't be expected to use them. It would be nice, though, to check if the other popular OSes use them, if possible. If they do, we can consider adding some code using these functions too. As far as ACPICA is concerned, I'm not sure if it's a good idea to have such a warning in the kernel at all. Perhaps with some special debug output enabled it makes sense, but otherwise I don't think it's even remotely necessary. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516818 User trenn@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516818#c8 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Robert.Moore@intel.com --- Comment #8 from Thomas Renninger 2009-06-30 10:16:11 MDT ---

From acpica mainline bugzilla (I wasn't that smart to create two bugs...):

-- Comment #1 from Bob Moore 2009-06-30 08:37:31 --- It's a BIOS bug, just like using any other undefined reserved name. In this case, it could very well be a serious bug since the intent may have been to use another similar name such as _S4D. Which is really one of the reasons for having the compiler check the reserved names in the first place. -- As said, I do not expect this is sever, but if HP wants to stay spec conform and avoid "fails" with Intel's Linux firmwarekit (and at some day get a SUSE/Novell certification for such BIOSes), they should make sure to not use this function. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516818 User john.brown3@hp.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516818#c10 --- Comment #10 from John Brown 2009-07-06 18:18:46 MDT --- I will check with our BIOS team on this issue and reply back soon. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516818 User trenn@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516818#c12 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #12 from Thomas Renninger 2009-07-14 06:02:43 MDT --- Thanks for clarification John. So this is indeed a BIOS bug (which is not sever). Still you should verify your ACPI tables with Intel's ACPI compiler, to make your ACPI code more robust, spec conform and Linux compatible. This is really easy and a little quick how-to can be found here: ftp://ftp.suse.com/pub/people/trenn/How_to_check_for_ACPI_BIOS_syntax_bugs.txt -> Closing invalid, because we cannot do anything and it's harmless. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.