These are very common errors in many BIOS. In short, BIOS's AML code
tries to access an IO address PMS1 (= 0xA40 + 2). However, AML declares
a region called SWCR as below.
OperationRegion (SWCR, SystemIO, IO2B, IO2L)
Field (SWCR, ByteAcc, NoLock, Preserve)
{
PMES, 1,
Offset (0x01),
PMEN, 1,
Offset (0x02),
PMS1, 8,
...
...
The problem is the length IO2L is declared twice in different scope:
ex. Name (IO2L, 0x40) and CreateByteField (CRS2, \_SB.PCI0.LPCB.SIO1._Y19._MIN,
IO2L). As the later is in closer scope when BIOS AML tries to access it, IO2L =
0 is used instead of IO2L = 0x40. As a result, kernel complains PMS1 is out of
range.
The easy fix for BIOS is to remove the name conflicts. However, BIOS
updates from Dell may be no longer possible. The questions are
therefore:
1. Why is this not caught when BIOS update is still possible?
2. How many impacts are the errors?
Q1 is out of scope. The answer for Q2 is "depends on other function
tests".
_PTS and _WAK are important ACPI methods that run when system is
suspending and resuming, respectively. On this system, there are many
AML code in both _PTS and _WAK. Failing to run either of them may skip
some functions or BIOS workarounds.
Having say that, I do not see any other failures by skipping these two
methods on this particular system, and I would dare to say there is
nothing wrong. This is also the same as the previous systems I have
analyzed the same mis-behaviours.
** Changed in: hwe-next
Status: In Progress => Won't Fix
** Changed in: linux-lts-trusty (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363934
Title:
[Dell Precision T1700] HIGH failures found in suspend log on 12.04.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1363934/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
