Ubuntu

[Toshiba Satellite L650 X5310] battery not being detected

Reported by tuxsage on 2011-01-15
120
This bug affects 24 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Low
Unassigned

Bug Description

I am using Toshiba L650 X5310 laptop and noticed that its not detecting battery and hence hibernate function is not available and its not able to show the battery status. I searched and found that a lot of people are experiencing the same problem, since this needs a kernel level fix, no resolutions/wordarounds are posted anywhere. I have tried many Ubuntu versions (old and new) and all of them posses the same issue. I have even tried several other distros(Centos/Mandriva/OpenSuse) but results were the same. Here is the demsg

root@me-Satellite-L650:~# dmesg | grep batt
[ 0.974257] ACPI: Battery Slot [BAT1] (battery absent)

root@me-Satellite-L650:~# acpi -V
Adapter 0: on-line
Cooling 0: LCD 0 of 7
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10

The Laptop runs without AC power supply, it means battery is able to power-up the laptop but it does it show a status.

https://drivers.toshiba-india.com/drivers.aspx?product=Laptop&series=Satellite&model=L650&cat=Bios&os=0

WORKAROUND: http://techinterplay.com/fix-toshiba-battery-issue-linux.html

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-24-generic 2.6.35-24.42
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: wl fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: efheem 1796 F.... pulseaudio
 /dev/snd/pcmC0D0p: efheem 1796 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd6100000 irq 45'
   Mixer name : 'Conexant CX20585'
   Components : 'HDA:14f15069,1179fd50,00100302'
   Controls : 6
   Simple ctrls : 4
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xd6020000 irq 46'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Sat Jan 15 21:01:30 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: TOSHIBA Satellite L650
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=fbdfde89-6a3c-44a3-9de3-e24548ce1222 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
WifiSyslog:

dmi.bios.date: 09/15/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.70
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd09/15/2010:svnTOSHIBA:pnSatelliteL650:pvrPSK2GG-00G001:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L650
dmi.product.version: PSK2GG-00G001
dmi.sys.vendor: TOSHIBA
---
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: faheem 1889 F.... pulseaudio
 /dev/snd/controlC0: faheem 1889 F.... pulseaudio
 /dev/snd/pcmC0D0p: faheem 1889 F...m pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
DistroRelease: Ubuntu 12.10
InstallationDate: Installed on 2012-01-26 (401 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: TOSHIBA Satellite L650
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=de5763bc-5fcd-4d9b-8e36-3903c487f782 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Tags: quantal running-unity
Uname: Linux 3.5.0-23-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-10-20 (133 days ago)
UserGroups:

WifiSyslog:

dmi.bios.date: 07/03/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.80
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr2.80:bd07/03/2012:svnTOSHIBA:pnSatelliteL650:pvrPSK2GG-00G001:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L650
dmi.product.version: PSK2GG-00G001
dmi.sys.vendor: TOSHIBA

tuxsage (tuxsage) wrote :
description: updated
description: updated
rvsh07 (rvsh07) wrote :

I have the same problem on my Toshiba Satellite L650-BT2N23. So far I have tried Ubuntu 9.04, 9.10, 10.04 and 10.10, in addition to other distros such as OpenSuSE, Fedora and Mandriva. I have also tried rebuilding some of the older Kernels with the 'copy_dsdt' patch described here (https://bugzilla.kernel.org/show_bug.cgi?id=14679), but nothing has worked.

Jeremy Foshee (jeremyfoshee) wrote :

Hi tuxsage,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
rvsh07 (rvsh07) wrote :

I have nearly the same configuration on my laptop, and exactly the same issue. I have tried the latest mainline kernel (2.6.38-999-generic_2.6.38-999.201101281114_amd64), and found that the issue persists. The ACPI functions were not enabled in the latest kernel and the battery was still not detected.

InTheFade (inthefade0) wrote :

I have an L640-01H and I experience the same problem in any distribution I try.

When started on battery power, "acpi -V" shows:

Adapter 0: off-line
Cooling 0: LCD 0 of 7
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10

The latest BIOS for my model (1.90) had no effect.

Jithin (logjinvan) wrote :

Hi,

Strange to see this bug closed. I am also having the same issue of the gnome power manager being absent of the Battery power notifier. The specification is the same with the laptop L650 X5310.

chelsea@blues:~$ dmesg |grep acpi
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x00] disabled)
[ 0.959203] ACPI: acpi_idle yielding to intel_idle
[ 10.603752] acpi device:0a: registered as cooling_device4

Jithin (logjinvan) wrote :

Hi,

This is the battery status in dmesg:

chelsea@blues:~$ dmesg |grep batt
[ 0.964414] ACPI: Battery Slot [BAT1] (battery absent)

tuxsage (tuxsage) on 2011-02-05
Changed in linux (Ubuntu):
status: Incomplete → New
Charles Jie (chjie) wrote :

I am using Toshiba L640 with Ubuntu10.10. I got the same dmesg and acpi -V results as Tuxsage's report.

