Marcello Nuccio, please do not mark this a duplicate of another bug, or vice
versa, especially without a technical justifying comment. There is not enough
evidence presented to verify this is a duplicate, nor do they share the same
hardware as verified by:
cd ~/Desktop && wget -c
https://bugs.l
*** This bug is a duplicate of bug 1329689 ***
https://bugs.launchpad.net/bugs/1329689
** This bug has been marked a duplicate of bug 1329689
Suspend fails with nouveau problem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Oh, and I would rate this not as Medium, but as high. Suspend is a
really major feature nowadays in the workflow of people - if that dows
not work as a regression in a LTS kernel, I think this deserves a high
priority (just my 2 cents).
--
You received this bug notification because you are a memb
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/132469
Um, no, not expired, still a very real bug!
Just because i don't have time to sit around and compiling kernels with
incremental changes doesn't mean the problem has gone away.
The only way i've gotten around this is to remove the nouveau module
altogether. I blacklisted the module in /etc/modprob
[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Conrad Hill-Knight, with the fix commit is identified, only then may it
be tested against the current Ubuntu kernel to see if you can
sucessfully suspend, of course without all the other issues encountered
with the mainline kernel.
--
You received this bug notification because you are a member of
Hi,
I'm not sure i identified the correct kernel that is the equivalent of
3.13.0-27. But both 3.13.0-27.49 and 3.13.0-27.50 correspond to actual
kernel version 3.13.11, according to the mapping file. The previously
working 3.13.0-24 is also not listed, but 3.13.0-24.46 and
3.13.0-24.47 are, and c
Conrad Hill-Knight, the next step is to fully reverse commit bisect the
kernel in order to identify the fix commit. Could you please do this
following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?
** Tags removed: kernel-fixed-upstream-3.15.0-03150
Hi,
I tried the latest kernel as suggested, and suspend works normally
again, with lid closure, and from the command line. This was tested
with:
Linux inanna 3.15.0-031500rc7-generic #201405251935 SMP Sun May 25
23:36:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Thanks,
-Conrad.
--
You received t
** Tags added: kernel-fixed-upstream-3.15.0-031500rc7
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1324697
Title:
Conrad Hill-Knight, could you please test the latest upstream kernel available
(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 upstream kernel, please comment on which kernel
13 matches
Mail list logo