It seems this broke in mainline 3.8 between 3.8.6 and 3.8.7. I am
running with 3.8.6 now and have not had a suspend failure yet.
That said, Christopher, I don't think I have any more time to debug
this, especially if you are unwilling to work with me on on finding the
right strategy. I feel like I
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
WORKAROUND: echo 0 > /sys/power/pm_async
(added to /etc/rc.local to be permanent)
I have tested:
* Stock Precise 3.2.0-23.36-generic: NOT reproducible
* Stock Precise 3.5
Hi Christopher, would you mind answering my question above about your
intent?
I haven't tested yet with my 966f1212e1ac5fe3ddf04479d21488ddb36a2608
build and am trying to find the mainline 3.8.x version where suspend
broke for me.
--
You received this bug notification because you are a member of
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
WORKAROUND: echo 0 > /sys/power/pm_async
(added to /etc/rc.local to be permanent)
I have tested:
* Stock Precise 3.2.0-23.36-generic: NOT reproducible
* Stock Precise 3.5
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
WORKAROUND: echo 0 > /sys/power/pm_async
(added to /etc/rc.local to be permanent)
I have tested:
* Stock Precise 3.2.0-23.36-generic: NOT reproducible
* Stock Precise 3.5
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
WORKAROUND: echo 0 > /sys/power/pm_async
- (added to /etc/rc.local to be permanent)
+ (added to /etc/rc.local to be permanent)
I have tested:
* Stock Precise 3.2.0-23.36-gen
Hey, is your intent to confirm that the upstream bug is the same or to
find the specific commit that caused the bug Or something else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133835
Title:
[G
Actually, I don't expect to demonstrate the problem with that commit since
v3.8.1 is fine. That commit just made the problem _possible_, everything else
just makes it more or less likely. As the upstream report says, "I found that
reverting
http://git.kernel.org/?p=linux/kernel/git/torvalds/linu
David Tombs, thank you for testing the requested kernel. Now, could you please
delete the .deb files you recently created, and execute the following via a
terminal (the expectation is that this kernel would demonstrate this problem):
cd ~/Desktop/linux-stable && git checkout
966f1212e1ac5fe3ddf0
Oops, I already compiled it by time you replied without
CONFIG_DEBUG_INFO and have been testing since. Suspend seems to work
fine with this build. I'm curious, where did you come up with that
commit?
I'll leave this as Incomplete per your previous comment. If you want me
to rebuild with completely
David Tombs, if you wouldn't mind, I would just perfrom the command
verbatim, with no modifications in syntax.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133835
Title:
[Gigabyte M57SLI-S4] Ubunt
OK. Is it OK if I compile with CONFIG_DEBUG_INFO=n? I usually do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133835
Title:
[Gigabyte M57SLI-S4] Ubuntu 12.10 immediately wakes up after suspend
T
David Tombs, could you please execute the following at a terminal, boot into
the kernel, and advise to the results (the expectation is that this will not
produce the problem):
cd ~/Desktop && git clone
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-stable && cd linu
Well, the upstream bug listed this commit as introducing the bug:
966f1212e1ac5fe3ddf04479d21488ddb36a2608
I think there are other commits that make it more or less likely to
occur but it's very hard to track down. It's not consistently
reproducible and very well might be a race condition since we
David Tombs, it still would be immensely helpful to know which commit
precisely caused this problem, as this typically gives developers more
of a clue on how to fix it. Would this be ok?
** Changed in: linux (Ubuntu)
Importance: Medium => Low
** Changed in: linux (Ubuntu)
Status: Confir
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
+
+ WORKAROUND: echo 0 > /sys/power/pm_async
+ (added to /etc/rc.local to be permanent)
I have tested:
* Stock Precise 3.2.0-23.36-generic: NOT reproducible
* Stock Precise 3.
It turned out mainline 3.8.10 was unreliable but 3.8.1 is still reliably
good so all I know is something changed between 3.8.1 and 3.8.11.
In better news, I am confident that this is upsteam bug 48951. I also
have an nvidia mcp5x controller and the workaround to disable async
suspend (echo 0 > /sy
DiegoRivera, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug
Control team, and Ubuntu Bug Squad would like you to please file a new report
by executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more on
18 matches
Mail list logo