On 5/8/13 9:31 AM, Lan Tianyu wrote:
>
> Hi,
> Could you apply a bug on the kernel bugzilla and attach the
> output of acpidump with these info?
> https://bugzilla.kernel.org
>
It's done: http://bugzilla.kernel.org/show_bug.cgi?id=60697
(though I'm not sure I picked the right
Jeffery To, 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#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
?
Tha
I've tested rc3; the issue still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179823
Title:
Bluetooth re-enabled after resume from hibernation
To manage notifications about this bug go to
Jeffrey To, thank you for bisecting. Could you please test the latest
mainline kernel via http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.11-rc3-saucy/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I had to bisect the mainline kernel, since the Ubuntu kernel skipped 3.6
(the issue was in every 3.7 kernel I tried). The result:
a57f7f9175b8ccbc9df83ac13860488913115de4 is the first bad commit
commit a57f7f9175b8ccbc9df83ac13860488913115de4
Author: Bob Moore
Date: Fri Aug 17 10:55:02 2012 +0
Jeffrey To, the next step is to perform a bisect between Quantal and
Raring, to identify the commit that caused this problem. Could you
please do this following https://wiki.ubuntu.com/Kernel/KernelBisection
?
** Tags removed: regression-potential
** Tags added: regression-release
--
You receive
I don't recall having this problem with Quantal. Also, as noted in the
original report, linrunner did some testing and found this to be a
regression in the 3.8 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Jeffery To, thank you for testing the newest mainline kernel. Did this
problem not occur in a release prior to Raring?
** Tags removed: kernel-bug-exists-upstream-v3.10-rc1 needs-upstream-testing
** Tags added: kerne-bug-exists-upstream kernel-bug-exists-upstream-v3.11-rc2
** Tags removed: kerne-
I've tried the v3.11-rc1-saucy and v3.11-rc2-saucy kernels; the results
were the same as the v3.10 kernel I tested earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179823
Title:
Bluetooth re-
Jeffery To, thanks for reflashing your BIOS. Could you please test the
newest mainline kernel available via http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.11-rc1-saucy/ and report the results?
** Tags removed: bios-outdated
** Tags added: latest-bios-1.40 needs-upstream-testing
--
You receive
I've installed the latest BIOS and the situation is unchanged.
Regarding the terminal command, this is the output:
6QET70WW (1.40 )
10/11/2012
According to the BIOS changelog
(http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS013909),
this was an embedded controller update that impro
Jeffrey To, as per
http://support.lenovo.com/en_US/downloads/default.page? an update is
available for your BIOS (140-1.15). If you update to this, does it
change anything?
If not, could you please both specify what happened, and provide the output of
the following terminal command:
sudo dmidecode
Tested with the latest mainline kernel; bug has not been fixed.
Additionally, after resuming from hibernate and turning off Bluetooth
(through System Settings), I'm no longer able to turn Bluetooth on (it
flips to on then immediately off). Not sure if this is related.
** Tags added: kernel-bug-ex
To clarify, the "no longer able to turn Bluetooth on" issue affects the
3.10 kernel only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179823
Title:
Bluetooth re-enabled after resume from hibernat
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
15 matches
Mail list logo