Morgan Bush (mwbush) wrote :

I have the same results with Toshiba L645 running Ubuntu 10.10.

Tyler LeBeau (tylerlebeau) wrote :

Another Satellite 645 having this issue on 10.10 - same results from acpi -V as above

Battery meter was working within windows 7 home that came pre-installed (which was promptly replaced due to Toshiba bloatware)

Tyler LeBeau (tylerlebeau) wrote :

Issue persists in fresh install of 11.04

Mostafa (mostafa-sedaghat) wrote :

I have same problem and i can't find any solution yet.

Tyler LeBeau (tylerlebeau) wrote :

No solution yet and losing hope... Been searching for over 2 weeks.

Brad Figg (brad-figg) on 2011-05-03
Changed in linux (Ubuntu):
status: New → Confirmed
ottod (otto-sistemasorion) wrote :

Failing here too. Toshiba Satellite L645-SP4130L, Insyde BIOS 2.30 (latest for this model).

Kumar Lomash (kumar-lomash) wrote :

Toshiba Satellite L655, same issue on 11.04

I would be happy to provide any data which would help fix this issue.

tuxsage (tuxsage) wrote :

Hello Everyone,

Thank you George Moutsopoulos so much for coming up with these links :-) I have got this issue resolved finally. I have made a post with step by step procedure for doing this at http://techinterplay.com/fix-toshiba-battery-issue-linux.html

yep same here. "Thank you George Moutsopoulos so much for coming up with these links :-) I have got this issue resolved finally".
tuxasage's post describes it all. Thanks everyone who worked on this.

rvsh07 (rvsh07) wrote :

Thanks George and tuxsage! I got the issue resolved as well. With the dsdt fixed, I can finally see the battery icon and statistics!

The only issue is that with the new kernel my wireless card (Broadcom) only works intermittently. At times, on startup it doesnt show any wireless networks and is unable to connect - a re-start sometimes fixes the issue. Other times it freezes up while connecting to the network and I have to reboot. Anyone else run into this problem?

Pedro Villavicencio (pedro) wrote :

seems to be a linux issue.

Changed in gnome-power-manager (Ubuntu):
status: New → Invalid
pascalc (pascal-chevrel) wrote :

Tuxsage instructions on how to create patch a custom kernel work for me as well with a Satellite L-735-116, thanks Tuxsage and George!

Patching the kernel is not really feature proof for people like myself who are Linux users and not linux hackers :)

What are the next step to get this fix included in Ubuntu or upstream in the Linux kernel? Are there people working on hardware support in the Ubuntu team and the Linux team following this bug report and taking action? If not, how can they be contacted so as to make sure this is fixed in the next Oneiric release?

pascalc (pascal-chevrel) wrote :

s/feature/future in my previous comment

pascalc (pascal-chevrel) wrote :

This is still not fixed in Ubuntu 11.10 with the 3.0 kernel, pretty disapointing that with a bug both reported upstream and downstream by many people and affecting basic funcitionnality of commonly available harware for end-users, nobody seems interested in fixing that bug. Let's hope the workaround tuxsage provided to the community still applies to 3.0 kernels...

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Rayner Vaz (ray13z) wrote :

Is there no way we can incorporate the kernel fix with the future updates? Will install only depending on make being Toshiba? Can anyone confirm that this affects only few or all Toshiba Laptops?

Fabio Motoki (fmotoki) wrote :

I have the same problem. Toshiba Satellite L655-S5158. No battery status. It hibernates tough. But when I try to wake it up, it reboots and loses the saved state.

root@toshiba-ubuntu:~# acpi -V
Adapter 0: on-line
Cooling 0: LCD 3 of 7
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10
root@toshiba-ubuntu:~#

root@toshiba-ubuntu:~# dmesg|grep batt
[ 0.871238] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 0.871274] ACPI: Battery Slot [BAT1] (battery absent)

root@toshiba-ubuntu:~# uname -a
Linux toshiba-ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

This also affects me with my Toshiba L750. Battery status detected following Tuxsage instructions.

Eduard Gotwig (gotwig) wrote :

I see the battery status in ubuntu 12.04, even its not much... 3 hours only... ouch.....

Eduard Gotwig (gotwig) wrote :

edit: 4 hours ^^

Changed in linux (Ubuntu):
status: Triaged → Fix Released
==BJ== (iambodin) wrote :

I'd tried Ubuntu 12.04 beta2 with my machine (Toshiba Satellite L640). But there isn't any battery status.

Hi everyone.

First of all, my computer is a Toshiba Satellite L750 with Windows 7 and Ununtu 10.04 (up to date).

I followed the steps described by tuxsage and it works fine, but only with ubuntu 10.04.

