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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1133835
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
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1133835
Title:
[Gigabyte M57SLI-S4] Ubuntu 12.10 immediately wakes up aft
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
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
It seems like linux 3.8 started out OK but broke at 3.8.11. I will
bisect 3.8.10 and 3.8.11 to find the commit.
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
I have tested:
* Stock Precise 3.2.0-23.36-generic: NOT reproducib
OK, working on it.
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
I have tested:
+ * Stock Precise 3.2.0-23-generic: NOT reproducible
+ * Stock Precise 3.5.0-18: reproducible
* Stock Quantal 3.5.0-25-generic: reproducible
*
** Description changed:
Since upgrading from 12.04 to 12.10 my computer immediately wakes up
after suspend.
+
+ I have tested:
+ * Stock Quantal 3.5.0-25-generic: reproducible
+ * Stock Raring 3.8.0-29-generic: reproducible
+ * Mainline 3.8.1-030801-generic: NOT reproducible (suspend works fi
Well this is interesting. I _can_ reproduce the issue with mainline
3.8.13-03081305-generic. I'll update the description with all the tests
I have run.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
--
You received this bug notification because you are a member of Kernel
I can also reproduce this in Raring with linux 3.8.0-29-generic (mapping
to mainline 3.8.13.5) so it would seem this problem is Ubuntu-specific.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
--
You received this bug notification because you are a member of Kernel
Package
Well, I could reproduce it in saucy but unfortunately I had no network
connectivity in saucy so I couldn't run apport-collect. Is there
anything else I can do to help?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a mem
18 matches
Mail list logo
