location
EFI_VARIABLE_NON_VOLATILE | EFI_VARIABLE_BOOTSERVICE_ACCESS |
EFI_VARIABLE_RUNTIME_ACCESS attribute and used size.
** Affects: fwts (Ubuntu)
Importance: Undecided
Assignee: Ivan Hu (ivan.hu)
Status: New
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) = Ivan Hu
Patch has been sent and acked,
http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=2e1338ddf7df09de06c66a9fed5f42f726c863b5
It will be contained in the next release 13.07.00.
** Changed in: fwts (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you
Get log with grub, set debug=all
and it stop at ,
...
loader/i386/efi/linux.c:60: Locating shim protocol
loader/i386/efi/linux.c:69: Asking shim to verify kernel signature
_
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
for the _Q33 - no CMOS handler.
The issue is the same as the bug#1143312,
Upstream has a patch to fix this issue. This shall be included in kernel 3.11,
The patch will be backported to 3.9+ kernel and will be included in ubuntu
13.10,
please refer to,
For the no handler issue,
The issue is the same as the bug#1143312,
Upstream has a patch to fix this issue. This shall be included in kernel 3.11,
The patch will be backported to 3.9+ kernel and will be included in ubuntu
13.10,
please refer to,
The _WAK error,
s4: HIGH Kernel message: [322397.358723] ACPI Error: Field [PMS1] access width
(1 bytes) too large for region [SWCR] (length 0) (20121018/exfldio-195)
s4: HIGH Kernel message: [322397.358724] ACPI Error: Field [PMS1]
Base+Offset+Width 2+0+1 is beyond end of region [SWCR]
s4: HIGH Kernel message: [322397.481202] ACPI Error: Field [DRQL] at 144
exceeds Buffer [NULL] size 128 (bits) (20121018/dsopcode-236)
s4: HIGH Kernel message: [322397.481205] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.LPCB.SIO1.DSRS] (Node 880427c4e7a8), AE_AML_BUFFER_LIMIT
*** This bug is a duplicate of bug 1232975 ***
https://bugs.launchpad.net/bugs/1232975
the same bug as #1232975
** This bug has been marked a duplicate of bug 1232975
[Dell Optiplex 9020] High kernel failures in suspend / hibernate log.
--
You received this bug notification because you
The same root cause with bug#1243493,
please refer to,
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1243493/comments/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234905
Title:
The error,
klog: HIGH Kernel message: [ 0.240390] [Firmware Bug]: ACPI: No _BQC method,
cannot determine initial brightness
due to the kernel cannot find the ACPI _BQC method provided by firmware.
and the kernel log info,
klog: HIGH Kernel message: [ 0.286778] pnp 00:05: [Firmware Bug]: [mem
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148649
Title:
HP Pavilion G7 - FWTS HIGH errors during suspend/resume and
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1151664
Title:
HP Pavilion g7 - FWTS failures when doing cert testing
To
The Patch, ACPI / EC: Restart transaction even when the IBF flag set, which
fixed AE_TIME issue has been upstreamed.
available in upstream v3.10-rc2.
commit ID 28fe5c825f8e15744d04c7c1b8df197950923ecd
also available in
Ubuntu-3.2.0-47.72
commit ID e26bc00134a1b56a6d0d5cb58459a90f8982ee74
It seems that the linux headers don't be installed.
Please install the linux-headers by
sudo apt-get install linux-headers-`iname -r`*
and build again.
** Changed in: fwts (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The Patch, ACPI / EC: Restart transaction even when the IBF flag set, which
fixed AE_TIME issue has been upstreamed.
available in upstream v3.10-rc2.
commit ID 28fe5c825f8e15744d04c7c1b8df197950923ecd
also available in
Ubuntu-3.2.0-47.72
commit ID e26bc00134a1b56a6d0d5cb58459a90f8982ee74
Checking with the testing log, the all high fails comes from the
firmware DMI/SMBIOS tables, DMIValueOutOfRange issues.
FAILED [HIGH] DMIValueOutOfRange: Test 1, Out of range value 0x00 (range
allowed 0x01..0x0b) while
accessing entry 'Voltage Probe (Type 26)' @ 0x000eb93c, field 'Location (bits
Please try to set Bios default, and make sure the Ubuntu UEFI boot entry is
deleted. And install the Ubuntu again.
If you install in Legacy PXE boot mode, the Ubuntu UEFI boot entry won't be
created, only boot from legacy mode.
If you install in the UEFI mode, the Ubuntu UEFI boot entry will be
It seems the same issue with #1143312
Please refer to the comments,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1143312/comments/27
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1143312/comments/28
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: acpid (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168332
Title:
HP ENVY 6 Sleekbook - ACPI errors during suspend
To manage notifications
Please run:
sudo acpidump acpidump.log
and attach the log to the bug for further investigation. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175475
Title:
fwts_test reports Critical
From Acpitable, seems the problem caused by the wmi method WMAA invoke when
S3, S4
Method (WMAA, 3, Serialized)
{
Return (HWMC (Arg1, Arg2))
}
Method (HWMC, 2, NotSerialized)
{
CreateDWordField (Arg1, Zero, SGIN)
It seems the same issue #1152484, please see my comment,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152484/comments/8
and also the comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152484/comments/12
--
You received this bug notification because you are a member of Ubuntu
It seems the same issue with #1148649
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1151664
Title:
HP Pavilion g7 - FWTS failures when doing cert testing
To manage notifications about this bug go
The fail,
FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string index 0x06
while accessing entry
'Portable Battery (Type 22)' @ 0x000e4bf6, field 'Device Chemistry', offset 0x09
ADVICE: DMI strings are stored in a manner that uses a special index to fetch
the Nth string from
the
Seems the same with Bug #1082272
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131449
Title:
[Lenovo k29]: ACPI AML intepreter has found some non-conforming AML
code
To manage notifications
In this case the BIOS assigns both offsets for MCE (0xf9) and IBS
(0x400) vectors to offset 0, which is why the second APIC setup (IBS)
failed.
According to AMD spec, AMD64 Architecture Programmer’s Manual Volume 2,
the IBS seems a software debug and performance monitor facility. Since
the S3
The pattern for klog database for was added on FWTS,
http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=f2297da6d04942199242b93742e4ec6f3c9513a3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
double check the battery key on the user guide,
there is no battery key.
** Attachment added: l430_l530_ug_en.pdf
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068754/+attachment/3597831/+files/l430_l530_ug_en.pdf
** Changed in: linux (Ubuntu)
Assignee: Ivan Hu (ivan.hu
** Changed in: linux-lts-raring (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253871
Title:
[Dell Inspiron 5437] HIGH failure: FADTPM1AInvalidWidth,
Checking the FADT table from acpidump,
seems the table is correct.
[0ACh 0172 12] PM1A Control Block : Generic Address Structure
[0ACh 0172 1] Space ID : 01 (SystemIO)
[0ADh 0173 1]Bit Width : 10
[0AEh 0174 1] Bit Offset : 00
The error is from the BIOS that contain two FADT tables, one comes from the
RSDT and the other comes from the XSDT. The FADT table from the RSDT is
uncompleted/wrong.
The FWTS FADT test happens to check the uncompleted/wrong one.
From the ACPI spec, An ACPI-compatible OS must use the XSDT if
The same acpica issue as bug#1253942, that causes false-alarm failures,
will keep following with Intel
https://bugs.acpica.org/show_bug.cgi?id=1062
please refer to,
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1253942/comments/3
attached the fwts result log, with the above
Base on the fwts log on the comment#3
there are 3 critical failures that come from buggy firmware,
method: Detected error 'Not found' when evaluating
'\_SB_.PCI0.RP05.PEGP.DD02._BCL'.
method: Detected error 'Not found' when evaluating
'\_SB_.PCI0.RP05.PEGP.DD02._BCM'.
method: Detected error
and high failures from comment3,
method: Detected error 'No return value' when evaluating
'\_SB_.PCI0.XHC_.RHUB.HS10._PLD'.
method: Detected error 'No return value' when evaluating
'\_SB_.PCI0.XHC_.RHUB.HS11._PLD'.
method: Detected error 'No return value' when evaluating
some high and critical failures from the fwts log on the comment#3,
Critical failures: 3
method: Detected error 'Not found' when evaluating
'\_SB_.PCI0.RP05.PEGP.DD02._BCL'.
method: Detected error 'Not found' when evaluating
'\_SB_.PCI0.RP05.PEGP.DD02._BCM'.
method: Detected error 'Not
Base on the fwts log on the comment#2,
There are some critical/high failures that from the buggy firmware.
Critical failures: 2
method: Detected error 'Type' when evaluating '\_SB_.PCI0.LPCB.H_EC.BAT0._PCL'.
method: Detected error 'Type' when evaluating '\_SB_.ADP1._PCL'.
are due the return
** Changed in: linux-lts-raring (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253942
Title:
[Dell Inspiron 3737] Multiple CRITICAL failures found in fwts
Patch sent to fwts-devel mailing list:
https://lists.ubuntu.com/archives/fwts-devel/2013-December/004105.html
** Changed in: linux-lts-raring (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch included in,
Firmware Test Suite 13.12.00
** Changed in: linux-lts-raring (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253871
Title:
** Changed in: linux-lts-raring (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255843
Title:
[Lenovo V480] Multiple CRITICAL/HIGH failures in the fwts
from comment#5 set it Fix Released
** Changed in: acpi (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191691
Title:
[Dell Latitude E6330] Many ACPI
the failures,
klog: HIGH Kernel message: [ 13.551401] ACPI Error: [\_SB_.PCI0.GFX0.DD02._BCL]
Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
klog: HIGH Kernel message: [ 13.551407] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.PEG0.PEGP.DD02._BCL] (Node 880159209cd0),
the _PRT failures,
klog: CRITICAL Kernel message: [ 5.345517] ACPI Exception: AE_NOT_FOUND,
Evaluating _PRT [AE_NOT_FOUND] (20121018/pci_irq-269)
klog: HIGH Kernel message: [ 5.345505] ACPI Error: [AR02] Namespace lookup
failure, AE_NOT_FOUND (20121018/psargs-359)
klog: HIGH Kernel message:
and the UUID failure,
\_SB_.PCI0:_OSC invalid UUID
seems that the NEXP equal to 0, that cause firmware report invalid UUID, need
firmware to check.
If (LAnd (LEqual (Arg0, GUID), NEXP))
{
.
}
Else
This seems that the buggy firmware, set the method _PSR as NotSerialized, but
create the objects.
As from the ACPI spec mention,
Functions are equivalent to a Method that specifies NotSerialized. As such, a
function should not
create any named objects, since a second thread that might re-enter
the failures are from the buggy firmware,
for
High failures: 1
klog: HIGH Kernel message: [ 0.00] ACPI Error: Gpe0Block - 32-bit FADT
register is too long (32 bytes, 256 bits) to convert to GAS struct - 255 bits
max, truncating (20121018/tbfadt-201)
seems the FADT table, GPEBlock setting
the failure of UUID,
\_SB_:_OSC invalid UUID
is due to the firmware checking another different UUID(ED855E0C-6C90
-47BF-47A6-2A26DE0FC5AD5C) by method OSCM and WOSC and return invalid
UUID before the actual Platform-Wide UUID (0811B06E-
4A27-44F9-8D60-3CBBC22E7B48) defined in the APCI spec and
the failures,
method: Detected error 'Region limit' when evaluating '\_PTS'.
method: Detected error 'Region limit' when evaluating '\_WAK'.
is due to the methods \_SB.PCI0.LPCB.SIOS (Arg0) and \_SB.PCI0.LPCB.SIOW
(Arg0)
firmware implemented the Mutex not proper, and cause the Region limit
the failures,
method: Detected error 'No return value' when evaluating
'\_SB_.PCI0.XHC_.RHUB.HS10._PLD'.
method: Detected error 'No return value' when evaluating
'\_SB_.PCI0.XHC_.RHUB.HS11._PLD'.
method: Detected error 'No return value' when evaluating
'\_SB_.PCI0.XHC_.RHUB.HS12._PLD'.
the mpcheck failures,
is come from the buggy firmware implement the improper mp table.
Fortunately, the ACPI enabled platform, the MP table is replaceed by the ACPI
MADT table.
** Changed in: linux-lts-raring (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification
FAILED [HIGH] KlogACPIErrorNoHandlerFor: Test 1, HIGH Kernel message: [
3992.376056] ACPI Error: No
handler for Region [RTCR] (880119042ea0) [SystemCMOS]
(20120320/evregion-376)
FAILED [HIGH] KlogACPIErrorRegionHas: Test 1, HIGH Kernel message: [
3992.376061] ACPI Error: Region
SystemCMOS
(Ubuntu)
Assignee: Ivan Hu (ivan.hu) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1143359
Title:
Dell Latittude 6340u - Systems will not boot in uEFI mode
To manage notifications
The severity for LVT issue was down to the medium after fwts version
V0.26.07. set the bug to invalid.
** Changed in: linux (Ubuntu Precise)
Status: Confirmed = Invalid
** Changed in: fwts
Status: New = Fix Committed
** Changed in: linux (Ubuntu Precise)
Assignee: Ivan Hu
** Changed in: fwts (Ubuntu)
Status: Incomplete = Invalid
** Changed in: fwts (Ubuntu)
Assignee: Ivan Hu (ivan.hu) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172813
** Changed in: fwts
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021496
Title:
[Dell Inspiron One 2305]: Fails to suspend without errors.
To manage
The severity for LVT issue was down to the medium after fwts version
V0.26.07. Set the bug to invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please provide Acpidump for further investigation. Thanks!
by
sudo acpidump acpidump.dat
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
fix committed 48bc2b2469e8db40775089eed42e7e24e808a279
** Changed in: fwts
Status: In Progress = Fix Committed
** Changed in: fwts (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For the CMOS issue, still waiting the Patch in comment#7 to be accepted.
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148649
For Q33 issue, it is still waiting for the patch to be accepted.
please refer to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1148649
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
More detail information,
This is caused by the wmi driver(hp-wmi.c) brings the input data 160bits
struct bios_args {
u32 signature;
u32 command;
u32 commandtype;
u32 datasize;
u32 data; --- 4 bytes data
};
into the the acpi method HWMC as Arg1,
Method (HWMC, 2, NotSerialized)
{
@Po-Hsu Lin,
not quiet sure what you mean in comment #4,
So, after you do the test, could it boot to UEFI mode?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1143359
Title:
Dell Latittude 6340u -
Public bug reported:
Modify the fwts category from Unsafe to UEFI, also change
FWTS_FLAG_UNSAFE to FWTS_FLAG_UEFI, in order to make the category more
specific and let users to be more aware of the tests.
** Affects: fwts (Ubuntu)
Importance: Low
Assignee: Ivan Hu (ivan.hu
** Changed in: fwts (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/1207178
Title:
UEFI: change the fwts_category Unsafe to UEFI
To manage
Assignee: Ivan Hu (ivan.hu)
Status: In Progress
** Changed in: fwts (Ubuntu)
Status: New = In Progress
** Changed in: fwts (Ubuntu)
Importance: Undecided = Low
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) = Ivan Hu (ivan.hu)
--
You received this bug notification because
)
Status: Fix Committed = Won't Fix
** Changed in: linux (Ubuntu Quantal)
Assignee: Ivan Hu (ivan.hu) = (unassigned)
** Changed in: linux (Ubuntu Raring)
Assignee: Ivan Hu (ivan.hu) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
It seems,
The shim installs the UEFI protocol in shim.c
EFI_STATUS efi_main (EFI_HANDLE image_handle, EFI_SYSTEM_TABLE *passed_systab)
{
...
shim_lock_interface.Verify = shim_verify;
...
uefi_call_wrapper(BS-InstallProtocolInterface, 4, handle,
** Changed in: linux-lts-saucy (Ubuntu)
Assignee: Anthony Wong (anthonywong) = Ivan Hu (ivan.hu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279169
Title:
[Dell Latitude 3330] HIGH failures
The S1 and S2 failures,
The failures come from firmware not provide _S1 and _S2 objects, so that the
kernel complains about cannot find _S1,_S2 namespace objects that contains the
register values for the sleep state when kernel would like to setup all the
sleep state information. This means
For the failure,
klog: HIGH Kernel message: [ 0.795261] \_SB_.PCI0:_OSC invalid UUID
seems from the NEXP value from firmware equal to zero, cause the _OSC return
got invalid UUID.
Method (_OSC, 4, Serialized) // _OSC: Operating System Capabilities
{
...
For the S1,S2 failures,
The failures come from firmware not provide _S1 and _S2 objects, so that the
kernel complains about cannot find _S1,_S2 namespace objects that contains the
register values for the sleep state when kernel would like to setup all the
sleep state information. This means
For the S1,S2 failures,
The failures come from firmware not provide _S1 and _S2 objects, so that the
kernel complains about cannot find _S1,_S2 namespace objects that contains the
register values for the sleep state when kernel would like to setup all the
sleep state information. This means
For the S1, S2, S3, S4 failures,
The failures come from firmware not provide _S1,_S2,_S3 and _S4 objects, so
that the kernel complains about cannot find _S1,_S2, _S3,_S4 namespace objects
that contains the register values for the sleep state when kernel would like to
setup all the sleep state
As for the failures,
klog: HIGH Kernel message: [ 2709.142899] ACPI Error: No handler for Region
[POWS] (880c69c51000) [IPMI] (20130517/evregion-162)
klog: HIGH Kernel message: [ 2709.142911] ACPI Error: Region IPMI (ID=7) has
no handler (20130517/exfldio-305)
klog: HIGH Kernel message: [
** Changed in: fwts
Status: Confirmed = Won't Fix
** Changed in: fwts (Ubuntu)
Status: Confirmed = 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/1269654
Title:
Klog high
The S1, S2 should work in fwts V14.02.00
** Changed in: linux-lts-saucy (Ubuntu)
Status: Confirmed = 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/1280103
Title:
[Dell Optiplex
The 'Not exist' issue has fixed by the fwts patch,
https://lists.ubuntu.com/archives/fwts-devel/2014-February/004404.html
It should work after fwts version V14.03.00.
Please follow by the bug#1285167
** Changed in: linux-lts-raring (Ubuntu)
Status: In Progress = Confirmed
--
You received
The 'Not exist' issue has fixed by the fwts patch,
https://lists.ubuntu.com/archives/fwts-devel/2014-February/004404.html
It should work after fwts version V14.03.00.
Please follow by the bug#1285167
** Changed in: linux-lts-raring (Ubuntu)
Status: In Progress = Confirmed
--
You received
The 'Not exist' issue has fixed by the fwts patch,
https://lists.ubuntu.com/archives/fwts-devel/2014-February/004404.html
It should work after fwts version V14.03.00.
Please follow by the bug#1285167
** Changed in: linux-lts-raring (Ubuntu)
Status: In Progress = Confirmed
--
You received
The s1, s2 failures,
klog: HIGH Kernel message: [ 0.185490] ACPI Exception: AE_NOT_FOUND, While
evaluating Sleep State [\_S1_]
(20130517/hwxface-571)
klog: HIGH Kernel message: [ 0.185497] ACPI Exception: AE_NOT_FOUND, While
evaluating Sleep State [\_S2_] (20130517/hwxface-571)
The failures
The brightness control related failures,
klog: HIGH Kernel message: [ 10.171918] ACPI Error:
[\_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND
(20130517/psargs-359)
klog: HIGH Kernel message: [ 10.171928] ACPI Error: Method parse/execution
failed
The DSM failures,
klog: HIGH Kernel message: [ 9.231078] ACPI Warning: \_SB_.PCI0.GFX0._DSM:
Argument #4 type mismatch - Found [Integer], ACPI requires [Package]
(20130517/nsarguments-95)
klog: HIGH Kernel message: [ 9.237756] ACPI Warning: \_SB_.PCI0.GFX0._DSM:
Argument #4 type mismatch -
For the Gpe0Block error, is from the buggy firmware that setting the
improper GPE0 Block Length, and the kernel should truncate that. It
should not cause any problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The s1, s2 failures,
klog: HIGH Kernel message: [ 0.189964] ACPI Exception: AE_NOT_FOUND, While
evaluating Sleep State [\_S1_] (20130517/hwxface-571)
klog: HIGH Kernel message: [ 0.189973] ACPI Exception: AE_NOT_FOUND, While
evaluating Sleep State [\_S2_] (20130517/hwxface-571)
The failures
And the UUID failure,
\_SB_.PCI0:_OSC invalid UUID
seems that the NEXP equal to 0, that cause firmware report invalid UUID, need
firmware to check.
If (LAnd (LEqual (Arg0, GUID), NEXP))
{
.
}
Else
This _OSC optional object is a control method that is used by OSPM to
communicate to the platform the feature support or capabilities provided
by a device’s driver. This object is a child object of a device and may
also exist in the \_SB scope, where it can be used to convey platform
wide OSPM
this is caused by varible
Name: .
Checking with the uefidump, it is the record log variable, that logs the system
oops that has ever occurred.
It should not affect system function.
** Attachment added: results.log
These not exist false alarm issue are fixed in the newer fwts version.
Please use the fwtw version after 14.03.00 to test.
** Changed in: linux-lts-saucy (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Compare with the PCI configure registers that change between sleep/wake
are the offset 0x2c~0x2f, which are the subsystem vendor ID and
subsystem ID, these IDs can mainly be used for further identification of
a device. If the chip in itself is a generic interface chip to a local
(onboard) bus, it
Compare with the PCI configure registers that change between sleep/wake
are the offset 0x2c~0x2f, which are the subsystem vendor ID and
subsystem ID, these IDs can mainly be used for further identification of
a device. If the chip in itself is a generic interface chip to a local
(onboard) bus, it
** Changed in: linux-lts-saucy (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312559
Title:
[Lenovo T540p] DevConfigDiffAfterS3 and DevConfigDiffAfterS4
To
The _PCL(Power Consumer List) method, evaluates to a list of pointers,
each pointing to a device or a bus powered by the power source device
(AC, battery). this method seems is defined but is not used in Linux
kernel. It should not affect the AC, battery functions.
The _BCM failure might affect
** Changed in: linux-lts-saucy (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280058
Title:
[Dell Inspiron 3437] HIGH failures found in FWTS report
PCI: :03:00.0, VID: 86:95, Class: 02:80 (Network controller)
Config:
: 86 80 95 08 06 00 10 00 c4 00 80 02 10 00 00 00
0010: 04 00 c0 f7 00 00 00 00 00 00 00 00 00 00 00 00
0020: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 22 02 ...
For those syntaxcheck failure shouldn't need to be cared, these failures
are due to the way the tables are being assembled without externals
being reference. We are re-working the interfaces with the ACPICA
assemmbler, iASL.
** Changed in: hwe-next
Status: New = Won't Fix
** Changed in:
As for the all _BCM related failures, seems from buggy firmware, need to
check if the brightness control function using these control function.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367084
The failure,
klog: HIGH Kernel message: [0.481244] \_SB_.PCI0:_OSC invalid UUID
seems that the NEXP equal to 0, that cause firmware report invalid UUID, need
firmware to check.
If (LAnd (LEqual (Arg0, GUID), NEXP))
{
.
And the failure,
klog: HIGH Kernel message: [ 766.299599] [Firmware Bug]: battery: (dis)charge
rate invalid.
is due to kernel complain about the firmware report the negative Present
Rate on the _BST method, and need firmware to check that.
the comment on kernel driver/acpi/battery.c,
/* For
The DSM failures,
klog: HIGH Kernel message: [9.454424] ACPI Warning: \_SB_.PCI0.GFX0._DSM:
Argument #4 type mismatch - Found [Integer], ACPI requires [Package]
(20131115/nsarguments-95)
klog: HIGH Kernel message: [9.454476] ACPI Warning: \_SB_.PCI0.GFX0._DSM:
Argument #4 type
For those syntaxcheck failure shouldn't need to be cared, these failures
are due to the way the tables are being assembled without externals
being reference. We are re-working the interfaces with the ACPICA
assemmbler, iASL.
--
You received this bug notification because you are a member of
1 - 100 of 252 matches
Mail list logo
