Workround provided from upstream dialogue - Thank you Aaron.
See http://marc.info/?l=linux-acpim=140686098023199w=2
In summary:
Switching to use the intel-backlight interface rather than the acpi_video0
interface makes the controls for brightness work after suspend. This can be
done by
Reported upstream. See http://marc.info/?l=linux-
acpim=140658075422146w=2.
As requested from upstream am attaching output from acpidump as
acpidump.txt
** Attachment added: acpidump.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4165307/+files/acpidump.txt
--
Christopher, Thank you for your guidance on this issue. I want to make
sure I report this upstream in the correct way and am unsure of which
upstream list I should be using.
https://wiki.ubuntu.com/DebuggingKernelSuspend mentions says Suspend and
Resume use facilities within your BIOS called
John D Marsden, I would start with linux-acpi. linux-pm is more for a
bug in the software of suspend itself, not buggy drivers that cause
suspend to not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
John D Marsden, the issue you are reporting is an upstream one. Could
you please report this problem through the appropriate channel by
following the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
Please provide a direct URL to your e-mail to the mailing list once you
I have tested against the kernel at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.16-rc5-utopic/ and can confirm that the bug as reported
still persists.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: kernel-bug-exists-upstream-3.16-rc4
** Tags added:
John D Marsden, could you please test the latest mainline kernel via
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc5-utopic/ and
advise to the results?
** Tags added: precise
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification
In answer to: if you remove the kernel parameter elevator=noop does this
change anything?
No it does not change anything. I tried with this kernel parameter removed on
the latest mainline upstream kernel 3.16-rc4.
As requested, tested on Precise 12.04.0 and 12.04.3 both obtained from
John D Marsden, did this problem not occur in a release prior to Trusty?
** 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.
https://bugs.launchpad.net/bugs/1338063
In answer to did this problem not occur in a release prior to Trusty?:
I'm sorry, I don't know for sure. I only noticed the problem the day I
first reported it, however my behaviour regarding shutdowns rather than
suspends has recently changed so that may well be why I noticed it. My
wife
John D Marsden, if you remove the kernel parameter elevator=noop does
this change anything?
As well, for regression testing purposes, could you please test Precise
12.04.0 (live is fine) via http://old-
releases.ubuntu.com/releases/12.04.0/ and advise to the results?
** Tags added: raring
**
John D Marsden, could you please provide the missing information
following https://wiki.ubuntu.com/DebuggingKernelSuspend ?
** Tags removed: kernel-bug-exists-upstream-3.16.0-031600rc4-generic
** Tags added: kernel-bug-exists-upstream-3.16-rc4
** Changed in: linux (Ubuntu)
Status:
As requested I followed the steps in
https://wiki.ubuntu.com/DebuggingKernelSuspend.
Results are:
1. Information from sticker on computer:
Manufacurer: Toshiba
Model: Protege Z835-ST6N03
Part No: PT224U-01W00C
2. Bios is already upgraded to latest version 1.80.
3. Booted in mianline
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148946/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338063
Title:
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148945/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338063
Title:
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148947/+files/Xorg.0.log.old
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags removed: bios-outdated-1.80
** Tags added: latest-bios-1.80
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338063
Title:
[Toshiba Portege Z835-ST6N03] Brightness control lost after suspend
John D Marsden, could you please test the latest upstream kernel available from
the very top line at the top of the page (not the daily folder) following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the issue. Once you've tested the
Installed latest upstream mainline kernel: 3.16.0-031600rc4-generic
Unfortunately this failed to solve the problem. Brightness control on
systems settings and via function keys works on initial boot but ceases
to work after a suspend, as before.
Thank you for your help.
** Changed in: linux
Clarification:
I have gone back to older kernels on my machine to confirm my feeling
that this only started happening recently. The oldest kernel on my
machine is 3.8.0-31-generic. The problem also occurs with when booted
with this kernel so my feeling that this was recent is wrong.
I have
Christopher, thank you for your advice and my apologies for not
following the protocol of first checking for BIOS updates.
I have now updated the BIOS. Results of sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date are:
Version 1.80
04/18/2013
so the update has worked.
21 matches
Mail list logo
