** 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 Ubuntu.
https://bugs.launchpad.net/bugs/897298
Title:
fwts should test chassis type
To manage notifications about this
@Colin,
I agree with your 1 + 2. Nothing stops engineers designing a small
battery to avoid sudden power loss. I guess some industrial PC may see
the need to install a battery.
Some ideas:
1. It would be a good idea to compare FADT and DMI. The challenge would
be how to match DMI's definition
I create deb packages with changes in comment#8.
The debs can be downloaded from
http://zinc.canonical.com/~alexhung/lp-897298/
It will be executed by sudo fwts dmi_decode and save the errors, if
any, to results.log.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: fwts (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/897298
Title:
fwts should test chassis type
To manage notifications about this bug go
SMBIOS and ACPI specifications has some similar definitions for chassis
type and battery
SMBIOS Type 3 (Chassis Type) -- ACPI FADT-Preferred_PM_Profile
SMBIOS Type 22 (Portable Battery) --- ACPI Battery device
The other way to solve the this problem is the compare SMBIOS and ACPI
by the above;
The driver that reports the status of the wireless devices finally calls
to an BIOS SMI handler, which is a proprietary and a blackbox. This need
to be fixed by BIOS.
However, clearing the bluetooth status (BIT 3 BIT 9) in the rfkill
driver does not fix the BT icon in task panel.
--
You
Public bug reported:
Ubuntu Version: 11.04
FWTS version: 0.22.14
Expected:
FWTS should report that C2/C3 are supported.
Instead:
FWTS reports C2/C3 are not supported as it checks P_LVL2_LAT and P_LVL3_LAT. C
states can be also supported by _CST objects.
** Affects: fwts (Ubuntu)
Hi Colin,
The _CST are not located in DSDT but in a SSDT. Maybe I can get a
machine and send you a screenshot if I can get a Sandy Bridge - probably
need to install a Windows because some utilities only run on Windows :(
Any idea whom I can borrow a Sandy bridge system from?
On Thu, 2011-08-25
@Colin,
The below code is dumped from a Huron River system with a SandyBridge
CPU (Insyde BIOS).
Name(SSDT, Package(12)
{
CPU0IST , 0xA4B29018, 0x0804, APIST , 0xA6E71A98, 0x0303,
CPU0CST , 0xA6E70798, 0x0727, APCST , 0xA6E6FD98, 0x0119
})
The _CST objects are hidden in a
. changes, you will get
these events.
Therefore it is safe to ignore the WMI 0x11 event silently.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Alex Hung (alexhung)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
BTO: Oneiric
BIOS Version: X11
CPU: Ivy Bridge
GPU: nVidia N13M-NS1-A1
Summary: An unknown WMI event during S3 testing
Steps ro reproduce:
run fwts s3 --s3-multiple 32
look at /var/log/kern.log
Expected results: no messages about unknow WMI events 0x11
Actual Result:
** Attachment added: kern.log
https://bugs.launchpad.net/bugs/879239/+attachment/2563942/+files/kern.log
** Changed in: linux (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The use ASUS_WMI_METHODID_DSTS2 is to make sure asus-wmi and asus-nb-wmi
will be loaded correctly - without an DSTS id assigned, many of the
functions in asus-wmi / asus-nb-wmi will not work. That's why hotkeys
are not working
Preivously asus bios will either respnod to ASUS_WMI_METHODID_DSTS or
@Dassburger,
thanks for the valuable information on asus_wmi_rfkill_init(). Will it
be possible to narrorw down which part of asus_wmi_rfkill_init cause the
hang? For instance, could it be one of the asus_new_rfkill() or
asus_setup_pci_hotplug() or so?
--
You received this bug notification
@Dassburger, it calls bios's wmi function and probably reads from ec
which generates interrupts (GPE events).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi
A patch implementing WMI 0x0D was sent to upstream (see http://www.mail-
archive.com/platform-driver-...@vger.kernel.org/msg04740.html)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Alex Hung (alexhung)
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed
: Alex Hung (alexhung)
Status: 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/1249256
Title:
hp-wmi calls WMI 0x05 instead of WMI 0x1b interfaces in new BIOS
To manage notifications
** Changed in: linux (Ubuntu Precise)
Status: New = 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/595896
Title:
Thinkpad SL510 Mute button not working
To manage notifications
I don't think there are others at the moment, as it does not specify
exact models. Let's close this bug and file others if we encounter
failures on other specified systems.
** Changed in: hwe-next
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed =
klog: HIGH Kernel message: [ 0.00] ACPI Warning: FADT (revision 5)
is longer than ACPI 2.0 version, truncating length 268 to 244
The error was generated by older version of linux kernel which complains
ACPI version is too new. This has no impacts and is fixed in newer
kernel.
** Changed in:
klog: HIGH Kernel message: [ 0.002488] ENERGY_PERF_BIAS: Set to
'normal', was 'performance'
The error is changed from error to info in fwts commit
c3a9eb921aaa468ff7fbc426d4df0cf55a8ad2e1 a while ago
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (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/1168332
Title:
HP ENVY 6 Sleekbook - ACPI errors during suspend
To manage
@a16g,
I agree with what you said. We should check whether any workaround added
during the enablement and ask s/w engineer not to add workaround unless
schedule will slip or BIOS won't fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Comment #6 and #10 are still valid for errors in #14. This seems happens
on a number of systems, but it does not cause any function failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1149269
ASUS 401A has some fundamental problems with its BIOS ASL code.
First, its _BCL returns
[ 344.088661] Brightness[0] = 100
[ 344.088669] Brightness[1] = 77
[ 344.088672] Brightness[2] = 60
[ 344.088675] Brightness[3] = 48
[ 344.088677] Brightness[4] = 43
[ 344.088680] Brightness[5] = 38
[
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1132649
Title:
display brightness is very low by default
To manage notifications
A little correct to #7, will also be in precise's lts-backport-quantal
kernel
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The patch in #6 is going to be included in quantal kernel (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1186062)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158129
Title:
fwts_test
This is a common BIOS bug and it is caused by BIOS AML trying to access
a variable that is outside the input buffer arg0, i.e. the below code:
CreateWordField (Arg0, 0x11, IRQE)
In ACPI spec, _SRS's input buffer needs to be the same size of _CRS as
defined below:
6.2.15 _SRS (Set Resource
** Changed in: linux (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/1149269
Title:
Dell Precision T1650 - FWTS reports critical errors during
As in colin's comment in #4, the error is caused by the firmware of the
Embedded Controller (EC). It is, however, a single error which returns
to a series of callers (_BST-ECG6-ECG2-ECBT-ECR1). This can be the
results of buggy EC firmware or can be EC is handling too many tasks and
is not able to
FAILED [MEDIUM] VirtDisabledByBIOS: Test 1, Virtualization extensions
supported but disabled by BIOS.
HP's BIOS spec, virtualization technology is disabled by default and is
required to be enabled manually. It seems HP thinks most users do not
need this feature. This can be fixed by enabling it
FAILED [LOW] LowMaxReadReq: Test 1, 1 devices have low MaxReadReq
settings. Firmware may have configured these too low.
In Intel's data sheet, this register is Read-Only and is hardwired to 0
enabling 128B maximum read request size. Therefore this is not a bug
but a limited feature.
--
You
FAILED [LOW] DMIBadDefault: Test 1, String index 0x03 in table entry
'Processor Information (Type 4)' @ 0x000e73b2, field 'Serial Number',
offset 0x20 has a default value 'To Be Filled By O.E.M.' and probably
has not been updated by the BIOS vendor.
FAILED [LOW] DMIBadDefault: Test 1, String
FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string
index 0x06 while accessing entry 'Portable Battery (Type 22)' @
0x000e728b, field 'Device Chemistry', offset 0x09
This is a real failure but kernel will ignore the information as
suggested in fwts.
ADVICE: DMI strings are stored
** Changed in: linux (Ubuntu)
Status: Confirmed = 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/1152458
Title:
HP Pavilion g7 - Assorted FWTS HIGH failures during testing
To
As Colin's comments in #5, this is a firmware's bug that needs BIOS's
attention; however, _GTF is needed for IDE controllers and HDDs and
optional for SATA controllers and HDDs. Failing to evaluate _GTF in
today's systems has no impacts to functionality and stability.
** Changed in: linux
Please ignore #5 to to #8 as I checked the incorrect log file.
FAILED [HIGH] KlogHpwmiUnknownEventid: Test 1, HIGH Kernel message: [
2477.032359] hp_wmi: Unknown event_id - 10 - 0x1
The above error was generated because new event id is defined by HP but
is yet included in current hp_wmi driver.
Some additional information to #5:
1) FAILED [HIGH] KlogACPIErrorNoHandlerFor: Test 1, HIGH Kernel message: [
3977.475196] ACPI Error: No
handler for Region [RCM0] (88013bf63798) [SystemCMOS]
(20120320/evregion-376)
2) FAILED [HIGH] KlogACPIErrorRegionHas: Test 1, HIGH Kernel message: [
A patch was sent to include the CMOS handler
(https://patchwork.kernel.org/patch/2052901/), but is not yet accepted.
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please also check:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153421/comments/7
We also feedback to BIOS vendors and OEMs and hopefully this error does
not occur in future machines.
** Changed in: linux (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110219
Title:
AMD's systems generate an additional KEY_SWITCHVIDEOMODE event
To
@Yung,
Can you please attach output of acpidump by running sudo acpidump
acpi.log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1166606
Title:
Dell Latitude E5430 - ACPI Error during suspend
This similar to lp#1145803. Please see more information @
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1145803/comments/6
ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST]
...
ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV._Q66]
...
ACPI Error: Method
*** This bug is a duplicate of bug 1143312 ***
https://bugs.launchpad.net/bugs/1143312
** This bug has been marked a duplicate of bug 1143312
HP ENVY 4 Sleekbook - Errors detected when running FWTS sleep tests
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu Precise)
Assignee: Alex Hung (alexhung) = 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/1021496
Title:
[Dell Inspiron One 2305]: Fails to suspend
** Changed in: linux (Ubuntu Quantal)
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/790835
Title:
[Asus EeePC 1001PXD] Wireless hotkey does not disable
** Changed in: linux (Ubuntu)
Status: Confirmed = 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/1167760
Title:
[HP 1000] Screen backlight is off after startup.
To manage
This bug is caused by BIOS reporting zero in _BQC when system boots up.
As a result, kernel will set the brightness to zero and the screen is
dimmed to complete black.
The attached patch adds a quirk to ignore the initial _BQC value and set
the brightness to max.
** Patch added:
** Changed in: linux (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/879239
Title:
Received unknown WMI event 0x11 during S3 testing
To manage
I noticed upstream kernel has a commit #b8df197950923ecd that may
workaround this as below:
commit 28fe5c825f8e15744d04c7c1b8df197950923ecd
Author: Lan Tianyu tianyu@intel.com
Date: Mon May 6 03:23:40 2013 +
ACPI / EC: Restart transaction even when the IBF flag set
The EC
The patch in #9 is in upstream kernel git-tree and will be included in
3.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152458
Title:
HP Pavilion g7 - Assorted FWTS HIGH failures during testing
** Tags removed: verification-needed-quantal
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110219
Title:
AMD's systems generate an additional KEY_SWITCHVIDEOMODE
Public bug reported:
The screen backlight is automatically set to off after boot/reboot
(after the Ubuntu logo screen).
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Alex Hung (alexhung)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned
** Attachment added: acpi.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184501/+attachment/3687538/+files/acpi.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184501
Title:
[HP
** Attachment added: dmi.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184501/+attachment/3687539/+files/dmi.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184501
Title:
[HP
** Changed in: linux (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/1184501
Title:
[HP m4] Screen backlight is off after startup.
To manage notifications
This is similar to https://bugs.launchpad.net/bugs/1167760, but is for
different model.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184501
Title:
[HP m4] Screen backlight is off after startup.
** Patch added:
0001-ACPI-video-ignore-BIOS-initial-backlight-value-for-H.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184501/+attachment/3688289/+files/0001-ACPI-video-ignore-BIOS-initial-backlight-value-for-H.patch
--
You received this bug notification because you are a
/+attachment/3483789/+files/acpi-rtc-dkms_1.0_all.deb
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Alex Hung (alexhung)
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
without other actions
Actual results: brightness changes and display device is also toggled.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Alex Hung (alexhung)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Alex Hung (alexhung)
--
You
run acpi_listen with fn+f5 shows:
video LCDD 0087
video VGA 0081
video VGA 0081
run acpi_listen with fn+f6 shows:
video LCDD 0086
video VGA 0081
video VGA 0081
The additional 0x81 events are generated by BIOS ASL.
run sudo showkey with fn+f5 shows:
keycode 224 pressed
keycode 224 released
keycode 227 pressed
keycode 227 released
run sudo showkey with fn+f5 shows:
keycode 225 pressed
keycode 225 released
keycode 227 pressed
keycode 227 released
** Changed in: linux (Ubuntu)
Status: New = In Progress
This is a common bug for many AMD platforms.
The root cause is AMD uses Notify(VGA, 0x81) as default event for BIOS
ASL to notify AMD's driver. Although changing the event number from 0x81
to others (i.e. 0xD0~0xD9) is possible, it is not always the case when
systems are shipped.
--
You
Two patches in kernel 3.7 fix this bug:
drm/radeon: block the keypress on ATIF events
(92fdf89aa95de32dba1cb44fe7f5c54824b4b2c4)
ACPI video: allow events handlers to veto the keypress
(8a37c65df9dcbd1c891df2b4a94157999b654841)
--
You received this bug notification because you are a member of
I applied a number of patches (commit # as below) on 12.04's lts-
backport-quantal kernel, and it can fix the problem.
92fdf89aa95de32dba1cb44fe7f5c54824b4b2c4
8a37c65df9dcbd1c891df2b4a94157999b654841
c49170742d6928b16fb3839b47a94cc41630dbe0
fda4b25c55a59ba12378e4b9e4553f6ea57d802d
Currently it only fixes radeon use case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110219
Title:
AMD's systems generate an additional KEY_SWITCHVIDEOMODE event
To manage notifications about
@James,
ACPI video.c module has a new function (i.e.
video_ignore_initial_backlight) that will ignore BIOS initial zero
brightness; however, DMI information is needed for the quirk.
Can you please run sudo dmidecode dmi.log and attach the output?
Let's see if we can add entries for the
Upstream has different patches for the same problem, and quirks are used
as the following commits for 12.04:
lts-backport-quantal: b53729e72e31a7f8ecb5b025f5799f4f363dc757
precise: 95fbf65ed2ed69e5ee6ff0cf4c944091687673a0
As a result, it seems to add DMI to video_dmi_table and calls
@David,
Yes the same patches discussed in the url you posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110219
Title:
AMD's systems generate an additional KEY_SWITCHVIDEOMODE event
To manage
** Changed in: linux (Ubuntu)
Status: In Progress = Won't Fix
** Changed in: linux (Ubuntu)
Assignee: Alex Hung (alexhung) = (unassigned)
** Changed in: linux (Ubuntu)
Importance: Medium = Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs
I submitted a kernel patch to create a CMOS handler for the problem
(https://patchwork.kernel.org/patch/2052901/). If it is accepted, it
will fix the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A little more information for #5 and #7
The call trace is like:
_PTS - S34E - _Q33 - no CMOS handler. As a result, they can be grouped as a
single bug, which can be solved by the patch in #7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
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/987607
Title:
[thinkpad x200] LCD brightness up/down hotkey adjusts two
key presses can change from lowest to highest (or
vice versa).
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Alex Hung (alexhung)
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
sudo showkey shows an extra duplicated keycode event with a single
hotkey press
i.e.
Fn+Home (brightness up)
keycode 225 press
keycode 225 release
keycode 225 press
keycode 225 release
Fn+End (brightness down)
keycode 224 press
keycode 224 release
keycode 224 press
keycode 224 release
--
You
The same behaviours can be observed on thinkpad x220
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987607
Title:
[thinkpad x200] LCD brightness up/down hotkey adjusts two levels with
one key
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/987607
Title:
[thinkpad x200] LCD brightness up/down hotkey adjusts two levels
in function hotkey_init, it uses tp_features.bright_acpimode and
acpi_video_backlight_support() to check whether standard acpi
brightness control is support; however, tp_features.bright_acpimode is
always false because it thinkpad-acpi checks the presence of
ACPI_VIDEO_HID device but it will not
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790835
Title:
[Asus EeePC 1001PXD] Wireless hotkey does not disable bluetooth
** Changed in: linux (Ubuntu)
Status: Fix Committed = 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/790835
Title:
[Asus EeePC 1001PXD] Wireless hotkey does not disable bluetooth
This bug is introduced in upstream acpica. A bug is submitted by cking
and we will watch for upstream fixes.
** 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.
** Changed in: hwe-next
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257268
Title:
dell-wmi does not convert the hotkey event to mic mute keycode
To
** Changed in: hwe-next/saucy
Status: In Progress = Fix Released
** 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/1249256
** Changed in: linux-lts-raring (Ubuntu)
Assignee: Ivan Hu (ivan.hu) = Alex Hung (alexhung)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263624
Title:
[HP Pavilion 14] Critical failure
** Changed in: linux-lts-raring (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263624
Title:
[HP Pavilion 14] Critical failure KlogAcpiCrtInvalidThreshold
Using fwdt to read _TZ.TZ01._CRT returns 0. This is 0 Kelvin and -273
Celsius. This is a firmware bug but _CRT is disabled by kernel, and is
as _CRT does not exist.
Impact: _CRT is used for OS to shut down a system when the temperature
is reached. This may sound serious but there are other
This should be fixed by BIOS updates but is not OS-related. As this will
fail thermal testing, it is suggested to feedback to OEM for fixing but
it won't impact Ubuntu's functionality.
** Changed in: linux-lts-raring (Ubuntu)
Status: Confirmed = Fix Released
** Changed in:
Information for the critical failure is available @ bug 1263624
The failures for method tests are due to upstream's acpica. We will be
waiting for Intel's updates.
** Changed in: linux-lts-raring (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you
The critical errors from the method test is caused by acpica.
Quoted from cking's email:
The core issue is that a traversal of an region linked list is looping
forever in ACPICA causing it not to return and making some fwts method
tests to fail on some platforms. I can reproduce the bug in
upstream bug# is available here:
https://bugs.acpica.org/show_bug.cgi?id=1062
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252154
Title:
[Dell Inspiron 3135] Multiple CRITICAL/HIGH failures in
** 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/1249978
Title:
[Dell Latitude E6440] [Firmware Bug]: ACPI(PEGP) defines _DOD
According to ACPI spec, _DOS indicates that the system BIOS is capable
of automatically switching the active display output or controlling the
brightness of the LCD.
However, kernel commit b03738430c7537d5f87948e0b35d8aaf2688c6b4 works around it
a while ago:
commit
Checking drivers/acpi/video.c also found it outputs a warning message
but with no control flow changes as below:
static int acpi_video_bus_check(struct acpi_video_bus *video)
{
...
/* Does this device support video switching? */
if (video-cap._DOS || video-cap._DOD) {
While it is certainly a firmware bug indeed as BIOS's DSDT violate acpi
spec, it seems no function is lost as kernel workaround it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249978
Title:
I also verified the display switch with d-sub interface, and display
switch works automatically when d-sub monitor is attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249978
Title:
[Dell
@colin,
Thanks, I will develop a patch for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249978
Title:
[Dell Latitude E6440] [Firmware Bug]: ACPI(PEGP) defines _DOD but not
_DOS
To manage
Tested Ubuntu 12.04.03 (kernel 3.8) and brightness hotkey works fine. I
am going to verify https://bugs.launchpad.net/ubuntu/+source/linux-lts-
raring/+bug/1249978/comments/2 on kernel 3.2 and to backport if it is
the fix.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
**
I tested patch @ #11, and brightness does not work. I also used the
drivrs/acpi/video.c in kernel 3.5, and brightness does not work either.
I executed lsmod | grep 915 and found this Haswell system does not
have i915 running. The brightness may not be working for more than one
reason - including
fwts patch is sent for review @ https://lists.ubuntu.com/archives/fwts-
devel/2013-November/004027.html
** Package changed: linux-lts-raring (Ubuntu) = fwts
** Changed in: fwts
Assignee: Firmware Test Suite Bug Team (firmware-bug-team) = Alex Hung
(alexhung)
** Changed in: fwts
1 - 100 of 860 matches
Mail list logo
