[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328801
T
Damien Cassou, please provide the information on the latest mainline
kernel. As well, let us broaden this to resume from suspend not working,
versus speculating to root cause at this point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I'm not really sure the problem I managed to reproduced on v3.15-rc2 is
the exact same. The symptoms are the same: I can't resume from suspend.
Still, as I don't have sound on v3.15-rc2, I don't think the problems
are related. Please advise on what I can do to help get this bug(s)
fixed.
--
You r
I have a hard time reproducing again. The problem is twofold:
1. the suspend/resume problem does not always happen
2. this kernel does neither have sound nor wifi which makes it inconvenient to
set as my default kernel
Do you think I could configure wifi and sound on the 3.15rc2 kernel?
--
You
Damien Cassou, please follow the steps as previously requested.
** Tags added: needs-suspend-debug
** 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.laun
Please find attached the /proc/acpi/wakeup while in v3.15-rc2-trusty. I
didn't follow the "resume-trace debugging procedure" as it looks like it
is related to debugging resume while I think my problem is on suspend:
when I close the lid and the light does not blink, I know the computer
won't resume
Using v3.15-rc2-trusty (3.15.0-031500rc2-generic #201404201435 SMP), I *managed
to reproduce* the suspend/resume problem.
Using this kernel, the wifi is not working: this is problematic because I can't
just report bugs using apport from there. Nevertheless, when the problem
occured again in v3.1