After some tries with some linux distributions I understand that it is a problem of the kernel, as it is common for all the distributions I tried on this laptop (I don't know if this affects to other models)

 I also tried this solution using Debian 6.0.4 and the result was that the kernel detects the battery but when it is not connected to AC power the brightness goes down so it is impossible to see the screen and there is no way to increase it. I need to restart the computer after that.

Ubuntu 10.04 works fine with the solution provided by Tuxsage but when I put the system in suspend mode, I cannot restart it. The keyboard is blocked and there is no way of knowing what is happening.

The worst of it is that linux users have to words like Tuxage says:

"The cause of issue is because Toshiba included two sets of boot data that tell the OS what hardware exists in the machine. Windows reads the correct one whereas Linux doesn’t. "

This is a message to all the people working in the kernel of linux. How is is possible that kwnowing the source of the problem this issue is not solved yet?

Please, forgive me if I am so severe with my words, but if we want to win the market share against other operatin systems this kind of issues need to be solved as soon as possible (reported several years ago, please correct me if I am wrong).

The user should be able to install any distribution of linux whit no "aesthetic" issues like this one. Linux shoul be (as far as possible) install and use it.

I am at your dispossal for any help, but I am a common user, no thecnical skill.

I hope that my comment helps linux to be stronger.

Regards.

kroq-gar78 (kroq-gar78) wrote :

When was this bug fixed? I just checked the latest update on 12.04, and the battery still doesn't work. Currently, I'm using a custom-compiled kernel with techinterplay's solution.

pascalc (pascal-chevrel) wrote :

+1, this is not fixed in 12.04, not fixed in proposed and not fixed with a 3.5.0 kernel. Just like others mentioned before.

Eduard Gotwig closed that bug as fixed in comment #27 but there is no link in his message showing a reference for a code commit pointing at the fix

I do not have rights in this tracker to reopen this bug, I hope somebody with enough rights will reopen this bug that is *still* affecting Toshiba users.

tuxsage (tuxsage) wrote :

This issue still exists and no fix has been released. Not sure why this is getting ignored everytime.

Changed in linux (Ubuntu):
status: Fix Released → Incomplete
iormundr (iormundr) wrote :

Have the same issue with L750 , can't identify the battery level and shows (Unknown time) in the remaining time to charge the battery ...

kroq-gar78 (kroq-gar78) wrote :

I think Confirmed fits this bug better than the Incomplete status since all of the info is there, but the bug just isn't fixed yet.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
no longer affects: gnome-power-manager (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

affects: gnome-power-manager (Fedora) → gnome-power-manager (Ubuntu)
Changed in gnome-power-manager (Ubuntu):
status: New → Confirmed
no longer affects: gnome-power-manager (Ubuntu)
tags: removed: able absent acpi battery detected hibernate not to toshiba
summary: - Toshiba Laptop battery not being detected
+ [Toshiba Satellite L650 X5310] battery not being detected
description: updated

tuxsage, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If not, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

As well, as per https://drivers.toshiba-india.com/DriversDetails.aspx?product=Laptop&series=Satellite&model=L650&cat=Bios&os=0 a BIOS update is available for your computer (V2.80). If you update to this, does it change anything?

If not, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.8-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete

apport information

tags: added: apport-collected quantal running-unity
description: updated

apport information

tuxsage (tuxsage) wrote : Lspci.txt

apport information

tuxsage (tuxsage) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

tuxsage (tuxsage) wrote : UdevDb.txt

apport information

apport information

tags: added: bios-outdated

apport information

description: updated

apport information

tuxsage (tuxsage) wrote : Lspci.txt

apport information

tuxsage (tuxsage) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

tuxsage (tuxsage) wrote : RfKill.txt

apport information

tuxsage (tuxsage) wrote : UdevDb.txt

apport information

apport information

description: updated

apport information

apport information

tuxsage (tuxsage) wrote : Lspci.txt

apport information

tuxsage (tuxsage) wrote : Lsusb.txt

apport information

apport information

description: updated

apport information

apport information

apport information

apport information

tuxsage (tuxsage) wrote : Lspci.txt

apport information

tuxsage (tuxsage) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

tuxsage (tuxsage) wrote : RfKill.txt

apport information

tuxsage (tuxsage) wrote : UdevDb.txt

apport information

apport information

apport information

George Moutsopoulos (gmoutso) wrote :

Tuxsage's instructions at
http://techinterplay.com/fix-toshiba-battery-issue-linux.html
work well. I upgraded my memory and I would have to repeat the process. However, there is now an upstream patch that solves it
https://bugzilla.kernel.org/show_bug.cgi?id=15707
https://bugzilla.kernel.org/attachment.cgi?id=87901

I applied the patch by hand (the patch command didn't work the first time, probably didn't do it correctly) and compiled the ubuntu kernel using the instructions at
http://www.howtogeek.com/howto/ubuntu/how-to-customize-your-ubuntu-kernel/

It works well.

George Moutsopoulos (gmoutso) wrote :

I also add attached linux-header with the patch.

description: updated
tags: added: bios-2.80
description: updated
description: updated
description: updated
tags: added: latest-bios-2.80
removed: bios-2.80 bios-outdated
description: updated

Tuxsage, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.